# AWP I0 / I1 Implementation Readiness

**Date:** 2026-08-20  
**Status:** **SPECIFICATION + I1 DESIGN COMPLETE; IMPLEMENTATION MAY START — external/live evidence gates remain explicit**  
**Purpose:** authoritative readiness ledger for canonical design, source/provider proof, Step-0 runtime gates and pre-I1 security readiness.

## Rule

A gate is `GREEN` only when its required evidence exists.

```text
GREEN       required evidence exists
SOURCE-FIT  source/API contract verified; live AWP consumer proof still pending
BLOCKED     required evidence cannot yet be obtained in the authorized environment
PENDING     work belongs to the active implementation workspace/lane
```

Specification/design completeness and live provider/infrastructure readiness are tracked separately.

## 1 — Canonical Specification

| Item | Result | Evidence |
|---|---|---|
| full target architecture/domain/workflow/UI/schema baseline | **GREEN** | `docs/specs/INDEX.md` + ratified specification system |
| Goal replaces generic GOLIVE primitive | **GREEN** | `specs/domains/goals.md`; Project/Planning/domain model |
| ProjectVision != Goal != Plan | **GREEN** | domain model + Projects + Planning |
| hard Task dependencies form DAG | **GREEN** | Work + Work Queue specs |
| manual Queue priority cannot violate dependency legality | **GREEN** | Work Queue + Queue UI contracts |
| cross-Plan dependencies | **GREEN** | Work Queue + dependency graph UI |
| provider/trust/persistence boundaries | **GREEN** | architecture + adapter specs |
| I0..I9 realization boundary | **GREEN** | Incremental Plan + Realization Matrix |
| full-spec completion record | **GREEN** | `AWP-SPECIFICATION-FINALIZATION-2026-08-20.md` |

Specification phase is closed for implementation. Future material changes require evidence-backed Decision/spec amendments.

## 2 — I1 Visual Design Complete

The owner explicitly approved the complete lifecycle set on 2026-08-20.

| State | Binding artifact | Result |
|---|---|---|
| U1 Project | `docs/mockups/i1/u1-project.html` + `u1-final.css` | **GREEN — OWNER APPROVED / FINAL** |
| U2 Active FactoryRun | `docs/mockups/i1/u2-factory-active.html` + U2 brief | **GREEN — OWNER APPROVED / FINAL** |
| U3 Waiting/failure/retry/WIP | `docs/mockups/i1/u3-waiting-failure-retry.html` | **GREEN — OWNER APPROVED / FINAL** |
| U4 ChangeSet/Review | `docs/mockups/i1/u4-review.html` | **GREEN — OWNER APPROVED / FINAL** |
| U5 Ready to Merge | `docs/mockups/i1/u5-ready-to-merge.html` | **GREEN — OWNER APPROVED / FINAL** |
| U6 Merged/completed | `docs/mockups/i1/u6-completed.html` | **GREEN — OWNER APPROVED / FINAL** |
| U2–U6 shared final style/interaction | `awp-i1-final.css` + `awp-i1-final.js` | **GREEN** |

### Binding U1

```text
Current Goals / Needs Your Attention / Blockers
Active Plans / FactoryRuns / Recently Completed
Queue / Next Up: Now / Next / Later / Waiting / Blocked
Project health / freshness / timezone / customize
```

### Binding U2/U3 FactoryRun

```text
header: Plan title + FR ID / state / elapsed / Plan / Goal / Scope
tabs: Overview / Tasks / AgentRuns / Timeline / ChangeSet
main:
  Task Progress & Topology
  Active AgentRuns or Recovery & Attempts
  Latest Activity
  WIP / Checkpoint Safety
  ChangeSet / Review
  Current / Next / Attention
```

U3 preserves U2 page identity and changes the hierarchy for recovery/failure.

### Binding U4/U5/U6 Review

```text
same ChangeSet/Review page identity
changed files + exact diff
findings + evidence + provenance
MergeGate / next action
```

U4 cannot merge while blocking findings remain; U5 exposes one trusted Merge action after exact-candidate gates are green; U6 is a read-only merged/completed outcome with next work.

**I1 Design Complete gate: GREEN.**

## 3 — Source / Provider Reuse Preflight

Detailed authority: [`AWP-I0-I1-REUSE-PREFLIGHT.md`](AWP-I0-I1-REUSE-PREFLIGHT.md).

| Concern | Result | Current evidence / next proof |
|---|---|---|
| Platform current source | GREEN source baseline | `platform-modules/mod@b7c7f97...`; Node 22.x; pnpm 9.7.0 |
| Platform AWP upstream smoke | GREEN source evidence | existing upstream smoke |
| exact AWP Platform consumer integration/pins | PENDING | Lane A/B first I0 workspace |
| Subrouter source/capability fit | SOURCE-FIT | multi-account routing/token mechanics reviewed |
| Subrouter AWP adapter | PENDING | Lane B AccountProvider consumer test |
| exact Overdeck I0/I1 physical harvest | **BLOCKED in GitHub-only environment** | run Lane E with authorized source/workstation access |
| DBOS source/contract | SOURCE-FIT | live kill/restart/idempotent-side-effect proof in Lane C |
| native K8s Workspace contract | SOURCE-FIT | live WIP/pod/control restart proof in Lane C |
| gVisor | SOURCE-FIT | representative toolchain proof in Lane C |
| Dev Container CLI | SOURCE-FIT | representative environment proof in Lane C |
| Fabro | SOURCE-FIT | runtime mapping proof in Lane B/C as assigned |
| ACP | SOURCE-FIT | supported-agent runtime proof in Lane B |
| GitHub VCS/publication | SOURCE-FIT | trusted publication E2E in I1 |
| GitHub Actions + ARC | SOURCE-FIT | live ephemeral runner proof in Lane C |
| MCP official SDK | SOURCE-FIT | application integration when control surface activates |

These are implementation evidence gates, not open product-spec questions.

## 4 — Step-0 Technical Exit Gate

Detailed authority: [`STEP-0-PREPARATION-DEPENDENCIES.md`](STEP-0-PREPARATION-DEPENDENCIES.md).

### Contract/source side

```text
[✓] three-plane gateway/control/execution boundary
[✓] modular-monolith dependency rules
[✓] PostgreSQL/Drizzle transaction/event/audit authority
[✓] SecretStore/CredentialReference boundary
[✓] Workspace/ExecutionProfile semantics
[✓] trusted Git publication boundary
[✓] DBOS/Fabro/ACP/GitHub/ARC provider boundaries
[✓] UI mechanics/reuse decisions
[✓] current Platform Node/pnpm source baseline
[✓] full I1 U1–U6 visual authority
```

### Executable/live side

| Gate | Status | Owner lane |
|---|---|---|
| workspace/bootstrap package consumer pins | PENDING | A0/A |
| DBOS crash/recovery matrix | PENDING/BLOCKED until environment | C |
| K3s Workspace/WIP failure matrix | PENDING/BLOCKED until environment | C |
| gVisor compatibility | PENDING/BLOCKED until environment | C |
| Dev Container representative proof | PENDING/BLOCKED until environment | C |
| Fabro runtime mapping | PENDING | B/C |
| ACP live coding-agent paths | PENDING | B |
| ARC ephemeral real workflow | PENDING/BLOCKED until cluster | C |
| trusted Git publication/merge E2E | PENDING | B + I1 convergence |

The whole Step-0 exit is not green until the required live proofs pass. This does **not** block local foundation/domain/UI work that does not depend on those proofs.

## 5 — Security Readiness

Threat-model authority: [`AWP-I0-I1-THREAT-MODEL.md`](AWP-I0-I1-THREAT-MODEL.md).

Threat-model design is complete for:

```text
gateway/control authorization
credential isolation
trusted publication
Kubernetes/Workspace isolation
WIP durability
Review -> Merge separation / TOCTOU
webhook replay/idempotency
account-router misrouting
Queue/dependency manipulation
ARC runner isolation
audit/redaction
```

Executable mitigation evidence is produced by the same I0/I1 implementation/live-provider lanes. Privileged I1 dogfood is not security-green until those proofs pass.

## 6 — Implementation Start Authority

Implementation may now start.

The binding parallel execution plan is:

[`AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md`](AWP-I0-I1-PARALLEL-IMPLEMENTATION-PLAN.md)

The first development conversation uses:

[`AWP-I0-DEVELOPMENT-AGENT-1-PROMPT.md`](AWP-I0-DEVELOPMENT-AGENT-1-PROMPT.md)

### First implementation increment

Canonical numbering is:

```text
I0 Foundation / self-hosting substrate
I1 First complete vertical slice
```

Development Agent 1 starts **I0-A0 Bootstrap**, lands convergence commit C0, then continues I0-A Core. Provider, execution and UI lanes branch from C0 and proceed in parallel under strict path ownership.

## What Is Safe to Implement Immediately

```text
runtime/workspace skeleton
final IDs/types/contracts
architecture dependency checks
PostgreSQL/Drizzle schema + transaction skeleton
business-event/audit skeleton
Principal/capability/config skeleton
Goal/Plan/Task/dependency Queue pure domain logic + tests
provider interfaces/test doubles
approved U1–U6 UI component implementation after stable read-model contracts
```

Provider-dependent subsystem completion remains conditional on its source/live proof.

## What Must Not Be Claimed Yet

Do not claim:

- exact Overdeck harvest complete;
- live DBOS/K3s/gVisor recovery proven before evidence;
- ARC ephemeral runner E2E proven before evidence;
- Fabro/ACP runtime integration proven before evidence;
- trusted publication/merge E2E proven before the actual I1 candidate flow;
- whole Step-0 exit green before all required live proofs.

## Current Overall Result

```text
canonical target specification          DONE / FINALIZED
I1 U1–U6 visual Design Complete         DONE / OWNER APPROVED
parallel implementation plan            DONE
first development-agent launch prompt   DONE
source/provider preflight               DONE to available evidence boundary
threat model                            DONE
implementation                          AUTHORIZED TO START I0
live/private-source evidence gates      remain explicit and lane-owned
```

The next action is **launch Development Agent 1 on I0-A0**.