# AWP Full Specification Completion Record

**Date:** 2026-08-20  
**Status:** **COMPLETE / FINALIZED FOR IMPLEMENTATION**  
**Finalization authority:** [`AWP-SPECIFICATION-FINALIZATION-2026-08-20.md`](AWP-SPECIFICATION-FINALIZATION-2026-08-20.md)

## Completion Summary

The complete target-state specification baseline is finalized and binding.

```text
ProjectVision   enduring product direction
Goal            current/future outcome
Plan            bounded work advancing Goal(s)
Task            executable work with hard dependencies
Queue           dependency-constrained dispatch projection
FactoryRun      orchestration instance
AgentRun        logical assignment
Attempt         concrete provider/model/account/workspace execution
ChangeSet       immutable candidate
Review          exact-candidate independent disposition
Merge           trusted control-plane protected action
```

`GOLIVE` is not a first-class primitive. Going live is represented as a Goal with launch/readiness criteria.

## Specification Families Complete

```text
Architecture / topology / trust / persistence      COMPLETE
Architecture Decisions / ADRs                     COMPLETE
Domain model / stable identities                  COMPLETE
ProjectVision / Goals / Planning / Work / Queue   COMPLETE
Factory / Agent / Workspace / Change / Review     COMPLETE
Accounts / Models / Providers / Connections       COMPLETE
CI / Verification / Artifacts                     COMPLETE
Release / Environment / Deployment                COMPLETE
Cluster / Incident / Resolver / Reliability       COMPLETE
Policy / Approval / Decision / autonomy           COMPLETE
Advisor Personas / Search                         COMPLETE TARGET SEMANTICS
Cross-domain workflows                            COMPLETE
Whole-product UI / information architecture       COMPLETE
Schema / transport / event / adapter families     COMPLETE
I0..I9 Increment Realization                      COMPLETE
Threat model                                      COMPLETE DESIGN
Reuse/source/provider decision map                 COMPLETE TO AVAILABLE SOURCE EVIDENCE
```

The canonical technical truth remains Markdown, with human HTML companions/index where required by the specification presentation standard.

## Core Reconciled Decisions

- ProjectVision, Goal and Plan are distinct authorities.
- Goals replace the earlier generic GOLIVE primitive.
- Task dependencies are hard directed relationships and may cross Plans within one Project where explicitly allowed.
- dependency cycles are invalid.
- manual Queue priority cannot override dependency legality.
- illegal Queue reordering is blocked/explained before mutation and revalidated server-side.
- Queue and Graph are projections over the same Work truth.
- the dependency visualization is a compound directed graph: Plan groups + Task nodes + prerequisite -> dependent edges.
- provider-native IDs never replace AWP IDs.
- execution agents do not own trusted publication/merge credentials.
- Review/evidence bind to an exact immutable candidate.
- Search/Advisor are cross-cutting product capabilities that activate in later increments without changing approved I1 placement.

## I1 Visual Design Complete

All required lifecycle states are owner-approved/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
```

Implementation references live in `docs/mockups/i1/` and the matching UI specs/briefs.

## Source / Reuse Status

Verified current Platform source baseline recorded by the preflight:

```text
platform-modules/mod
revision     b7c7f97fa0c51a1cc2f5d87ee752a3c08a08495a
Node engine  22.x
pnpm         9.7.0
```

Subrouter source/capability fit is recorded at source-contract level. Exact AWP consumer integration/pins belong to the I0 implementation workspace.

Exact current Overdeck physical harvest remains an implementation evidence lane when authorized source access is available. No paths/commits may be invented from historical context.

## Remaining Gates Are Not Specification Gaps

The following remain implementation/live-evidence work:

```text
exact Platform package consumer integration/pins
exact current Overdeck I0/I1 harvest
Subrouter AWP adapter proof
DBOS crash/recovery/idempotent-side-effect proof
Kubernetes Workspace/WIP recovery proof
gVisor representative compatibility proof
Dev Container representative environment proof
Fabro runtime mapping proof
ACP supported-agent proof
ARC ephemeral runner E2E
trusted Git publication/merge E2E
executable security mitigations tied to the active deployment
```

They must be proven when their subsystem is introduced. A blocked environment is not interpreted as a successful proof.

## Full-Specification Gate Result

```text
[✓] full architecture target set exists
[✓] full domain target set exists
[✓] full major workflow set exists
[✓] full UI/page target set exists
[✓] schemas/contracts/adapters define ownership/compatibility boundaries
[✓] human presentation/index coverage exists
[✓] Increment Realization is explicit
[✓] major primitive/flow cross-links exist
[✓] material ADR/Decision authority exists
[✓] temporary/dogfood behavior is explicit
[✓] I0/I1 implementation boundary is unambiguous
[✓] I1 U1–U6 visual authority is approved
```

**Full-specification completion gate: GREEN.**

## Implementation Boundary

```text
I0  foundation / self-hosting substrate
I1  Project + ProjectVision + Goal -> Plan -> Task/Queue -> FactoryRun -> AgentRun/Attempt -> ChangeSet -> Review -> trusted Merge
I2  real Planning + full Goal management/readiness
I3  Decisions/Approvals/autonomy + Project Manager + Search
I4  full Factory/Agent observability + AWP Advisor
I5  CI control plane
I6  Release/Deployment
I7  Cluster product surface
I8  self-healing Incident/Resolver
I9  enterprise + reliability/SLO
```

## Implementation Handoff

Parallel implementation is governed by:

- [`AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md`](AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md)
- [`AWP-I0-DEVELOPMENT-AGENT-1-PROMPT.md`](AWP-I0-DEVELOPMENT-AGENT-1-PROMPT.md)

The first development agent starts I0-A0 Bootstrap, lands convergence point C0, then independent path-owned provider/execution/UI/evidence lanes may proceed in parallel.

## Anti-Drift Rule

Implementation does not silently supersede this record. New evidence that materially changes a seam, authority rule, workflow or approved UI state requires an explicit Decision/spec amendment.

## Final Result

**Specification authoring/reconciliation: COMPLETE.**  
**I1 high-fidelity Design Complete: COMPLETE.**  
**Implementation: AUTHORIZED TO START WITH I0.**