Skip to content

CTC Work Tracks

  • Status: CURRENT AGENT INSTRUCTION
  • Effective date: 2026-08-14
  • New-System status: ../../new-system/docs/ROADMAP.md

1. Tracks

NEW SYSTEM

Use for successor Product, UX, Process, architecture, packages, UI, knowledge/catalog, Runtime and NS Tasks. Required startup is defined by new-system/AGENTS.md. All current NS Tasks use Work Graph.

LEGACY OPERATIONAL

Use only for an explicit named current PHP operation/defect/compatibility problem. Preserve current positive behavior. Do not reopen root P1-P12 or implement successor architecture in Legacy core.

TRANSITION / CUTOVER

Use for route/writer/parity/UAT/canary/rollback/caller-zero under transition/** and exact NS5/NS6 Tasks.

DESIGN / RECONSTRUCTION / EVIDENCE

  • NS0-002: initial UX direction and representative surfaces; no Runtime or invented Process semantics.
  • NS0-003: read-only current-state Process/domain/data/role/integration/source reconciliation.
  • NS0-004: reconcile final UI/page contracts with approved Process results; no Runtime.

No DB/provider/config/route/service/Wiki/physical effect is implied.

2. Current Program

root P1-P12 = STOPPED / FROZEN
NS0-001     = COMPLETE / DOCUMENTED
NS0-002     = ACTIVE
NS0-003     = PLANNED / BLOCKED ON NS0-002
NS0-004     = PLANNED / BLOCKED ON NS0-003
NS1+        = dependency-controlled by New-System Roadmap

3. Mandatory Boundaries

  • Initial UI direction before detailed Process reconstruction.
  • Process meaning before business implementation.
  • Final Process-reconciled UI contract before UI/Runtime Foundation.
  • Fixed structure/module registry before package creation.
  • Self-contained exact NS Task before work.
  • One writer per shared authority.
  • RESTRICTION DELTA = NONE unless exactly approved.
  • Unknown is inspected, not converted into policy/denial/caller-zero.
  • Docs/catalog/Source Registry/context update with code.
  • Repository/Git/DB/config/provider/route/service/Wiki/physical effects remain separate.
  • No GitHub Actions or hosted CI.

4. Mixed Requests

Split urgent Legacy operational work, New-System/reconstruction handoff and restriction/effect decisions. Do not let future architecture block the smallest safe current operation.

---

Source: .agents/rules/PHASE_AND_OPERATION_TRACKS.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.