# AWP Plans Index **Current phase:** **I0/I1 IMPLEMENTATION IN PROGRESS — start ratified 2026-08-21** **Browse:** markdown is canonical; run `pnpm docs:serve` and use [`../specs/view.html`](../specs/view.html)`?doc=../plans/.md`. Plans preserve product-development policy, delivery order, design decisions, evidence and execution boundaries. Most of this directory is **reference material** — see the source-of-truth rule in [`../../README.md`](../../README.md). ## Binding — Read Before Implementing 1. Repo-root [`GOLIVE.md`](../../GOLIVE.md) — AWP's one journey, acceptance criteria and cut list; the project's only progress metric. 2. [Governance Amendment 2026-08-21](AWP-GOVERNANCE-AMENDMENT-2026-08-21.md) — current gate state, proof scope, visual-freeze revocation, authority rule. 3. [I0/I1 Authority](I0-I1-AUTHORITY.md) — the distilled implementation digest. 4. [Pain Invariants](AWP-PAIN-INVARIANTS.md) — owner pain chains, design invariants and the regression test each subsystem ships with before it goes live. 5. [AWP Priority Decision 2026-08-21](AWP-PRIORITY-DECISION-2026-08-21.md) — why AWP stays active, review date 2026-09-15, no new vision extensions before the journey passes. 6. The 9 ADRs under [`../specs/adr/`](../specs/adr/). ## Reference / Historical Context 0. [External Consultation Record 2026-08-21](AWP-CONSULTATION-2026-08-21.md) — findings, standing doctrine (spec format, token economics, verification, scope) and open follow-ups from the full-project review. 1. [Specification + Design Finalization Record](AWP-SPECIFICATION-FINALIZATION-2026-08-20.md) — closes the specification phase and records U1–U6 owner approval. 2. [I0/I1 Parallel Implementation Plan](AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md) — path ownership, parallel lanes and convergence points. 3. [Development Agent 1 Launch Prompt](AWP-I0-DEVELOPMENT-AGENT-1-PROMPT.md) — prompt for the first implementation conversation. 4. [I0/I1 Implementation Readiness](AWP-I0-I1-IMPLEMENTATION-READINESS.md) — evidence ledger. 5. [Incremental Delivery Plan](AWP-INCREMENTAL-DELIVERY-PLAN.md) — I0 -> I1 -> ... -> I9 implementation order. 6. [Increment Realization Matrix](AWP-INCREMENT-REALIZATION-MATRIX.md) — capability activation/deepening map. ## Vision Authority - [Original owner VISION](../VISION.md) — original AWP/Overdeck product intent. - [Additive VISION — 2026-08-20](../VISION-EXTENSIONS-2026-08-20.md) — Project Manager/AWP Advisors, reusable expert personas and advanced Search. The additive Vision is separate so original owner wording is not silently rewritten. ## Specification / Delivery Authority - [Full Specification Ratification](AWP-FULL-SPECIFICATION-RATIFICATION.md) — binding full-specification-first / incremental-realization methodology. - [Full Specification Completion Record](AWP-FULL-SPECIFICATION-COMPLETION.md) — semantic completion/evidence record. - [Specification + Design Finalization Record](AWP-SPECIFICATION-FINALIZATION-2026-08-20.md) — final implementation handoff. - [Traceability and Contradiction Review](AWP-FULL-SPECIFICATION-TRACEABILITY-REVIEW.md) — cross-domain seam/authority review. - [Pre-Run Vision-Drift Gap Review](AWP-PRE-RUN-VISION-DRIFT-GAP-REVIEW.md) — owner-intent/FOSS/harvest/UI omission audit. - [VISION -> Specification Traceability](AWP-VISION-TO-SPEC-TRACEABILITY.md) — original Vision trace. - [UI / Page Spec Completeness Audit](AWP-UI-SPEC-COMPLETENESS-AUDIT.md) — page contract completeness. - [Target-State / Increment Strategy](AWP-TARGET-STATE-AND-INCREMENT-REALIZATION-STRATEGY.md) — anti-drift rationale and rules. - [Increment Realization Matrix](AWP-INCREMENT-REALIZATION-MATRIX.md) — binding capability map I0–I9. - [Incremental Delivery Plan](AWP-INCREMENTAL-DELIVERY-PLAN.md) — dogfood-first implementation order. ## Final Product Model ```text ProjectVision enduring product direction Goal current/future outcome Plan bounded work advancing Goal(s) Task executable work with dependencies Queue dependency-constrained dispatch projection FactoryRun orchestration instance AgentRun logical agent assignment Attempt concrete execution ChangeSet immutable candidate Review exact-candidate independent disposition Merge trusted control-plane protected mutation ``` `GOLIVE` is not a first-class primitive. A launch target is represented as a Goal with launch/readiness criteria. ## I1 Visual Authority — Owner Approved All I1 lifecycle mockups are final: ```text U1 Project Overview APPROVED / FINAL U2 Active FactoryRun APPROVED / FINAL U3 Waiting / Failure / Retry + WIP safety APPROVED / FINAL U4 ChangeSet / Review APPROVED / FINAL U5 Ready to Merge APPROVED / FINAL U6 Merged / Completed APPROVED / FINAL ``` References: - [`../mockups/i1/README.md`](../mockups/i1/README.md) - [U1 Project High-Fidelity Brief](AWP-U1-PROJECT-HIGH-FIDELITY-BRIEF.md) - [U2 FactoryRun High-Fidelity Brief](AWP-U2-FACTORYRUN-HIGH-FIDELITY-BRIEF.md) - [`../specs/ui/project.md`](../specs/ui/project.md) - [`../specs/ui/factory-run.md`](../specs/ui/factory-run.md) - [`../specs/ui/review.md`](../specs/ui/review.md) Material visual relocation or lifecycle-semantic change now requires an explicit owner-approved amendment. ## Reuse / FOSS / Harvest Authority - [Binding FOSS Decisions](AWP-FOSS-DECISIONS.md) - [FOSS Specification Coverage Matrix](AWP-FOSS-SPEC-COVERAGE-MATRIX.md) - [FOSS Minimalism Decision Pass](AWP-FOSS-MINIMALISM-DECISION-PASS.md) - [FOSS Reuse Deep Research](AWP-FOSS-REUSE-DEEP-RESEARCH.md) - [Overdeck Capability Harvest Plan](AWP-OVERDECK-CAPABILITY-HARVEST-PLAN.md) - [I0/I1 Reuse and Source Preflight](AWP-I0-I1-REUSE-PREFLIGHT.md) - [Platform/FOSS/Proven-Capability Reuse Spec](../specs/architecture/platform-reuse.md) - [Control Surfaces Spec](../specs/architecture/control-surfaces.md) Canonical no-rebuild order: ```text project-native -> current platform-modules/mod -> proven current Overdeck harvest -> native Node/Postgres/K3s/Kubernetes -> open standard -> selected narrow FOSS/provider -> custom generic mechanics only with explicit gap evidence ``` Exact Overdeck physical harvest remains an implementation evidence lane where current source access is required. Unavailable source is not permission to invent paths or duplicate potentially existing mechanics. ## Architecture Authority - [Architecture Baseline](AWP-ARCHITECTURE-BASELINE.md) - [Deployment Topology](AWP-DEPLOYMENT-TOPOLOGY.md) - [Integration / Connections Architecture](AWP-INTEGRATION-CONNECTIONS-ARCHITECTURE.md) - [Architecture Closure Audit](AWP-ARCHITECTURE-CLOSURE-AUDIT.md) - [Step 0 Dependency / Architecture Readiness](STEP-0-PREPARATION-DEPENDENCIES.md) - [I0/I1 Threat Model](AWP-I0-I1-THREAT-MODEL.md) Canonical architecture: ```text stateless edge/gateway -> authoritative modular-monolith control plane -> K3s execution plane ``` Implementation-grade architecture is indexed from [`../specs/INDEX.md`](../specs/INDEX.md#architecture). ## Advisor Personas / Search Authority - [Advisor Personas + Advanced Search Product Design](AWP-ADVISORY-PERSONAS-AND-SEARCH-DESIGN.md) - [Advisor / Search Dependency Decisions](AWP-ADVISOR-SEARCH-DEPENDENCY-DECISIONS.md) - [Advisory Agent Architecture](../specs/architecture/advisory-agents.md) - [Search and Command Palette Architecture](../specs/architecture/search-and-command-palette.md) - [Advisory Personas Domain](../specs/domains/advisory-personas.md) - [Advisory Conversation Workflow](../specs/workflows/advisory-conversation.md) - [Advisor Chat UI](../specs/ui/advisory-chat.md) - [Search / Command Palette UI](../specs/ui/search-command-palette.md) Advisor/Search final placement is specified now; operational activation remains I3/I4 according to the Increment Realization Matrix. ## Planning Authority Canonical relationship: ```text ProjectVision enduring what/why/for-whom/non-goals/constraints Goal current/future outcome Plan bounded software work intent advancing Goal(s) ``` Planning history/rationale: - [Planning Decision Register](AWP-PLANNING-DECISION-REGISTER.md) - [Planning Module Design](AWP-PLANNING-MODULE-DESIGN.md) - [Planning UX Design](AWP-PLANNING-UX-DESIGN.md) - [Planner Leadership UX](AWP-PLANNER-LEADERSHIP-UX.md) - [Quality / CI Planning](AWP-QUALITY-CI-PLANNING-DESIGN.md) - [Verification Enforcement](AWP-VERIFICATION-ENFORCEMENT-DESIGN.md) - [Delivery / Connections Planning](AWP-DELIVERY-CONNECTIONS-PLANNING-DESIGN.md) - [Engineering Communication Policy](AWP-ENGINEERING-COMMUNICATION-POLICY.md) ## Implementation / Parallel Execution Binding plan: [`AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md`](AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md) Canonical first implementation flow: ```text I0-A0 bootstrap convergence -> I0-A core domain/data/application -> parallel B provider + C execution + D UI + E source evidence -> I0 exit -> I1 end-to-end Project -> Merge dogfood ``` Recommended lane branches: ```text impl/i0-a-bootstrap impl/i0-a-core impl/i0-b-providers impl/i0-c-execution impl/i1-d-ui evidence/i0-e-overdeck-harvest ``` Every lane uses an isolated worktree and durable `docs/progress/.md` checkpoint. ## Current Execution — I1 Convergence The C0/I0 lane-launch sequence in the historical implementation documents has already happened and is **not** current execution guidance. Current work is constrained to repairing and proving the existing I0/I1 journey: ```text NOW 1. keep GOLIVE at 0/30 until current canonical-path evidence exists 2. converge the repaired default full-chain autonomy and ADR-0009 single-operator session boundary 3. reconcile concurrent dogfood/recovery work into one exact candidate without dropping either lane's fixes 4. require exact-head buildbox/architecture/security gates THEN 5. make canonical main truthful through normal landing governance 6. deploy the exact converged candidate to dogfood 7. run the real authenticated owner Project -> Goal -> Plan -> Task/Queue -> one FactoryRun/work graph -> AgentRun/Attempt -> ChangeSet -> independent Review -> automatic trusted Merge journey 8. advance GOLIVE only from fresh evidence produced by that same architecture DO NOT 9. start I2-I9 product expansion before the I1 journey is genuinely proven 10. restore fixture-era/historical GOLIVE completion claims ``` Current durable review/gate context lives in `docs/progress/2026-08-23-awp-direction-drift-audit.md`, `docs/progress/2026-08-23-i0-single-operator-session-gates.md`, and the active I1 dogfood reconciliation ledger. Do not restart product/spec design unless new implementation evidence reveals a material contradiction.