Product Specifications

These are the canonical mutable product specifications. Read only the pages relevant to the current ticket and preserve each page's approval and dependency boundaries. Repository code, assets, fixtures, mockups, and catalog machinery remain in the repository. Recorded labels below preserve source status and qualifications; they do not imply independent implementation verification.

Specification	Scope	Recorded status / qualifications	Key dependencies
Delivery Goals and roadmap readiness	Phase-scoped goals and structural readiness	Delivered contract; completed RR-R10 is not an active assignment	Dashboard design; ADR-001; ADR-003; retained repository mockups
Agent-driven delivery dashboard	Whole product dashboard and lifecycle behavior	Current product design; individual proposals retain their own qualifications	Accepted ADRs and ticket-specific decisions
Managed repository documentation	Managed documentation product behavior	Active delivered contract; later amendments retain their own boundaries	ADR-006 records the accepted M1 architecture; later source/adoption boundaries remain separate
Project execution	Opt-in app-owned execution	Current contract; grants no live execution authority; named acceptance remains pending	ADR-008; open issues linked from the specification
Active phase selection	Active-phase authority and UI	Delivered contract	ADR-001; ADR-003
Codex plugin lifecycle	Managed local plugin lifecycle	Approved	ADR-002; installed/runtime state remains separately verified
Delivery Goals Phase Board	Goals and Phase Board presentation	Delivered contract	Delivery Goals/readiness specification; retained repository mockups
Ticket Tasks	App-owned per-ticket task plans and presentation	Owner-approved product contract	ADR-005 records the accepted exact planning package; current delivery remains ticket-owned
Repository plan reconstruction	One-time plan reconstruction	Product decisions approved; implementation and publication retain stated dependencies	Managed-documentation reconciliation and linked design prerequisites
Shared Execution V1	Shared execution compatibility contract	Active source specification; adoption/runtime proof remain separate	ADR-001, ADR-002, ADR-006, ADR-007

Proposed future behavior

• Portable continuity V2: retained Phase 7 design for complete project export/import. The owner approved V2 state preservation and content access independent of a checkout on October 16, 2026. Formal ADR reconciliation remains; encoding and recovery are proposed, not delivered.