docs(ship): P2 complete → v1.26.2 (v1.27 fix-stale-wire)

---ci---
project: acdl
phase: 2
milestone: v1.27
status: complete
---ci---

.ciagent/ARCHITECTURE.md

@@ -563,7 +563,7 @@ audit record (D-204).
 
 The full evidence (every ARN, the confidence JSON, the Decision Ledger
 rows, the module-completeness gaps the live apply uncovered) is in
-`.ciagent/P4-PILOT-RUN-EVIDENCE.md`.
+`.ciagent/archive/P4-PILOT-RUN-EVIDENCE-v1.26.md` (archived v1.27).
 
 ### §12.9 — Secret Rotation (v1.26 P3 W7, SPEC §5.9 — current)
 

.ciagent/CHECKPOINT.json

@@ -1,15 +1,17 @@
 {
-  "phase": 0,
-  "stage": "research",
+  "phase": 2,
+  "stage": "complete",
   "milestone": "v1.27",
-  "phase_role": "pre_execution",
+  "phase_role": "execution",
   "attempts": 0,
-  "updated_at": "2026-08-19T04:30:00Z",
+  "updated_at": "2026-08-19T05:15:00Z",
   "project": "acdl",
   "projects": ["acdl", "nova-blockchain-exchange"],
   "active_milestone": "v1.27",
   "milestone_branch": "milestone/v1.27-po-state-catalog",
-  "phase_branch": "phase/00-pre-execution",
+  "phase_branch": "phase/02-fix-stale-wire",
   "tag_line": "v1.26.x",
-  "notes": "NFR milestone. PO state catalog + .ciagent/ compression. 3 phases planned (P1 author+archive, P2 fix-stale+wire, P3 final)."
+  "current_phase": {"phase": 2, "tag": "v1.26.2", "status": "complete"},
+  "previous_phase": {"phase": 1, "tag": "v1.26.1", "status": "complete"},
+  "notes": "v1.27 P2 complete. PROJECT.md + ROADMAP.md phase-status fixed (P3/P4/P5 complete, v1.25.5 shipped). STATE.md wired into PLAN.md + NORTH_STAR.md + ROADMAP.md P5 ship-update lists. archive/README.md updated with 8 archived files. 0 active dangling references. Next: P3 final-review-ship."
 }

.ciagent/IAM_POLICY.md

@@ -56,7 +56,8 @@ and covered by the baseline test.
 ## OIDC act_runner role (CAP-022, Phase 56)
 
 The OIDC role for the Gitea `act_runner` was created in Phase 08 and
-gone since (CAPABILITY_INVENTORY.md CAP-022). Phase 56 re-creates it
+gone since (`archive/CAPABILITY_INVENTORY-v1.10.md` CAP-022, archived
+v1.27). Phase 56 re-creates it
 with a trust policy for the Gitea runner ARN. The role grants the
 spike-runner-equivalent permissions to the runner via `sts:AssumeRole`,
 so the runner does not need a long-lived access key. This closes the
@@ -73,7 +74,7 @@ bootstrap root key; the runner then assumes the role.
 
 The OIDC role for the Gitea `act_runner` was planned in Phase 08 but
 never created (the spike used a long-lived key per D-039 waiver).
-CAPABILITY_INVENTORY.md CAP-022 recorded "iam:ListRoles shows no acdl*
+`archive/CAPABILITY_INVENTORY-v1.10.md` CAP-022 recorded "iam:ListRoles shows no acdl*
 roles." Phase 56 re-created the role:
 
 - **Role name:** `acdl-act-runner-role`

.ciagent/NORTH_STAR.md

@@ -231,6 +231,18 @@ their AI engineering teams reach for first when an agent needs to deploy.
   leadership. The deck's Proof section cites grounded metrics; its
   Roadmap section cites deferred targets honestly.
 
+## Relationship to engineering files (v1.27 update)
+
+- **NORTH_STAR.md** (this file) = the *why* — PO-authored strategic
+  direction, loaded every ci-run via `config.strategic_direction_file`.
+- **STATE.md** = the *what exists* — PO-owned capability catalog,
+  additive, updated at every milestone ship (P-final Wave 3). The PO
+  reads STATE.md before writing new REQ-NNN specs to avoid re-spec'ing
+  existing capability and to respect the invariants.
+- **ARCHITECTURE.md** = the *how* — the durable target architecture.
+- **CHECKPOINT.json** = the *now* — authoritative live phase/ship
+  state.
+
 ## v1.25 update — swappable policy-engine substrate
 
 Strategic Objective #2 (provable trust) gained a concrete substrate in

.ciagent/PLAN.md

@@ -248,4 +248,21 @@ Each phase ships a self-contained, verifiable slice:
   moved). The active `.ciagent/` root drops from 25 to 17 files.
 - P2 ships 3 fixed files + 3 wired files + archive README + consumer
   pointer. The kept files match CHECKPOINT.json state.
-- P3 ships the milestone release + cleared checkpoint.
+- P3 ships the milestone release + cleared checkpoint.
+
+---
+
+## Durable convention (v1.27 establishes)
+
+The P-final (milestone-ship) Wave 3 file-update list for every future
+milestone includes `.ciagent/STATE.md`:
+
+1. Append new capability entries for each shipped REQ (one row per
+   capability; group by domain).
+2. Mark any deprecated capability with a `Deprecated` row citing the
+   milestone + replacement.
+3. Bump the "Last milestone ship" header in STATE.md.
+
+This is wired into the v1.25 + v1.26 P5 "Updated at ship" lists in
+`ROADMAP.md` (see those sections). The next milestone's P0 PLAN.md
+inherits this convention by reading ROADMAP.md.

.ciagent/PROJECT.md

@@ -129,7 +129,11 @@ human at stage gates" model from the NORTH_STAR.
 
 ## Capability Status (Re-Verified 2026-07-27)
 
-> Source of truth: `.ciagent/CAPABILITY_INVENTORY.md` (Phase 54, D-093).
+> **PO-facing capability catalog:** `.ciagent/STATE.md` (additive;
+> updated at milestone ship). CAP-NNN IDs cross-reference the regression
+> gate at `core/regression_verify.py`.
+> Source of truth (the 2026-07-27 sweep, archived v1.27):
+> `.ciagent/archive/CAPABILITY_INVENTORY-v1.10.md` (Phase 54, D-093).
 > Tier: **local** = runs via emulating adapters (no AWS); **live-aws** =
 > runs against the live AWS account (581513795199).
 
@@ -156,7 +160,7 @@ service live, CloudFront production stack, uptime-kuma, OIDC role). The
 code would deploy them; the local emulators (Phase 53) prove the runtime
 behavior. Re-bootstrap of the OIDC role + IAM re-grant requires an admin
 principal — escalated, not silently skipped. See
-`CAPABILITY_INVENTORY.md` §"Cloud capabilities NOT re-verified".
+`CAPABILITY_INVENTORY-v1.10.md` §"Cloud capabilities NOT re-verified".
 
 **Regression gate.** `bash scripts/run_regression.sh` re-runs all 16
 auto-verifiable capabilities and fails closed on any non-Verified result.
@@ -421,14 +425,17 @@ already exist).
 - The consumer deploy MUST go through `deploy.yml@v1.25` — no direct
   `terraform apply` bypassing the platform's gates.
 
-### v1.26 phase status (live — see CHECKPOINT.json for the authoritative state)
+### v1.26 phase status (shipped — tag `v1.25.5` = the v1.26 release, merged to main 2026-08-19)
 
 - **P0** pre-execution (SPECIFY→CLARIFY→RESEARCH→IDEATE→PLAN→GRILL) — complete, tag `v1.25.0`.
 - **P1** blockchain-core (REQ-310,311,312) — complete, tag `v1.25.1`.
 - **P2** consumer-contract-and-deploy (REQ-313,314,322) — complete, tag `v1.25.2`.
-- **P3** pilot-metrics-and-policies (REQ-315,316,317,318,319,320) — pending.
-- **P4** pilot-run-and-docs (REQ-316,321) — pending.
-- **P5** final review + audit + milestone ship — pending. Tag `v1.25.5` = the v1.26 release.
+- **P3** pilot-metrics-and-policies (REQ-315,316,317,318,319,320) — complete, tag `v1.25.3`.
+- **P4** pilot-run-and-docs (REQ-316,321) — complete, tag `v1.25.4` (live apply against `581513795199` succeeded; confidence 0.800 pass; outcome backfilled).
+- **P5** final review + audit + milestone ship — complete, tag `v1.25.5` = the v1.26 release (PROCEED; 0 P0 remain; audit CLEAN; merged to main).
 
 > Phase-by-phase task breakdown, wave ordering, and persona assignments
-> live in `.ciagent/PLAN.md` (the active phase plan, retained in full).
+> live in `.ciagent/PLAN.md` (the active phase plan, retained in full).
+> v1.26 pre-execution artifacts (CLARIFY/GRILL/IDEATE/RESEARCH) are in
+> git history (pre-v1.27-P0 commits); the v1.26 phase verifications +
+> review are archived at `.ciagent/archive/{VERIFY-P03,VERIFY-P04,REVIEW-AUDIT-P05}.md`.

.ciagent/ROADMAP.md

@@ -173,12 +173,15 @@ final). Tags: `v1.24.0` (P0) → `v1.24.5` (P5 = milestone release).
   summary; delete all milestone branches.
 - Updated `REQUIREMENTS.md` (mark REQ-291..309 complete), `ROADMAP.md`
   (mark v1.25 complete), `NORTH_STAR.md` (note Strategic Objective #2 —
-  provable trust via a replaceable policy-engine substrate).
+  provable trust via a replaceable policy-engine substrate),
+  `STATE.md` (append v1.25 capability rows — note: STATE.md was authored
+  in v1.27 with the v1.25 capabilities backfilled; the v1.25 ship did
+  not update STATE.md because STATE.md did not yet exist).
 - **Requirements:** REQ-291..309 (19 requirements).
 
 ---
 
-## v1.26 (active, tag line `v1.25.x`): Live Pilot Estate Activation
+## v1.26 (complete, tag `v1.25.5` = the v1.26 release, merged to main 2026-08-19): Live Pilot Estate Activation
 
 `D-096` lifts. The first real consumer estate — a stock exchange on a
 homegrown Proof-of-Authority blockchain (equities only, single
@@ -235,7 +238,7 @@ REQ-315..322), 3 deferred. Adversarial grill: PROCEED 0.84.
 - Cross-cutting: `v1.25` floating tag → `v1.25.0` (Phase 0 ship) on the
   platform repo.
 
-### Phase P3 — pilot-metrics-and-policies (planned, tag v1.25.3)
+### Phase P3 — pilot-metrics-and-policies (complete, tag v1.25.3)
 - REQ-315: `adapters/kyverno-json/policies/settlement-finality.json` —
   kyverno-json policy asserting all matches in the promotion window have
   committed blocks (securities-specific). Authored + tested in v1.26;
@@ -258,7 +261,7 @@ REQ-315..322), 3 deferred. Adversarial grill: PROCEED 0.84.
 - REQ-320: `adapters/kyverno-json/policies/pilot-readiness/no-placeholder-account.json`
   — declarative gate preventing apply against a placeholder account.
 
-### Phase P4 — pilot-run-and-docs (planned, tag v1.25.4)
+### Phase P4 — pilot-run-and-docs (complete, tag v1.25.4)
 - REQ-321: `adapters/README.md` (new consumer row) +
   `docs/METRICS.md` (Post-Pilot metrics grounded note) +
   `.ciagent/ARCHITECTURE.md` §12.8 (Pilot Estate) +
@@ -269,7 +272,7 @@ REQ-315..322), 3 deferred. Adversarial grill: PROCEED 0.84.
   events land in the Decision Ledger; the regression gate (CAP-025)
   verifies the round-trip.
 
-### Phase P5 — final review + audit + milestone ship (Final Phase, planned, tag v1.25.5)
+### Phase P5 — final review + audit + milestone ship (Final Phase, complete, tag v1.25.5 = the v1.26 release)
 - Multi-persona code review across P1..P4 (lead-developer, backend-
   engineer, data-engineer, policy-engineer, blockchain-engineer).
   Auto-fix P0; flag P1+.
@@ -281,7 +284,8 @@ REQ-315..322), 3 deferred. Adversarial grill: PROCEED 0.84.
   full milestone summary; delete all milestone branches.
 - Update `REQUIREMENTS.md` (mark REQ-310..322 complete), `ROADMAP.md`
   (mark v1.26 complete), `NORTH_STAR.md` (note Strategic Objectives #1
-  + #3 — first real consumer estate; Post-Pilot denominators activated).
+  + #3 — first real consumer estate; Post-Pilot denominators activated),
+  `STATE.md` (append v1.26 capability rows; bump "Last milestone ship").
 
 > **Phase task-level breakdown, wave ordering, and persona
 > assignments:** `.ciagent/PLAN.md` (the active phase plan, retained in

.ciagent/STATE.md

@@ -228,9 +228,9 @@
 | CAP-028 | T+1 settlement service | v1.26 / `v1.25.1` | `settlement/service.py` | REQ-312 | local | idempotent; finality = block commit |
 | CAP-029 | Consumer `contract.yaml` (blockchain exchange) | v1.26 / `v1.25.2` | `nova-blockchain-exchange/contract.yaml`, `contracts/*.yml` | REQ-313 | local | per-env variants (dev/qa/prod); validated against contract schema |
 | CAP-030 | Consumer deploy via `deploy.yml@v1.25` (inline adapter) | v1.26 / `v1.25.2` | `nova-blockchain-exchange/.github/workflows/deploy.yml`, `.gitea/workflows/deploy.yml` | REQ-314 | local | no cross-repo `uses:` (SPEC §10 Q1); checkout `acdl/acdl @ v1.25` into `platform/`, run `run_platform.sh` |
-| CAP-031 | Live pilot apply (CAP-025 round-trip) | v1.26 / `v1.25.4` | `core/regression_verify.py` | REQ-316 | live-aws | contract→adapter→plan→policy→confidence→attestation→outbox against `581513795199` |
+| CAP-025 | Live-pilot-apply regression capability (round-trip) | v1.26 / `v1.25.3` | `core/regression_verify.py` | REQ-316 | local | contract→adapter→plan→policy→confidence→attestation→outbox round-trip assertion |
+| CAP-031 | Live pilot apply evidence (`blkex-pilot-apply-v0.2`) | v1.26 / `v1.25.4` | `.ciagent/archive/P4-PILOT-RUN-EVIDENCE-v1.26.md` | REQ-316, REQ-321 | live-aws | confidence 0.800 pass; outcome backfilled; hash chain valid; live apply against `581513795199` |
 | CAP-032 | AWS key rotation scheduled workflow | v1.26 / `v1.25.3` | `workflows-src/rotate-aws-key.yml` | SPEC §5.9 | local | daily rotation; forge-agnostic token name (REQ-230) |
-| — | Live pilot run evidence (`blkex-pilot-apply-v0.2`) | v1.26 / `v1.25.4` | `.ciagent/archive/P4-PILOT-RUN-EVIDENCE-v1.26.md` | REQ-316, REQ-321 | live-aws | confidence 0.800 pass; outcome backfilled; hash chain valid |
 
 ### Domain 10 — Forge / CI runtime
 

.ciagent/archive/README.md

@@ -8,12 +8,20 @@ state for offline agent loading.
 
 ## Why archive
 
-The active milestone is v1.26 (Live Pilot Estate Activation). The
-`.ciagent/` root held ~11,164 lines dominated by completed-milestone
-narratives (v1.0–v1.24). Per the run.md context-loading model, agents
-read `.ciagent/` every `/ci-run`; the historical narrative was not
-load-bearing for v1.26 execution and was relocated to keep the working
-context lean.
+The active milestone is v1.27 (PO State Catalog & Ciagent Compression).
+The `.ciagent/` root was compressed twice:
+
+1. **v1.26 P2 compression** (~11,164 lines → ~5,232): the
+   completed-milestone narratives (v1.0–v1.24) were relocated. Per the
+   run.md context-loading model, agents read `.ciagent/` every
+   `/ci-run`; the historical narrative was not load-bearing for v1.26
+   execution and was relocated to keep the working context lean.
+2. **v1.27 P1 compression** (~5,232 → ~3,882): the v1.26 phase
+   verifications + review + evidence + the dated CAPABILITY_INVENTORY
+   (superseded by STATE.md) + AUTONOMY_THESIS (folded into NORTH_STAR)
+   + COST (predates v1.26 pilot) were relocated. The 4 pre-execution
+   files (CLARIFY/GRILL/IDEATE/RESEARCH) were rewritten by v1.27 P0
+   and stay active through v1.27.
 
 ## Contents
 
@@ -40,6 +48,47 @@ architecture reference.
 | `VERIFY.md` | 86 | Per-phase verification records |
 | `PRE_MORTEM.md` | 228 | Pre-mortem analyses for completed milestones |
 
+### v1.27 compression — archived files (8 files, lossless `git mv`)
+
+> The v1.27 NFR milestone (PO State Catalog & Ciagent Compression) archived
+> 7 platform-root files + 1 consumer file. All are byte-identical
+> relocations; git history at the pre-v1.27 commits preserves the
+> authoritative state.
+
+#### Snapshots of superseded durable references (3 files)
+
+| File | Original (lines) | Superseded by | Status at time of snapshot |
+|---|---|---|---|
+| `CAPABILITY_INVENTORY-v1.10.md` | 120 | `.ciagent/STATE.md` (v1.27) | The 2026-07-27 re-verification sweep (v1.1→v1.8 capabilities). Predates v1.26 pilot (CAP-025 absent; blockchain capabilities absent). |
+| `AUTONOMY_THESIS-v1.21.md` | 65 | `NORTH_STAR.md` Vision + Anti-Goals #2 | "Last refined: v1.21" — the autonomy-in-operations thesis, fully folded into NORTH_STAR.md. |
+| `COST-v1.14.md` | 106 | (future cost milestone) | AWS cost report dated 2026-07-29, framed "v1.0 → v1.14". Predates v1.26 live pilot (ECS + ALB + DynamoDB + S3 costs not reflected). |
+
+#### v1.26 phase verifications + review + evidence (4 files)
+
+| File | Original (lines) | Phase(s) documented |
+|---|---|---|
+| `VERIFY-P03.md` | 39 | v1.26 P3 verification — PASS (shipped `v1.25.3`) |
+| `VERIFY-P04.md` | 31 | v1.26 P4 verification — PASS (shipped `v1.25.4`) |
+| `REVIEW-AUDIT-P05.md` | 218 | v1.26 P5 final review + audit — PROCEED (shipped `v1.25.5`; 0 P0 remain; audit CLEAN) |
+| `P4-PILOT-RUN-EVIDENCE-v1.26.md` | 46 | v1.26 live apply evidence (`blkex-pilot-apply-v0.2`; confidence 0.800 pass; outcome backfilled; hash chain valid) |
+
+#### Consumer subproject archive (1 file)
+
+| File | Original (lines) | Phase(s) documented |
+|---|---|---|
+| `nova-blockchain-exchange/archive/ROADMAP-v1.26.md` | 57 | v1.26 consumer roadmap (P3/P4/P5 marked "planned" at archive time; v1.26 shipped `v1.25.5`). Phase narrative preserved in the platform `.ciagent/ROADMAP.md` §v1.26. |
+
+#### v1.26 pre-execution artifacts (in git history, not archived to disk)
+
+The v1.26 pre-execution files (CLARIFY, GRILL, IDEATE, RESEARCH) were
+overwritten by the v1.27 P0 pre-execution cycle. The v1.26-era content
+is preserved in git history at the pre-v1.27-P0 commits (search the
+log for `docs(P00):` commits on the `milestone/v1.26-pilot-activation`
+line). The v1.27 P0 versions stay active through v1.27; they archive at
+v1.28 P1 if v1.28 happens. Decisions D-200..D-213 (v1.26) are folded
+into `PROJECT.md` load-bearing decisions; D-214..D-225 (v1.27) live in
+the active `CLARIFY.md`.
+
 ### Live operational files NOT archived
 
 These files remain at their canonical `.ciagent/` paths because they are

.ciagent/nova-blockchain-exchange/PROJECT.md

@@ -89,4 +89,9 @@ of normal operations.
 - The AWS bootstrap (S3 state bucket + DynamoDB outbox) was re-run in
   the pre-run (Workstream A3) — the platform components exist.
 - The consumer repo was created on Gitea (Workstream A4) and cloned to
-  `/root/nova-blockchain-exchange`.
+  `/root/nova-blockchain-exchange`.
+- **Phase-by-phase history:** `.ciagent/ROADMAP.md` §v1.26 (the
+  consumer ROADMAP is archived at
+  `.ciagent/nova-blockchain-exchange/archive/ROADMAP-v1.26.md` since
+  v1.27 — the platform ROADMAP is the source of truth for milestone
+  phase narrative).

.ciagent/nova-blockchain-exchange/README.md

@@ -5,7 +5,7 @@
 > secrets to set, what the contract looks like, and how to verify the
 > result. The platform side is documented in
 > `.ciagent/ARCHITECTURE.md` §12.8; the live-pilot evidence is in
-> `.ciagent/P4-PILOT-RUN-EVIDENCE.md`.
+> `.ciagent/archive/P4-PILOT-RUN-EVIDENCE-v1.26.md` (archived v1.27).
 
 This is a **consumer** of the Nova platform, not a fork. The consumer
 repo owns the app code (the blockchain, the order-matching engine, the
@@ -161,8 +161,8 @@ Ledger. Neither trusts the other.
 
 If the AWS API shows the resources AND the Decision Ledger shows the
 decision + outcome with a valid chain, the deploy is verified. See
-`.ciagent/P4-PILOT-RUN-EVIDENCE.md` for the full pilot-evidence
-checklist (every ARN, the confidence JSON, the backfill timestamp).
+`.ciagent/archive/P4-PILOT-RUN-EVIDENCE-v1.26.md` for the full pilot-evidence
+checklist (every ARN, the confidence JSON, the backfill timestamp; archived v1.27).
 
 ---
 
@@ -170,8 +170,8 @@ checklist (every ARN, the confidence JSON, the backfill timestamp).
 
 - `.ciagent/ARCHITECTURE.md` §12.8 — the pilot-estate architecture
   (this guide is the consumer-facing companion to that section).
-- `.ciagent/P4-PILOT-RUN-EVIDENCE.md` — the live-pilot evidence
-  (run `blkex-pilot-apply-v0.2`).
+- `.ciagent/archive/P4-PILOT-RUN-EVIDENCE-v1.26.md` — the live-pilot evidence
+  (run `blkex-pilot-apply-v0.2`; archived v1.27).
 - `.ciagent/nova-blockchain-exchange/PROJECT.md` — the consumer
   project charter (vision, scope, decisions D-200..D-205).
 - `.ciagent/nova-blockchain-exchange/REQUIREMENTS.md` — the consumer