Skip to content

Decision 0014 — Continuous Phase-1/Phase-2 Development

  • Status: ACCEPTED RATIONALE / NOT EXECUTION AUTHORITY
  • Authority: RATIONALE_ONLY
  • Date: 2026-08-23
  • Supersedes: the strict implementation-start sequencing portion of Decision 0013
  • Current Roadmap: ../ROADMAP.md

Context

Phase 1 has a usable local Product Core and authenticated C1/C2 Booking read paths, while its full mutation, fault, cleanup and target-role acceptance matrix still requires one final integrated run. Repeatedly stopping development to rerun the same broad suite delays the second real Product consumer and does not improve the missing evidence.

Decision

Phase-2 source development may start from the proven Phase-1 Product Core before Phase-1 reaches ACCEPTED, provided that:

  • every unexecuted Phase-1 acceptance scenario remains NOT_RUN;
  • Phase-2 acceptance cannot complete until the Phase-1 matrix and Phase-1 regressions pass;
  • final verification runs once after the requested Phase-2 development is complete;
  • DB migration/data mutation, deployment, route/writer cutover and Legacy retirement remain separately authorized effects.

A read-only Transload collection may be used during Phase 2 as the second operational consumer of shared Workspace/Collection contracts. It does not move current CTC Transload migration or writer ownership out of Phase 3.

Consequences

  • NS1-017 may hand off at its established evidence level without claiming acceptance.
  • NS2-003 may activate for bounded source slices.
  • NS2-008 owns the final integrated Phase-1 regression and Phase-2 acceptance fan-in.
  • Missing business-policy decisions still block only the affected writer, not independent read-only or source-contract work.

Rollback

Restore strict phase serialization in the Roadmap and live registry; no Runtime, DB, route or writer effect is required to roll back this sequencing decision.

---

Source: new-system/docs/decisions/0014-continuous-phase1-phase2-development.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.