Skip to content

Phase 9: Cross-Cutting Invariants & Conformance #24

Description

@Wahbeh-Mohammad

Audit what Phases 0–8 built. Deliberately narrow: §19/§20 (XCUT/NFR) only — it does not re-litigate every
open judgment call that happens to say "Phase 9" somewhere.

Scope

  • Per-ID disposition table for all 24 XCUT IDs and all 17 NFR IDs (the first systematic tabulation of the
    XCUT family — only two incidental citations existed across every prior spec/plan).
  • @dexpace/shrink-test — private, unpublished devDependency closing NFR-9: esbuild bundle/minify/tree-shake
    step, a dual-package-hazard fixture app, and a child-process round-trip guard wired into the default build as
    bun run shrink-test.
  • tests/conformance/xcut/ — a top-level integration suite driving 5c/7b's standardResilience() composed
    pipeline (fixtures/composed-pipeline.ts).
  • NFR-13 SPDX-header sweep across every package — several phase plans carry no header instruction.

Spec refs

Product spec §19, §20, appendix B.

Dependencies

Phases 0–8b (audits them all).

Docs

  • Design: docs/superpowers/specs/2026-07-28-phase9-cross-cutting-conformance-design.md
  • Plan: docs/superpowers/plans/2026-07-28-phase9-cross-cutting-conformance.md
  • Validation prompt: docs/validation-prompts/phase9-cross-cutting-conformance-validation-prompt.md

Explicitly not in scope

PAGE/SSE/SERDE disposition stays with 6c/6b/6a. RECOV-* disposition stays with 5a. AUTH-*/REDIR-*
interpretive calls and preset-shape questions belong to Phase 10.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions