# AWP Plans Index

**Human view:** [`INDEX.html`](INDEX.html)  
**Current phase:** **SPECIFICATION + I1 DESIGN COMPLETE; I0 IMPLEMENTATION AUTHORIZED**  
**Implementation coordination:** [`AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md`](AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md)

Plans preserve product-development policy, delivery order, design decisions, evidence and execution boundaries. Approved specs under `../specs/` are implementation source of truth.

## Finalization / Start Here

Read these first before implementation:

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) — binding path ownership, parallel lanes and convergence points.
3. [Development Agent 1 Launch Prompt](AWP-I0-DEVELOPMENT-AGENT-1-PROMPT.md) — copy/paste prompt for the first implementation conversation.
4. [I0/I1 Implementation Readiness](AWP-I0-I1-IMPLEMENTATION-READINESS.md) — current green/red evidence ledger.
5. [Incremental Delivery Plan](AWP-INCREMENTAL-DELIVERY-PLAN.md) — canonical I0 -> I1 -> ... -> I9 implementation order.
6. [Increment Realization Matrix](AWP-INCREMENT-REALIZATION-MATRIX.html) — 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.html) — 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.html) — binding full-specification-first / incremental-realization methodology.
- [Full Specification Completion Record](AWP-FULL-SPECIFICATION-COMPLETION.html) — 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.html) — cross-domain seam/authority review.
- [Pre-Run Vision-Drift Gap Review](AWP-PRE-RUN-VISION-DRIFT-GAP-REVIEW.html) — owner-intent/FOSS/harvest/UI omission audit.
- [VISION -> Specification Traceability](AWP-VISION-TO-SPEC-TRACEABILITY.html) — original Vision trace.
- [UI / Page Spec Completeness Audit](AWP-UI-SPEC-COMPLETENESS-AUDIT.html) — 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.html) — binding capability map I0–I9.
- [Incremental Delivery Plan](AWP-INCREMENTAL-DELIVERY-PLAN.html) — 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.html)
- [U2 FactoryRun High-Fidelity Brief](AWP-U2-FACTORYRUN-HIGH-FIDELITY-BRIEF.md)
- [`../specs/ui/project.html`](../specs/ui/project.html)
- [`../specs/ui/factory-run.html`](../specs/ui/factory-run.html)
- [`../specs/ui/review.html`](../specs/ui/review.html)

Material visual relocation or lifecycle-semantic change now requires an explicit owner-approved amendment.

## Reuse / FOSS / Harvest Authority

- [Binding FOSS Decisions](AWP-FOSS-DECISIONS.html)
- [FOSS Specification Coverage Matrix](AWP-FOSS-SPEC-COVERAGE-MATRIX.html)
- [FOSS Minimalism Decision Pass](AWP-FOSS-MINIMALISM-DECISION-PASS.html)
- [FOSS Reuse Deep Research](AWP-FOSS-REUSE-DEEP-RESEARCH.html)
- [Overdeck Capability Harvest Plan](AWP-OVERDECK-CAPABILITY-HARVEST-PLAN.html)
- [I0/I1 Reuse and Source Preflight](AWP-I0-I1-REUSE-PREFLIGHT.html)
- [Platform/FOSS/Proven-Capability Reuse Spec](../specs/architecture/platform-reuse.html)
- [Control Surfaces Spec](../specs/architecture/control-surfaces.html)

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.html#architecture`](../specs/INDEX.html#architecture).

## Advisor Personas / Search Authority

- [Advisor Personas + Advanced Search Product Design](AWP-ADVISORY-PERSONAS-AND-SEARCH-DESIGN.html)
- [Advisor / Search Dependency Decisions](AWP-ADVISOR-SEARCH-DEPENDENCY-DECISIONS.html)
- [Advisory Agent Architecture](../specs/architecture/advisory-agents.html)
- [Search and Command Palette Architecture](../specs/architecture/search-and-command-palette.html)
- [Advisory Personas Domain](../specs/domains/advisory-personas.html)
- [Advisory Conversation Workflow](../specs/workflows/advisory-conversation.html)
- [Advisor Chat UI](../specs/ui/advisory-chat.html)
- [Search / Command Palette UI](../specs/ui/search-command-palette.html)

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/<lane>.md` checkpoint.

## Immediate Next Work

```text
NOW
1. launch Development Agent 1 from AWP-I0-DEVELOPMENT-AGENT-1-PROMPT.md
2. Agent 1 lands C0 bootstrap convergence commit
3. in parallel immediately, launch Lane E Overdeck/source harvest if authorized source access exists

AFTER C0
4. launch Lane B providers
5. launch Lane C durable execution/K3s/ARC
6. launch Lane D I1 UI against stable contracts
7. continue Lane A core domain/persistence/application

CONVERGE
8. close required I0 source/runtime/security evidence gates
9. pass I0 exit
10. dogfood I1 Project -> Goal -> Plan -> Task/Queue -> FactoryRun -> AgentRun/Attempt -> ChangeSet -> Review -> trusted Merge
```

Do not restart product/spec design unless new implementation evidence reveals a material contradiction.