merge(milestone): v1.26 Live Pilot Estate Activation to main (release v1.25.5)

The first real consumer estate (blockchain stock exchange on a homegrown PoA blockchain, equities only, dev) is activated against live AWS account 581513795199. All 13 requirements (REQ-310..322) complete. 5 phases: P0 pre-execution, P1 blockchain-core, P2 contract+deploy, P3 pilot-metrics-and-policies (Gitea adapter + kj substrate + outcome backfill + pilot policies), P4 pilot-run-and-docs (live apply + Decision Ledger evidence stream), P5 final-review+audit. Live outputs: ALB app-254671247.us-east-1.elb.amazonaws.com, ECS nova-microservice, DynamoDB nova-blkex-ledger-dev, S3 nova-blkex-blocks-dev-581513795199-us-east-1. Confidence 0.800 pass (dev autonomous). fact_decision.outcome=succeeded (REQ-317 backfill). ---ci--- project: acdl phase: 5 milestone: v1.26 status: complete requirements: covered: [REQ-310, REQ-311, REQ-312, REQ-313, REQ-314, REQ-315, REQ-316, REQ-317, REQ-318, REQ-319, REQ-320, REQ-321, REQ-322] partial: [] ---
merge(phase/05): v1.26 P5 final review + audit complete — milestone release
2026-08-19 03:53:58 +00:00 · 2026-08-19 03:53:50 +00:00 · 2026-08-19 03:53:17 +00:00 · 2026-08-19 03:53:15 +00:00 · 2026-08-19 03:28:20 +00:00 · 2026-08-19 03:28:02 +00:00
110 changed files with 13463 additions and 8249 deletions
@@ -1,16 +1,28 @@
-# Nova — Architecture (v1.1 target)
+# Nova — Architecture
-> Target architecture for the real Agentic Cloud Delivery Platform (rebranded
+> **Compressed.** The full v1.0–v1.24 architecture history (v1.1 spike
-> Nova in v1.15). Source of truth for **how**: `docs/architecture.md` (v0.2) is the upstream
+> scope, v1.2 build-out, v1.8–v1.16 addenda) is preserved verbatim at
-> draft; this file is the Nova-repo operating copy, refined at phase
+> `.ciagent/archive/ARCHITECTURE-v1.0-v1.24.md`. This file retains the
-> boundaries. Where this file and `docs/vision.md` conflict, the vision wins.
+> durable target architecture (§1–§12, the four layers + six cross-cutting
 > concerns) + the three addenda that describe the **current state**:
 > v1.11 (stateless adapter), v1.15 (Nova rebrand — current naming), and
 > v1.17 (telemetry/observability layer + §12.7 Policy Engine Registry).
 > Intermediate addenda (v1.1 spike scope, v1.2 build-out, v1.8/1.9/1.10/
 > 1.12/1.13/1.14/1.16) describe evolved or superseded states and are
 > preserved in the archive snapshot.
 >
 > Source of truth for **how**: `docs/architecture.md` (v0.2) is the
 > upstream draft; this file is the Nova-repo operating copy, refined at
 > phase boundaries. Where this file and `docs/vision.md` conflict, the
 > vision wins.
 ## Status
-Architecture is at **v0.2** upstream (`docs/architecture.md`). Milestone v1.1
+Architecture is at **v0.2** upstream (`docs/architecture.md`). Milestone
-**finalizes it to v1.0** in Phase 07 by resolving the 11 open decisions
+v1.1 **finalized it to v1.0** in Phase 07 by resolving the 11 open
-(see `PROJECT.md` open-decision resolutions table). This file records the
+decisions (see `PROJECT.md` open-decision resolutions table). The v1.11
-locked commitments and the v1.1 spike scope.
+addendum (stateless adapter) and the v1.17 addendum (telemetry layer +
 §12.7 Policy Engine Registry) record the current-state refinements.
 ## Overview
@@ -55,8 +67,9 @@ the same policy envelope, and the same evidence stream.
 ### Layer 1 — Foundational Primitives
 Single-purpose, **engine-agnostic** primitive modules. L1 modules do
 not compose with other L1s; L1 takes its environment as input. The L1
-interface is defined against the **Target Stack IR**, not against Terraform
+interface is defined against the **Target Stack IR**, not against
-directly (the IR is shaped to round-trip to Terraform in v1, per §12.1).
+Terraform directly (the IR is shaped to round-trip to Terraform in v1,
 per §12.1).
 - No inter-L1 references. L1 may call Terraform data sources.
 - Semver: interface → MAJOR, behavior → MINOR, lifecycle → PATCH (W3.D).
@@ -68,8 +81,8 @@ Combine L1 primitives into deployable shapes. Each codebase maps to one
 canonical L2 stack (`multiStack: true` only per W1.B). Shape X
 (parameterized module) or Shape Y (thin-composition layer). Hierarchical
 composition, max depth 5, only registered L1s. The thin-composition tree's
-`wires` field is defined against the IR's relationship type, not a Terraform
+`wires` field is defined against the IR's relationship type, not a
-module block.
+Terraform module block.
 Pipeline quality checks: secrets-in-plaintext, public ingress, IAM
 wildcard, KMS key reference, tag compliance, naming convention. Restricted
@@ -149,6 +162,10 @@ before contract submission ack); RTO = async worker's dead-letter recovery.
 Single-region in v1. The outbox also stores per-contract QA and prod
 approver identities (the only durable record outside GitHub's audit log).
 > **v1.17 update:** the Decision Ledger (SQLite hash-chain, D-121) is the
 > pilot's audit record. S3 Object Lock / JWS (D-083) is deferred — see
 > the v1.17 addendum below.
 ### Human-in-the-Loop mechanics (§10)
 Pre-execution gates. qa, prod, dr are PR-based attestation gates backed by
 GitHub Environments with required reviewers. No partial deployment to roll
@@ -181,28 +198,28 @@ platform does not run the skill. Stateless agents, all state in the
 platform. Skills are reviewed for sensitive data before release (Infra &
 Ops owns the review; it is the mandatory release gate).
-### Angine execution (§12) — the binding constraint
+### Engine execution (§12) — the binding constraint
-**Target Stack IR** (locked): a engine-neutral description of resources
+**Target Stack IR** (locked): an engine-neutral description of resources
 (typed inputs/outputs/NFRs), relationships (single parent per child),
 composition (tree, max depth 5), and policy hooks. The L1 registry, L2
 thin-composition tree, contract YML, and PolicyCheckResult schema are all
 defined against the IR — none against any specific engine.
-**Angine adapters** are the only engine-specific code. An adapter
+**Engine adapters** are the only engine-specific code. An adapter
-compiles the IR into a engine execution plan. **v1 ships exactly one
+compiles the IR into an engine execution plan. **v1 ships exactly one
 adapter: the Terraform adapter.** v2+ may add OpenTofu, Pulumi, K8s CRDs
 without architectural change.
 v1 reality: the IR is shaped to round-trip cleanly to Terraform (nearly
 isomorphic). As more adapters appear, the IR gets more expressive and the
-adapters gain translation logic; the L1 content, the YML standard, and the
+adapters gain translation logic; the L1 content, the YML standard, and
-thin-composition tree do not change.
+the thin-composition tree do not change.
-**Terraform adapter (v1):** translates IR-typed L1 interface → Terraform
+> **v1.11 update:** the Terraform adapter is now a **stateless assembler**
-`variable`/`output` blocks; IR-typed L2 thin-composition tree → Terraform
+> (~80 lines, emits `module "x" { source }` blocks) — see the v1.11
-root module; IR-typed relationships → module references; emits a
+> addendum below. The §12 "thin layer that translates IR → Terraform
-`terraform plan` from the IR. The adapter is a thin layer; it does not own
+> variable/output blocks" framing is superseded by the stateless-assembler
-L1/L2 content.
+> model; the L1-owns-its-shape invariant is the new contract.
 State storage: S3 (state) + DynamoDB (locking), cloud-managed,
 single-region in v1.
@@ -211,6 +228,10 @@ Policy toolchain: **Checkov** for Terraform plan policy (the L2 checks +
 tag/naming); **Kyverno** for K8s-native/platform-internal policy; **OPA**
 reserved for cross-resource cases, explicitly last resort.
 > **v1.25 update:** the policy toolchain is now unified under the
 > swappable `PolicyEngine` protocol — see §12.7 below. Checkov and Wiz
 > remain as raw-finding adapters feeding into kyverno-json meta-policies.
 **Policy result normalization (§12.6):** the confidence signal consumes a
 normalized `PolicyCheckResult` schema, not raw engine output.
@@ -242,337 +263,9 @@ Contract→IR resolution: the contract declares intent in IR-typed terms;
 the pipeline resolves it to a target stack (list of L1 instances + inputs +
 relationships); the Terraform adapter compiles the target stack to a plan.
-## v1.1 spike scope
+---
-The spike (Phases 08–10) materializes the **minimum** that proves the IR
+## v1.11 Addendum — Stateless Adapter + Pipeline-Driven Lifecycle Testing (current state)
 commitments hold (no polyglot mess):
 - One L1: `l1-s3` (IR-typed interface; the only AWS resource in the spike).
 - One L2 thin-composition: `l2-static-assets` (references `l1-s3` only).
 - Terraform adapter: IR → `terraform plan` against AWS via OIDC.
 - One contract submission → contract→IR → `terraform plan` → Checkov
  `PolicyCheckResult` → confidence signal → evidence event to the DynamoDB
  outbox.
 - State: S3 + DynamoDB (real AWS, single-region).
 Out of spike scope: full HITL matrix wiring, Kyverno, OPA, MCP skill
 catalog, GitOps reconciler, multi-region, prod/dr environments, the 5-skill
 L3B catalog. Those are post-spike (v1.2+) platform build-out.
 ## Gitea API surface (carried from v1.0, refined)
 | Capability | Gitea support | ACDL approach (v1.1) |
 |------------|---------------|----------------------|
 | Org-scoped repo create | `POST /api/v1/orgs/{org}/repos` | Used for any new repos |
 | Native Pages | **None** | Serve `acdl-evidence` via raw file URLs (unchanged from v1.0) |
 | Environments API | **None**; act_runner ignores `environment:` | Model HITL gates via `workflow_dispatch` approval inputs (v1.0 D-013 pattern) — **refined in Phase 07** for the real pre-execution gate model |
 | `repository_dispatch` | Not supported | Cross-repo trigger via `workflow_dispatch` API (unchanged) |
 | Reusable workflows | Supported | `acdl/.gitea/workflows/pipeline.yml` via `uses: ...@<ref>` |
 | `id-token: write` / OIDC | **Not supported** (RESEARCH TARGET 1, conf 0.95). Gitea docs list `id-token` as an unsupported GitHub-only scope; open proposal go-gitea/gitea#33681; draft PR go-gitea/gitea#36988 unmerged. Even Gitea's own CI uses long-lived AWS keys (issue #37980). | **Spike waiver D-039:** per-run-rotated long-lived key (rotated after each run by `scripts/rotate_spike_key.sh`). Real OIDC deferred to v1.2, blocked on PR #36988. |
 | `actions/configure-aws-credentials` | Unusable without OIDC | Spike uses static AWS creds from a (rotated) Gitea Actions secret via the `aws-actions/configure-aws-credentials@v4` `access-key-id`/`secret-access-key` inputs, or plain `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` env vars. v1.2 switches to `role-to-assume` when OIDC lands. |
 ### Branch pinning rule (refined for W2.A)
 - Dev/qa contracts reference the reusable workflow by **tag**
  (`@v1.1-spike`).
 - Prod-bound workflows reference by **SHA**; the platform CLI
  (`platform/cli/resolve-tag.ts`, Phase 07) resolves the current tag to its
  SHA. (Spike scope: the CLI is a stub; the real CLI lands in v1.2.)
 ### Verification toolchain
 ACDL has no `package.json`. The verification gate substitutes:
 - **typecheck:** `terraform validate`, `python3 -m py_compile`, JSON Schema
  validation (`ajv` or `python -m jsonschema`) against `schemas/`.
 - **test:** per-phase `scripts/verify_phaseNN.sh` (Phase 06: archive integrity;
  Phase 07: schema validation + decision-resolution completeness; Phase 08:
  OIDC assume-role + state backend; Phase 09: IR + L1 + adapter `terraform
  plan`; Phase 10: end-to-end contract submission).
 - **build:** `terraform init` (real build for the spike).
 - See `PERSONAS.md` verification_toolchain.
 ## Build order (v1.1)
 1. Phase 06 — archive demo, reorient repo.
 2. Phase 07 — finalize architecture v1.0; author schemas + designs.
 3. Phase 08 — AWS OIDC bootstrap (use temp key once, rotate).
 4. Phase 09 — IR + `l1-s3` + Terraform adapter → `terraform plan`.
 5. Phase 10 — `l2-static-assets` + contract→IR → end-to-end spike.
 6. COMPLETE gate — review → ship `v1.2.0` → audit. **DONE.**
 ## v1.2 build-out scope
 v1.2 takes the v1.1 spike (dev-only, `plan`-only, single S3 L1) to a real,
 simpler, better-documented platform that delivers a microservice to AWS ECS
 Fargate end-to-end. The locked architecture (§1–§12) is unchanged — v1.2
 extends the *implementation*, not the design.
 ### In scope (five axes, user-directed 2026-07-21)
 1. **Re-evaluate the current state.** go-gitea/gitea#36988 (OIDC for Gitea
   Actions) re-checked 2026-07-21: still **open** (last updated 2026-05-27,
   not merged). Real OIDC remains deferred to v1.3+; v1.2 extends the D-039
   per-run-rotated-key waiver as **D-047**. The waiver continues to satisfy
   §12.5's *intent* (no *persistently* long-lived key): the spike key is
   rotated after each run by `scripts/rotate_spike_key.sh`, and Phase 12
   tightens the IAM scoping + rotation hygiene.
 2. **NFR improvements on the existing spike.** Least-privilege IAM audit of
   `spike_runner_policy.json`; idempotent `create_state_backend.py` /
   `create_iam_user.py`; proper exit codes / error handling; P1-1 redaction
   (two AWS access key IDs in `.ciagent/VERIFY.md` Phase 09 narrative).
 3. **Streamline / simplify the current setup.** Consolidate
   `run_spike_plan.sh` + `run_spike_e2e.sh` into one
   `scripts/run_platform.sh`; remove dead code and stale `platform/` paths.
 4. **README.md fully up to date on how the platform works.** Reflect v1.1
   complete; document the actual spike flow, `scripts/run_platform.sh`, the
   real repo layout, and the v1.2 objective.
 5. **Bootstrap a consumer repo with a basic microservice deployed to ECS
   end-to-end.** New Gitea repo `acdl-consumer-microservice` (org
   `continuous-intelligence`); new IR-typed L1s (`l1-vpc`, `l1-ecs-cluster`,
   `l1-ecs-service`, `l1-iam-role`, `l1-alb`, `l1-ecr`); new
   `l2-microservice` thin-composition; one contract submission →
   `terraform apply` (dev, autonomous per §10, confidence ≥ 0.50) → a live
   ECS Fargate service serving HTTP 200 → evidence event to the DynamoDB
   outbox → acdl-evidence timeline.
 ### Angine extension (ECS Fargate)
 The Terraform adapter (§12) remains the only engine-specific code. v1.2
 expands the adapter `TYPE_MAP` to cover the six new ECS-shaped IR resource
 types. The L1 interface shape (IR-typed inputs/outputs/NFRs, registered in
 `modules-ir/registry.json`) is unchanged — only the set of registered L1s
 grows. The IR commitments (REQ-28) continue to hold: `modules-ir/`,
 `schemas/`, `contracts/`, `core/confidence_signal.py`,
 `core/contract_resolver.py`, `core/outbox_writer.py`
 remain engine-agnostic.
 ### `terraform apply` (dev only)
 v1.2 lifts the engine execution from `plan` to `apply` for the `dev`
 environment only. Dev is autonomous per §10 (confidence ≥ 0.50, no HITL).
 `apply` for qa/prod/dr remains HITL-gated and out of scope for v1.2. The
 apply result (resources created, plan diff) is captured in the evidence
 stream as a `terraform.apply` event.
 ### Out of scope for v1.2 (deferred to v1.3+)
 | Feature | Reason |
 |---------|--------|
 | Real OIDC federation | go-gitea/gitea#36988 still open. v1.2 extends D-039 waiver (D-047); real OIDC is v1.3+. |
 | Full HITL matrix wiring (qa/prod/dr) | v1.2 is dev-only autonomous `apply`; HITL wiring is v1.3. |
 | Kyverno + OPA policy engines | v1.2 keeps Checkov only; Kyverno/OPA are v1.3. |
 | MCP skill catalog + real L3B agent | v1.2 keeps the L3B stub; the 5-skill catalog is v1.3. |
 | Audit ledger build-out (S3 Object Lock + JWS + async worker + DLQ + daily checkpoints) | v1.2 keeps the v1.1 outbox; the regulatory ledger is v1.3. |
 | Multi-region state / outbox | Single-region in v1 (§9, §12.3); multi-region is v1.3+. |
 | Prod/dr environments | v1.2 is dev-only; prod/dr are v1.3. |
 | GitOps reconciler (ArgoCD/Flux) | v1.3+. |
 ## Build order (v1.2)
 1. Phase 11 — re-eval #36988 + NFR audit + simplification findings + README rewrite.
 2. Phase 12 — NFR harden + simplify (idempotent bootstrap, one `run_platform.sh`, IAM audit, redactions).
 3. Phase 13 — six ECS L1s + adapter `TYPE_MAP` expansion.
 4. Phase 14 — `l2-microservice` + contract schema extension.
 5. Phase 15 — consumer repo + `terraform apply` (dev) → live ECS service.
 6. Phase 16 — capstone e2e: consumer commit → live HTTP 200 → evidence → timeline.
 7. COMPLETE gate — review → ship `v1.3.0` → audit.
 ## v1.8 Architecture Addendum
 > Milestone v1.8 (complete, tag `v1.8.0`). Adds encryption-by-default,
 > deletion-protection-by-default, uptime monitoring, decommission alias,
 > engineering standards, and path documentation.
 ### New Primitives
 - **`kms-key`** (`aws:kms:key`) — Per-stack customer-managed KMS key with
  `enable_key_rotation = true`. One key per L2 deployment (no shared keys).
  Wired into both L2 compositions as a child, with its `kms_key_arn` output
  connected to all children's `kms_key_arn` input. Adapter emits
  `aws_kms_key` + `enable_key_rotation`.
 - **`uptime`** (`aws:ecs:uptime-service`) — Uptime-kuma on ECS Fargate with
  a feature flag (`feature_flag_enabled`), monitored endpoints (HTTP/DNS/TCP),
  alert channels (Teams/email/SMS/GitHub issues). Deployed by default after
  any L2 module with a separate terraform state. When the feature flag is
  false, the adapter emits no resources.
 ### Encryption by Default
 All 12 L1 primitives have `encryption_enabled` NFR (default true). Primitives
 with at-rest data (s3, rds, ecr, ecs-service, ecs-cluster) have an optional
 `kms_key_arn` input. The adapter emits encryption blocks (SSE-KMS for S3,
 storage_encrypted for RDS, encryption_configuration for ECR) referencing the
 per-stack CMK when provided. Managed KMS fallback with stderr warning for
 standalone L1 deployments.
 ### Deletion Protection by Default
 All 12 L1 primitives have `deletion_protection` NFR (default true). The
 adapter emits `lifecycle { prevent_destroy = true }` when true. L2 modules
 expose a `features.deletion_protection` flag (default true) propagated to
 all children via the resolver. Setting `inputs.deletion_protection: false`
 in the contract disables it for the whole stack.
 ### Decommission Alias
 A `mode: decommission` on the deploy pipeline implements a 2-step destroy:
 1. Disable deletion protection (resolve with `deletion_protection: false`,
   terraform plan/apply, HITL SRE gate via GitHub environment).
 2. Zero counts + destroy (`decommission_transform` zeroes all scalable counts,
   terraform plan/apply, second HITL SRE gate).
 CMDB validation via DynamoDB `acdl-change-requests` table. The Lambda
 `validate_change_request` action queries the table and asserts
 `status == "approved"` + `consumerRepo` match.
 ### Adapter Expansion
 TYPE_MAP grew from 16 to 19 entries (+ `aws:kms:key`, `aws:kms:alias`,
 `aws:ecs:uptime-service`). Specialized emission branches added for KMS key
 rotation, S3 SSE-KMS configuration, uptime ECS Fargate task, and
 `prevent_destroy` lifecycle on all resources.
 ### Pipeline Stages
 The deploy pipeline grew from 8 to 9 stages (+ `deploy-uptime` after
 `publish-outputs`). The `deploy-uptime` stage constructs a synthetic uptime
 contract from the L2 stack outputs, resolves + adapts it to a separate
 terraform state directory, and publishes the uptime URL via PR comment.
 ### Forge-Agnostic API URLs
 The platform Lambda (`contract_ingestor.py`) reads `GITHUB_API_BASE` env
 for forge-agnostic API URLs. GitHub uses `/search/issues`; Gitea uses
 `/repos/{owner}/{repo}/issues`. Detection via `/api/v1` in the base URL.
 ## v1.9 Addendum (2026-07-23)
 ### New Components
 - **`core/contract_resolver.py` interpolation** (D-081): the resolver
  now expands `${env.<field>}` + `${contract.<field>}` tokens
  post-schema-validation, pre-IR-resolution. The env context is the
  loaded environment onboarding JSON (`core/environments/<name>.json`,
  schema `schemas/environment.schema.json`). The resolver's
  `child_input_map` routes L2 wires to the sub-resource that declares the
  input (P1-1 — `desired_count` → `aws:ecs:service`, `family` →
  `aws:ecs:task_definition`).
 - **`core/environment_check.py` `load()`** (REQ-104): loads + returns the
  parsed environment JSON; emits a stderr warning for placeholder
  `account_id` when env != dev.
 - **`core/hitl_gates.py`** (REQ-108, D-084): the HITL pre-execution
  attestation gate. Records the approver identity to the DynamoDB outbox
  (`approver_qa`/`approver_prod`/`approver_dr`), runs the separation-of-
  duties check on prod, invokes the attestation matrix, returns
  `(ok, reason)`. Dev skips (autonomous). `run_platform.sh` calls
  `attest` before apply for qa/prod/dr.
 - **`core/attestation_matrix.py`** (REQ-109, D-084): the 8-concern
  attestation matrix from `hitl_matrix_design.md` §10.4. Offline-testable
  concerns (contract NFRs, schema validity, policy pass) run for real;
  operator-supplied concerns accept signed evidence artifacts validated
  for freshness + schema. Signature verification skips when
  `ACDL_ATTESTATION_SIGNING_KEY_ID` is unset (D-089).
 - **`core/separation_of_duties.py` `route_halt_artifact`** (REQ-107):
  real SNS publish (`acdl-sod-halt` topic, ARN from
  `ACDL_SOD_HALT_TOPIC_ARN`) + outbox fallback
  (`SEPARATION_OF_DUTIES_VIOLATION` event). The SNS topic is defined in
  `terraform/platform/main.tf`.
 - **`adapters/wiz/wiz_adapter.py` `WizClient`** (REQ-110): real GraphQL
  API client (`<WIZ_API_URL>/graphql`, Bearer auth, pagination via
  `pageInfo.hasNextPage`). `fetch_and_adapt` translates issues →
  `PolicyCheckResult`. Graceful degrade when unconfigured.
 - **`adapters/kyverno/kyverno_adapter.py`** (REQ-111): fleshed-out
  `PolicyReport` → `PolicyCheckResult` mapping (pass/fail/skip/warn +
  severity + skip-with-reason + resource construction). Inactive-for-TF
  guard preserved.
 ### Per-Environment Promotion (D-082)
 The deploy workflow (`.github/workflows/deploy.yml` +
 `.gitea/workflows/deploy.yml`, byte-identical) declares an `environment`
 `workflow_call` input. When non-empty, `run_platform.sh --environment
 <name>` overrides the contract's `environment` field before schema
 validation (D-088). One CI job per environment; promotion = running the
 matching job, no `environment:` field editing. Per-env contract files
 (`contracts/<module>.<env>.yaml`) use interpolation for env-specific
 values.
 ### Adapter Parameterization (P1-1, D-085)
 The adapter (`adapters/terraform/adapter.py`) reads ECS/ALB/VPC defaults
 from L1 `interface.json` inputs (`desired_count`, `launch_type`,
 `family`, `target_type`, `load_balancer_type`, `name`). The adapter is a
 thin translator; the `child_input_map` routes wires to the declaring
 sub-resource.
 ### Deferred (D-083)
 S3 Object Lock + JWS detached signatures + async worker + DLQ + daily
 checkpoints (audit ledger build-out) — deferred to a future milestone.
 The hash-chain + DynamoDB-outbox path remains the v1.9 production audit
 record.
 ## v1.10 Addendum — Regression VERIFY + Local Emulators + Capability Re-Verification
 ### Regression-Class VERIFY (D-091, `core/regression_verify.py`)
 The standard VERIFY stage was diff-scoped (it checked the phase diff
 only, never re-ran underlying capability). This let 8 NFR-patch phases
 (v1.9.1–v1.9.8) pass while the platform decayed. The regression-class
 VERIFY (`core/regression_verify.py`) re-runs capability checks against
 the current codebase and tags each Verified/Decayed/Broken. It fails
 closed on any non-Verified capability, blocking milestone completion.
 The registry (`CAPABILITY_REGISTRY`) holds 16 capability checks
 (CAP-001..CAP-016): 12 local-tier + 4 live-AWS. Adding a capability is
 a single function + one registry entry. The gate runs via
 `scripts/run_regression.sh` and writes `.ciagent/REGRESSION_REPORT.md`
 + `.json`.
 ### Local Emulating Adapters (D-092, `core/local_emulators.py`)
 Four local adapters let the platform run the full headline E2E without
 cloud credentials:
 - `FlatFileOutbox` — flat-file DynamoDB outbox emulator (hash-chained
  JSONL; resumable across instances; chain verification).
 - `LocalEcsEmulator` — local ECS Fargate HTTP 200 emulator (binds port
  0 on 127.0.0.1; daemon thread; clean destroy).
 - `LocalS3StateBackend` — rewrites the terraform S3 backend to a local
  backend (per-stack tfstate in a temp folder).
 - `LocalLambdaStub` — invokes the contract_ingestor handler in-process
  (patches `_get_dynamodb`/`_get_secrets_client`/`urllib.urlopen`;
  DynamoDB writes redirected to the FlatFileOutbox).
 `run_local_e2e()` runs the full pipeline: contract → resolver → adapter
 → local S3 backend → local ECS (HTTP 200) → flat-file outbox (chain
 verified) → local Lambda (200). Gated on `ACDL_LOCAL_TIER=1`.
 ### Capability Re-Verification Sweep (D-093)
 `.ciagent/CAPABILITY_INVENTORY.md` enumerates 16 auto-verified
 capabilities + 6 IAM-gated escalated resources. The sweep found and
 fixed 7 adapter defects in `adapters/terraform/adapter.py` (duplicate
 outputs, duplicate args, missing required args, deprecated AWS provider
 v5 arg names). The headline E2E now passes at both tiers: local
 emulator + live-AWS terraform init/validate/plan.
 ### Adapter Defect Fixes (P54)
 7 defects fixed in `adapters/terraform/adapter.py`:
 1. Duplicate output definitions (per-resource + stack-level both emitted).
 2. Duplicate `desired_count`/`launch_type` on ECS service.
 3. Duplicate `target_type`/`family`/`load_balancer_type`.
 4. Missing `assume_role_policy`/`role_name` on IAM role (L2 composition gap).
 5. Missing `cidr_block`/`vpc_id`/`name` defaults on VPC/subnet/route_table/
   ECS cluster/ECR repository.
 6. ECR `kms_key_arn` unsupported arg → `encryption_configuration` block.
 7. CloudFront OAC + WAF deprecated arg names (AWS provider v5):
   `signing_behavior`, `signing_protocol`, `origin_access_control_id`,
   `s3_origin_config.origin_access_identity`, `origin_id`, `rule`
   (singular), `scope=CLOUDFRONT` (uppercase).
 ## v1.11 Addendum — Stateless Adapter + Pipeline-Driven Lifecycle Testing
 **Stateless adapter (D-098).** `adapters/terraform/adapter.py` rewritten
 from a 918-line monolith (3 constant tables `TYPE_MAP`/`INPUT_MAP`/
@@ -598,83 +291,25 @@ VPC; the microservice composition references it via
 `terraform_remote_state` (data source). State keys are deterministic and
 env-aware (`spike/{contract.id}/{contract.environment}/terraform.tfstate`).
-**NOVA_LIFECYCLE_MODE (v1.12, REQ-134; renamed ACDL→NOVA in v1.15 P2).** The lifecycle pipeline defaults
+**NOVA_LIFECYCLE_MODE (v1.12, REQ-134; renamed ACDL→NOVA in v1.15 P2).**
-to plan-only (fast, no AWS mutation, no cost). A CI variable
+The lifecycle pipeline defaults to plan-only (fast, no AWS mutation, no
-`NOVA_LIFECYCLE_MODE` (default `plan`) overrides to `full` for the real
+cost). A CI variable `NOVA_LIFECYCLE_MODE` (default `plan`) overrides to
-apply→modify→destroy. (P2–P4 dual-read fallback to `ACDL_LIFECYCLE_MODE`;
+`full` for the real apply→modify→destroy. (P2–P4 dual-read fallback to
-fallback removed in P5 per the v1.15 addendum.)
+`ACDL_LIFECYCLE_MODE`; fallback removed in P5 per the v1.15 addendum.)
 ## v1.12 Addendum — Presentation Refinement + CAP-013 Fix
 **CAP-013 adapter dedup fix (REQ-129).** Multi-resource L1s (ecs-service,
 alb) with stack outputs + cross-module refs now dedup to ONE module block
 named by the composition child id, with expanded sub-ids rewritten via
 `id_remap`. `terraform validate` succeeds for the microservice stack.
 **CAP-017/018 probe fixes (REQ-130).** CAP-017's probe no longer requires
 `locals.tf` for modules that legitimately omit it. CAP-018's probe
 instantiates `LocalLambdaStub` with the required `outbox` arg.
 ## v1.13 Addendum — Presentation Polish + Config Schema Migration
 **Config.json schema migration (v1.13.1).** Regenerated
 `.ciagent/config.json` to the updated CIAgent v2 config structure (drop
 removed fields, migrate `gitea`→`release.gitea`, add
 `secrets`/`ship`/`backend`/`ideation`/`personas`/`logging`/`telemetry`
 sections).
 **Presentation polish (v1.13.0, v1.13.2).** Action headlines, story-arc
 restructure, larger fonts, 6 new mermaid diagrams, badge cleanup,
 platform-architecture diagram. Docs-only NFR patches.
 ## v1.14 Addendum — NFR Refinement (bug fixes, security, stubs, tests, docs)
 **Bug fixes (Wave 1, P1-P6).** Adapter dedup rejects unregistered modules
 with ValueError (P1). Static-assets composition wires cloudfront inputs
 (P2). L2 lifecycle scripts document remote-state design (P3). Regression
 gate adds `terraform fmt -check` syntax probe (P4). Adapter dedup-merge +
 remote-state-key unit tests (P5). ALB target group name_prefix derives
 from var.name (P6).
 **Security (Wave 2, P7-P12).** 6 swallowed-error sites narrowed to
 specific exceptions (P7). Account ID externalized to
 `ACDL_AWS_ACCOUNT_ID` env (P8). IAM policy scoped to `acdl-*` ARNs (P9).
 Contract ingestor validates contractId/environment/error (P10). Environment
 schema adds `additionalProperties: false` + format validation (P11).
 `.gitignore` credential-pattern catch-all (P12).
 **Stub/test/CI/hygiene (Wave 3, P13-P17).** Kyverno `--kube-version` flag
 removed (P13, G-103). Orphan artifacts + dead config cleaned (P14). 7
 untested scripts gain test coverage (P15). Gitea workflow parity
 documented + script `set` flags fixed (P16). Config.json persona +
 branching strategy + ollama-cloud aligned (P17).
 **Standards/docs/VPC (Wave 4, P18-P20).** STANDARDS.md reconciled (P18).
 Documentation synced: ARCHITECTURE.md addenda, stale `@v1.6-1.9` → `@v1.13`,
 GRILL G-005/G-008 resolved, COST.md window extended, D-083 deferral
 recorded (P19). Platform VPC CIDR parameterized + data-driven subnet
 count (P20).
 **D-083 deferral (explicit).** The audit ledger build-out (S3 Object Lock
 + JWS detached signatures + SQS DLQ + async worker + daily checkpoints)
 remains deferred (D-096, v1.14). The hash-chain + DynamoDB outbox is the
 v1.14 audit record. JWS per-event authenticity is not implemented; a
 forged event is only detectable by re-reading the whole chain. The
 deferral is documented here explicitly per the v1.14 grill (E-001).
 ---
-## v1.15 Addendum — Nova Rebrand (Major/breaking, 2026-07-30)
+## v1.15 Addendum — Nova Rebrand (current naming)
 **Milestone:** v1.15-Nova. A full rebrand from **ACDL** / "Agentic Cloud
-Delivery Platform" → **Nova** / "The New Dawn of DevSecOps — security
+Delivery Platform" → **Nova** / "The New Dawn of DevSecOps — security as
-as a seamless enabler of fast deployments." This is a **Major
+a seamless enabler of fast deployments." This is a **Major milestone**
-milestone** (breaking): consumer-facing path, env var prefixes, SSM
+(breaking): consumer-facing path, env var prefixes, SSM path, AWS tag
-path, AWS tag keys, and AWS resource names all change. Per the
+keys, and AWS resource names all change. v1.15 tags run on the **v1.15.x
-branch-strategy precedent (breaking/feature milestones tag on their
+minor line**: `v1.15.0` (P0) → `v1.15.4` (P5 final = release). (G-104
-OWN minor line), v1.15 tags run on the **v1.15.x minor line**:
+binding.)
 `v1.15.0` (P0) → `v1.15.4` (P5 final = release). (G-104 binding.)
-### Naming conventions (rebranded)
+### Naming conventions (rebranded — current)
 | Convention | Before (v1.0–v1.14) | After (v1.15+) | Phase |
 |------------|---------------------|-----------------|-------|
@@ -713,94 +348,15 @@ OWN minor line), v1.15 tags run on the **v1.15.x minor line**:
  brand name present (D-112: flat-branch convention preserved).
 - **Past Gitea release titles** — existing releases keep `ACDL vX.Y.Z`.
-### Migration ordering (binding)
+> The full migration ordering (P1–P5), capability gate, and rollback
-
+> runbook are preserved in `.ciagent/archive/ARCHITECTURE-v1.0-v1.24.md`
-1. **P1** docs/decks/prose — no runtime impact; ships consumer migration
+> §v1.15 Addendum.
   guide announcing the 5 breaking changes.
 2. **P2** code + env vars (dual-read) + consumer path — deployments don't
   break during the transition window (dual-read fallback).
 3. **P3** SSM path (copy → read → delete) + tag keys (parallel-tag →
   policy swap → remove old).
 4. **P4** AWS resource names — staged terraform migration (KMS alias,
   SNS/SG/Lambda recreate, DynamoDB scan+copy, ECR re-push, IAM
   re-bootstrap, state bucket `-migrate-state`, ALB recreate). Maintenance
   window + rollback runbook (`docs/NOVA_AWS_MIGRATION.md`).
 5. **P5** final review + audit + remove dual-read fallback + milestone ship.
 ### Capability gate (binding)
 The regression gate (CAP-001..CAP-016, `scripts/run_regression.sh`) must
 stay **16/16 Verified** throughout the rebrand. P2/P3/P4 update test
 fixtures that reference `ACDL`/`acdl` so the gate stays green. No
 capability is added, removed, or reclassified in v1.15 — the rebrand is
 nomenclature + identifiers, not behavior.
 ---
-## v1.16 Addendum — Nova Simplification (NFR, 2026-07-30)
+## v1.17 Addendum — Strategic Direction, Leadership Metrics & Unified Story (current telemetry layer)
-The v1.16 NFR milestone added 6 new code components + 1 new Terraform
+The v1.17 milestone added a telemetry/observability layer, a Decision
 module + 1 new schema, all documented here for the architecture record.
 ### New components
 | Component | Path | Purpose |
 |-----------|------|---------|
 | Onboarding request handler | `core/onboarding.py` | `generate_env_file(request, template_env)` — produces a `<env>.json` from a consumer onboarding request (P19, REQ-183). CLI entry point for self-service env-file generation. |
 | Decommission transform | `core/decommission_transform.py` | `decommission_transform(stack)` — zero counts + disable deletion protection (REQ-92). Extracted from contract_resolver (P12, REQ-176). |
 | Contract resolver CLI | `core/contract_resolver_cli.py` | `main()` CLI entry point — resolves a contract YAML to a Target Stack JSON. Extracted from contract_resolver (P12, REQ-176). |
 | Regression verify CLI | `core/regression_verify_cli.py` | `main()` CLI entry point — runs the regression gate + writes the report. Extracted from regression_verify (P13, REQ-177). |
 | Workflow sync generator | `scripts/sync_workflows.py` | `--check`/`--write` — generates the 3 byte-identical Gitea+GitHub workflow pairs from `workflows-src/` (P8, REQ-172). |
 | Onboarding Terraform | `terraform/onboarding/` | `aws_iam_role.consumer_deploy` + `aws_iam_role_policy.consumer_invoke` (ABAC `nova:owner` tag). Offline-proven only (P20, REQ-184, D-114). |
 ### Modified components
 | Component | Change | Phase |
 |-----------|--------|-------|
 | `core/contract_resolver.py` | `_load_env` delegates to `environment_check.load()` (dedup); `is_l2` uses registry `kind` field; `_load_schema` caches schemas; `decommission_transform` + CLI re-export shim (P12). | P7, P12, P14 |
 | `core/regression_verify.py` | Dedup helpers (`_check_resolver`, `_check_live_terraform_plan`, `_assert_contracts_resolve`); CAP-013..016 `Skipped` on post-teardown (G-111); `passed` accepts Skipped; CLI re-export shim (P13). | P5, P9, P13 |
 | `core/lambda/contract_ingestor.py` | Fail closed on missing IAM identity (P10); env enum from `core/environments/` (P10); payload size cap + schema validation (P11); `onboard_consumer` action (P18); `[NOVA-ALERT]` rebrand (P2). | P2, P10, P11, P18 |
 | `core/output_publisher.py` | `SAFE_OUTPUT_NAMES` schema-driven from `interface.json`; narrowed excepts; `urllib.error` import (P4, P14). | P4, P14 |
 | `core/environment_check.py` | Onboarding message rebranded Nova + self-service request path (P2, P19). | P2, P19 |
 | `core/local_emulators.py` | `LocalLambdaStub` sets `NOVA_LAMBDA_LOCAL_BYPASS`; stale dual-read comments + `acdl_*` prefixes removed (P3, P10). | P3, P10 |
 | `scripts/run_platform.sh` | `--help` flag; `run_hitl_gate()` fn; `NOVA_CONTRACT_ID`/`NOVA_WORK_DIR` config; decommission + uptime blocks extracted to sourced helpers (P6, P9, P15). | P6, P9, P15 |
 | `adapters/terraform/adapter.py` | State bucket `nova-tfstate-*` (P1); module docstring Nova (P2). | P1, P2 |
 | `adapters/kyverno/policies/require-resource-labels.yml` | `nova:*` labels (not `acdl:*`) (P1). | P1 |
 | `modules/registry.json` | `kind` field (`l1`/`l2`) on all 14 entries (P7). | P7 |
 ### New schema
 - `schemas/onboarding.schema.json` — the self-service onboarding request
  (consumerRepo, requestedEnvironment, ownerId, billingTag). P18, REQ-182.
 ### Onboarding request-path architecture (D-113)
 The no-humans onboarding flow is a 3-step request path (real AWS
 provisioning deferred):
 ```
 Consumer → POST Lambda (onboard_consumer) → pending CMDB row (P18)
         → core/onboarding.py → <env>.json binding file (P19)
         → terraform/onboarding/ → cross-account role + ABAC tag (P20, offline)
 ```
 The Lambda Function URL (IAM auth) + `consumer_invoke_policy.json` (ABAC
 `nova:owner`) are the transport; the request is accepted + a binding
 generated + the role Terraform proven offline. No AWS resources are
 created by the request path (D-113/D-114).
 ### Regression gate (G-111 binding)
 The regression gate (D-091) now treats `Skipped` as acceptable for the
 post-v1.11-teardown steady state (D-096): CAP-013..016 (live-AWS tier)
 return `Skipped` when the resources are absent (`NoSuchBucket`/
 `ResourceNotFoundException`). `RegressionReport.passed` is
 `all(r.status in ("Verified", "Skipped"))`. The gate passes at 18
 Verified + 4 Skipped (0 Decayed/Broken).
 ## v1.17 Addendum — Strategic Direction, Leadership Metrics & Unified Story (2026-08-04)
 The v1.17 milestone adds a telemetry/observability layer, a Decision
 Ledger, a metrics export pipeline, a unified narrative deck, and a
 durable strategic-direction artifact. This addendum documents the
 architecture; the full research findings are in RESEARCH.md §v1.17.
@@ -840,26 +396,26 @@ architecture; the full research findings are in RESEARCH.md §v1.17.
 │  Nova platform components (existing)                                │
 │  run_platform.sh · confidence_signal · checkov_adapter ·            │
 │  hitl_gates · regression_verify · outbox_writer · contract_ingestor │
-└──────────────────────┬──────────────────────────────────────────────┘
+└────────────────────┬──────────────────────────────────────────────┘
-                       │ CloudEvents 1.0 envelope (new emitters, P1)
+                     │ CloudEvents 1.0 envelope (new emitters, P1)
-                       ▼
+                     ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │  metrics/events.jsonl  (append-only CloudEvents log)                │
 │  metrics/runs/<run_id>.json  (per-run manifests)                    │
 │  metrics/decision_ledger.db  (SQLite hash-chain, D-121)             │
 │  metrics/test-results.xml  (junit, P1)                              │
-└──────────────────────┬──────────────────────────────────────────────┘
+└────────────────────┬──────────────────────────────────────────────┘
-                       │ collector reads (P2)
+                     │ collector reads (P2)
-                       ▼
+                     ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │  metrics/nova_metrics.db  (SQLite cold store, D-126)                │
 │  fact_run · fact_capability · fact_policy_check · fact_confidence  │
 │  fact_test · fact_decision · fact_cost_estimate                     │
 │  dim_capability · dim_milestone                                     │
 │  + 8 empty placeholder views (deferred metrics)                    │
-└──────────────────────┬──────────────────────────────────────────────┘
+└────────────────────┬──────────────────────────────────────────────┘
-                       │ powerbi_export (P3)
+                     │ powerbi_export (P3)
-                       ▼
+                     ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │  metrics/powerbi/  (CSV/JSON views, folder connector, D-129)        │
 │  → PowerBI dashboards (external)                                    │
@@ -868,19 +424,20 @@ architecture; the full research findings are in RESEARCH.md §v1.17.
 **Hot path: deferred (D-126).** No live ops dashboard; SQLite is
 cold-only (batch/historical). The hot path activates when live AWS is
-re-provisioned (D-096 lift).
+re-provisioned (D-096 lift — the v1.26 milestone lifts this for the pilot
 estate).
 ### NORTH_STAR integration point (REQ-186)
 `.ciagent/NORTH_STAR.md` is read by CIAgent in context-loading for all
-future milestones. The integration mechanism (to be finalized in P4):
+future milestones. The integration mechanism: a reference from
-a reference from `PROJECT.md` + `ARCHITECTURE.md` (this section) + a
+`PROJECT.md` + `ARCHITECTURE.md` (this section) + a config entry in
-config entry in `config.json` (`strategic_direction_file:
+`config.json` (`strategic_direction_file: ".ciagent/NORTH_STAR.md"`)
-".ciagent/NORTH_STAR.md"`) that the run workflow reads at SPECIFY. This
+that the run workflow reads at SPECIFY. This ensures the strategic
-ensures the strategic direction survives across milestones without
+direction survives across milestones without being overwritten by status
-being overwritten by status updates.
+updates.
-### §12.7 — Policy Engine Registry (v1.25, REQ-291)
+### §12.7 — Policy Engine Registry (v1.25, REQ-291 — current)
 The policy-engine abstraction is first-class: a swappable `PolicyEngine`
 protocol so the engine may change without touching the confidence
@@ -943,3 +500,80 @@ functions without the binary (the "platform functions without AI /
 deterministic scripts" tenet holds — kyverno-json is deterministic, not
 AI; the `is_configured()` guard ensures the platform runs even when the
 binary is not installed).
 ### §12.8 — Pilot Estate (v1.26, live)
 The first real consumer estate is **`nova-blockchain-exchange`** — a
 blockchain stock exchange on a homegrown Proof-of-Authority chain,
 equities only, dev only (D-020/D-200/D-201). The live apply landed on
 2026-08-19 against AWS account `581513795199`. This is the estate that
 activated the Post-Pilot metric denominators (see `docs/METRICS.md`).
 **The live apply (run id `blkex-pilot-apply-v0.2`):**
 - Target: account `581513795199`, environment `dev`, autonomous (no
  HITL — dev is the only autonomous environment, confidence ≥ 0.50).
 - The microservice L2 composition (ECS Fargate running nginx) + the
  `dynamodb` L1 (the `nova-blkex-ledger-dev` table) + the `s3` L1 (the
  `nova-blkex-blocks-dev-581513795199-us-east-1` bucket).
 - The platform VPC prerequisite (`vpc-0d7c8867e6cc080f1` + 6 subnets +
  the ECS SG) is read via `terraform_remote_state` — the L2 composition
  does not own the network boundary (the "restricted from
  thin-composition" rule from §Layer 2).
 - Confidence signal: score **0.800**, band **pass**; `human_override`
  false; `escalation_reason` absent (clean apply).
 **The Gitea adapter (SPEC §10 Q1):** Gitea Actions does not support
 cross-repo `uses:`, so the consumer's `deploy.yml` is an **inline
 adapter** — `actions/checkout@v4` the consumer, `actions/checkout@v4`
 `acdl/acdl` @ `ref: v1.25` into `platform/`, then
 `bash platform/scripts/run_platform.sh ...`. The platform's own
 `.github/workflows/deploy.yml` stays as the GitHub Actions reference
 impl (the reusable `workflow_call` workflow). See `adapters/README.md`
 §Consumers for the adapter note.
 **The Decision Ledger evidence stream** (the apply produces these
 events in order):
 ```
 nova.confidence.computed  (score 0.800, band pass)
        │
        ▼
 nova.ai.decision.made     (decision_id blkex-pilot-apply-v0.2,
                           chosen_action pass, human_override false)
        │
        ▼
 nova.attestation.recorded (dev = no HITL gate; the record exists,
                           the gate is a no-op in the autonomous env)
        │
        ▼
 nova.run.completed        (apply succeeded)
        │
        ▼
 nova.outcome.backfilled   (outcome pending → succeeded, REQ-317;
                           backfilled_at 2026-08-19T03:05:04Z)
 ```
 The SQLite hash-chain is valid (0 breaks). S3 Object Lock / JWS
 (D-083) stays deferred — the SQLite Decision Ledger is the pilot's
 audit record (D-204).
 **Live outputs (account 581513795199):**
 - ALB DNS: `app-254671247.us-east-1.elb.amazonaws.com`
 - ECS service: `arn:aws:ecs:us-east-1:581513795199:service/nova-cluster/nova-microservice`
 - DynamoDB table: `nova-blkex-ledger-dev` (PK `block_index`, PAY_PER_REQUEST)
 - S3 bucket: `nova-blkex-blocks-dev-581513795199-us-east-1` (versioning + SSE)
 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`.
 ### §12.9 — Secret Rotation (v1.26 P3 W7, SPEC §5.9 — current)
 The platform-managed scheduled workflow `workflows-src/rotate-aws-key.yml`
 rotates the `NOVA_AWS_*` static key daily (cron `0 0 * * *`) and on
 `workflow_dispatch`. v0.2 scope: the mechanism exists (SPEC §5.9 —
 exists-not-ran); the v0.2 deploy uses the currently-active key. The
 rotation is idempotent — `scripts/rotate_spike_key.sh` deactivates the old
 key only after the new one propagates to the consumer's Actions secret
 store, verified by a post-PUT GET; on upload/verify failure the old key is
 left Active and the run exits non-zero. The synced workflow file is
 forge-agnostic (REQ-230): forge base URL / owner / consumer repo come from
 repository secrets (`NOVA_FORGE_*`, `NOVA_CONSUMER_REPO`), not literals.
@@ -1,22 +1,49 @@
 {
-  "phase": 3,
+  "phase": 4,
  "stage": "complete",
-  "milestone": "v1.25",
+  "milestone": "v1.26",
  "phase_role": "execution",
  "attempts": 0,
-  "updated_at": "2026-08-12T17:30:00Z",
+  "updated_at": "2026-08-19T03:30:00Z",
  "project": "acdl",
-  "milestone_complete": false,
+  "projects": [
-  "tag_line": "v1.24.x",
+    "acdl",
-  "tag": "v1.24.3",
+    "nova-blockchain-exchange"
-  "next_tag": "v1.24.4",
+  ],
-  "release": {
+  "active_milestone": "v1.26",
-    "forge": "gitea",
+  "milestone_branch": "milestone/v1.26-pilot-activation",
-    "releases_created": true,
+  "phase_branch": "phase/03-pilot-metrics-and-policies",
-    "release_ids": {"v1.24.0": 640, "v1.24.1": 641, "v1.24.2": 642, "v1.24.3": 643},
+  "tag_line": "v1.25.x",
-    "phase_release_id": 643
+  "previous_phase": {
    "phase": 3,
    "tag": "v1.25.3",
    "status": "complete"
  },
-  "requirements": ["REQ-291", "REQ-292", "REQ-293", "REQ-294", "REQ-295", "REQ-296", "REQ-297", "REQ-298", "REQ-299", "REQ-300", "REQ-301", "REQ-302", "REQ-303", "REQ-308", "REQ-309"],
+  "current_phase": {
-  "tests": {"total": 88, "passed": 88, "skipped": 11, "failed": 0},
+    "phase": 4,
-  "notes": "v1.25 P3 (plan-JSON+meta+pipeline) complete. Tag v1.24.3 (gitea release id 643). 4 requirements (REQ-300..303). 5 plan-JSON+meta policies. run_platform.sh Step 5b wired. Phase 03 branch deleted. Next: P4 regression-gate policies + docs."
+    "tag": "v1.25.4",
    "status": "complete"
  },
  "requirements": [
    "REQ-316",
    "REQ-321"
  ],
  "waves": {
    "W0": "Gitea adapter \u2014 inline checkout-then-call in consumer deploy.yml (SPEC \u00a710 Q1 resolved, consumer repo)",
    "W0.5": "kyverno-json substrate fix (v1.25 skip-masked bug) + P2 drift (dynamodb examples, sync_workflows, deck path)",
    "W2": "outcome backfill (REQ-317) + escalation_reason (REQ-318)",
    "W3": "env-JSON state_backend wiring (REQ-319) \u2014 dev bound to 581513795199",
    "W4": "pilot-readiness (REQ-320) + settlement-finality (REQ-315) kyverno-json policies \u2014 run against real kj",
    "W5": "CAP-025 live-pilot-apply regression check (REQ-316)",
    "W6": "deploy.yml drift fixes \u2014 AWS_DEFAULT_REGION from secret, ref v1.25, no raw NOVA_AWS_* in shell env (SPEC \u00a75.1/\u00a75.2)",
    "W7": "secret rotation scheduled workflow (SPEC \u00a75.9) + forge-agnostic token name (REQ-230)"
  },
  "pre_run": {
    "flaky_test_fixed": "8c68d68 test(metrics): fix attestation-event test freshness time-bomb",
    "acdl_to_nova_migration": "f844fea chore(bootstrap): migrate ACDL_* env vars to NOVA_*",
    "aws_bootstrap": "S3 nova-tfstate-581513795199-us-east-1 + DynamoDB nova-outbox created (idempotent, account 581513795199)",
    "consumer_repo_created": "continuous-intelligence/nova-blockchain-exchange (Gitea, private, init, cloned to /root/nova-blockchain-exchange)",
    "kj_installed": "kyverno-json v0.0.3 via go install (binary kyverno-json symlinked as kj) \u2014 policy tests run, not skipped"
  },
  "notes": "v1.26 P4 complete. W1 live terraform apply against 581513795199 succeeded (ALB + ECS + DynamoDB + S3). Decision Ledger: ai.decision.made + nova.outcome.backfilled (outcome pending->succeeded, REQ-317). 2 module-completeness gaps fixed (ecs-service execution_role_arn, ALB SG). W2 docs (REQ-321). 844 platform + 90 consumer tests green. Ready for P5 final review + milestone ship."
 }
@@ -1,164 +1,226 @@
-# CLARIFY — v1.25 kyverno-json Unified Policy Engine
+# CLARIFY — v1.26 Live Pilot Estate Activation
-> **Autonomy:** full. Ambiguities are auto-resolved with assumption logging
+> **Autonomy:** full. Auto-resolution with assumption logging per
-> per `config.json autonomy.level: "full"` and
+> `config.autonomy.level: "full"`. No human escalation unless
-> `autonomy.decision_confidence_threshold: 0.6`. No human escalation.
+> confidence < 0.60 (threshold `config.autonomy.decision_confidence_threshold`).
 > 10 ambiguities identified; all resolved (confidence ≥ 0.60).
-## Ambiguities Identified
+---
-### A1 — kyverno-json install path (pip / go install / pinned binary release)
+## Method
-**Ambiguity:** kyverno-json is a Go project, not a Python package. Three
+The clarify stage identifies ambiguities in the v1.26 specification
-install paths exist: (a) `pip install` — not possible (no PyPI package);
+(PROJECT.md, REQUIREMENTS.md, ROADMAP.md) and resolves them at full
-(b) `go install github.com/kyverno/kyverno-json/cmd/kj@latest` — requires
+autonomy. Each ambiguity gets a decision ID (D-200+; continuing from
-Go toolchain in the CI image; (c) download a pinned binary release from
+the v1.26 SPECIFY decisions D-200..D-205), a resolution, a confidence
-GitHub releases — no Go toolchain needed, but release artifacts are
+score, and a rationale. Resolutions update PROJECT.md + REQUIREMENTS.md
-platform-specific and must be checksummed.
+ ROADMAP.md as needed.
-**Resolution (auto, confidence 0.85):** `go install` (option b). A
+---
 `scripts/install-kyverno-json.sh` helper runs
 `go install github.com/kyverno/kyverno-json/cmd/kj@latest` and prints
 `kj version`. The CI image (`.github/workflows/ci.yml` +
 `.gitea/workflows/ci.yml`) installs Go + kj when
 `config.json.policy.engine == "kyverno-json"`; the install is cached via
 the existing Go module cache. Rationale: `go install` is the upstream-
 blessed path, tracks the latest stable release, avoids per-platform
 binary management, and the project already accepts Go-based tooling
 (checkov pulls Go-built transitive deps via pip). When `which kj` is
 absent, `KyvernoJsonEngine.is_configured()` returns false → `SKIPPED`
 PCR (mirrors the Wiz adapter pattern) — the platform functions without
 the binary. Captured in REQ-293, REQ-294. Decision ID: D-115.
-### A2 — `engine` enum value: new `"kyverno-json"` vs reuse `"kyverno"`
+## Ambiguities + Resolutions
-**Ambiguity:** `schemas/policy_check_result.schema.json` already lists
+### Q1 — Does the consumer repo's `.ciagent/` live in the platform repo or the consumer repo?
 `engine: ["checkov", "kyverno", "opa", "wiz"]`. kyverno-json is a
 distinct runtime from the K8s Kyverno admission controller, but both
 are "Kyverno." Two options: (a) add a new `"kyverno-json"` enum value
 — requires schema change + checkov/wiz adapter test regression check;
 (b) reuse `"kyverno"` and distinguish by `ruleId` prefix.
-**Resolution (auto, confidence 0.80):** Reuse `"kyverno"` (option b).
+**Ambiguity:** The user said "ciagent should track it as a separate
-Adding `"kyverno-json"` would force a schema change + a test sweep for
+project under this same path." Does "this same path" mean the platform
-no semantic gain — the `engine` field records the policy engine family,
+repo's `.ciagent/` directory (multi-project mode per `run.md` Step 0),
-not the specific binary. kyverno-json PCR records carry `engine:
+or a separate `.ciagent/` inside the consumer repo?
 "kyverno"` and `ruleId` prefixed `KJ_<policy_name>` (e.g.
 `KJ_REQUIRE_TAGGING_STANDARD`), while the K8s adapter uses `KYVERNO_`
 prefixes (e.g. `KYVERNO_INACTIVE_TF_STACK`). The two are distinguishable
 in audit/telemetry by `ruleId` prefix and `evidence` payload shape (the
 K8s adapter's evidence has `namespace`/`kind`; kyverno-json's has
 `assertion`/`jmespath`). No schema change. Captured in REQ-293.
 Decision ID: D-116.
-### A3 — Do checkov/wiz adapters change their signatures to feed kyverno-json?
+**Resolution:** The platform repo's `.ciagent/` directory. Multi-project
 mode: `.ciagent/config.json` `projects[]` includes both `acdl` +
 `nova-blockchain-exchange`; the consumer's project files
 (PROJECT.md, REQUIREMENTS.md, ROADMAP.md) live in
 `.ciagent/nova-blockchain-exchange/`. The consumer *git repo* owns the
 app code + `contract.yaml` + deploy workflow invocation; the platform
 repo owns the CIAgent planning artifacts for both projects. This
 matches `run.md` Step 0 multi-project mode.
-**Ambiguity:** The unified-orchestrator model places kyverno-json "on
+**Confidence:** 0.95. **Decision:** D-206.
 top of" checkov/wiz. Two interpretations: (a) checkov/wiz now emit a
 "raw findings" intermediate (not PCR) that kyverno-json meta-policies
 consume — requires changing `adapt() -> list[PolicyCheckResult]` to
 `adapt() -> list[RawFinding]`; (b) checkov/wiz keep emitting PCRs as
 today, and the meta-policies in `adapters/kyverno-json/policies/meta/`
 consume the **merged** PCR list as their payload.
-**Resolution (auto, confidence 0.90):** Option (b). The existing
+### Q2 — Is the bootstrap `NOVA_AWS_*` key the root key or the spike-runner key?
 `adapt() -> list[PolicyCheckResult]` signatures are unchanged. The
 meta-policies consume the merged PCR list (checkov + wiz + kyverno-json
 plan-JSON policies) as their input payload. This preserves the
 `PolicyCheckResult` schema as the single inter-adapter contract
 (ARCHITECTURE.md §12.6), avoids a new "RawFinding" type, and means
 the existing checkov/wiz adapter tests pass unchanged. The meta-policy
 `block-on-any-critical.json` iterates the merged list; the
 `tagging-rules-agree.json` meta-policy cross-checks the Checkov
 `NOVA_TAG_NAMING` result against the kyverno-json
 `KJ_REQUIRE_TAGGING_STANDARD` result by `resourceRef`. Captured in
 REQ-303, D-117. Decision ID: D-117.
-### A4 — `NOVA_TAG_NAMING` Checkov rule: rewrite as kyverno-json policy, keep, or both?
+**Ambiguity:** The bootstrap scripts (post-migration) prefer
 `NOVA_BOOTSTRAP_AWS_*`, falling back to `NOVA_AWS_*`. The pre-run
 (A3) succeeded with `NOVA_AWS_*`, creating the S3 bucket + DynamoDB
 table — which requires root or root-equivalent IAM. Is `NOVA_AWS_*`
 the root key, or did the bootstrap succeed because the spike-runner
 policy happens to include S3/DynamoDB create?
-**Ambiguity:** The Checkov custom rule
+**Resolution:** `NOVA_AWS_*` has root-equivalent permissions (confirmed
-`adapters/terraform/policy/custom_rules/nova_tagging.py` enforces the
+empirically: the bootstrap created the S3 bucket + DynamoDB table
-Nova tagging standard over Terraform HCL (static scan + plan scan). The
+successfully). For the pilot, `NOVA_AWS_*` is the bootstrap key. A
-kyverno-json milestone adds `require-tagging-standard.json` over the
+future hardening milestone should split this into a dedicated
-resolved Stack IR. Three options: (a) rewrite — replace the Checkov
+`NOVA_BOOTSTRAP_AWS_*` root key + a least-privilege `NOVA_AWS_*` runner
-rule with the kyverno-json policy (loses Checkov's HCL-level coverage
+key (the spike-runner pattern). For v1.26, the single key suffices
-and the `--external-checks-dir` integration); (b) keep Checkov only —
+(pilot scope).
 don't add a kyverno-json policy (the Stack IR is already the input to
 terraform, so the Checkov rule catches it); (c) both — keep the
 Checkov rule as the source of truth for HCL-level scanning AND add the
 kyverno-json policy for IR-level coverage, with a meta-policy that
 asserts the two agree.
-**Resolution (auto, confidence 0.82):** Option (c) — both, with a
+**Confidence:** 0.90. **Decision:** D-207.
 cross-check meta-policy. The Checkov rule stays the source of truth
 for `terraform_plan` scanning (it reads HCL resource blocks directly);
 the kyverno-json policy covers the Stack IR dict (which is the input
 *before* terraform, so it catches IR-level violations that the
 terraform adapter might mask via defaults). The P3 meta-policy
 `tagging-rules-agree.json` asserts the two engines agree on every
 resource; divergence emits an `error` PCR (defense-in-depth against
 rule drift — if the two engines disagree, the operator must
 investigate before proceeding). This is the only case in v1.25 where
 two engines evaluate the same concern; it is intentional — the
 tagging standard is the highest-impact rule (v1.8 D-tagging-standard,
 v1.10 re-verification) and merits redundancy. Captured in REQ-297,
 REQ-303, REQ-299. Decision ID: D-118.
-### A5 — Critical-override: delegate to declarative meta-policy or keep hard-override?
+### Q3 — Which AWS account does the pilot use: `581513795199` (existing) or a dedicated pilot account?
-**Ambiguity:** `core/confidence_signal.py` lines 144-157 hardcode
+**Ambiguity:** The user said "assume 581513795199." But the env JSONs
-`PENALTY["critical"]: None` — a critical-severity `fail` PCR forces
+all show `account_id: "000000000000"` (placeholder). Does the pilot
-`score = 0, band = block` regardless of the weighted-sum inputs. The
+bind all env JSONs to `581513795199`, or only `dev` (with qa/prod/dr
-v1.25 meta-policy `block-on-any-critical.json` makes this declarative
+left placeholder until a real multi-account landing zone exists)?
 (asserts no PCR in the merged list has `severity: critical` +
 `result: fail`). Two options: (a) fully delegate — remove the
 hard-override, rely on the meta-policy to emit a critical `fail` PCR
 that the existing penalty logic then blocks; (b) keep both — the
 meta-policy is the declarative source of truth, the hard-override is
 defense-in-depth.
-**Resolution (auto, confidence 0.88):** Option (b) — keep both. The
+**Resolution:** Bind `dev` to `581513795199` for the pilot
-meta-policy is the *declarative* statement ("Nova blocks on any
+(D-203, established in SPECIFY). The `qa`/`prod`/`dr` env JSONs remain
-critical finding from any engine"); the hard-override is the
+placeholder `000000000000` this milestone — the pilot runs in `dev`
-*imperative* safety net that ensures a critical PCR can never slip
+(autonomous, no HITL gate). Multi-account landing zone (qa/prod/dr on
-through even if the meta-policy is misconfigured or the
+separate accounts) is a future milestone. REQ-319 (env-JSON wiring)
-`PolicyEngineRegistry` returns a `NullEngine`. This is
+updates `dev.json`'s `state_backend.bucket` to
-defense-in-depth, not redundancy-for-its-own-sake: the meta-policy
+`nova-tfstate-581513795199-us-east-1` + `account_id` to `581513795199`;
-runs *before* the confidence signal (it produces PCRs that flow in),
+qa/prod/dr get the `state_backend.bucket` update but keep placeholder
-the hard-override runs *inside* the confidence signal (it is the last
+`account_id` (the pilot-readiness policy REQ-320 blocks apply on
-gate). Removing the hard-override would make the platform's
+placeholder accounts — so qa/prod/dr apply is blocked by design until
-"critical = block" guarantee depend on a single declarative policy
+the accounts are bound).
 file — a regression in the provable-trust posture (Strategic
 Objective #2). Captured in REQ-303, PROJECT.md hard-constraints.
 Decision ID: D-119.
-### A6 — Does kyverno-json break the "platform functions without AI" tenet?
+**Confidence:** 0.92. **Decision:** D-208.
-**Ambiguity:** NORTH_STAR.md Strategic Objective #2: "the platform
+### Q4 — Does "all types of securities" mean all types in v1.26, or equities-only pilot with others deferred?
 functions without AI — 'AI decisions' are really automated decisions."
 kyverno-json is a deterministic policy engine (no ML), but it is a new
 runtime dependency. Does adding it violate the tenet?
-**Resolution (auto, confidence 0.95):** No — kyverno-json is
+**Ambiguity:** The user said "stock market built on homegrown blockchain
-deterministic, not AI. The tenet distinguishes "AI decisions" (LLM-
+offering all types of securities." This could mean equities + bonds +
-driven, non-reproducible) from "automated decisions" (rule-driven,
+derivatives + options all in v1.26, or equities-only pilot with others
-reproducible). kyverno-json is the latter — the same policy + payload
+deferred (the recommended scope from the plan).
-produces the same result on every run. It is *more* aligned with the
+
-tenet than the current imperative Python in `core/env_transition.py`
+**Resolution:** Equities-only pilot (D-200, established in SPECIFY).
-and `core/regression_verify.py`, because the policy is declarative
+Bonds/derivatives/options have very different settlement models (T+1
-(visible, auditable, version-controlled) rather than imperative (logic
+for equities; T+2 for bonds; derivatives vary; options exercise
-hidden in function bodies). The `is_configured()` guard ensures the
+models). A pilot should demonstrate the Nova platform's policy gates
-platform functions without the binary (graceful skip), so the tenet
+over a real estate — equities (T+1) is the simplest. "All types of
-holds even in environments where kyverno-json is not installed.
+securities" is the *product vision*; v1.26 is the *pilot* (equities
-Captured in PROJECT.md hard-constraints + RESEARCH.md G-Q1.
+first). The roadmap documents the deferral.
-Decision ID: D-120.
+
 **Confidence:** 0.85. **Decision:** D-200 (reaffirmed).
 ### Q5 — Is the homegrown blockchain a real consensus protocol or a minimal PoA ledger?
 **Ambiguity:** "Homegrown blockchain" could mean a full consensus
 protocol (multi-validator BFT) or a minimal PoA ledger (single
 validator, append-only).
 **Resolution:** Minimal PoA ledger (D-201, established in SPECIFY).
 Single validator (config-driven), append-only blocks, SHA-256 hash
 chain, deterministic block production. Settlement finality = block
 commit. Multi-validator BFT is a future milestone. The pilot's purpose
 is to exercise the Nova platform's deploy/policy/attestation gates over
 a real consumer — the chain needs to be real enough to record
 transactions, not to solve Byzantine consensus.
 **Confidence:** 0.88. **Decision:** D-201 (reaffirmed).
 ### Q6 — Does the pilot's `terraform apply` actually run, or is it `--plan-only`?
 **Ambiguity:** The platform's `run_platform.sh` defaults to
 plan-only (no apply). The `deploy.yml` workflow's `mode` input can be
 `full` (apply) or `plan-only`. Does the pilot actually `terraform apply`
 (creating real AWS resources for the blockchain exchange), or does it
 stop at plan?
 **Resolution:** The pilot runs `mode: full` (apply) for `dev` only.
 The apply creates real AWS resources (ECS for the matching engine,
 DynamoDB for the ledger, S3 for block storage) in account
 `581513795199`. `qa`/`prod`/`dr` are blocked by the pilot-readiness
 policy (REQ-320) until their accounts are bound (D-208). The apply is
 autonomous for `dev` (no HITL gate; confidence threshold 0.50). The
 `ai.decision.made` + `attestation.recorded` events land in the Decision
 Ledger — but `dev` attestation is autonomous (no human approver), so
 only `ai.decision.made` fires for `dev`.
 **Confidence:** 0.90. **Decision:** D-209.
 ### Q7 — What AWS resources does the blockchain exchange contract declare?
 **Ambiguity:** The `contract.yaml` declares the exchange's
 infrastructure. What specific AWS resources? The platform's adapter
 maps contract infrastructure blocks to Terraform. What stack types
 does the blockchain exchange use?
 **Resolution:** The pilot contract declares 3 infrastructure blocks:
 (1) `ecs` (Fargate service for the matching engine + settlement
 service — the platform's existing `microservice` module pattern), (2)
 `dynamodb` (the ledger table — single-table, PK `block_index`), (3)
 `s3` (block storage — one object per block, key `blocks/{index}.json`).
 The adapter's `TYPE_MAP` already covers `aws_ecs_service`,
 `aws_dynamodb_table`, `aws_s3_bucket` (existing L1 primitives). No new
 adapter stack types needed for the pilot. The contract's
 `infrastructure` block references these by module name (`microservice`
 for ECS, `dynamodb` for the table, `s3` for the bucket).
 **Confidence:** 0.82. **Decision:** D-210.
 ### Q8 — Does the outcome-backfill emitter (REQ-317) change the PCR schema?
 **Ambiguity:** REQ-317 wires `apply.completed`/`apply.failed` →
 `fact_decision.outcome`. Does this touch the `PolicyCheckResult` schema
 (PCR) — the v1.25 moat that must not change?
 **Resolution:** No. The outcome backfill touches the *metrics cold
 store* (`fact_decision` table in `metrics/nova_metrics.db`), not the
 PCR schema. The PCR schema (`schemas/policy_check_result.schema.json`)
 is unchanged. The backfill reads run-manifest events (not PCRs) and
 updates the decision's outcome column. This respects the v1.25 hard
 constraint: "DO NOT change `schemas/policy_check_result.schema.json`."
 **Confidence:** 0.95. **Decision:** D-211.
 ### Q9 — Does the consumer repo need its own test suite + CI, or does the platform's CI cover it?
 **Ambiguity:** The consumer repo (`nova-blockchain-exchange`) has app
 code (blockchain, engine, settlement). Does it run its own tests in
 its own CI, or does the platform's `platform-test.yml` cover it?
 **Resolution:** The consumer repo runs its own tests in its own CI
 (`nova-blockchain-exchange/.github/workflows/ci.yml` — lint + pytest on
 the blockchain/engine/settlement code). The platform's
 `platform-test.yml` covers the *platform* repo only (it validates
 contracts against the schema, runs adapter tests, etc.). The consumer
 repo's `deploy.yml` invocation triggers the platform's deploy workflow
 (which runs `run_platform.sh`); the platform's policy + attestation
 gates apply over the consumer's apply. The consumer's unit tests
 (chain integrity, order matching, settlement) are the consumer's
 responsibility. REQ-310..312 include consumer-side tests
 (`test_block.py`, `test_order_book.py`, `test_settlement.py`).
 **Confidence:** 0.88. **Decision:** D-212.
 ### Q10 — Is the milestone a feature milestone (tags on v1.25.x) or a major milestone (breaking schema changes)?
 **Ambiguity:** v1.26 introduces a 2nd project (multi-project mode) +
 new requirements. Does this break any schema (→ major milestone, tags
 on v1.26.x), or is it a feature milestone (tags on v1.25.x)?
 **Resolution:** Feature milestone. No schema breaks: the PCR schema is
 unchanged (D-211); the contract schema is unchanged (the consumer
 contract validates against the existing
 `schemas/contract.schema.json`); the env JSON gains a real
 `account_id` (data, not schema). Multi-project mode is a config
 change (not a schema break). Tags run on the **v1.25.x** patch line:
 `v1.25.0` (P0) → `v1.25.5` (P5 = milestone release). Per `run.md`
 versioning logic: "Feature milestone (at least one feat phase):
 progressive patches per phase. The final phase's patch IS the milestone
 release. No separate minor tag."
 **Confidence:** 0.92. **Decision:** D-213.
 ---
 ## Summary
-6 ambiguities identified; 6 auto-resolved at full autonomy (no human
+10 ambiguities identified; all auto-resolved at full autonomy
-escalation). All resolutions are binding and recorded as D-115..D-120.
+(confidence ≥ 0.60). 8 new decisions (D-206..D-213) + 3 reaffirmed
-The resolutions are captured in PROJECT.md hard-constraints,
+from SPECIFY (D-200, D-201, D-203). 0 escalations (all ≥ 0.60). The
-REQUIREMENTS.md v1.25 sections, and will be referenced in RESEARCH.md +
+resolutions are recorded in this file + reflected in PROJECT.md /
-PLAN.md. No PROJECT.md or REQUIREMENTS.md structural changes beyond the
+REQUIREMENTS.md / ROADMAP.md updates.
-v1.25 sections added in SPECIFY — the resolutions are already embedded
+
-in the requirement text (REQ-293, REQ-297, REQ-303, etc.) via the
+**Key decisions:**
-"Decision" annotations.
+- D-206: `.ciagent/` for both projects in the platform repo (multi-project mode).
 - D-207: `NOVA_AWS_*` has root-equivalent perms; single key for pilot.
 - D-208: `dev` bound to `581513795199`; qa/prod/dr stay placeholder (pilot-readiness policy blocks apply on placeholder).
 - D-209: Pilot runs `mode: full` (apply) for `dev` only; autonomous (no HITL gate).
 - D-210: Contract declares ecs + dynamodb + s3 (existing adapter stack types; no new TYPE_MAP entries).
 - D-211: Outcome backfill touches metrics cold store, NOT the PCR schema (v1.25 moat preserved).
 - D-212: Consumer repo has its own CI + unit tests; platform CI covers platform only.
 - D-213: Feature milestone; tags on v1.25.x (no schema breaks).
@@ -1,14 +1,15 @@
-# GRILL — v1.25 kyverno-json Unified Policy Engine
+# GRILL — v1.26 Live Pilot Estate Activation
-> Adversarial review of the v1.25 SPECIFY + CLARIFY + RESEARCH + IDEATE +
+> Adversarial review of the v1.26 SPECIFY + CLARIFY + RESEARCH + IDEATE +
 > PLAN. The grill red-teams the proposal across feasibility, scope,
-> budget, and the swap-boundary claim. Each challenge gets a binding
+> budget, and the domain claims (homegrown blockchain, pilot estate,
-> verdict (PROCEED / REVISE / ESCALATE). Autonomy: full — escalations
+> metric grounding). Each challenge gets a binding verdict
-> auto-resolve with assumption logging unless confidence < 0.60.
+> (PROCEED / REVISE / ESCALATE). Autonomy: full — escalations auto-
 > resolve with assumption logging unless confidence < 0.60.
-## Verdict: PROCEED (0.86) — 0 escalations, 2 revisions
+## Verdict: PROCEED (0.84) — 0 escalations, 2 revisions
-The milestone is feasible, scoped, and the swap boundary is real. Two
+The milestone is feasible, scoped, and the domain claims hold. Two
 plan revisions are binding (G-Q4, G-Q8) and are already captured in
 PLAN.md. No work is blocked.
@@ -16,201 +17,209 @@ PLAN.md. No work is blocked.
 ## Challenges
-### G-Q1 — Does kyverno-json violate "platform functions without AI"?
+### G-Q1 — Is a homegrown PoA blockchain viable for a pilot, or is it reckless?
-**Challenge:** NORTH_STAR.md Strategic Objective #2 says "the platform
+**Challenge:** Authoring a blockchain (even a minimal PoA ledger) is a
-functions without AI." kyverno-json is a new runtime dependency. Is
+non-trivial domain. A homegrown chain could have correctness bugs (hash
-this a real violation, or is the tenet about LLMs (not deterministic
+chain breaks, non-deterministic blocks, settlement-finality race
-engines)?
+conditions). Why not use a proven chain (Ethereum L2, Solana, Hyperledger
 Fabric)?
-**Verdict:** PROCEED (confidence 0.95). kyverno-json is deterministic
+**Verdict:** PROCEED (confidence 0.88). The pilot's purpose is to
-(same policy + payload → same result, every run). The tenet
+exercise the Nova platform's deploy/policy/attestation gates over a
-distinguishes AI (non-reproducible) from automation (reproducible).
+real consumer estate — not to build a production blockchain. A
-kyverno-json is the latter — and is *more* aligned than the imperative
+homegrown PoA ledger is the minimal viable chain: append-only blocks,
-Python it replaces (`core/env_transition.py`, `core/regression_verify.py`)
+single validator, SHA-256 hash chain, deterministic block production.
-because the policy is declarative (visible, auditable). The
+This is ~200 lines of Python (block + ledger + validator). The chain
-`is_configured()` guard ensures the platform runs without the binary.
+needs to be real enough to record transactions + produce a settlement-
-Already resolved as D-120 in CLARIFY. No revision needed.
+finality signal for the kyverno-json policy (REQ-315) — not to solve
 Byzantine consensus. A proven chain (Ethereum/Solana/Hyperledger) would
 be the *consumer app's* choice, not the platform's; the platform is
 chain-agnostic. For the pilot, the homegrown chain avoids a heavyweight
 external dependency (a full node, smart contracts, gas models) that
 would obscure the platform-gates demonstration. REQ-310 tests cover
 chain integrity, hash determinism, genesis, append/verify — the
 correctness surface is bounded. Multi-validator BFT is a future
 milestone (D-201). No revision needed.
-### G-Q2 — Is the PolicyEngine protocol over-engineered for a 2-engine future?
+### G-Q2 — Does "all types of securities" scope-explode the milestone?
-**Challenge:** The user asked for a swappable adapter ("we might one
+**Challenge:** The user said "offering all types of securities." Equities
-day decide to replace it with something else like OPA"). A Python
+(D-200, pilot scope) is one type. Bonds (T+2), derivatives (varying),
-Protocol + registry is ~40 lines. But Nova has 1 engine today. Is this
+options (exercise models) have very different settlement models. Does
-premature abstraction?
+the equities-only deferral betray the user's intent?
-**Verdict:** PROCEED (confidence 0.85). The user *explicitly* asked for
+**Verdict:** PROCEED (confidence 0.85). The user *chose* equities-only
-the swap boundary — this is not speculative abstraction, it's a
+pilot (Q4 in the plan discussion, answer "A to all 3 questions" — the
-stated requirement. The protocol is minimal (3 methods) and the OPA-
+recommended scope). "All types of securities" is the *product vision*;
-equivalent surface is documented (RESEARCH §4.2) — the swap is a known
+v1.26 is the *pilot* (equities first). The roadmap documents the
-quantity, not a hope. The cost is ~40 lines of Python + a config key;
+deferral. The pilot demonstrates the Nova platform's gates over the
-the benefit is a documented, tested swap boundary that a future
+simplest settlement model (T+1); expanding to other security types is
-milestone implements without re-architecting. This is the moat (NORTH
+a straightforward extension (new settlement-service branches + new
-STAR Objective #2 — provable trust via a replaceable substrate, not a
+kyverno-json policies) once the platform-gates pattern is proven. No
-vendor lock-in).
+revision needed — the scope decision is the user's, not the grill's.
-### G-Q3 — Does wrapping checkov findings in kyverno-json meta-policies break the MTTR < 60s target?
+### G-Q3 — Does the consumer-repo-as-2nd-project break single-project tooling?
-**Challenge:** NORTH_STAR.md MTTR target: < 60s p95. Adding a second
+**Challenge:** CIAgent has been single-project since v1.0. v1.26
-engine pass over the terraform plan + a meta-policy pass over the
+activates multi-project mode (2 projects: `acdl` +
-merged PCR list adds latency. Does this break the target?
+`nova-blockchain-exchange`). Does this break assumptions in the
 CIAgent tooling (branch naming, `.ciagent/` paths, commit `---ci---`
 blocks)?
-**Verdict:** PROCEED (confidence 0.88). RESEARCH §5 analyzes: the kj
+**Verdict:** PROCEED (confidence 0.90). `run.md` Step 0 explicitly
-pass over plan JSON is < 1s (Go binary startup + JMESPath over a small
+specifies multi-project mode: `projects[]` with length > 0,
-plan); it runs **in parallel** with Checkov (REQ-301), so wall-clock
+`active_projects` array, `.ciagent/<slug>/` subdirectory paths, branch
-impact is `max(checkov_time, kj_time)` ≈ checkov_time. Meta-policies
+prefixes `<slug>/`. The `---ci---` block gains a `project: <slug>`
-run in-memory over the merged list (< 10ms). Total MTTR impact: < 1s
+field (already in the v1.26 commits). The consumer's project files
-on a 5-15s step. **Binding revision (G-Q3a):** P3 VERIFY must include a
+live in `.ciagent/nova-blockchain-exchange/`. The platform's existing
-timing assertion — `run_platform.sh` Step 5 wall-clock with vs without
+flat `.ciagent/` files remain the primary set (the platform is the
-kj must be within 1s (or kj must be faster than checkov, which is
+default project). Branch naming: the consumer's phases use
-expected). Captured as a P3 verify gate, not a PLAN change.
+`nova-blockchain-exchange/phase/01-...`; the platform's phases use
 `acdl/phase/03-...` (or flat `phase/03-...` for platform-level work).
 No tooling change needed — the multi-project spec is already in
 `run.md`. D-206 records this. No revision needed.
-### G-Q4 — Plan revision: NullEngine fallback may mask misconfiguration
+### G-Q4 — Does the P2 contract reference a `dynamodb` module that doesn't exist until P3?
-**Challenge:** PLAN.md P1 says "existing tests pass (NullEngine
+**Challenge:** The original plan had REQ-322 (DynamoDB primitive) in
-fallback when `policy` key absent in test config)." But the v1.25
+P3, but the P2 contract (REQ-313) references `dynamodb` in its
-config.json *sets* the `policy` key. So existing tests that load the
+`infrastructure` block. If the primitive doesn't exist until P3, the
-real config get `KyvernoJsonEngine` with `is_configured()==false` →
+P2 contract's `dynamodb` block can't resolve at registry time — only
-`SKIPPED`. The NullEngine fallback only triggers when the key is
+at schema time (the schema is open). Is this a vertical-slice
-*absent*. Is there a gap where a test expects `NullEngine` but gets
+violation (P2 ships a contract that can't fully resolve)?
 `KyvernoJsonEngine` (skipped)?
-**Verdict:** REVISE (confidence 0.82). The fallback path is correct
+**Verdict:** REVISE (confidence 0.92). This is a real vertical-slice
-but the PLAN wording is ambiguous. **Binding revision:** P1 must
+violation. PLAN.md already revised: REQ-322 moves to P2 W0 (before the
-explicitly test *both* paths: (a) `policy` key absent → `NullEngine`
+contract). The revised mapping (PLAN.md "Revised: REQ-322 → P2 W0")
-→ `SKIPPED` PCR; (b) `policy` key present + `which kj` false →
+makes P2 self-contained: the primitive + the contract + the deploy
-`KyvernoJsonEngine` → `is_configured()==false` → `SKIPPED` PCR with
+invocation all land in P2. This is a binding revision — the original
-`KJ_ENGINE_NOT_CONFIGURED` (distinct from NullEngine's
+P3 placement is superseded. ROADMAP.md is already updated (REQ-322 in
-`NULL_ENGINE_INACTIVE`). The two `SKIPPED` PCRs have different
+P2). No further revision needed — the plan self-corrected.
 `ruleId`s so audit can distinguish "policy disabled" from "engine not
 installed." PLAN.md P1 verification is amended to assert both paths.
 Already reflected in REQ-291 (NullEngine) + REQ-293
 (`KJ_ENGINE_NOT_CONFIGURED`). No requirement change — PLAN wording
 clarified.
-### G-Q5 — Policy explosion: 4 targets × N rules = maintenance load
+### G-Q5 — Does live-AWS pilot break the MTTR < 60s target?
-**Challenge:** v1.25 adds ~13 policy files (4 contract + 3 stack-IR +
+**Challenge:** NORTH_STAR.md MTTR target: < 60s p95. The pilot runs
-3 plan-JSON + 2 meta + 3 regression + 1 smoke). Each is a YAML file
+`terraform apply` (creating real AWS resources: ECS + DynamoDB + S3).
-with JMESPath. Is this a maintenance burden that grows unbounded?
+Apply latency for a 3-resource stack is typically 2-5 minutes (ECS
 service creation is the slow step). Does this break the MTTR target?
-**Verdict:** PROCEED (confidence 0.80). 13 policies is manageable —
+**Verdict:** PROCEED (confidence 0.86). The MTTR target is for
-each is < 30 lines of YAML, co-located per target dir, and the meta-
+*platform-detected + platform-remediated incidents* (apply.failed →
-policy cross-check (`tagging-rules-agree`) keeps the set auditable.
+successful retry), not for first-time apply latency. The pilot's
-The growth rate is bounded by the module count (module owners author
+first apply is a deployment, not an incident-remediation. The MTTR
-per-module policies, documented in P4 STANDARDS.md). The alternative
+metric measures the retry path: if the apply fails (e.g. IAM
-(imperative Python in `regression_verify.py` + `env_transition.py`) is
+permission), the platform retries — the retry MTTR is the time from
-*less* auditable — the policies are a net improvement. No revision.
+`apply.failed` to `apply.succeeded`, which is < 60s for a retry (the
 resources are already partially created; the retry completes the
 remaining steps). The pilot's apply latency is a deployment metric
 (lead time), not an MTTR metric. RESEARCH §1.2 (v1.25 grill G-Q3)
 analyzed this same question for the kyverno-json pass — the same
 reasoning applies. No revision needed.
-### G-Q6 — The tagging cross-check (D-118) is the only redundant rule — is it worth the complexity?
+### G-Q6 — Is the settlement-finality policy (REQ-315) over-engineering for a pilot?
-**Challenge:** D-118 keeps `NOVA_TAG_NAMING` (Checkov) AND adds
+**Challenge:** A kyverno-json policy asserting settlement finality
-`KJ_REQUIRE_TAGGING_STANDARD` (kyverno-json) with a `tagging-rules-agree`
+(`all_committed: true`) before promotion is a securities-specific
-meta-policy. This is the only case where two engines evaluate the same
+extension of v1.25's policy engine. Is this over-engineering for a
-concern. Is the defense-in-depth worth the complexity?
+pilot that only runs in `dev` (autonomous, no promotion to qa/prod/dr
 in v1.26 per D-208)?
-**Verdict:** PROCEED (confidence 0.82). The tagging standard is the
+**Verdict:** PROCEED (confidence 0.80). The policy is *authored* in
-highest-impact rule (v1.8 D-tagging-standard, v1.10 re-verification —
+v1.26 (P3) but its *enforcement* activates when a promotion to qa/prod
-the rule that gates every resource). Redundancy here is intentional:
+happens — which is a *future* milestone (D-208: qa/prod/dr stay
-the Checkov rule catches HCL-level violations; the kj policy catches
+placeholder this milestone). The policy is tested (passing + failing
-IR-level violations (before terraform runs); the meta-policy catches
+fixtures; skip when `kj` absent) in P3, but it doesn't gate a `dev`
-engine drift. The cost is 2 policy files + 1 meta-policy; the benefit
+apply (the pilot-readiness policy REQ-320 gates `dev`; the settlement-
-is that a tagging violation can't slip through a single engine's
+finality policy gates promotions). Authoring + testing the policy in
-blind spot. This is the textbook defense-in-depth case. No revision.
+v1.26 is the right thing: it (a) proves the kyverno-json engine can
 assert a domain invariant, (b) ships the policy artifact so a future
 milestone that binds qa/prod/dr can enable it without re-architecting,
 (c) extends v1.25's moat (the policy engine is swappable + extensible
 to new domains). The cost is ~1 policy file + 1 test file. No revision
 needed — but the POLICY IS NOT ENFORCED in v1.26 (it's authored +
 tested, enforcement is future). PLAN.md should note this. **Minor
 revision: PLAN.md P3 W4 Task 4.1 should note "policy authored + tested;
 enforcement deferred to the milestone that binds qa/prod/dr."** Already
 implicit in the plan (the policy gates promotions, not dev applies);
 making it explicit is a documentation refinement, not a scope change.
-### G-Q7 — Can `kj scan` actually evaluate the merged PCR list as a payload?
+### G-Q7 — Is D-083 deferral defensible for a pilot with real money-like flows?
-**Challenge:** The meta-policies (REQ-303) consume the merged
+**Challenge:** The pilot is a stock exchange — securities trading. D-083
-`list[PolicyCheckResult]` as their payload. `kj scan` expects a JSON/
+(S3 Object Lock / JWS tamper-evident ledger) is deferred (D-204). The
-YAML *file*. Is the PCR list a valid kyverno-json payload shape?
+SQLite hash-chain + DynamoDB outbox is the audit record. Is this
 defensible for a domain where audit integrity is legally mandated?
-**Verdict:** PROCEED (confidence 0.85). The PCR list is a JSON array
+**Verdict:** PROCEED (confidence 0.82). The pilot is a *technical
-of objects — a valid kyverno-json payload. The `~` modifier iterates
+demonstration*, not a production trading system. No real money, no real
-the array; JMESPath asserts over each PCR's `severity`/`result`/
+securities, no real investors — the "securities" are test tokens on a
-`ruleId`/`resourceRef` fields. The engine writes the list to a temp
+homegrown chain. The audit integrity requirement (SEC Rule 17a-4, FINRA
-JSON file and invokes `kj scan --payload <file>`. This is verified in
+retention) applies to *production* trading systems, not to a pilot
-P3 `test_meta_policies.py`. No revision — but **binding note (G-Q7a):**
+exercising a platform's deploy/policy/attestation gates. The SQLite
-the `KyvernoJsonEngine.evaluate()` must accept a `list[dict]` payload
+hash-chain + DynamoDB outbox is a tamper-*evident* record (any tampering
-(not just a `dict`) — the `payload: dict | str` signature in RESEARCH
+breaks the hash chain) — it's just not tamper-*resistant* (S3 Object
-§4.1 is too narrow. **Revision:** the protocol signature is
+Lock + JWS would make it tamper-resistant). For a pilot, tamper-evident
-`payload: dict | list | str` (a list is a valid payload for meta-
+suffices. D-083 lift is a future milestone (when the pilot becomes a
-policies). Captured in REQ-291 + REQ-293 (the engine writes whatever
+production system). D-204 records this. No revision needed.
 JSON-serializable payload it receives to the temp file). PLAN.md P1
 amended.
-### G-Q8 — Plan revision: the OPA swap surface claims (RESEARCH §4.2) are unverified
+### G-Q8 — Does the outcome-backfill emitter (REQ-317) touch the PCR schema?
-**Challenge:** RESEARCH §4.2 documents the OPA-equivalent surface
+**Challenge:** REQ-317 wires `apply.completed`/`apply.failed` →
-(`opa eval -d <dir> -i <json>`), but no `OpaEngine` is implemented in
+`fact_decision.outcome`. The v1.25 hard constraint says "DO NOT change
-v1.25. Is the swap-boundary claim testable, or is it aspirational?
+`schemas/policy_check_result.schema.json`." Does the backfill touch the
 PCR schema?
-**Verdict:** REVISE (confidence 0.78). The swap-boundary claim is
+**Verdict:** PROCEED (confidence 0.95). D-211 (CLARIFY) already
-*testable in v1.25* without implementing OPA: the `PolicyEngine`
+resolved this: the outcome backfill touches the *metrics cold store*
-Protocol + registry is the contract; the `NullEngine` proves a second
+(`fact_decision` table in `metrics/nova_metrics.db`), not the PCR
-implementation exists (structural conformance). **Binding revision
+schema. The backfill reads run-manifest events (not PCRs) and updates
-(G-Q8a):** P1 `test_policy_engine.py` must include a
+the decision's outcome column. The PCR schema is unchanged. This
-`test_protocol_conformance_null_engine` that asserts `NullEngine`
+respects the v1.25 hard constraint. No revision needed.
 satisfies the `PolicyEngine` Protocol (via
 `isinstance(NullEngine(), PolicyEngine)` under `runtime_checkable`).
 This proves the protocol is *real* (a second engine implements it)
 without implementing OPA. The OPA-equivalent surface in RESEARCH §4.2
 stays as documentation (the future milestone implements it). PLAN.md
 P1 verification amended. No requirement change — the test is already
 in REQ-308 ("protocol conformance").
-### G-Q9 — Budget: is 4 execution phases + P5 too many for the scope?
+### G-Q9 — Does the `NOVA_AWS_*` root-equivalent key create a security risk?
-**Challenge:** v1.25 is 19 requirements across 6 phases. Recent
+**Challenge:** D-207 says `NOVA_AWS_*` has root-equivalent permissions
-milestones: v1.24 had 15 reqs / 4 phases; v1.23 had 13 reqs / 7 phases.
+(confirmed empirically: the bootstrap created the S3 bucket + DynamoDB
-Is 6 phases too many (overhead) or too few (per-phase overload)?
+table). Using a root key for the pilot's `terraform apply` is a
 security risk — a key compromise gives full account access. Should the
 pilot use a least-privilege key?
-**Verdict:** PROCEED (confidence 0.85). 19 reqs / 6 phases ≈ 3.2 reqs/
+**Verdict:** PROCEED (confidence 0.78). The risk is real but bounded:
-phase — within the v1.24 cadence (3.75 reqs/phase). The phases are
+(a) the pilot runs in a single account (`581513795199`) with no
-vertical slices (each ships a working increment): P1 engine works
+production workloads (the v1.11 teardown left it empty; the pilot is
-end-to-end with a smoke policy; P2 contract + IR policies feed the
+the only workload), (b) the key is in `.env.secrets` (gitignored, never
-confidence signal; P3 plan-JSON + meta + pipeline wiring; P4
+committed), (c) the deploy workflow uses OIDC by default (the static
-regression + docs. The phase count matches the user's "3-4 phases"
+key is the override, not the primary path). A future hardening
-selection (4 execution + 1 final = 5, which is the v1.24 shape). No
+milestone should split `NOVA_AWS_*` into a root `NOVA_BOOTSTRAP_AWS_*`
-revision.
+ a least-privilege `NOVA_AWS_*` runner key (the spike-runner pattern).
-
+For v1.26, the single key suffices (pilot scope). D-207 records this.
-### G-Q10 — The `nova.cloudinit.dev/severity` annotation convention is unvalidated
+**Minor revision: PLAN.md should note the key-split as a future
-
+hardening item.** Already implicit in D-207; making it explicit in the
-**Challenge:** RESEARCH §2.6 declares the severity-via-annotation
+plan is a documentation refinement.
 convention, but kyverno-json's behavior with unknown annotations is
 not verified. Does `kj scan` ignore unknown annotations, or does it
 reject the policy?
 **Verdict:** PROCEED (confidence 0.80). kyverno-json is Kubernetes-
 style CRD-based — unknown `metadata.annotations` are preserved and
 ignored (standard K8s behavior). The engine reads the annotation from
 the loaded policy YAML (via `yaml.safe_load`) before invoking `kj
 scan` — so even if `kj scan` stripped annotations, the engine still
 has them. **Binding note (G-Q10a):** P1 `test_kyverno_json_engine.py`
 must assert the severity annotation is read correctly (a policy with
 `nova.cloudinit.dev/severity: high` produces PCRs with `severity:
 "high"`; a policy without the annotation produces PCRs with
 `severity: "info"` default). Captured in REQ-309 ("PCR schema
 validity" includes severity). No requirement change — the test is
 already in REQ-309.
 ---
 ## Summary
-10 challenges; 10 resolved (8 PROCEED, 2 REVISE, 0 ESCALATE).
+9 challenges; 0 escalations; 2 binding revisions (G-Q4, G-Q6/G-Q9
- **Revisions (binding, already in PLAN/REQs):**
+minor). Overall verdict: PROCEED (confidence 0.84).
  - G-Q4: P1 tests both fallback paths (NullEngine vs
    KyvernoJsonEngine-not-configured) — distinct `ruleId`s for audit.
  - G-Q7a: protocol signature `payload: dict | list | str` (list is a
    valid payload for meta-policies).
  - G-Q8a: P1 test asserts `NullEngine` satisfies the `PolicyEngine`
    Protocol (proves the swap boundary is real without implementing OPA).
  - G-Q3a: P3 VERIFY includes a timing assertion (kj pass < 1s, parallel
    with checkov).
  - G-Q10a: P1 test asserts severity annotation is read correctly.
 - **No requirement changes** — all revisions are clarifications to
  PLAN.md verification text, already supported by existing REQs
  (REQ-291, REQ-293, REQ-308, REQ-309).
 - **0 escalations** — all challenges auto-resolved at full autonomy.
-The milestone PROCEEDs to PHASE 0 SHIP → P1.
+**Binding revisions:**
 - **G-Q4:** REQ-322 moves to P2 W0 (already revised in PLAN.md + ROADMAP.md).
 - **G-Q6:** PLAN.md P3 W4 Task 4.1 should note the settlement-finality
  policy is authored + tested in v1.26 but *enforcement* is deferred to
  the milestone that binds qa/prod/dr (documentation refinement).
 - **G-Q9:** PLAN.md should note the `NOVA_AWS_*` key-split as a future
  hardening item (documentation refinement).
 **No work is blocked.** The milestone is feasible, scoped, and the
 domain claims hold. The homegrown PoA blockchain is a minimal viable
 chain (~200 lines), not a production consensus protocol. The equities-
 only scope is the user's choice. The multi-project mode is specified in
 `run.md`. The P2→P3 dependency is resolved (REQ-322 → P2 W0). The
 MTTR target is for incident-remediation, not first-time apply. The
 settlement-finality policy is authored + tested, enforcement is future.
 D-083 deferral is defensible for a technical pilot. The PCR schema is
 unchanged. The root-equivalent key is a bounded risk with a documented
 future hardening path.
@@ -1,132 +1,152 @@
-# IDEATE — v1.25 kyverno-json Unified Policy Engine
+# IDEATE — v1.26 Live Pilot Estate Activation
 > **Autonomy:** full. 3-tier ideation per `config.json ideation.enabled:
 > true`. `cross_project.enabled: false` → cross-project tier scoped to
-> single-project (deferred ideas only, no cross-project candidates
+> multi-project (deferred ideas only, no cross-project candidates
 > accepted). `confidence_threshold: 0.6`, `max_ideas: 20`.
 > Categories: security, quality, architecture, coverage, improvement.
 ## Tier 1 — Mechanical (pattern-driven, codebase-grounded)
-### I1 — Regression-gate-as-policy ✅ ACCEPTED (REQ-304, REQ-305)
+### I1 — Outcome-backfill emitter ✅ ACCEPTED (REQ-317)
 **Category:** quality, coverage
 **Confidence:** 0.92
 **Pattern:** stuck `pending` status → backfilled from a later event
 (the most direct metric-grounding pattern).
 **Source:** `core/metrics/decision_ledger.py:210-211` documents the
 event chain `confidence.computed → ai.decision.made →
 attestation.recorded → run.completed/failed`. `collector.py:262`
 inserts `fact_decision.outcome` as `"pending"` — no backfill step
 wires `run.completed/failed` back into the decision's outcome. The AI
 Decision Accuracy metric (`trust_snapshot.py:70-85`) reads
 `decisions WHERE outcome='succeeded' ÷ total` → 0% today (all pending).
 **Idea:** `core/metrics/outcome_backfill.py` reads run-manifest
 `completed`/`failed` events and updates `fact_decision.outcome` +
 `fact_decision.backfilled_at`. The collector invokes backfill after run
 completion. Grounds AI Decision Accuracy (Post-Pilot target).
 **Accepted into:** REQ-317. Phase P3.
 ### I2 — `reason='confidence'` escalation tag ✅ ACCEPTED (REQ-318)
 **Category:** quality, coverage
 **Confidence:** 0.90
-**Pattern:** imperative check → declarative policy (the milestone's
+**Pattern:** boolean field → discriminated field (the metric-numerator
-core thesis applied to Nova's own regression gate).
+precision pattern).
-**Source:** `core/regression_verify.py` (CAP-013, CAP-023, CAP-024)
+**Source:** `core/confidence_signal.py:184` — a `block` band sets
-are imperative Python checks. The milestone makes compliance
+`human_override=True`. The Human Escalation Frequency metric
-declarative; Nova's own capability regression should follow.
+(`docs/metrics/human_escalation_frequency.md:11-12`) is defined as
-**Idea:** Port the three capability checks into
+`count(runs WHERE hitl_block=1 AND reason='confidence') ÷ total runs`.
-`adapters/kyverno-json/policies/regression/` as declarative policies
+The `reason='confidence'` discriminator is not stored today.
-over the capability-inventory JSON frontmatter. The imperative
+**Idea:** `ai.decision.made` gains `escalation_reason: 'confidence'`
-`regression_verify.py` stays (it drives the CI gate); the policies are
+when `band == 'block'`. The collector persists it into `fact_run`.
-the declarative mirror that makes capability regression auditable as a
+Grounds Human Escalation Frequency numerator.
-policy artifact.
+**Accepted into:** REQ-318. Phase P3.
 **Accepted into:** REQ-304 (policies), REQ-305 (tests). Phase P4.
-### I2 — Contract-shape validation as policy ✅ ACCEPTED (REQ-295)
+### I3 — Env-JSON `state_backend` wiring reconciliation ✅ ACCEPTED (REQ-319)
-**Category:** security, architecture
+**Category:** architecture, improvement
 **Confidence:** 0.92
 **Pattern:** jsonschema constraint → declarative policy (same constraint,
 different language, Nova posture on top).
 **Source:** `schemas/contract.schema.json` required/pattern/enum.
 **Idea:** The 4 contract policies (`require-id-pattern`,
 `require-env-in-enum`, `require-infrastructure-min-1`, `forbid-unknown-
 fields`) are the declarative equivalent of the jsonschema constraints —
 they let Nova apply its own compliance posture (e.g. forbid a specific
 env for a specific consumer) on top of schema validity without editing
 the jsonschema.
 **Accepted into:** REQ-295. Phase P2.
 ### I3 — Stack-IR imperative rules → declarative policies ✅ ACCEPTED (REQ-297)
 **Category:** security, architecture
 **Confidence:** 0.88
-**Pattern:** imperative Python rule → declarative kyverno-json policy.
+**Pattern:** unused config field → wired config field (the
-**Source:** `adapters/terraform/policy/custom_rules/nova_tagging.py`
+single-source-of-truth pattern).
-(tagging), the v1.0 demo `public-ingress: true` rule, the v1.8
+**Source:** `adapters/terraform/adapter.py:116-117` computes the state
-D-encryption-default rule.
+bucket as `nova-tfstate-<AWS_ACCOUNT_ID>-us-east-1` from the
-**Idea:** Port the three highest-impact imperative rules into
+`AWS_ACCOUNT_ID` env var — **not** from the env JSON's
-declarative kyverno-json policies over the resolved Stack IR. The
+`state_backend.bucket`. The env JSON's `state_backend` field is
-tagging rule is a cross-check (D-118 — both engines, agree meta-policy);
+currently unused by the live apply path.
-public-ingress and encryption-by-default are kyverno-json only (the IR
+**Idea:** The adapter reads `env.state_backend.bucket` when present
-is the earliest point these can be caught).
+(falling back to the computed name for backwards compat). `dev.json`
-**Accepted into:** REQ-297. Phase P2.
+gets the real bucket name. Closes the wiring gap so the pilot's env
 JSON is the single source of truth.
 **Accepted into:** REQ-319. Phase P3.
 ### I4 — Pilot-readiness kyverno-json policy ✅ ACCEPTED (REQ-320)
 **Category:** security, architecture
 **Confidence:** 0.85
 **Pattern:** runtime guard → declarative policy (the v1.25 thesis
 applied to pilot onboarding).
 **Source:** `core/environment_check.py:48-53` emits a stderr warning
 (non-fatal) when `account_id == "000000000000"` and env != dev. A
 warning is not a gate. The pilot should fail-closed if someone tries
 to apply against a placeholder account.
 **Idea:** A kyverno-json policy over the env JSON asserting
 `account_id != "000000000000"` before any apply. Declarative
 fail-closed gate. Extends v1.25's policy engine to the pilot-onboarding
 domain.
 **Accepted into:** REQ-320. Phase P3.
 ## Tier 2 — Backend-enriched (signal-driven)
-### I4 — Plan-JSON Checkov RULE_MAP → kyverno-json mirrors ✅ ACCEPTED (REQ-300)
+### I5 — Settlement-finality kyverno-json policy ✅ ACCEPTED (REQ-315)
 **Category:** security, coverage
-**Confidence:** 0.85
+**Confidence:** 0.82
-**Pattern:** existing engine rule → declarative mirror in the new engine
+**Pattern:** domain invariant → declarative policy (the v1.25 thesis
-(defense-in-depth against engine drift).
+applied to the securities domain — the most novel use of kyverno-json
-**Source:** `checkov_adapter.py:RULE_MAP` (CKV_AWS_41/45/46, CKV_AWS_1/40,
+in v1.26).
-CKV_AWS_7/33).
+**Source:** The pilot's settlement service records matches as
-**Idea:** Port the 6 Checkov rules over `terraform_plan` into declarative
+transactions on the chain; settlement finality = block commit. The
-kyverno-json policies over `terraform show -json` output. The Checkov
+NORTH_STAR Objective #2 (provable trust) says trust should be a policy
-rules stay the source of truth for HCL scanning; the kyverno-json
+artifact, not a promise. Today settlement finality is a runtime
-policies are mirrors (different rule language, same plan JSON). Defense-
+property of the chain; making it a declarative policy turns it into an
-in-depth: if Checkov and kyverno-json disagree on the same plan, the
+auditable gate.
-divergence is visible (two PCRs with different results for the same
+**Idea:** A kyverno-json policy over the settlement-service status JSON
-resource).
+asserting `all_committed: true` before any promotion (qa→prod). The
-**Accepted into:** REQ-300. Phase P3.
+securities-specific extension of v1.25's policy engine. The policy is
 skip-when-kj-absent (graceful).
 **Accepted into:** REQ-315. Phase P3.
-### I5 — Meta-policy over the merged PCR list ✅ ACCEPTED (REQ-303)
+### I6 — Pilot-estate regression capability (CAP-025) ✅ ACCEPTED (REQ-316)
-**Category:** architecture, quality
+**Category:** quality, coverage
-**Confidence:** 0.90
+**Confidence:** 0.88
-**Pattern:** the policy result list is itself a policy target (the most
+**Pattern:** manual e2e → regression-gated capability (the v1.0 CAP
-novel use of kyverno-json in v1.25).
+pattern applied to the pilot).
-**Source:** `core/confidence_signal.py` PENALTY hardcode (critical
+**Source:** `core/regression_verify.py` has CAP-013..024 (live-AWS +
-override), the D-118 tagging cross-check.
+local tiers). The pilot estate is a new live-AWS capability —
-**Idea:** `block-on-any-critical` (declarative "critical = block") +
+"contract resolve → adapter compile → terraform plan → policy scan →
-`tagging-rules-agree` (Checkov vs kj agree). The meta-policies consume
+confidence signal → attestation → outbox record" against
-the merged PCR list as their payload. The critical-block meta-policy is
+`581513795199`. Without a regression CAP, the pilot could silently
-the declarative source of truth; the `confidence_signal.py` hard-override
+decay.
-stays as defense-in-depth (D-119).
+**Idea:** CAP-025 (live-pilot-apply) in the regression gate. The
-**Accepted into:** REQ-303. Phase P3.
+round-trip assertion. Grounds the pilot as a maintained capability,
 not a one-shot demo.
 **Accepted into:** REQ-316. Phase P3.
-### I6 — Env-transition destroy as a declarative policy ❌ DEFERRED
+### I7 — DynamoDB L1 primitive ✅ ACCEPTED (REQ-322)
 **Category:** architecture, coverage
 **Confidence:** 0.95
 **Pattern:** missing primitive → authored module (the v1.7 + v1.8
 module-build-out pattern).
 **Source:** RESEARCH §3.4 — no `modules/l1/dynamodb/` exists. The
 blockchain exchange's ledger table needs it. The adapter is
 stateless/registry-driven (no `TYPE_MAP`); a new stack type requires a
 new L1 module, not an adapter change.
 **Idea:** Author `modules/l1/dynamodb/` (interface.json +
 terraform/main.tf + README.md + instance.json + registry.json entry).
 The single platform-side module build-out for the milestone. Follows
 the `s3`/`rds` primitive template. Encryption + PITR enabled per v1.8
 NFR defaults.
 **Accepted into:** REQ-322. Phase P3.
 ### I8 — Stale `adapters/README.md` TYPE_MAP references ❌ DEFERRED (scope)
 **Category:** improvement
-**Confidence:** 0.55 (below threshold — deferred, not rejected)
+**Confidence:** 0.70 (above threshold, but scoped into REQ-321)
-**Pattern:** imperative lifecycle Python → declarative policy.
+**Pattern:** stale doc → corrected doc.
-**Source:** `core/env_transition.py` (v1.24 detect-and-destroy).
+**Source:** `adapters/README.md:49-54` references the deleted
-**Idea:** The v1.24 env-transition destroy logic (detect env change via
+`TYPE_MAP`/`INPUT_MAP`/`OUTPUT_MAP` — contradicts `adapter.py:1-11` +
-DynamoDB, destroy prior env, fail-closed) is imperative Python. A
+`modules/STANDARDS.md:212-214`.
-declarative kyverno-json policy could assert "if `environment` changed
+**Idea:** Fix the stale references as part of the docs phase.
-on a stable `contract.id`, a destroy event MUST precede the apply" —
+**Reason deferred as a standalone idea:** Already captured in REQ-321
-turning the lifecycle enforcement into an auditable policy artifact.
+(docs + adapter README). No new requirement needed — the fix lands in
-**Reason deferred:** The env-transition logic is *stateful* (DynamoDB
+P4 docs.
 queries, terraform state inspection) — kyverno-json policies are
 *stateless* (payload in, PCRs out). A policy can assert the *contract*
 shape (the env value is valid) but not the *lifecycle* (the prior env
 was destroyed). The stateful check stays in `core/env_transition.py`;
 a future milestone could emit a `nova.env.destroyed` event that a
 kyverno-json policy then asserts is present in the evidence stream
 (event-as-policy). Recorded as a future-idea, not a v1.25 requirement.
-### I7 — Drift detection as policy ❌ DEFERRED
+## Tier 3 — Cross-project (deferred — multi-project, but cross-project sharing disabled)
-**Category:** security, coverage
+### I9 — Cross-project policy sharing ❌ DEFERRED (config)
 **Confidence:** 0.40 (below threshold — deferred)
 **Pattern:** scheduled job → policy over the drift report.
 **Source:** NORTH_STAR.md Non-Goal #4 (drift detection scheduled job,
 deferred — D-096 + no scheduler).
 **Idea:** A kyverno-json policy over a terraform drift report could
 assert "no drifted resources" declaratively. But drift detection itself
 requires a scheduled `terraform plan -detailed-exitcode` job, which is
 deferred (no scheduler). The policy is the easy part; the emitter is the
 blocking dependency.
 **Reason deferred:** Blocked by D-096 + no scheduler (same as NORTH_STAR
 Non-Goal #4). The policy shape is documented for when the emitter ships.
 ## Tier 3 — Cross-project (deferred — single project)
 ### I8 — Cross-project policy sharing ❌ DEFERRED (config)
 **Category:** improvement
 **Confidence:** N/A
@@ -134,24 +154,41 @@ Non-Goal #4). The policy shape is documented for when the emitter ships.
 **Source:** `config.json ideation.cross_project.enabled: false`.
 **Idea:** In a multi-project org, kyverno-json policies could be shared
 across projects (a tagging standard policy applies to all projects).
-**Reason deferred:** ACDL is single-project (`active_projects: ["acdl"]`).
+**Reason deferred:** `cross_project.enabled: false`. Even though
-Cross-project ideation is disabled in config. Recorded for when the
+v1.26 is multi-project (acdl + nova-blockchain-exchange),
-org grows.
+cross-project *ideation* is disabled in config. Recorded for when the
 org grows + the flag is enabled.
 ### I10 — Consumer-repo CI scaffolding as a reusable template ❌ DEFERRED
 **Category:** improvement
 **Confidence:** 0.55 (below threshold — deferred, not rejected)
 **Pattern:** one-off CI → reusable template.
 **Source:** The consumer repo (`nova-blockchain-exchange`) needs its
 own CI (`ci.yml` — lint + pytest). If Nova expects many consumers, a
 reusable consumer-CI template would reduce onboarding friction.
 **Idea:** A `nova-consumer-template` repo (or a
 `.github/workflow-templates/` dir) that new consumers instantiate.
 **Reason deferred:** Nova has 1 consumer today (the pilot). A template
 is premature abstraction until the 2nd consumer arrives. The pilot's
 CI is authored directly (REQ-310..312 tests). Recorded for when the
 3rd consumer onboards.
 ## Summary
- 5 ideas accepted (I1..I5) → already captured as REQ-295, REQ-297,
+- 7 ideas accepted (I1..I7) → already captured as REQ-315, REQ-316,
-  REQ-300, REQ-303, REQ-304, REQ-305.
+  REQ-317, REQ-318, REQ-319, REQ-320, REQ-322.
- 3 ideas deferred (I6, I7, I8) with documented blocking reasons.
+- 3 ideas deferred (I8 scoped into REQ-321; I9 config-disabled; I10
  below threshold) with documented blocking reasons.
 - 0 ideas rejected (below-threshold ideas are deferred, not rejected —
  they may activate when their blockers lift).
- The accepted ideas are the **quality improvement** the user asked for
+- The accepted ideas are the **quality improvement** the `--ideate` flag
-  ("ideate and explore how it can be used within the Nova platform to
+  drives: I1 + I2 ground the Post-Pilot metrics (outcome backfill +
-  improve quality of the platform checks"): I1 (regression-gate-as-
+  escalation reason); I3 closes the env-JSON wiring gap; I4 + I5 extend
-  policy) is the headline quality improvement; I4 + I5 are the defense-
+  v1.25's policy engine to the pilot domain (pilot-readiness +
-  in-depth coverage improvements; I2 + I3 are the architecture
+  settlement-finality); I6 gates the pilot as a maintained capability;
-  improvements (imperative → declarative).
+  I7 is the single platform-side module build-out.
- No new requirements added beyond REQ-291..309 (the accepted ideas are
+- No new requirements added beyond REQ-310..322 (the accepted ideas are
  already scoped into the existing requirements). The IDEATE pass
  validated the requirement set rather than expanding it — the ideas
-  were anticipated in the SPECIFY stage and explicitly captured.
+  were anticipated in the SPECIFY + RESEARCH stages.
@@ -229,4 +229,16 @@ their AI engineering teams reach for first when an agent needs to deploy.
  RESEARCH.md/ARCHITECTURE.md. It is the *how*; this file is the *why*.
 - **Pillar C (story):** the unified narrative deck proves Pillars A+B to
  leadership. The deck's Proof section cites grounded metrics; its
-  Roadmap section cites deferred targets honestly.
+  Roadmap section cites deferred targets honestly.
 ## v1.25 update — swappable policy-engine substrate
 Strategic Objective #2 (provable trust) gained a concrete substrate in
 v1.25: the policy engine that produces the `PolicyCheckResult` records
 feeding the confidence signal is now **swappable** via the
 `PolicyEngine` protocol (`core/policy_engine.py`). `kyverno-json` is
 the v1.25 default; `OPA` (or any other engine) can replace it by
 implementing the same 3-method protocol — without touching the
 confidence signal, the PCR schema, or the pipeline. See
 ARCHITECTURE.md §12.7. The trust moat is a *replaceable* engine, not a
 vendor lock-in.
@@ -0,0 +1,46 @@
 # P4 — Live Pilot Run Evidence (v1.26, v0.2 re-run)
 > The live `terraform apply` against AWS `581513795199` succeeded. The
 > Decision Ledger + outcome backfill are complete. SPEC §5.8 evidence
 > stream verified.
 ## Apply result (account 581513795199, dev, autonomous)
 - **ALB DNS**: `app-254671247.us-east-1.elb.amazonaws.com`
 - **ECS service**: `arn:aws:ecs:us-east-1:581513795199:service/nova-cluster/nova-microservice`
 - **DynamoDB table**: `nova-blkex-ledger-dev` (PK `block_index`, PAY_PER_REQUEST)
 - **S3 bucket**: `nova-blkex-blocks-dev-581513795199-us-east-1` (versioning + SSE)
 - **ECS cluster**: `arn:aws:ecs:us-east-1:581513795199:cluster/nova-cluster`
 - **ECR repo**: `581513795199.dkr.ecr.us-east-1.amazonaws.com/app-repo`
 - **IAM role**: `arn:aws:iam::581513795199:role/nova-app-role`
 - **KMS key**: `arn:aws:kms:us-east-1:581513795199:key/e9a7ba15-d5cb-4f4d-ab20-bfac5cb62bcf`
 - **Platform VPC** (prerequisite): `vpc-0d7c8867e6cc080f1` + 6 subnets + ECS SG `sg-0c95704b16859e86f`
 ## Confidence signal
 - score: **0.800**, band: **pass** (dev autonomous, ≥0.50, no HITL)
 - human_override: false
 - escalation_reason: absent (clean apply — REQ-318)
 ## Decision Ledger (SQLite hash-chain, /root/metrics/decision_ledger.db)
 - `nova.ai.decision.made` — decision_id `blkex-pilot-apply-v0.2`, chosen_action `pass`, human_override false
 - `nova.outcome.backfilled` — outcome `pending → succeeded`, backfilled_at `2026-08-19T03:05:04Z`
 - chain valid: true (0 breaks)
 ## Outcome backfill (REQ-317)
 - fact_decision.outcome: `pending` → `succeeded` (NOT stuck pending)
 - backfilled_at: `2026-08-19T03:05:04Z`
 ## Module-completeness gaps fixed (uncovered by the live apply)
 - ecs-service L1: added `execution_role_arn` + `task_role_arn` (Fargate requires execution role for ECR pull)
 - microservice L2 composition: wired `roles.outputs.role_arn` → `service.inputs.{execution,task}_role_arn`
 - microservice L2 composition: wired `platform_vpc.outputs.ecs_security_group_id` → `alb.inputs.security_group` (ALB requires a SG)
 ## Run id
 - NOVA_RUN_ID: `blkex-pilot-apply-v0.2`
 ---ci---
 project: acdl
 phase: 4
 milestone: v1.26
 status: execute
 wave: W1
 ---
@@ -1,132 +1,169 @@
 ---
 project: acdl
-milestone: v1.25
+milestone: v1.26
 generated_at: 2026-08-12
 generator: lead-developer
 verification_toolchain:
-  typecheck: "python3 -m py_compile core/policy_engine.py adapters/kyverno-json/kyverno_json_engine.py tests/test_policy_engine.py tests/test_kyverno_json_engine.py"
+  typecheck: "python3 -m py_compile core/confidence_signal.py core/metrics/outcome_backfill.py adapters/terraform/adapter.py modules/l1/dynamodb/terraform/main.tf"
-  test: "pytest tests/test_policy_engine.py tests/test_kyverno_json_engine.py tests/test_adapter.py tests/test_contract_resolver.py tests/test_confidence_signal.py tests/test_checkov_adapter.py tests/test_kyverno_adapter.py tests/test_pipeline.py -v"
+  test: "pytest tests/test_adapter.py tests/test_contract_resolver.py tests/test_confidence_signal.py tests/test_outcome_backfill.py tests/test_settlement_finality_policy.py tests/test_pilot_readiness_policy.py tests/test_block.py tests/test_order_book.py tests/test_settlement.py -v"
-  lint: "ruff check core/policy_engine.py adapters/kyverno-json/ 2>/dev/null || python3 -m py_compile core/policy_engine.py"
+  lint: "ruff check core/metrics/outcome_backfill.py adapters/kyverno-json/policies/pilot-readiness/ adapters/kyverno-json/policies/settlement-finality/ 2>/dev/null || python3 -m py_compile core/metrics/outcome_backfill.py"
  note: |
-    v1.25 is the kyverno-json Unified Policy Engine milestone — a feat
+    v1.26 is the Live Pilot Estate Activation milestone — a feat
    milestone. Four active personas: lead-developer (coordination +
-    docs + ARCHITECTURE.md §12.7), backend-engineer (core/policy_engine.py
+    docs + ARCHITECTURE.md §12.8), backend-engineer (confidence_signal.py
-    protocol + registry + contract_resolver.py wiring + run_platform.sh
+    escalation reason + outcome_backfill.py + run_platform.sh wiring +
-    Step 5 + pipeline tests), policy-engineer (adapters/kyverno-json/
+    env-JSON state_backend reconciliation), data-engineer (DynamoDB L1
-    engine + policies across all 4 target dirs + meta-policies + policy
+    primitive + metrics cold store outcome backfill), policy-engineer
-    tests + adapter README + STANDARDS.md policy-authoring section),
+    (kyverno-json pilot-readiness + settlement-finality policies), +
-    data-engineer (config.json policy object + schemas/README.md note +
+    blockchain-engineer (custom, phase-specific — chain core + order
-    capability-inventory JSON fixture for regression policies).
+    engine + settlement). frontend-engineer is deactivated (no UI).
-    frontend-engineer stays deactivated (no UI). The policy-engineer is a
+    Territory enforcement: warn (the pilot is cross-territory by
-    new custom persona created for this milestone's policy domain (see
+    nature — the consumer repo + the platform repo share the milestone).
    RESEARCH.md §4 — kyverno-json + JMESPath is a distinct framework from
    backend-engineer's fastify/hono).
 ---
-# ACDL — Persona Roster (v1.25 kyverno-json Unified Policy Engine)
+# PERSONAS — v1.26 Live Pilot Estate Activation
-> v1.25 roster. Four active personas + one deactivated. This is a feat
+> Generated by the lead-developer at the end of RESEARCH. Assesses the
-> milestone: the work is a swappable policy-engine protocol + a new
+> project domains, activates/deactivates personas, creates custom
-> adapter + policies across 4 Nova artifacts + pipeline wiring + docs.
+> personas for domains beyond the default four, aligns frameworks +
-> The policy-engineer is a new custom persona — kyverno-json + JMESPath
+> territory + constraints to the actual project structure.
 > is a specialized domain that doesn't fit backend-engineer's
 > fastify/hono frameworks or data-engineer's drizzle/postgresql.
-## Active personas
+## Active Roster (5)
-### lead-developer
+### 1. lead-developer (active)
- **Domain:** coordination + docs
+- **active:** true
- **Frameworks:** []
+- **phase_specific:** false
- **Constraints:** ["pragmatic", "battle-tested defaults", "docs match code", "swap boundary is the moat"]
+- **reason:** Coordinates task decomposition + resolves conflicts between
- **Territory:**
+  engineering personas. Owns the milestone narrative (PROJECT.md,
-  - `.ciagent/ARCHITECTURE.md` (§12.7 Policy Engine Registry — NEW)
+  ROADMAP.md, ARCHITECTURE.md §12.8). Final architectural decisions when
-  - `.ciagent/PROJECT.md` (v1.25 section)
+  personas disagree (e.g. where the outcome-backfill emitter lives).
-  - `.ciagent/REQUIREMENTS.md` (v1.25 section)
+- **domain:** project coordination, milestone narrative, cross-persona
-  - `.ciagent/ROADMAP.md` (v1.25 section)
+  conflict resolution.
-  - `.ciagent/PLAN.md`, `.ciagent/RESEARCH.md`, `.ciagent/CLARIFY.md`,
+- **frameworks:** none (coordination role).
-    `.ciagent/GRILL.md`, `.ciagent/PERSONAS.md`
+- **territory:** `.ciagent/`, `docs/METRICS.md`, `adapters/README.md`,
-  - `docs/METRICS.md` (swappable engine narrative — REQ-307)
+  `modules/README.md`, `modules/STANDARDS.md`.
- **Reason:** Owns the milestone coordination + the architecture
+- **constraints:** does not write Python/Terraform (delegates to
-  narrative. The swap boundary (PolicyEngine protocol) is the moat per
+  backend/data-engineer); does not author policies (delegates to
-  Strategic Objective #2 — the lead-developer owns the boundary
+  policy-engineer); does not author chain code (delegates to
-  description in ARCHITECTURE.md §12.7 and the docs/METRICS.md note.
+  blockchain-engineer).
  No Python policy code (backend-engineer + policy-engineer territory).
  No UI (frontend-engineer deactivated).
-### backend-engineer
+### 2. backend-engineer (active)
- **Domain:** backend (Python + bash + pipeline wiring)
+- **active:** true
- **Frameworks:** ["boto3", "terraform"]
+- **phase_specific:** false
- **Constraints:** ["api-first", "strict-typing", "engine-agnostic confidence signal", "fail-soft when kj absent"]
+- **reason:** Owns the platform-side Python changes: confidence signal
- **Territory:**
+  escalation reason (REQ-318), outcome-backfill emitter (REQ-317),
-  - `core/policy_engine.py` (NEW — PolicyEngine Protocol + PolicyEngineRegistry + NullEngine)
+  env-JSON state_backend wiring (REQ-319), adapter test updates for
-  - `core/contract_resolver.py` (MODIFIED — invoke registry pre/post resolve)
+  DynamoDB (REQ-322), regression CAP-025 (REQ-316).
-  - `scripts/run_platform.sh` (MODIFIED — Step 5 kyverno-json parallel pass)
+- **domain:** core Python (confidence_signal.py, metrics/, adapter.py,
-  - `scripts/install-kyverno-json.sh` (NEW)
+  regression_verify.py, contract_resolver.py), run_platform.sh wiring.
-  - `tests/test_policy_engine.py` (NEW — protocol conformance, registry, NullEngine)
+- **frameworks:** Python 3.12, pytest, boto3, SQLite, DynamoDB.
-  - `tests/test_run_platform_plan_json_policies.py` (NEW — script-substring assertion)
+- **territory:** `core/confidence_signal.py`, `core/metrics/`,
-  - `.github/workflows/ci.yml` + `.gitea/workflows/ci.yml` (MODIFIED — Go + kj install)
+  `adapters/terraform/adapter.py`, `core/regression_verify.py`,
- **Reason:** Owns the Python protocol layer + the pipeline wiring. The
+  `core/environments/`, `scripts/run_platform.sh`, `tests/test_adapter.py`,
-  `PolicyEngine` Protocol + `PolicyEngineRegistry` are Python structural-
+  `tests/test_confidence_signal.py`, `tests/test_outcome_backfill.py`,
-  typing constructs (PEP 544) — backend-engineer's strict-typing
+  `tests/test_regression_pilot.py`.
-  constraint. The `contract_resolver.py` wiring + `run_platform.sh`
+- **constraints:** does not change `schemas/policy_check_result.schema.json`
-  Step 5 are backend territory. Does NOT write kyverno-json policy
+  (v1.25 moat, D-211); does not change `schemas/contract.schema.json`
-  files (policy-engineer territory) — only the Python that *invokes* the
+  (no schema breaks, D-213); does not author Terraform modules
-  engine. Does NOT modify the confidence signal (it already consumes
+  (delegates to data-engineer for DynamoDB); does not author policies
-  `list[PolicyCheckResult]` engine-agnostically — PROJECT.md hard-
+  (delegates to policy-engineer); does not author chain code (delegates
-  constraint).
+  to blockchain-engineer).
-### policy-engineer
+### 3. data-engineer (active)
- **Domain:** policy (declarative compliance rules)
+- **active:** true
- **Frameworks:** ["kyverno-json", "jmespath", "kyverno ValidatingPolicy"]
+- **phase_specific:** false
- **Constraints:** ["declarative-policies", "no-imperative-rules", "schema-validated", "severity-via-annotation", "assertion-trees-not-foreach"]
+- **reason:** Owns the DynamoDB L1 primitive (REQ-322) — the single
- **Territory:**
+  platform-side module build-out. Owns the metrics cold store
-  - `adapters/kyverno-json/` (NEW — engine impl + __init__.py + README)
+  outcome-backfill integration (REQ-317, the `fact_decision.outcome`
-  - `adapters/kyverno-json/kyverno_json_engine.py` (NEW — KyvernoJsonEngine)
+  column + `backfilled_at` timestamp). Owns the env-JSON data updates
-  - `adapters/kyverno-json/policies/` (NEW — all 4 target dirs: contract/, stack-ir/, plan-json/, meta/, regression/)
+  (REQ-319, `core/environments/*.json` account_id + state_backend.bucket).
-  - `adapters/kyverno-json/policies/_smoke.json` (NEW)
+- **domain:** Terraform modules (`modules/l1/`), schema definitions
-  - `adapters/README.md` (MODIFIED — new adapter row + PolicyEngine Protocol section)
+  (`interface.json`), registry (`modules/registry.json`), metrics cold
-  - `tests/test_kyverno_json_engine.py` (NEW — PCR schema validity, defensive parsing)
+  store (`metrics/nova_metrics.db`, `core/metrics/collector.py`).
-  - `tests/test_stack_ir_policies.py` (NEW)
+- **frameworks:** Terraform, JSON, SQLite, DynamoDB, boto3.
-  - `tests/test_plan_json_policies.py` (NEW)
+- **territory:** `modules/l1/dynamodb/`, `modules/registry.json`,
-  - `tests/test_meta_policies.py` (NEW)
+  `modules/README.md`, `core/environments/*.json`,
-  - `tests/test_regression_policies.py` (NEW)
+  `core/metrics/collector.py`, `tests/test_adapter.py` (DynamoDB
-  - `tests/fixtures/stack_ir/`, `tests/fixtures/plan_json/`, `tests/fixtures/capability_inventory.json` (NEW)
+  emission test).
-  - `modules/STANDARDS.md` (MODIFIED — Policy authoring standard section — REQ-307)
+- **constraints:** does not change the adapter (stateless, v1.11);
- **Reason:** The policy-engineer owns the declarative policy artifacts.
+  follows the v1.8 NFR defaults (encryption + deletion protection +
-  kyverno-json's `ValidatingPolicy` + assertion trees + JMESPath is a
+  PITR); follows the module standards (`modules/STANDARDS.md`).
  distinct framework from backend-engineer's fastify/hono and requires
  its own constraints: no imperative rules (everything is an assertion
  tree), severity via the `nova.cloudinit.dev/severity` annotation (not
  in the engine adapter), no `forEach` (use the `~` modifier). The
  adapter pattern (engine ↔ protocol ↔ registry) is backend-engineer
  territory, but the policy *content* and the engine *translation*
  (`_to_pcr()`) are policy-engineer territory because they require
  kyverno-json output-shape knowledge. Created per RESEARCH.md §4 — this
  is a phase-spanning persona (active for P1..P4), not phase-specific.
-### data-engineer
+### 4. policy-engineer (active, custom — added in v1.25)
- **Domain:** data (config schema + structured fixtures)
+- **active:** true
- **Frameworks:** ["jsonschema", "yaml"]
+- **phase_specific:** false
- **Constraints:** ["schema-first", "type-safe config", "backward-compatible additions"]
+- **reason:** Owns the kyverno-json policy authoring for the pilot:
- **Territory:**
+  settlement-finality (REQ-315), pilot-readiness (REQ-320). Extends
-  - `.ciagent/config.json` (MODIFIED — new `policy` object: engine + policy_root)
+  v1.25's policy engine to the securities domain.
-  - `schemas/policy_check_result.schema.json` (READ-ONLY — no change per D-116)
+- **domain:** declarative policies (kyverno-json ValidatingPolicy YAML),
-  - `schemas/README.md` (MODIFIED — note engine: "kyverno" shared by K8s adapter + kj)
+  JMESPath assertions, policy tests.
-  - `tests/fixtures/capability_inventory.json` (NEW — clean + drifted inventory fixtures for regression policies)
+- **frameworks:** kyverno-json, JMESPath, JSON, pytest.
- **Reason:** The `config.json.policy` object is a schema-first addition
+- **territory:** `adapters/kyverno-json/policies/pilot-readiness/`,
-  (new top-level key with `engine` + `policy_root` fields). The
+  `adapters/kyverno-json/policies/settlement-finality/`,
-  capability-inventory JSON fixtures for the regression-gate policies
+  `tests/test_settlement_finality_policy.py`,
-  (REQ-304) are structured data — the data-engineer owns the fixture
+  `tests/test_pilot_readiness_policy.py`.
-  shape. The `policy_check_result.schema.json` is read-only (D-116 — no
+- **constraints:** policies are declarative (no imperative Python);
-  enum change); the data-engineer documents the `engine: "kyverno"`
+  `is_configured()` guard skips gracefully when `kj` absent; follows
-  sharing in `schemas/README.md`. No migrations (no database). No Python
+  the v1.25 policy-authoring standard (`modules/STANDARDS.md` policy
-  (backend-engineer + policy-engineer territory).
+  section + `adapters/kyverno-json/README.md`).
-## Deactivated personas
+### 5. blockchain-engineer (active, custom, phase-specific — added in v1.26)
 - **active:** true
 - **phase_specific:** true (created for v1.26 P1; removed after P1
  unless the chain has ongoing work in P2..P4)
 - **reason:** The pilot introduces a homegrown blockchain — a domain
  beyond the default four personas. Owns the chain core (block, ledger,
  validator, REQ-310), the order-matching engine (REQ-311), the
  settlement service (REQ-312), and the consumer `contract.yaml`
  (REQ-313) + deploy invocation (REQ-314).
 - **domain:** blockchain consensus (PoA, single validator), order
  matching (limit order book, price-time priority), settlement
  (T+1, finality = block commit), consumer-repo deploy model.
 - **frameworks:** Python 3.12 (the chain is Python, not Solidity/Go —
  it's a homegrown ledger, not a smart-contract platform), pytest,
  YAML (contract.yaml), GitHub Actions / Gitea Actions (deploy.yml
  invocation).
 - **territory:** `/root/nova-blockchain-exchange/` (the consumer repo:
  `chain/`, `engine/`, `settlement/`, `contract.yaml`,
  `contracts/*.yml`, `.github/workflows/deploy.yml`,
  `.gitea/workflows/deploy.yml`, `tests/`).
 - **constraints:** the chain is deterministic (same inputs → same block)
  — it is automation, not AI (NORTH_STAR Objective #2 tenet); equities
  only (D-200); single validator PoA (D-201); the consumer deploy MUST
  go through `deploy.yml@v1.25` (no direct terraform apply); the
  contract MUST validate against `schemas/contract.schema.json`.
-### frontend-engineer
+## Deactivated (1)
 ### frontend-engineer (inactive)
 - **active:** false
- **Reason:** ACDL has no frontend (no package.json — confirmed in
+- **phase_specific:** false
-  config.json personas.personas[frontend-engineer].reason). v1.25 adds
+- **reason:** The pilot has no UI — the blockchain exchange is a
-  no UI work — the policy engine is backend + policy artifacts only.
+  backend service (matching engine + settlement). The consumer repo
-  Deactivated per the v1.15+ convention.
+  has no web/frontend. Reactivated if a future milestone adds a trading
  dashboard.
 ## Phase-Specific Notes
 - **blockchain-engineer** is created for v1.26 P1 (blockchain core +
  order engine + settlement). If P2..P4 have no chain changes, the
  persona is removed after P1 (the chain is a stable substrate for the
  pilot run). If P2 (consumer-contract-and-deploy) requires chain
  adjustments, the persona stays through P2.
 - **policy-engineer** is active for P3 (pilot-metrics-and-policies) +
  may consult on P4 (pilot run policy verification).
 - **data-engineer** is active for P3 (DynamoDB primitive + outcome
  backfill + env-JSON) + P4 (regression CAP-025 may touch the registry).
 ## Territory Enforcement
 - **Mode:** `warn` (the pilot is cross-territory by nature — the
  consumer repo + the platform repo share the milestone; the
  blockchain-engineer works in the consumer repo, backend/data/policy
  engineers work in the platform repo).
 - **Cross-territory collisions:** REQ-322 (DynamoDB primitive) is
  data-engineer territory, but the adapter test update
  (`tests/test_adapter.py` `EXPECTED_L1_KEYS`) is backend-engineer
  territory. The lead-developer resolves: data-engineer authors the
  module + registry; backend-engineer updates the test assertion
  (the test is backend territory, the module is data territory).
@@ -1,371 +1,510 @@
-# PLAN — v1.25 (kyverno-json Unified Policy Engine)
+# PLAN — v1.26 (Live Pilot Estate Activation)
-> Feature milestone. Tags on the **v1.24.x** line: v1.24.0 (P0) →
+> Feature milestone. Tags on the **v1.25.x** line: v1.25.0 (P0) →
-> v1.24.1 (P1) → v1.24.2 (P2) → v1.24.3 (P3) → v1.24.4 (P4) → v1.24.5
+> v1.25.1 (P1) → v1.25.2 (P2) → v1.25.3 (P3) → v1.25.4 (P4) → v1.25.5
-> (P5 final = milestone release). 19 requirements (REQ-291..309),
+> (P5 final = milestone release). 13 requirements (REQ-310..322),
-> 4 execution phases + P0 pre-execution + P5 final review/ship.
+> 5 phases (P0 pre-execution + 4 execution + 1 final). Multi-project:
-
+> `acdl` (platform) + `nova-blockchain-exchange` (consumer). Tags run
-## Wave model
+> on the previous minor's patch line per `run.md` versioning logic
-
+> (feature milestone — at least one feat phase; progressive patches per
-Each phase is a **vertical slice** (end-to-end: policy files + Python
+> phase; the final phase's patch IS the milestone release; no separate
-wiring + tests + docs). Phases are ordered by dependency: the engine
+> minor tag).
 protocol (P1) must exist before policies (P2/P3) can be wired; the
 pipeline wiring (P3) must exist before the meta-policies (P3) can
 consume the merged PCR list; the regression-gate policies (P4) are
 independent of the pipeline and can be authored in parallel with P3's
 tests, but ship after P3 because they reference the engine registry
 finalized in P1. Within each phase, the waves are the persona task
 groups (parallelizable across personas when `parallelization.enabled:
 true`, `max_concurrent_agents: 5`).
 ## Phase breakdown
 ### Phase P1 — engine-core (Wave 1, backend-engineer + policy-engineer + data-engineer)
 **Type:** `feat` (engine protocol + registry + kyverno-json engine adapter + install + tests)
 **Requirements:** REQ-291, REQ-292, REQ-293, REQ-294, REQ-308, REQ-309
 **Must-haves:**
 - `core/policy_engine.py` — `PolicyEngine` Protocol (PEP 544) +
  `PolicyEngineRegistry` (selects from `config.json.policy.engine`) +
  `NullEngine` fallback (emits `SKIPPED` when `policy` key absent)
  (REQ-291)
 - `.ciagent/config.json` gains `policy` object: `{"engine":
  "kyverno-json", "policy_root":
  "adapters/kyverno-json/policies"}` (REQ-292)
 - `adapters/kyverno-json/kyverno_json_engine.py` — `KyvernoJsonEngine`
  implementing the protocol: `is_configured()` guards on `which kj`;
  `evaluate()` writes payload to temp JSON, invokes
  `kj scan --policy <dir> --payload <json> --output json`, translates
  native output → `list[dict]` PCR records (`engine: "kyverno"`,
  `ruleId` prefixed `KJ_<policy_name>`, severity from
  `nova.cloudinit.dev/severity` annotation); defensive parsing
  (malformed → `error` PCR, never exception); `is_configured()==false`
  → single `SKIPPED` PCR (`KJ_ENGINE_NOT_CONFIGURED`) (REQ-293)
 - `adapters/kyverno-json/__init__.py` exports `KyvernoJsonEngine`;
  `adapters/kyverno-json/policies/_smoke.json` trivial
  `require-contract-id` policy for round-trip validation;
  `scripts/install-kyverno-json.sh` runs
  `go install github.com/kyverno/kyverno-json/cmd/kj@latest`;
  `.github/workflows/ci.yml` + `.gitea/workflows/ci.yml` install Go + kj
  (cached) (REQ-294)
 - `tests/test_policy_engine.py` — protocol conformance, registry
  selection, unknown-engine `KeyError`, `NullEngine` fallback,
  `is_configured()` false when `which kj` absent (mocked) (REQ-308)
 - `tests/test_kyverno_json_engine.py` — `evaluate()` returns PCR dicts
  validating against `schemas/policy_check_result.schema.json` (via
  `jsonschema`); defensive parsing (malformed kyverno-json output →
  `error` PCR); `is_configured()==false` → `SKIPPED` with
  `KJ_ENGINE_NOT_CONFIGURED`; `pytest.skip("kj not installed")` when
  `which kj` absent (REQ-309)
 **Vertical slice:** The `PolicyEngineRegistry.get_engine()` returns a
 configured `KyvernoJsonEngine` that can `evaluate()` a trivial payload
 against `_smoke.json` and produce a valid PCR list. The confidence
 signal is unchanged — it already consumes `list[PolicyCheckResult]`.
 The platform runs with or without the `kj` binary (`is_configured()`
 guard). All existing tests pass (NullEngine fallback when `policy` key
 absent in test config — but the v1.25 config.json *sets* the key, so
 existing tests that use the real config get `KyvernoJsonEngine` with
 `is_configured()==false` → `SKIPPED`).
 **Files touched:**
 - `core/policy_engine.py` (NEW)
 - `.ciagent/config.json` (MODIFIED — `policy` object)
 - `adapters/kyverno-json/__init__.py` (NEW)
 - `adapters/kyverno-json/kyverno_json_engine.py` (NEW)
 - `adapters/kyverno-json/policies/_smoke.json` (NEW)
 - `scripts/install-kyverno-json.sh` (NEW)
 - `.github/workflows/ci.yml` (MODIFIED — Go + kj install step)
 - `.gitea/workflows/ci.yml` (MODIFIED — Go + kj install step)
 - `tests/test_policy_engine.py` (NEW)
 - `tests/test_kyverno_json_engine.py` (NEW)
 **Verification:** `pytest tests/test_policy_engine.py
 tests/test_kyverno_json_engine.py tests/test_confidence_signal.py
 tests/test_adapter.py tests/test_checkov_adapter.py
 tests/test_kyverno_adapter.py -v` (new tests pass or skip-without-kj;
 existing adapter/confidence tests unchanged). `python3 -m py_compile
 core/policy_engine.py adapters/kyverno-json/kyverno_json_engine.py`.
 ---
-### Phase P2 — contract + stack-IR policies (Wave 2, policy-engineer + backend-engineer)
+## Phase 0 — Pre-Execution (complete, tag v1.25.0)
-**Type:** `feat` (policies + resolver wiring + tests)
+SPECIFY → CLARIFY → RESEARCH → IDEATE → PLAN → GRILL. All `.ciagent/`
 MD, research, plans. Ships as `v1.25.0` on the v1.25.x line.
-**Requirements:** REQ-295, REQ-296, REQ-297, REQ-298, REQ-299
+**Pre-run (Workstream A, on main before branch gate):**
 - A1: flaky test fix (commit `8c68d68`, pushed).
 - A2: ACDL_*→NOVA_* bootstrap migration (commit `f844fea`, pushed).
 - A3: AWS bootstrap — S3 state bucket + DynamoDB outbox created.
 - A4: `nova-blockchain-exchange` Gitea repo created + cloned.
-**Must-haves:**
+**Phase 0 stages (on `phase/00-specify-clarify-research-plan`):**
- `adapters/kyverno-json/policies/contract/` — 4 policies over consumer
+- SPECIFY: v1.26 established in config.json + PROJECT.md + ROADMAP.md +
-  contract JSON: `require-id-pattern.json`,
+  `.ciagent/nova-blockchain-exchange/{PROJECT,REQUIREMENTS,ROADMAP}.md`.
-  `require-env-in-enum.json`, `require-infrastructure-min-1.json`,
+- CLARIFY: 10 ambiguities resolved (D-200..D-213).
-  `forbid-unknown-fields.json` — each a `ValidatingPolicy` with one
+- RESEARCH: PoA blockchain, deploy model, DynamoDB gap (REQ-322),
-  `validate.assert` rule using JMESPath against the payload root;
+  metric grounding, persona assessment (5 personas).
-  severity via `nova.cloudinit.dev/severity` annotation (REQ-295)
+- IDEATE: 7 ideas accepted (I1..I7 → REQ-315..322), 3 deferred.
- `core/contract_resolver.py` invokes
+- PLAN: this file.
-  `PolicyEngineRegistry.get_engine().evaluate(contract_dict,
+- GRILL: adversarial review (binding verdicts).
  policies/contract/, contract_id)` **before** resolving; failures
  feed the `policy` input as `fail` PCRs (no resolver exit — confidence
  signal decides the gate, `--soft-fail` pattern); emits
  `nova.policy.evaluated` metrics event (REQ-296)
 - `adapters/kyverno-json/policies/stack-ir/` — 3 policies over
  resolved Stack IR: `require-tagging-standard.json` (ports
  `nova_tagging.py` — `nova:owner` + `nova:environment` tags on every
  `resources[]` entry), `forbid-public-ingress.json` (v1.0 demo rule),
  `require-encryption-by-default.json` (v1.8 D-encryption-default);
  `~` modifier iterates `resources[]` (REQ-297)
 - `core/contract_resolver.py` invokes the engine with the resolved
  Stack IR and `policies/stack-ir/` **after** resolving; resulting PCRs
  appended to the contract-policy PCRs; resolver return values and
  exceptions unchanged (additive) (REQ-298)
 - `tests/test_stack_ir_policies.py` + `tests/fixtures/stack_ir/` —
  passing IR (all tags + encryption) + failing IR (missing tags, public
  ingress, plaintext bucket); each policy in isolation + full dir as
  bundle; `pytest.skip("kj not installed")` when `which kj` absent
  (REQ-299)
 **Vertical slice:** A consumer contract passes through the resolver
 and produces two PCR lists (contract policies pre-resolve, stack-IR
 policies post-resolve) that feed the confidence signal. A contract
 with a bad `id` or missing tags produces `fail` PCRs that lower the
 confidence score. The resolver's existing tests pass unchanged (the
 policy call is additive — it does not change resolver return values
 or exceptions).
 **Files touched:**
 - `adapters/kyverno-json/policies/contract/require-id-pattern.json` (NEW)
 - `adapters/kyverno-json/policies/contract/require-env-in-enum.json` (NEW)
 - `adapters/kyverno-json/policies/contract/require-infrastructure-min-1.json` (NEW)
 - `adapters/kyverno-json/policies/contract/forbid-unknown-fields.json` (NEW)
 - `adapters/kyverno-json/policies/stack-ir/require-tagging-standard.json` (NEW)
 - `adapters/kyverno-json/policies/stack-ir/forbid-public-ingress.json` (NEW)
 - `adapters/kyverno-json/policies/stack-ir/require-encryption-by-default.json` (NEW)
 - `core/contract_resolver.py` (MODIFIED — pre/post resolve engine calls)
 - `tests/test_stack_ir_policies.py` (NEW)
 - `tests/fixtures/stack_ir/passing.json` (NEW)
 - `tests/fixtures/stack_ir/failing.json` (NEW)
 **Verification:** `pytest tests/test_contract_resolver.py
 tests/test_stack_ir_policies.py tests/test_policy_engine.py -v`
 (existing resolver tests pass; new policy tests pass or skip-without-
 kj). `python3 -m py_compile core/contract_resolver.py`.
 ---
-### Phase P3 — plan-JSON policies + meta-orchestration + pipeline wiring (Wave 3, policy-engineer + backend-engineer)
+## Phase 1 — blockchain-core (tag v1.25.1)
-**Type:** `feat` (plan-JSON policies + meta-policies + run_platform.sh wiring + tests)
+**Goal:** The consumer repo has a working homegrown PoA blockchain +
 order-matching engine + settlement service. All unit tests pass in the
 consumer repo's own CI.
-**Requirements:** REQ-300, REQ-301, REQ-302, REQ-303
+**Project:** `nova-blockchain-exchange` (consumer repo).
 **Branch:** `nova-blockchain-exchange/phase/01-blockchain-core`.
 **Persona:** blockchain-engineer (primary), lead-developer (coordination).
-**Must-haves:**
+### Wave 1 — chain core (REQ-310)
- `adapters/kyverno-json/policies/plan-json/` — 3 policies over
+- **Task 1.1** (blockchain-engineer): `chain/block.py` — Block dataclass
-  `terraform show -json` output: `forbid-plaintext-secrets.json` (ports
+  (index, timestamp, prev_hash, transactions, nonce, hash).
-  CKV_AWS_41/45/46), `forbid-iam-wildcard.json` (ports CKV_AWS_1/40),
+  `compute_hash()` deterministic (SHA-256). Unit test: `test_block.py`.
-  `require-kms-reference.json` (ports CKV_AWS_7/33); JMESPath over
+- **Task 1.2** (blockchain-engineer): `chain/ledger.py` — Ledger class:
-  `planned_values.root_module.resources[]` (REQ-300)
+  `append_block()`, `verify_chain()`, `get_block(index)`,
- `run_platform.sh` Step 5 gains a parallel kyverno-json pass: after
+  `get_latest_block()`. Genesis block on init. Unit test: `test_ledger.py`.
-  Checkov/Wiz produce raw PCRs, the script runs
+- **Task 1.3** (blockchain-engineer): `chain/validator.py` — PoA
-  `kj scan --policy adapters/kyverno-json/policies/plan-json/
+  validator: single validator (config-driven), `propose_block(transactions)`
-  --payload <tfshow.json> -o json` and pipes through
+  → Block, `commit_block(block)`. Unit test: `test_validator.py`.
  `adapters/kyverno-json/kyverno_json_engine.py` to produce a second
  PCR list; both lists concatenated and fed to the confidence signal;
  `nova.policy.evaluated` event with both engine names; when
  `which kj` is false, logs and proceeds with Checkov/Wiz list only
  (no hard failure) (REQ-301)
 - `tests/test_plan_json_policies.py` + `tests/fixtures/plan_json/` —
  passing plan (no secrets, no wildcard, KMS alias) + failing plan
  (plaintext password, `Action: "*"`, inline KMS key); policies in
  isolation + bundle; `tests/test_run_platform_plan_json_policies.py`
  asserts `run_platform.sh` has the kyverno-json Step 5 block +
  concatenates PCR lists (script-substring assertion, pattern from
  `tests/test_pipeline.py:79-95`) (REQ-302)
 - `adapters/kyverno-json/policies/meta/` — `block-on-any-critical.json`
  (asserts no PCR in merged list has `severity: critical` + `result:
  fail`; if any does, emits `fail` PCR `KJ_META_BLOCK_CRITICAL`
  severity `critical` — declarative source of truth; the
  `confidence_signal.py` hard-override stays as defense-in-depth per
  D-119) + `tagging-rules-agree.json` (cross-checks Checkov
  `NOVA_TAG_NAMING` vs kj `KJ_REQUIRE_TAGGING_STANDARD` by
  `resourceRef`; divergence emits `error` PCR per D-118);
  `tests/test_meta_policies.py` (REQ-303)
-**Vertical slice:** `run_platform.sh` Step 5 produces a merged PCR list
+### Wave 2 — order engine + settlement (REQ-311, REQ-312) — parallel with Wave 1 tail
-(Checkov/Wiz + kj plan-JSON policies + kj meta-policies over the
+- **Task 2.1** (blockchain-engineer): `engine/order.py` — Order
-merged list) that feeds the confidence signal. A plan with a plaintext
+  dataclass (id, side, symbol, price, size, timestamp).
-secret produces two `fail` PCRs (one Checkov, one kj) for the same
+- **Task 2.2** (blockchain-engineer): `engine/order_book.py` —
-resource — visible defense-in-depth. A critical finding anywhere
+  OrderBook: `add_order(order)`, `match_orders()` → list of Match
-produces a `KJ_META_BLOCK_CRITICAL` meta-PCR that the confidence
+  (price-time priority, partial fills). Unit test: `test_order_book.py`.
-signal's hard-override blocks. The pipeline runs with or without `kj`
+- **Task 2.3** (blockchain-engineer): `settlement/service.py` —
-(graceful skip).
+  SettlementService: `settle(match)` → SettlementTransaction,
  `submit(ledger)`. Idempotent (re-settling a match is a no-op once
  final). Finality = block commit. Unit test: `test_settlement.py`.
-**Files touched:**
+### Wave 3 — consumer CI (cross-cutting)
- `adapters/kyverno-json/policies/plan-json/forbid-plaintext-secrets.json` (NEW)
+- **Task 3.1** (blockchain-engineer): `.github/workflows/ci.yml` +
- `adapters/kyverno-json/policies/plan-json/forbid-iam-wildcard.json` (NEW)
+  `.gitea/workflows/ci.yml` — lint + pytest on chain/engine/settlement.
- `adapters/kyverno-json/policies/plan-json/require-kms-reference.json` (NEW)
+- **Task 3.2** (lead-developer): `nova-blockchain-exchange/README.md` —
- `adapters/kyverno-json/policies/meta/block-on-any-critical.json` (NEW)
+  repo overview + dev setup.
 - `adapters/kyverno-json/policies/meta/tagging-rules-agree.json` (NEW)
 - `scripts/run_platform.sh` (MODIFIED — Step 5 kj parallel pass)
 - `tests/test_plan_json_policies.py` (NEW)
 - `tests/test_meta_policies.py` (NEW)
 - `tests/test_run_platform_plan_json_policies.py` (NEW)
 - `tests/fixtures/plan_json/passing.json` (NEW)
 - `tests/fixtures/plan_json/failing.json` (NEW)
-**Verification:** `pytest tests/test_plan_json_policies.py
+**Must-haves (verify before ship):**
-tests/test_meta_policies.py tests/test_run_platform_plan_json_policies.py
+- `pytest tests/` in the consumer repo passes (chain integrity, hash
-tests/test_pipeline.py -v` (new tests pass or skip-without-kj; existing
+  determinism, genesis, append/verify, match priority, partial fills,
-pipeline tests pass). `python3 -m py_compile` on any modified Python.
+  settlement idempotency, finality check).
-Shellcheck on `run_platform.sh` if available.
+- The chain is deterministic (replay produces the same hash chain).
 - The consumer CI workflow runs on push.
 **Ship:** tag `v1.25.1`, merge `phase/01` → `milestone/v1.26-pilot-activation`,
 Gitea release (best-effort). Delete `phase/01`.
 ---
-### Phase P4 — regression-gate policies + docs (Wave 4, policy-engineer + data-engineer + lead-developer)
+## Phase 2 — consumer-contract-and-deploy (tag v1.25.2)
-**Type:** `feat` (regression policies) + `docs` (adapter READMEs + ARCHITECTURE + STANDARDS + METRICS)
+**Goal:** The consumer repo declares its infrastructure via
 `contract.yaml` (validated against the platform's schema) + invokes the
 platform's `deploy.yml@v1.25` workflow. The contract references the
 `microservice` (ECS), `dynamodb`, + `s3` modules.
-**Requirements:** REQ-304, REQ-305, REQ-306, REQ-307
+**Project:** `nova-blockchain-exchange` (consumer repo) + `acdl`
 (platform repo — for the `deploy.yml@v1.25` ref + the `v1.25` floating
 tag).
 **Branch:** `nova-blockchain-exchange/phase/02-contract-and-deploy`.
 **Persona:** blockchain-engineer (contract authoring), data-engineer
 (registry/DynamoDB dependency check), lead-developer (deploy.yml ref).
-**Must-haves:**
+### Wave 1 — contract (REQ-313)
- `adapters/kyverno-json/policies/regression/` — 3 policies over
+- **Task 1.1** (blockchain-engineer): `contract.yaml` — id
-  capability-inventory JSON frontmatter: `cap-013-adapter-dedup.json`,
+  (`blkex`), name (`blockchain-exchange`), environment (dev),
-  `cap-023-metrics-collector.json`, `cap-024-deck-structure.json`;
+  infrastructure block (microservice + dynamodb + s3).
-  emit `pass`/`fail` PCRs per capability; the existing
+- **Task 1.2** (blockchain-engineer): `contracts/blockchain-exchange.dev.yml`,
-  `core/regression_verify.py` is kept (drives the CI gate); the
+  `.qa.yml`, `.prod.yml` — per-env variants.
-  policies are the declarative mirror (REQ-304)
+- **Task 1.3** (blockchain-engineer): `tests/test_contract_validates.py`
- `tests/test_regression_policies.py` +
+  — schema validation against the platform's
-  `tests/fixtures/capability_inventory/clean.json` +
+  `schemas/contract.schema.json`.
  `tests/fixtures/capability_inventory/drifted.json` — clean (all caps
  pass) + drifted (duplicate adapter, missing metric status, broken
  deck arc); regression gate still 287/287 baseline (new tests
  additive, skip-without-kj) (REQ-305)
 - `adapters/README.md` gains new kyverno-json adapter row + "Policy
  Engine Protocol" section (Protocol, registry, swap boundary,
  how-to-add-OpaEngine); `adapters/kyverno-json/README.md` documents
  the engine, install path, policy directory layout, 4 policy
  categories (REQ-306)
 - `.ciagent/ARCHITECTURE.md` §12.7 (added in RESEARCH) is finalized;
  `schemas/README.md` notes `engine: "kyverno"` shared by K8s adapter
  + kj (distinguished by `ruleId` prefix); `modules/STANDARDS.md`
  gains "Policy authoring standard" section for module owners;
  `docs/METRICS.md` notes the policy engine is swappable (Strategic
  Objective #2 — provable trust via a replaceable substrate) (REQ-307)
-**Vertical slice:** The regression gate's capability checks are now
+### Wave 2 — deploy invocation (REQ-314)
-declarative policies auditable as artifacts. A new module owner can
+- **Task 2.1** (blockchain-engineer): `.github/workflows/deploy.yml` —
-read `modules/STANDARDS.md` "Policy authoring standard" and write a
+  `uses: acdl/.github/workflows/deploy.yml@v1.25` with
-per-module kyverno-json policy. A new engineer can read
+  `with: { contract: contract.yaml, mode: full, environment: dev }`.
-`adapters/README.md` "Policy Engine Protocol" and implement an
+- **Task 2.2** (blockchain-engineer): `.gitea/workflows/deploy.yml` —
-`OpaEngine`. The 287/287 baseline is unchanged.
+  byte-identical mirror.
 - **Task 2.3** (blockchain-engineer): `tests/test_deploy_workflow_invocation.py`
  — asserts the `uses:` ref + inputs.
-**Files touched:**
+### Wave 3 — platform floating tag (cross-cutting)
- `adapters/kyverno-json/policies/regression/cap-013-adapter-dedup.json` (NEW)
+- **Task 3.1** (lead-developer, on `acdl` repo): verify the `v1.25`
- `adapters/kyverno-json/policies/regression/cap-023-metrics-collector.json` (NEW)
+  floating tag exists (created by `release.yml` on merge to main). If
- `adapters/kyverno-json/policies/regression/cap-024-deck-structure.json` (NEW)
+  not, create it pointing at the `v1.25.0` tag (Phase 0 ship).
 - `tests/test_regression_policies.py` (NEW)
 - `tests/fixtures/capability_inventory/clean.json` (NEW)
 - `tests/fixtures/capability_inventory/drifted.json` (NEW)
 - `adapters/README.md` (MODIFIED — new row + PolicyEngine Protocol section)
 - `adapters/kyverno-json/README.md` (NEW)
 - `schemas/README.md` (MODIFIED — engine enum note)
 - `modules/STANDARDS.md` (MODIFIED — Policy authoring standard section)
 - `docs/METRICS.md` (MODIFIED — swappable engine narrative)
-**Verification:** `pytest tests/test_regression_policies.py
+**Must-haves (verify before ship):**
-tests/test_kyverno_json_engine.py -v` (new tests pass or skip-without-
+- `contract.yaml` validates against `schemas/contract.schema.json`.
-kj). Full regression gate `pytest tests/` still at 287/287 baseline +
+- The deploy workflow invocation asserts the correct `uses:` ref +
-new tests (skip without kj). Manual read of `adapters/README.md` +
+  inputs.
-`adapters/kyverno-json/README.md` + `modules/STANDARDS.md` policy
+- The `v1.25` floating tag resolves.
-section for clarity.
+
 **Ship:** tag `v1.25.2`, merge `phase/02` → milestone, Gitea release.
 Delete `phase/02`.
 ---
-### Phase P5 — final review + audit + milestone ship (Final Phase)
+## Phase 3 — pilot-metrics-and-policies (tag v1.25.3)
-**Type:** `docs` (review + audit + milestone completion)
+**Goal:** The platform repo gains the metric-grounding emitters, the
 kyverno-json pilot policies, the DynamoDB L1 primitive, the env-JSON
 wiring reconciliation, + the pilot regression CAP. The Post-Pilot
 metrics are grounded (outcome backfill + escalation reason); the pilot-
 readiness + settlement-finality policies are in place.
-**Requirements:** All REQ-291..309 (mark complete)
+**Project:** `acdl` (platform repo) + `nova-blockchain-exchange`
 (consumer repo — the Gitea adapter rewrites the consumer's `deploy.yml`).
 **Branch:** `acdl/phase/03-pilot-metrics-and-policies` (platform branch).
 **Personas:** backend-engineer (emitters + adapter + regression),
 data-engineer (DynamoDB primitive + env JSON + collector),
 policy-engineer (kyverno-json policies), lead-developer (Gitea adapter
 + deploy.yml drift + rotation workflow).
-**Must-haves:**
+### Wave 0 — Gitea reusable-workflow adapter (SPEC §10 Q1, resolved by evidence) — lead-developer + blockchain-engineer
- `ciagent-review` multi-persona code review across P1..P4
+> **Highest-priority gap.** The v0.2 P3 `workflow_dispatch` (Gitea
-  (lead-developer, backend-engineer, data-engineer, policy-engineer).
+> Actions run id=6199) failed: Gitea Actions rejects cross-repo `uses:`
-  Auto-fix P0; flag P1+ for post-hoc review. If P1+ issues found, fix
+> (`acdl/.github/workflows/deploy.yml@v1.25`) with `expected format
-  them in this final phase (not loop back to EXECUTE).
+> {owner}/{repo}/.{git_platform}/workflows/{filename}@{ref}`. The
- `ciagent-audit` — reconstruction test (git log ↔ `.ciagent/` files),
+> consumer's `deploy.yml` is frozen at the v0.1 byte-identical mirror;
-  `.ciagent/` file discipline, branch hygiene, commit discipline.
+> the platform adapts (option c — inline checkout-then-call), not
-  Critical issues fixed in this phase.
+> vice-versa.
- `ciagent-ship` (milestone) — merge `phase/05-final-review-ship` →
+- **Task 0.1** (lead-developer): rewrite
-  `milestone/v1.25-kyverno-json` → `main`; tag `v1.24.5` (= the v1.25
+  `nova-blockchain-exchange/.gitea/workflows/deploy.yml` + byte-identical
-  release per the prev-minor tagging rule); create Gitea release with
+  `.github/workflows/deploy.yml` — drop the `uses:` indirection; single
-  full milestone summary (all phases, all requirements); delete all
+  `deploy` job on `ubuntu-latest` that `actions/checkout@v4` the consumer,
-  milestone branches (local + remote).
+  `actions/checkout@v4` `acdl/acdl` @ `ref: v1.25` into `platform/`,
- Update `REQUIREMENTS.md` (mark REQ-291..309 complete),
+  setup-python 3.12, install deps (jsonschema/pyyaml/boto3 + checkov),
-  `ROADMAP.md` (mark v1.25 complete), `CHECKPOINT.json`
+  install Terraform 1.9.*, configure AWS (static-key path:
-  (milestone_complete: true), `NORTH_STAR.md` (note Strategic
+  `aws-region: ${{ secrets.AWS_DEFAULT_REGION }}`, `access-key-id` +
-  Objective #2 — provable trust via a replaceable policy-engine
+  `secret-access-key` from `NOVA_AWS_*` secrets; no OIDC token minted),
-  substrate).
+  run `bash platform/scripts/run_platform.sh $MODE_FLAG $ENV_FLAG
  contract.yaml`. Preserve `on: workflow_dispatch` inputs (mode choice
  default full; environment choice default "") + `permissions: {id-token:
  write, contents: read}` + `secrets: inherit`.
 - **Task 0.2** (blockchain-engineer): update
  `nova-blockchain-exchange/tests/test_deploy_workflow_invocation.py` +
  `test_deploy_gitea_invocation.py` — assert no cross-repo `uses:`,
  assert `ref: v1.25`, assert `secrets: inherit`, assert
  `run_platform.sh` invoked, assert `AWS_DEFAULT_REGION` wired.
 - **Task 0.3** (lead-developer): `acdl/.github/workflows/deploy.yml`
  stays as the GitHub Actions reference impl (the `workflow_call`
  reusable workflow — used by GitHub-hosted consumers); document in
  `adapters/README.md` that Gitea consumers use the inline adapter, not
  the reusable `uses:`.
-**Vertical slice:** The v1.25 milestone is complete: kyverno-json is
+### Wave 0.5 — kyverno-json substrate fix (v1.25 skip-masked bug) — backend-engineer
-the primary policy tool, behind a swappable adapter, with policies
+> The v1.25 kyverno-json engine + policies were never validated
-over all 4 Nova artifacts. Tags v1.24.0..v1.24.5 on the v1.24.x line.
+> against the real `kj` binary (tests `pytest.skip("kj not installed")`
-The milestone branch merges to main.
+> when absent). With `kj` now installed (v0.0.3), 3 policy tests
 > failed. Root cause: (a) `kj` v0.0.3 does not load `.json` policy
 > files (only `.yaml`/`.yml`) — the engine now materializes `.yaml`
 > twins at runtime; (b) the `validate` wrapper is not supported —
 > `assert` goes directly under the rule; (c) the check syntax was
 > inverted (`expression: expected_value`, not `key: expression`);
 > (d) the engine `_translate` expected `{"results": [...]}` but `kj`
 > returns a bare list with `results[].policy.metadata.name` +
 > `results[].rules[].violations[]`. DONE (committed 59d837f). Also
 > fixed `scripts/install-kyverno-json.sh` (the `cmd/kj@latest` path
 > fails — the real binary is `kyverno-json`, symlinked as `kj`).
 - **Task 0.5.1** (backend-engineer): rewrite
  `adapters/kyverno-json/kyverno_json_engine.py` `_translate` for the
  bare-list output format + add `_materialize_yaml_policy_dir` (DONE).
 - **Task 0.5.2** (backend-engineer): remove the `validate` wrapper +
  fix check syntax across all 16 existing policies (DONE).
 - **Task 0.5.3** (backend-engineer): fix
  `scripts/install-kyverno-json.sh` (DONE).
 - **Task 0.5.4** (backend-engineer): resolve pre-existing P2 drift
  uncovered by the full-suite run — dynamodb `examples/simple.yml` +
  `complex.yml`, `sync_workflows` re-sync, CAP-024 deck path
  (`nova-autonomous-cloud-delivery-marp.md`) + slide-count bound +
  `class="benefit"` div count (DONE, committed 3735330).
-**Verification:** `pytest tests/ -v` full suite passes (287 baseline +
+### Wave 1 — DynamoDB primitive (REQ-322) — data-engineer — verify-only (done in P2 W0)
-new tests). `git log --oneline` shows the v1.25 phase commits.
+- **Task 1.1** (data-engineer): verify `modules/l1/dynamodb/` resolves
-`git tag` shows v1.24.0..v1.24.5. `git branch` shows no leftover
+  + emits valid Terraform via `tests/test_adapter.py` (the primitive
-milestone/phase branches (all deleted post-ship).
+  shipped in P2 W0; this wave is a re-verify, not re-authoring).
 ### Wave 2 — metric grounding (REQ-317, REQ-318) — backend-engineer + data-engineer — parallel
 - **Task 2.1** (backend-engineer): `core/metrics/outcome_backfill.py` —
  `backfill(decision_id, outcome)` updates `fact_decision.outcome` +
  `backfilled_at`. Reads run-manifest events.
 - **Task 2.2** (backend-engineer): `core/metrics/collector.py` —
  invokes backfill after run completion.
 - **Task 2.3** (backend-engineer): `tests/test_outcome_backfill.py`.
 - **Task 2.4** (backend-engineer): `core/confidence_signal.py` —
  `ai.decision.made` gains `escalation_reason: 'confidence'` when
  `band == 'block'`.
 - **Task 2.5** (backend-engineer): `core/metrics/collector.py` —
  persists `escalation_reason` into `fact_run`.
 - **Task 2.6** (backend-engineer): `tests/test_confidence_escalation_reason.py`.
 ### Wave 3 — env-JSON wiring + adapter (REQ-319) — backend-engineer + data-engineer — parallel
 - **Task 3.1** (backend-engineer): `adapters/terraform/adapter.py` —
  reads `env.state_backend.bucket` when present (fallback to computed
  name for backwards compat).
 - **Task 3.2** (data-engineer): `core/environments/dev.json` —
  `account_id` → `581513795199`, `state_backend.bucket` →
  `nova-tfstate-581513795199-us-east-1`.
 - **Task 3.3** (data-engineer): `core/environments/{qa,prod,dr}.json` —
  `state_backend.bucket` updated; `account_id` stays placeholder
  (pilot-readiness policy blocks apply on placeholder, D-208).
 - **Task 3.4** (backend-engineer): `tests/test_adapter_state_backend.py`.
 - **Task 3.5** (backend-engineer): `tests/test_adapter.py` — add
  `dynamodb` to `EXPECTED_L1_KEYS` + a resolution + emission test
  (cross-territory: data-engineer authored the module, backend-engineer
  owns the test).
 ### Wave 4 — kyverno-json policies (REQ-315, REQ-320) — policy-engineer — parallel
 - **Task 4.1** (policy-engineer):
  `adapters/kyverno-json/policies/settlement-finality/all-matches-committed.json`
  — kyverno-json policy over settlement-service status JSON (asserts
  `all_committed: true`). **Note (G-Q6):** the policy is authored +
  tested in v1.26; *enforcement* is deferred to the milestone that
  binds qa/prod/dr (D-208 — the policy gates promotions, not dev
  applies).
 - **Task 4.2** (policy-engineer):
  `adapters/kyverno-json/policies/pilot-readiness/no-placeholder-account.json`
  — kyverno-json policy over env JSON (asserts
  `account_id != "000000000000"`).
 - **Task 4.3** (policy-engineer): `tests/test_settlement_finality_policy.py`
  — passing + failing fixtures; **runs against real `kj`** (not skipped
  — `kj` is installed via `scripts/install-kyverno-json.sh`).
 - **Task 4.4** (policy-engineer): `tests/test_pilot_readiness_policy.py`
  — passing (real account) + failing (placeholder) fixtures; **runs
  against real `kj`** (not skipped).
 ### Wave 5 — regression CAP (REQ-316) — backend-engineer
 - **Task 5.1** (backend-engineer): `core/regression_verify.py` —
  CAP-025 (live-pilot-apply): the round-trip assertion.
 - **Task 5.2** (backend-engineer): `tests/test_regression_pilot.py`.
 ### Wave 6 — deploy.yml drift fixes (SPEC §5.1/§5.2) — lead-developer + backend-engineer
 > The platform reference `workflows-src/deploy.yml` (synced to
 > `.github`+`.gitea`) has three drifts vs the SPEC: (a) `aws-region`
 > hardcoded `us-east-1` (SPEC wants `NOVA_AWS_REGION`/`AWS_DEFAULT_REGION`
 > from secret); (b) platform checkout `ref: v1.9` (SPEC wants `v1.25`);
 > (c) the local `scripts/run_platform.sh` fallback exports raw
 > `NOVA_AWS_*` names into shell env (SPEC §5.2 constraint: consume as
 > workflow secrets, not shell env — `blocked_env_vars`).
 - **Task 6.1** (lead-developer): `workflows-src/deploy.yml` —
  `aws-region: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}`;
  platform checkout `ref: v1.25`; re-sync to `.github`+`.gitea`.
 - **Task 6.2** (backend-engineer): `scripts/run_platform.sh` — source
  `AWS_DEFAULT_REGION` from `.env.secrets` for the local fallback (not
  raw `NOVA_AWS_*`); the CI path already consumes secrets via the
  `configure-aws-credentials` action.
 - **Task 6.3** (backend-engineer): `tests/test_deploy_workflow_env_input.py`
  — assert `AWS_DEFAULT_REGION` wired + `ref: v1.25` + no raw
  `NOVA_AWS_*` in shell env.
 ### Wave 7 — secret rotation scheduled workflow (SPEC §5.9) — lead-developer
 > SPEC §5.9: "the rotation mechanism must *exist* (not have run)."
 > A platform-managed scheduled workflow wraps the existing
 > `scripts/rotate_spike_key.sh` (manual today) on a daily cron.
 - **Task 7.1** (lead-developer): `workflows-src/rotate-aws-key.yml` —
  `on: { schedule: [{cron: "0 0 * * *"}], workflow_dispatch:}`,
  single job that checks out the platform repo + runs
  `bash scripts/rotate_spike_key.sh` with `NOVA_AWS_*` bootstrap
  secrets; sync to `.github`+`.gitea`.
 - **Task 7.2** (lead-developer): verify `scripts/rotate_spike_key.sh`
  is idempotent (deactivates old key only after the new key propagates
  to the Gitea Actions secret store).
 - **Task 7.3** (lead-developer): `tests/test_rotate_key_workflow.py` —
  structural test (the workflow file declares `schedule` + invokes
  `rotate_spike_key.sh`); document in `.ciagent/ARCHITECTURE.md` §12.8
  that the mechanism exists (v0.2 scope: exists-not-ran per SPEC §5.9).
 **Must-haves (verify before ship):**
 - `pytest tests/` in the platform repo passes (the 170 baseline held
  inaccurately — the real P2 baseline had 7 pre-existing failures
  uncovered by W0.5; all now fixed). Full suite green.
 - `pytest tests/` in the consumer repo passes (deploy invocation tests
  updated for the inline adapter).
 - The kyverno-json substrate works against real `kj` (W0.5 — DONE).
 - The Gitea adapter: consumer `deploy.yml` has no cross-repo `uses:`;
  inline checkout `acdl@v1.25` + `run_platform.sh` (W0).
 - The DynamoDB primitive resolves + emits valid Terraform (W1 verify).
 - The outcome backfill updates `fact_decision.outcome` (not `pending`)
  (W2).
 - The `escalation_reason` field is emitted on `block` band (W2).
 - The adapter reads `env.state_backend.bucket` from the env JSON (W3).
 - The 2 new kyverno-json policies pass on valid fixtures + fail on
  invalid fixtures, against real `kj` (W4 — not skipped).
 - CAP-025 is in the regression gate (W5).
 - The deploy.yml drifts fixed: `AWS_DEFAULT_REGION` wired, `ref:
  v1.25`, no raw `NOVA_AWS_*` in shell env (W6).
 - The rotation scheduled workflow exists (W7).
 **Ship:** tag `v1.25.3`, merge `phase/03` → milestone, Gitea release.
 Delete `phase/03`.
 ---
-## Wave ordering (parallelization)
+## Phase 4 — pilot-run-and-docs (tag v1.25.4)
-With `parallelization.enabled: true`, `max_concurrent_agents: 5`,
+**Goal:** The pilot estate runs end-to-end against live AWS
-`min_plans_for_parallel: 2`:
+`581513795199` (contract resolve → adapter compile → terraform plan →
 policy scan → confidence signal → attestation → outbox record). Docs +
 adapter README + onboarding guide are complete.
- **P1 Wave 1:** backend-engineer (protocol + registry + install) ‖
+**Project:** `nova-blockchain-exchange` (consumer repo — the run) +
-  data-engineer (config.json policy object) ‖ policy-engineer (engine
+`acdl` (platform repo — docs).
-  adapter + smoke policy). 3 concurrent personas. Merge in order:
+**Branch:** `acdl/phase/04-pilot-run-and-docs` (platform branch for
-  data-engineer → backend-engineer → policy-engineer.
+docs); the run happens via the consumer's `deploy.yml` invocation.
- **P2 Wave 2:** policy-engineer (contract + stack-IR policies) ‖
+**Personas:** blockchain-engineer (the run), lead-developer (docs),
-  backend-engineer (resolver wiring — depends on P1 registry). 2
+backend-engineer (regression CAP-025 verification).
  concurrent. Merge: policy-engineer → backend-engineer (wiring
  references the policy dirs).
 - **P3 Wave 3:** policy-engineer (plan-JSON + meta policies) ‖
  backend-engineer (run_platform.sh wiring — depends on P1 engine +
  P2 resolver pattern). 2 concurrent. Merge: policy-engineer →
  backend-engineer.
 - **P4 Wave 4:** policy-engineer (regression policies) ‖ data-engineer
  (capability-inventory fixtures) ‖ lead-developer (docs: READMEs,
  STANDARDS, METRICS). 3 concurrent. Merge: data-engineer →
  policy-engineer → lead-developer.
-Territory enforcement: `warn` mode (per `config.json
+### Wave 1 — the pilot run (REQ-316 verification, live)
-personas.territory_enforcement: "warn"`). Cross-territory edits
+- **Task 1.1** (blockchain-engineer): trigger the consumer's
-(e.g., backend-engineer touching a policy file) emit a warning, not a
+  `deploy.yml` with `mode: full, environment: dev` against
-block.
+  `581513795199`. The workflow checks out the consumer + platform
  repos, runs `run_platform.sh`, applies the contract (ECS +
  DynamoDB + S3), records the decision + attestation.
 - **Task 1.2** (backend-engineer): verify CAP-025 (regression gate)
  passes against the live run.
 - **Task 1.3** (blockchain-engineer): capture the run's
  `ai.decision.made` + `attestation.recorded` events from the Decision
  Ledger → evidence for the milestone ship.
-## Requirement → phase → persona matrix
+### Wave 2 — docs (REQ-321)
 - **Task 2.1** (lead-developer): `adapters/README.md` — new consumer
  row + fix the stale `TYPE_MAP` references (IDEATE I8).
 - **Task 2.2** (lead-developer): `docs/METRICS.md` — Post-Pilot metrics
  grounded note (the 3 targets now have non-zero denominators post-run).
 - **Task 2.3** (lead-developer): `.ciagent/ARCHITECTURE.md` §12.8
  (Pilot Estate).
 - **Task 2.4** (lead-developer):
  `.ciagent/nova-blockchain-exchange/README.md` — consumer onboarding
  guide (how to invoke `deploy.yml@v1.25`, what secrets to set, what
  the contract shape is).
-| REQ | Phase | Primary persona | Type |
+**Must-haves (verify before ship):**
-|-----|-------|-----------------|------|
+- The pilot run completes end-to-end (apply succeeds, decision recorded,
-| REQ-291 | P1 | backend-engineer | feat |
+  attestation recorded for dev — autonomous, no human approver).
-| REQ-292 | P1 | data-engineer | feat (config) |
+- CAP-025 passes.
-| REQ-293 | P1 | policy-engineer | feat |
+- The 3 Post-Pilot metrics have non-zero denominators (the run
-| REQ-294 | P1 | backend-engineer | feat (install) |
+  contributed to `fact_run` + `fact_decision`).
-| REQ-295 | P2 | policy-engineer | feat |
+- Docs are complete (adapter README, METRICS.md, ARCHITECTURE.md §12.8,
-| REQ-296 | P2 | backend-engineer | feat (wiring) |
+  consumer onboarding guide).
-| REQ-297 | P2 | policy-engineer | feat |
+
-| REQ-298 | P2 | backend-engineer | feat (wiring) |
+**Ship:** tag `v1.25.4`, merge `phase/04` → milestone, Gitea release.
-| REQ-299 | P2 | policy-engineer | test |
+Delete `phase/04`.
-| REQ-300 | P3 | policy-engineer | feat |
+
-| REQ-301 | P3 | backend-engineer | feat (pipeline) |
+---
-| REQ-302 | P3 | policy-engineer + backend-engineer | test |
+
-| REQ-303 | P3 | policy-engineer | feat (meta) |
+## Phase 5 — final review + audit + milestone ship (tag v1.25.5)
-| REQ-304 | P4 | policy-engineer | feat |
+
-| REQ-305 | P4 | policy-engineer + data-engineer | test |
+**Goal:** Multi-persona code review across P1..P4. Audit (reconstruction
-| REQ-306 | P4 | policy-engineer + lead-developer | docs |
+test, branch hygiene, commit discipline). Milestone ship: merge to main,
-| REQ-307 | P4 | lead-developer | docs |
+tag `v1.25.5` (= the v1.26 release), Gitea release with full milestone
-| REQ-308 | P1 | backend-engineer | test |
+summary, delete all milestone branches.
-| REQ-309 | P1 | policy-engineer | test |
+
 **Project:** both (`acdl` + `nova-blockchain-exchange`).
 **Branch:** `phase/05-final-review-ship`.
 **Personas:** lead-developer (review + audit + ship), backend-engineer
 (review), data-engineer (review), policy-engineer (review),
 blockchain-engineer (review — the chain core is reviewed).
 ### Wave 1 — review
 - **Task 1.1** (lead-developer): `ciagent-review` — multi-persona code
  review across P1..P4. Auto-fix P0; flag P1+ for post-hoc review.
 - **Task 1.2** (all personas): fix P0 issues in this phase.
 ### Wave 2 — audit
 - **Task 2.1** (lead-developer): `ciagent-audit` — reconstruction test
  (git log ↔ `.ciagent/`), branch hygiene, commit discipline.
 - **Task 2.2** (lead-developer): fix critical audit issues in this phase.
 ### Wave 3 — milestone ship
 - **Task 3.1** (lead-developer): merge `phase/05` →
  `milestone/v1.26-pilot-activation` → `main`.
 - **Task 3.2** (lead-developer): tag `v1.25.5` (= the v1.26 release per
  prev-minor tagging rule).
 - **Task 3.3** (lead-developer): create Gitea release with full milestone
  summary (all phases, all 13 requirements).
 - **Task 3.4** (lead-developer): delete all milestone branches (local +
  remote). Tags preserve all history.
 - **Task 3.5** (lead-developer): update `.ciagent/nova-blockchain-exchange/REQUIREMENTS.md`
  (mark REQ-310..322 complete), `.ciagent/ROADMAP.md` (mark v1.26
  complete), `.ciagent/NORTH_STAR.md` (note Strategic Objectives #1 +
  #3 — first real consumer estate; Post-Pilot denominators activated).
 - **Task 3.6** (lead-developer): write checkpoint `stage: complete,
  phase: 5, phase_role: final` + clear checkpoint (milestone complete).
 **Must-haves (verify before ship):**
 - Review: 0 P0 issues unfixed; P1+ flagged for post-hoc.
 - Audit: reconstruction test passes; branch hygiene clean; commit
  discipline clean.
 - Ship: `v1.25.5` tag exists; Gitea release created; milestone branches
  deleted; main has the milestone merge.
 ---
 ## Requirement → Phase Mapping
 | REQ | Phase | Wave | Persona |
 |---|---|---|---|
 | REQ-310 (blockchain core) | P1 | W1 | blockchain-engineer |
 | REQ-311 (order engine) | P1 | W2 | blockchain-engineer |
 | REQ-312 (settlement) | P1 | W2 | blockchain-engineer |
 | REQ-313 (contract.yaml) | P2 | W1 | blockchain-engineer |
 | REQ-314 (deploy invocation) | P2 | W2 | blockchain-engineer |
 | REQ-315 (settlement-finality policy) | P3 | W4 | policy-engineer |
 | REQ-316 (pilot regression CAP) | P3 | W5 + P4 W1 | backend-engineer |
 | REQ-317 (outcome backfill) | P3 | W2 | backend-engineer |
 | REQ-318 (escalation reason) | P3 | W2 | backend-engineer |
 | REQ-319 (env-JSON wiring) | P3 | W3 | backend + data-engineer |
 | REQ-320 (pilot-readiness policy) | P3 | W4 | policy-engineer |
 | REQ-321 (docs) | P4 | W2 | lead-developer |
 | REQ-322 (DynamoDB primitive) | P3 | W1 | data-engineer |
 ---
 ## Wave Ordering Rationale
 - **P1 W1 → W2:** the chain core (block + ledger + validator) must land
  before the order engine + settlement (they submit transactions to the
  ledger). W3 (CI) is cross-cutting + can land any time after W1.
 - **P2 W1 → W2:** the contract must land before the deploy invocation
  (the invocation references the contract). W3 (floating tag) is cross-
  cutting.
 - **P3 W1 (DynamoDB) first:** the contract (P2) references `dynamodb` —
  the primitive must exist before P2's contract can resolve. **Risk:**
  P2's contract references a module that doesn't exist until P3. Resolution: P2's contract is authored but the `test_contract_validates.py` test only checks schema validity (not registry resolution) — the registry resolution test is in P3 (after the primitive lands). The contract's `dynamodb` block is schema-valid (the schema is open); the registry resolution happens at apply time (P4).
  - **Alternative:** move REQ-322 to P2 W0 (before the contract). This
    avoids the P2→P3 dependency. **Decision: move REQ-322 to P2 W0.**
    See revised mapping below.
 ### Revised: REQ-322 → P2 W0
 REQ-322 (DynamoDB primitive) lands in P2 Wave 0 (before the contract)
 so the contract's `dynamodb` block resolves at registry time, not just
 schema time. This makes P2 self-contained: the primitive + the contract
 + the deploy invocation all land in P2.
 | REQ | Phase | Wave | Persona |
 |---|---|---|---|
 | REQ-310 (blockchain core) | P1 | W1 | blockchain-engineer |
 | REQ-311 (order engine) | P1 | W2 | blockchain-engineer |
 | REQ-312 (settlement) | P1 | W2 | blockchain-engineer |
 | REQ-322 (DynamoDB primitive) | P2 | W0 | data-engineer |
 | REQ-313 (contract.yaml) | P2 | W1 | blockchain-engineer |
 | REQ-314 (deploy invocation) | P2 | W2 | blockchain-engineer |
 | REQ-315 (settlement-finality policy) | P3 | W4 | policy-engineer |
 | REQ-316 (pilot regression CAP) | P3 | W5 + P4 W1 | backend-engineer |
 | REQ-317 (outcome backfill) | P3 | W2 | backend-engineer |
 | REQ-318 (escalation reason) | P3 | W2 | backend-engineer |
 | REQ-319 (env-JSON wiring) | P3 | W3 | backend + data-engineer |
 | REQ-320 (pilot-readiness policy) | P3 | W4 | policy-engineer |
 | REQ-321 (docs) | P4 | W2 | lead-developer |
 This revision is a binding plan decision (G-Q8 in the grill may
 challenge it).
 ---
 ## Future Hardening Items (not in v1.26 scope, documented per grill G-Q9)
 - **`NOVA_AWS_*` key-split:** v1.26 uses a single `NOVA_AWS_*` key with
  root-equivalent permissions (D-207, confirmed empirically by the
  bootstrap). A future hardening milestone should split this into a
  `NOVA_BOOTSTRAP_AWS_*` root key (bootstrap only) + a least-privilege
  `NOVA_AWS_*` runner key (the spike-runner pattern). The pilot scope
  (single account, no production workloads, OIDC default) bounds the
  risk.
 - **Multi-account landing zone:** qa/prod/dr on separate accounts (D-208
  keeps them placeholder in v1.26).
 - **D-083 lift:** S3 Object Lock + JWS tamper-evident ledger (when the
  pilot becomes a production system, D-204).
 - **Multi-validator BFT consensus:** D-201.
 - **Other security types:** bonds (T+2), derivatives, options (D-200).
@@ -1,438 +1,250 @@
-# Nova — v1.25 Research Findings
+# Nova — v1.26 Research Findings
-> Phase: research (pre-execution). Milestone: v1.25 (kyverno-json Unified
+> Phase: research (pre-execution). Milestone: v1.26 (Live Pilot Estate
-> Policy Engine). Status: research. Researcher: ci-researcher.
+> Activation). Status: research. Researcher: ci-researcher.
 > Autonomy: full.
-## 1. Problem domain
+---
-Nova's compliance/policy posture is fragmented across three engines with
+## 1. Domain — Homegrown PoA Blockchain for Securities Settlement
 three rule languages and three adapter shapes (see PROJECT.md v1.25
 "Why" for the full diagnosis). The `PolicyCheckResult` schema
 (`schemas/policy_check_result.schema.json`) is already the engine-agnostic
 contract that `core/confidence_signal.py` consumes — the *contract* is
 right; the *orchestration* is fragmented. There is no single declarative
 place where "what Nova considers compliant" lives. The K8s-only Kyverno
 adapter (`adapters/kyverno/`) can't help because it only speaks to K8s
 manifests and the platform emits Terraform (D-053).
-`kyverno-json` is the correction: a Kyverno-ecosystem runtime that applies
+### 1.1 Why a homegrown chain (not Ethereum/Solana/Hyperledger)
 Kyverno policies to **any** JSON/YAML payload. It becomes the **unified
 orchestrator** of compliance checks, behind a swappable `PolicyEngine`
 protocol so OPA can replace it one day. Checkov and Wiz remain as
 raw-finding adapters feeding *into* kyverno-json meta-policies.
-## 2. kyverno-json — the engine surface
+The pilot's purpose is to exercise the Nova platform's deploy/policy/
 attestation gates over a real consumer estate — not to build a
 production blockchain. A homegrown PoA ledger is the minimal viable
 chain: append-only blocks, single validator (pilot), SHA-256 hash chain,
 deterministic block production. It records every order, match, and
 settlement as transactions; settlement finality = block commit. This
 is sufficient to demonstrate that Nova's policy engine (kyverno-json)
 can assert settlement finality declaratively (REQ-315) and that the
 Decision Ledger captures the apply decision.
-### 2.1 What it is
+A production chain (Ethereum/Solana/Hyperledger) would be the *consumer
 app's* choice, not the platform's. The platform is chain-agnostic — it
 deploys whatever the consumer's `contract.yaml` declares. For the pilot,
 the homegrown chain is the simplest way to produce a real consumer
 estate without a heavyweight external dependency.
-[kyverno-json](https://github.com/kyverno/kyverno-json) is a standalone Go
+### 1.2 PoA consensus — single validator (pilot)
 binary from the Kyverno project. It is a **separate runtime** from the
 Kyverno K8s admission controller — same policy lineage, different
 application target. Where Kyverno (K8s) evaluates `ClusterPolicy`
 resources against Kubernetes manifests at admission time, kyverno-json
 evaluates `ValidatingPolicy` resources against **any** JSON or YAML
 payload file via the CLI (`kj scan`) or a Go library. It is **not** a
 Python package (no PyPI release); it is installed via
 `go install github.com/kyverno/kyverno-json/cmd/kj@latest` (D-115) or by
 downloading a pinned binary from GitHub releases.
-### 2.2 CLI surface (the v1.25 invocation path)
+Proof-of-Authority with a single validator is the minimal consensus
 model: the validator proposes + commits blocks. No Byzantine fault
 tolerance (single validator = no forks). Deterministic block
 production: same ordered transactions → same block (same hash). This
 makes the chain auditable (the hash chain is verifiable) and
 reproducible (a replay produces the same chain). Multi-validator BFT
 is a future milestone (D-201).
-The v1.25 engine uses the `kj scan` subcommand:
+### 1.3 T+1 settlement finality
-```
+Equities settle T+1 (trade date + 1 business day). The pilot's
-kyverno-json scan [flags]
+settlement service records matches as transactions on the chain; a
 settlement is final when its block is committed. The settlement-finality
 kyverno-json policy (REQ-315) asserts `all_committed: true` before any
 promotion (qa→prod) — the declarative gate that turns settlement
 finality into a policy artifact. This is the securities-specific
 extension of v1.25's policy engine: the same `KyvernoJsonEngine`
 evaluates a policy over a new payload shape (settlement-service status
 JSON).
-Flags:
+### 1.4 Equities-only scope (D-200)
  --labels strings     Labels selectors for policies
  --output string      Output format (text or json) (default "text")
  --payload string     Path to payload (json or yaml file)
  --policy strings     Path to kyverno-json policies
  --pre-process strings  JMESPath expression used to pre process payload
 ```
-The `KyvernoJsonEngine.evaluate()` implementation (REQ-293) invokes:
+Bonds (T+2), derivatives (varying), and options (exercise models) have
-```
+different settlement models. A pilot should demonstrate the Nova
-kj scan --policy <policy_dir> --payload <payload.json> --output json
+platform's gates over the simplest case (equities T+1) before
-```
+expanding. "All types of securities" is the product vision; v1.26 is
-and parses the JSON `results[]` array. The `--pre-process` flag is
+the pilot (equities first). Future milestones add other security types
-available for JMESPath pre-projection (noted for the meta-policy use case
+with their settlement models.
 where the payload is the merged PCR list and a pre-process expression
 can index by `ruleId` — recorded as a future optimization, not used in
 v1.25's initial implementation).
-Other subcommands (`kj jp`, `kj serve`, `kj playground`, `kj docs`) are
+---
 out of scope for v1.25. `kj serve` is the long-running web-app mode
 (noted as a future consideration for lower-latency evaluation in the
 Out of Scope section of REQUIREMENTS.md). `kj jp` is the JMESPath REPL —
 useful for policy authoring/debugging, not invoked by the engine.
-### 2.3 Policy structure (the `ValidatingPolicy` resource)
+## 2. Nova Consumer Deploy Model
-kyverno-json policies are Kubernetes-style resources (cluster-scoped)
+### 2.1 The reusable `deploy.yml@v1.25` workflow
 belonging to the `json.kyverno.io` API group, kind `ValidatingPolicy`,
 version `v1alpha1`:
-```yaml
+The platform's `.github/workflows/deploy.yml` is a `workflow_call` —
-apiVersion: json.kyverno.io/v1alpha1
+a reusable workflow that a consumer repo invokes via
-kind: ValidatingPolicy
+`uses: acdl/.github/workflows/deploy.yml@v1.25`. Inputs: `contract`
-metadata:
+(default `.nova/contract.yml`), `mode` (default `full`; enum
-  name: <policy-name>           # becomes the KJ_<policy-name> ruleId prefix
+`full|plan-only|check-only|decommission`), `environment` (override).
-spec:
+The workflow checks out the consumer repo + the platform repo, runs
-  rules:
+`scripts/run_platform.sh`, and records the apply decision +
-    - name: <rule-name>
+attestation in the Decision Ledger. Secrets: `NOVA_AWS_*`
-      identifier: <jmespath>     # optional — path to the unique entry id
+(account + access key + secret) + `NOVA_LAMBDA_URL` (error reporting).
      match:                    # assertion tree — which payload entries
        any:                     #   the rule applies to
        - <assertion>
      exclude:                  # optional — exclude matching entries
        any:
        - <assertion>
      context:                  # optional — named bindings available to
        - name: <binding>       #   the rule's assertions ($<binding>)
          variable: <value>
      validate:
        message: "<human-readable>"   # optional per-rule message
        assert:
          all:                  # all assertions must hold
          - check: <assertion-tree>
            message: "<per-check>"
        # OR
          any:                  # at least one assertion must hold
          - check: <assertion-tree>
 ```
-Key differences from K8s Kyverno policies:
+The pilot consumer (`nova-blockchain-exchange`) invokes this workflow
- **Always cluster-scoped** — no `namespace` field.
+with `mode: full` for `dev` (D-209). The `.gitea/workflows/deploy.yml`
- **No `forEach`, pattern operators, anchors, or wildcards.** Iteration
+mirror is byte-identical (the platform's deploy workflow is
-  is done via the `~` projection modifier in assertion trees (see §2.4).
+forge-agnostic — Gitea + GitHub).
 - **Assertion trees** with JMESPath expressions replace Kyverno's
  pattern-matching syntax (see §2.4).
-### 2.4 Assertion trees (the rule language)
+### 2.2 `run_platform.sh --apply` path (confirmed)
-An `assert` declaration contains an `all` or `any` list. Each entry has a
+`scripts/run_platform.sh:431-455` — the `--apply` (or `mode: full`)
-`check` (the assertion tree — a nested JMESPath projection) and an
+path runs `terraform apply -auto-approve` after the HITL gate
-optional `message`. **All comparisons happen in the leaves of the tree.**
+(`:438`). For `dev` (autonomous, no HITL gate), the apply proceeds
 directly. The apply records the env via `core/env_transition.py record`
 (`:450`). The full pipeline (no `--apply` flag) continues to Step 7
 (confidence signal) + Step 8 (outbox write).
-A simple example (assert a pod doesn't use the default service account):
+**Gap (noted in RESEARCH §4):** the `--apply` path exits before the
-```yaml
+outbox write (Step 8). The pilot runs the full pipeline (not `--apply`
-validate:
+alone), so the outbox write happens. The `run.completed` event lands in
-  assert:
+the JSONL Decision Ledger (not the DynamoDB outbox) — this is by design
-    all:
+(the outbox is the platform-run evidence stream; the Decision Ledger is
-    - message: "serviceAccountName 'default' is not allowed"
+the cold store for metrics).
      check:
        spec:
          (serviceAccountName == 'default'): false
 ```
-The `(expression)` syntax evaluates a JMESPath expression; the result
+### 2.3 Contract schema — multi-module manifest
 becomes the current object for descendants; the leaf value is compared
 to the expected value.
-**Iteration via the `~` modifier.** The `~` prefix on a key applies
+`schemas/contract.schema.json:7,24-48` — required fields: `id`,
-descendant assertions to **each element** of an array/map individually
+`name`, `environment`, `infrastructure`. The `infrastructure` block is
-(rather than comparing the whole array). Given `foo.bar: [1,2,3]`:
+`minProperties: 1` with `patternProperties` accepting any module name
-```yaml
+key. Multi-module manifest is supported: one contract can declare
-check:
+`infrastructure: { microservice: {...}, dynamodb: {...}, s3: {...} }`.
-  foo:
+The constraint is the `modules/registry.json` (the module must be
-    ~.bar:               # iterate each element
+registered), not the schema.
      (@ < `5`): true    # assert each element < 5
 ```
 The `~index_name.bar` form binds the index (array) or key (map) to
 `$index_name` for use in descendants. This is how v1.25 iterates
 `resources[]` in the Stack IR policies (REQ-297) and
 `planned_values.root_module.resources[]` in the plan-JSON policies
 (REQ-300).
-**Explicit bindings** via `->binding_name` allow descendants to refer
+---
 to a parent node via `$binding_name`. Built-in bindings: `$payload`
 (the whole input), `$policy`, `$rule`.
-**Escaping** via `\key\` prevents projection when a payload key collides
+## 3. Platform Module Readiness (the critical finding)
 with the projection syntax. Not needed for Nova payloads (no `(key)`
 fields), noted for completeness.
-### 2.5 Output shape (what `kj scan --output json` produces)
+### 3.1 The adapter is stateless (v1.11 rewrite)
-The JSON output is a `results[]` array. Each result entry has (at
+`adapters/terraform/adapter.py:1-11` — the adapter is a "STATELESS
-minimum):
+ASSEMBLER" that owns no module content. There is **no `TYPE_MAP`**,
- `policy`: the policy metadata.name
+`INPUT_MAP`, or `OUTPUT_MAP` (deleted in the v1.11 stateless rewrite;
- `rule`: the rule name
+`modules/STANDARDS.md:212-214` confirms). A new stack type requires a
- `result`: `"pass"` | `"fail"` | `"error"` | `"skip"` (lowercase)
+new L1 module (`modules/l1/<name>/` with `interface.json` +
- `message`: the assertion message (or engine error message)
+`terraform/main.tf` + `README.md` + `instance.json`) + a
- `resource`: the matched payload entry (the `identifier` value, or the
+`modules/registry.json` entry — not an adapter change.
  whole payload when no identifier/match)
 - `namespace`/`kind`/`name`: K8s-style fields (present but empty for
  non-K8s payloads — the K8s Kyverno adapter's evidence uses these; the
  kyverno-json engine's evidence uses `assertion`/`jmespath` instead)
 - `severity`: not present by default (kyverno-json does not assign
  severities — the Nova policy author assigns severity via a Nova-
  specific annotation; see §2.6)
-The `KyvernoJsonEngine._to_pcr()` translator (REQ-293) maps:
+### 3.2 ECS — ready
 - `policy` → `ruleId` (prefixed `KJ_<policy_name>` per D-116)
 - `result` → `result` (`pass`/`fail`/`error` → pass/fail/error;
  `skip`/`skipped` → skipped)
 - `message` → `message`
 - `resource` → `resourceRef` + `evidence.resource`
 - severity from the policy's `metadata.annotations` (see §2.6)
 - `engine: "kyverno"` (per D-116 — no new enum value)
-### 2.6 Severity assignment (Nova convention)
+`modules/l1/ecs-service/terraform/main.tf:1,11` —
 `aws_ecs_task_definition` + `aws_ecs_service`. `interface.json:5-6` —
 `type: aws:ecs:task_definition`. `registry.json:29-37` — registered.
 Tests: `test_adapter.py:164-185,257-360`, `test_contract_resolver.py:61-92`.
 The `microservice` L2 (`modules/l2/microservice/composition.json`)
 references 6 L1 children (ecs-cluster, ecr, iam-role, alb, ecs-service,
 kms-key) — the ECS pattern is fully wired end-to-end.
-kyverno-json does not natively assign severities to results. Nova's
+### 3.3 S3 — ready
 confidence signal requires a `severity` per PCR (critical/high/medium/
 low/info). The v1.25 convention: each Nova policy file declares its
 severity via a `metadata.annotations` field:
-```yaml
+`modules/l1/s3/terraform/main.tf:1` — `aws_s3_bucket` (+ versioning +
-metadata:
+SSE). `interface.json:5-6` — `type: aws:s3:bucket`. `registry.json:2-10`
-  name: forbid-public-ingress
+— registered. Tests: `test_adapter.py:56-110,241-257`,
-  annotations:
+`test_contract_resolver.py:36-51,92-130`.
    nova.cloudinit.dev/severity: high
 ```
-The `KyvernoJsonEngine._to_pcr()` reads this annotation from the loaded
+### 3.4 DynamoDB — GAP (REQ-322)
 policy YAML (not from the scan result — the result doesn't carry it) and
 applies it to every result that policy produces. Default when absent:
 `info`. This keeps severity in the policy (declarative, version-
 controlled) rather than in the engine adapter (imperative). The
 annotation key is `nova.cloudinit.dev/severity` (matches the existing
 `nova.cloudinit.dev` namespace used in `schemas/tagging-standard.json`).
-## 3. The four policy targets (v1.25 scope)
+**No `modules/l1/dynamodb/` directory, no `registry.json` key, no
 `interface.json`, no `terraform/`, no tests.** The blockchain exchange's
 ledger table needs this primitive. REQ-322 authors it: `interface.json`
 (stack type `aws:dynamodb:table`), `terraform/main.tf`
 (`aws_dynamodb_table` with PK + optional SK, `PAY_PER_REQUEST` default,
 encryption + PITR enabled per v1.8 NFR defaults), `README.md`,
 `instance.json`, + `registry.json` entry. The adapter needs no change
 (stateless); the contract's `infrastructure.dynamodb` block references
 this primitive. This is the single platform-side module build-out for
 the milestone.
-### 3.1 Consumer contract JSON (REQ-295)
+### 3.5 Stale doc (not a blocker)
-The payload is the parsed contract dict (the raw YAML loaded as JSON).
+`adapters/README.md:49-54` references the deleted `TYPE_MAP`/
-Policies assert the `contract.schema.json` constraints declaratively:
+`INPUT_MAP`/`OUTPUT_MAP` — contradicts `adapter.py:1-11` +
-`require-id-pattern` (JMESPath regex `^[a-z][a-z0-9-]{2,5}$` over
+`modules/STANDARDS.md:212-214`. REQ-321 (docs) should fix this.
 `id`), `require-env-in-enum` (`environment` in `["dev","qa","prod","dr"]`),
 `require-infrastructure-min-1` (`length(infrastructure) > 0`),
 `forbid-unknown-fields` (keys subset of the 4 allowed). These are the
 declarative equivalent of the jsonschema constraints — they let Nova
 apply its own compliance posture (e.g. forbid a specific env for a
 specific consumer) on top of schema validity without editing the
 jsonschema.
-**Invocation point:** `core/contract_resolver.py` pre-resolve (REQ-296).
+---
 Early-fail: if a contract policy fails, the resolver still proceeds
 (the confidence signal decides the gate, consistent with the existing
 `--soft-fail` Checkov pattern) — but the failing PCRs are in the
 `policy` input, which lowers the score.
-### 3.2 Resolved Target Stack IR JSON (REQ-297)
+## 4. Metric Pipeline Grounding (Post-Pilot targets)
-The payload is the resolved Stack IR dict produced by
+### 4.1 AI Decision Accuracy — outcome backfill (REQ-317)
 `core/contract_resolver.py` (the merged module outputs). Policies
 assert over `resources[]` (the array of resolved resources):
 `require-tagging-standard` (every resource's `tags` has `nova:owner` +
 `nova:environment` — ports
 `adapters/terraform/policy/custom_rules/nova_tagging.py`),
 `forbid-public-ingress` (no resource has `public_ingress: true` — the
 v1.0 demo rule, now declarative), `require-encryption-by-default` (every
 S3/EBS/KMS-aliased resource carries encryption config — ports the v1.8
 D-encryption-default rule). The `~` modifier iterates `resources[]`.
-**Invocation point:** `core/contract_resolver.py` post-resolve (REQ-298).
+`core/metrics/decision_ledger.py:210-211` documents the event chain:
-Additive — the resolver's return values and exceptions are unchanged;
+`confidence.computed → ai.decision.made → attestation.recorded →
-the PCRs are appended to the contract-policy PCRs.
+run.completed/failed`. `collector.py:262` inserts `fact_decision.outcome`
 as `"pending"` — **there is no outcome-backfill step** wiring
 `run.completed`/`run.failed` back into `fact_decision.outcome`. The AI
 Decision Accuracy metric (`trust_snapshot.py:70-85`, `_get_ai_decision_accuracy`)
 reads `decisions WHERE outcome='succeeded' ÷ total` — so it reads 0%
 today (all pending). REQ-317 adds `core/metrics/outcome_backfill.py`
 that reads run-manifest events and updates `fact_decision.outcome` +
 `fact_decision.backfilled_at`. The PCR schema is unchanged (D-211).
-### 3.3 Terraform plan JSON (REQ-300)
+### 4.2 Human Escalation Frequency — `reason='confidence'` tag (REQ-318)
-The payload is `terraform show -json <tfplan>` output. Policies assert
+`core/confidence_signal.py:184` — a `block` band sets
-over `planned_values.root_module.resources[]`:
+`human_override=True` in the `ai.decision.made` event.
-`forbid-plaintext-secrets` (no `aws_db_instance.password` /
+`run_platform.sh:636` fails the pipeline on `block`. The Human
-`aws_iam_user.login_profile.password` in plaintext — ports
+Escalation Frequency metric (`docs/metrics/human_escalation_frequency.md:11-12`)
-`CKV_AWS_41/45/46`), `forbid-iam-wildcard` (no `Action: "*"` or
+is defined as `count(runs WHERE hitl_block=1 AND reason='confidence') ÷
-`Resource: "*"` in `aws_iam_policy.PolicyDocument` — ports
+total runs`. The `reason='confidence'` discriminator is **not currently
-`CKV_AWS_1/40`), `require-kms-reference` (KMS keys referenced by alias,
+stored** — `hitl_block` is a boolean from the manifest. REQ-318 adds
-not inline key material — ports `CKV_AWS_7/33`). These are declarative
+`escalation_reason: 'confidence'` to the `ai.decision.made` event when
-**mirrors** of `checkov_adapter.py:RULE_MAP` — the Checkov rule stays
+`band == 'block'` + persists it into `fact_run` via the collector.
 the source of truth for `terraform_plan` scanning; the kyverno-json
 policy covers the same plan JSON with a different rule language
 (defense-in-depth against engine drift).
-**Invocation point:** `run_platform.sh` Step 5 (REQ-301). After
+### 4.3 Touchless Resolution Rate — denominator activates post-pilot
 Checkov/Wiz produce raw PCRs, the script runs `kj scan` over the plan
 JSON; both PCR lists concatenate into the confidence signal's `policy`
 input. When `which kj` is false, the script logs and proceeds with the
 Checkov/Wiz list only.
-### 3.4 PolicyCheckResult records (meta-policies, REQ-303)
+`docs/metrics/touchless_resolution_rate.md:12-15` — defined as a SQL
 query over `fact_run` (`runs WHERE hitl_block=0 ÷ total runs`). The data
 lands in `fact_run.hitl_block` via `collector.py:216-227`. No dedicated
 emitter computes the ratio — it's a downstream query. The denominator
 is 0 today (no consumer runs). The pilot run activates the denominator.
-The payload is the **merged** `list[PolicyCheckResult]` produced by
+---
 checkov + wiz + the plan-JSON policies. This is the most novel target —
 kyverno-json policies over the policy results themselves.
 `block-on-any-critical` asserts no PCR has `severity: "critical"` +
 `result: "fail"`; if any does, the meta-policy emits a `fail` PCR with
 `ruleId: "KJ_META_BLOCK_CRITICAL"` and severity `critical`. This is the
 declarative source of truth for "critical = block" (D-119 — the
 `confidence_signal.py` `PENALTY["critical"]: None` hard-override stays
 as defense-in-depth). `tagging-rules-agree` cross-checks the Checkov
 `NOVA_TAG_NAMING` result against the kyverno-json
 `KJ_REQUIRE_TAGGING_STANDARD` result by `resourceRef`; divergence emits
 an `error` PCR (D-118).
-**Invocation point:** after the three target policies (contract/stack-
+## 5. kyverno-json Policy Extensibility
 IR/plan-JSON) produce their PCR lists, the merged list is the payload
 for the meta-policies. The meta-policy PCRs are appended to the merged
 list, which is what the confidence signal consumes.
-## 4. The `PolicyEngine` swap boundary
+`adapters/kyverno-json/kyverno_json_engine.py:74-80` — the engine is
 **policy-dir agnostic**: it loads whatever subdir the caller passes.
 Existing subdirs: `contract/`, `stack-ir/`, `plan-json/`, `meta/`,
 `regression/`. Adding a new subdir (e.g. `pilot-readiness/`,
 `settlement-finality/`) requires: (1) `mkdir
 adapters/kyverno-json/policies/<name>/`, (2) drop `ValidatingPolicy`
 YAML/JSON files, (3) wire a caller. No engine code change needed.
 Test pattern: one test file per subdir (`tests/test_<name>_policies.py`).
-### 4.1 Protocol shape (REQ-291)
+The pilot adds two new policy subdirs: `pilot-readiness/`
 (REQ-320, no-placeholder-account) + `settlement-finality/` (REQ-315,
 all-matches-committed). Both follow the established pattern.
-A Python `Protocol` (PEP 544 — structural subtyping, no inheritance):
+---
 ```python
 class PolicyEngine(Protocol):
    @property
    def name(self) -> str: ...
    def is_configured(self) -> bool: ...
    def evaluate(self, payload: dict | str, policy_dir: Path,
                 contract_id: str) -> list[dict]: ...
 ```
 `list[dict]` (not `list[PolicyCheckResult]` — there's no dataclass; the
 schema is enforced via `jsonschema` validation in tests, matching the
 existing adapter pattern). The registry selects the active engine from
 `config.json.policy.engine`. A `NullEngine` is the fallback when the
 `policy` key is absent (emits `SKIPPED` — backward compatibility for
 tests that don't set the key).
-### 4.2 The OPA-equivalent surface (future swap)
+## 6. Env-JSON Wiring Reconciliation (REQ-319)
-OPA (Open Policy Agent) is the most likely future replacement. The
+`core/environments/dev.json:4` — `account_id: "000000000000"` (placeholder).
-mapping:
+`core/environment_check.py:48-53` warns (non-fatal) when account_id is
-| Nova `PolicyEngine` member | kyverno-json impl | OPA equivalent |
+placeholder + env != dev. `adapters/terraform/adapter.py:116-117` —
-|---|---|---|
+computes the state bucket as `nova-tfstate-<AWS_ACCOUNT_ID>-us-east-1`
-| `name` | `"kyverno-json"` | `"opa"` |
+from the `AWS_ACCOUNT_ID` env var, **not** from the env JSON's
-| `is_configured()` | `which kj` | `which opa` |
+`state_backend.bucket`. This is the wiring gap: the env JSON's
-| `evaluate(payload, policy_dir, contract_id)` | `kj scan --policy <dir> --payload <json> -o json` | `opa eval -d <dir> -i <json> 'data.nova.<...>'` |
+`state_backend` field is currently unused by the live apply path.
-| Policy file format | `ValidatingPolicy` (YAML) | Rego (`.rego`) |
+REQ-319 makes the adapter read `env.state_backend.bucket` when present
-| Result shape | `results[]` (pass/fail/error/skip) | `result` (set of violations) |
+(falling back to the computed name for backwards compat) + updates
-| Severity | Nova annotation `nova.cloudinit.dev/severity` | Nova convention (Rego `metadata` or a wrapper) |
+`dev.json` to the real account `581513795199` + real bucket
 `nova-tfstate-581513795199-us-east-1`.
-The protocol is minimal (3 members) specifically so the OPA
+---
 implementation is a known quantity: an `OpaEngine` class that shells to
 `opa eval`, translates the Rego violation set to PCR dicts, and
 implements `is_configured()` via `which opa`. The policy *files* would
 need rewriting (Rego, not ValidatingPolicy) — but the protocol, the
 registry, the confidence signal, and the PCR schema are all untouched.
 This is the swap boundary the user asked for ("Implemented as an
 adapter since we might one day decide to replace it with something else
 like OPA").
-### 4.3 Why not a full plugin registry?
+## 7. Risk Analysis
 A `setuptools` entry-point plugin registry (like checkov's
 `--external-checks-dir`) was considered and rejected: Nova has 1 active
 engine today (kyverno-json) and at most 2 in the foreseeable future
 (kyverno-json + OPA). A `Protocol` + `dict` registry in
 `core/policy_engine.py` is the right weight — discoverable, typed,
 testable, and ~40 lines. An entry-point registry adds packaging
 complexity (entry-point metadata, version resolution) for no gain at
 this scale. The `register(name, factory)` method on the registry is
 the extension point if a future milestone needs runtime plugin
 discovery.
 ## 5. Latency / MTTR impact (G-Q3 anticipation)
 NORTH_STAR.md MTTR target: < 60s p95. `run_platform.sh` Step 5 today
 runs Checkov over the terraform plan (typically 5-15s for a small
 stack). Adding `kj scan` over the same plan JSON adds:
 - Process spawn: ~50ms (Go binary startup)
 - Policy load: ~20ms (a handful of YAML files)
 - Assertion evaluation: ~100-500ms (JMESPath over a small plan)
 - Total: < 1s for a typical Nova stack
 The kyverno-json pass runs **in parallel** with Checkov (REQ-301 — the
 script launches both and waits on both), so the wall-clock impact is
 `max(checkov_time, kj_time)` ≈ checkov_time (kj is faster). The
 contract + stack-IR policies run during resolve (already a fast step).
 Meta-policies run over the merged list (in-memory, < 10ms). **No
 measurable MTTR impact** is expected. This will be verified in P3
 VERIFY with a timing assertion.
 ## 6. "Platform functions without AI" tenet (G-Q1 / D-120)
 kyverno-json is deterministic (same policy + payload → same result,
 every run). It is not an LLM, not a probabilistic model, not a
 "judgement" engine. The NORTH_STAR.md tenet ("the platform functions
 without AI — 'AI decisions' are really automated decisions")
 distinguishes AI (non-reproducible) from automation (reproducible).
 kyverno-json is the latter. Adding it is **more** aligned with the
 tenet than the current imperative Python in `core/env_transition.py`
 and `core/regression_verify.py`, because the policy is declarative
 (visible, auditable, version-controlled) rather than imperative (logic
 hidden in function bodies). The `is_configured()` guard ensures the
 platform functions without the binary (graceful skip → `SKIPPED` PCR
 → confidence signal proceeds).
 ## 7. ECS policy catalog overlap (prior art)
 The kyverno-json catalog ships ECS policies that overlap with Nova's
 L1 modules: `ecs-cluster-enable-logging`, `ecs-cluster-required-
 container-insights`, `ecs-service-public-ip`, `ecs-service-required-
 latest-platform-fargate`, `ecs-task-definition-fs-read-only`. These are
 **reference policies**, not drop-in Nova policies — they target the
 AWS ECS API shape (`type: aws_ecs_service` etc.), not Nova's Stack IR
 shape. v1.25 policies target the Nova IR (REQ-297) and the terraform
 plan JSON (REQ-300), not the raw AWS API. The catalog is useful as
 prior art for JMESPath patterns over ECS resources — the
 `ecs-service-public-ip` policy's `contains('$allowed-values',
@.assign_public_ip)` pattern informs the Nova `forbid-public-ingress`
 policy shape. No catalog policies are imported directly in v1.25.
 ## 8. Risks & mitigations
 | Risk | Likelihood | Impact | Mitigation |
 |---|---|---|---|
-| `kj` binary not in CI image | medium | blocks P3+ tests | `is_configured()` guard + `pytest.skip` + `scripts/install-kyverno-json.sh` |
+| `NOVA_AWS_*` key lacks a needed IAM permission mid-pilot | Low (bootstrap succeeded → root-equivalent) | High (blocks apply) | D-207; the key has root-equivalent perms (empirically confirmed). |
-| kyverno-json output shape changes across versions | low | breaks `_to_pcr()` | pin `@latest` to a known-good commit in `install-kyverno-json.sh` after P1 smoke; defensive parsing (malformed → `error` PCR, not exception) |
+| DynamoDB primitive takes longer than expected (new module) | Medium | Medium | REQ-322 is the single platform-side build-out; the `s3`/`rds` primitives are the template — straightforward. |
-| Policy explosion (4 targets × N rules) | medium | maintenance load | wave ordering (PLAN); policies co-located per target dir; meta-policy cross-check keeps the set auditable |
+| Homegrown chain has a correctness bug (hash chain breaks) | Low | High | REQ-310 tests cover chain integrity, hash determinism, genesis, append/verify. |
-| Checkov + kj tagging-rule drift | medium | false `error` PCRs | `tagging-rules-agree` meta-policy emits `error` on divergence (visible, not silent); the Checkov rule stays source of truth for HCL, kj for IR |
+| `deploy.yml@v1.25` ref doesn't resolve (floating tag) | Low | High | The platform's `release.yml` creates + force-moves the `v1.25` + `v1` floating tags on merge to main. The pilot contract uses `@v1.25`. |
-| OPA swap turns out harder than the protocol implies | low | future milestone rework | RESEARCH §4.2 documents the OPA-equivalent surface; the protocol is the contract, not the implementation |
+| Settlement-finality policy false-negatives (blocks a valid promotion) | Medium | Medium | REQ-315 tests cover passing + failing fixtures; the policy is skip-when-kj-absent (graceful). |
-| `--pre-process` needed for meta-policies but undocumented behavior | low | meta-policy bugs | v1.25 meta-policies use plain assertion trees over the PCR list (no pre-process); `--pre-process` noted as a future optimization only |
+| D-083 deferral challenged (audit ledger not tamper-evident) | Low | Low | D-204; the SQLite hash-chain + DynamoDB outbox is the pilot's audit record. Tamper-evidence is a future milestone. |
-## 9. Assumptions (logged, full autonomy)
+---
- A1: `kj scan --output json` produces a stable `results[]` array shape.
+## 8. Persona Assessment
  Will be verified in P1 smoke test (`_smoke.json` policy + a trivial
  payload); if the shape differs, `_to_pcr()` is adjusted defensively
  (malformed → `error` PCR). Confidence: 0.85.
 - A2: The `nova.cloudinit.dev/severity` annotation convention is
  read by the engine from the policy YAML (loaded once per evaluate()
  call). kyverno-json does not validate unknown annotations — they pass
  through. Confidence: 0.90.
 - A3: The `~` projection modifier iterates `resources[]` in the Stack
  IR and `planned_values.root_module.resources[]` in the plan JSON
  correctly. Verified in P2/P3 tests. Confidence: 0.85.
 - A4: `go install` works in the CI image (Go toolchain available or
  installable). If not, the binary-release download path is the
  documented fallback in `install-kyverno-json.sh`. Confidence: 0.80.
 - A5: The `NullEngine` fallback (when `policy` key absent in
  config.json) keeps all existing tests passing — they don't set the
  key, so they get `NullEngine` → `SKIPPED` PCRs → confidence signal
  proceeds with `policy` input `[SKIPPED]` → per-input score 1.0
  (skipped counts as pass in `_per_input_score`). Confidence: 0.95
  (verified against `confidence_signal.py:84-89`).
-## 10. Decisions referenced
+See `PERSONAS.md` (next section, produced by the lead-developer at the
-
+end of RESEARCH). The active roster: backend-engineer (blockchain core
-D-115 (install path), D-116 (engine enum reuse), D-117 (adapter
+ settlement + outcome backfill), data-engineer (DynamoDB primitive +
-signatures unchanged), D-118 (tagging cross-check), D-119 (critical-
+metrics cold store), policy-engineer (kyverno-json policies), +
-override defense-in-depth), D-120 (deterministic not AI). See
+blockchain-engineer (custom, phase-specific — chain consensus, order
-CLARIFY.md for the full resolution text.
+matching, settlement finality). frontend-engineer is deactivated (no
-
+UI in the pilot).
 ## 11. Architecture updates (deferred to RESEARCH-stage file edits)
 - `.ciagent/ARCHITECTURE.md` gains §12.7 "Policy Engine Registry" with
  the registry diagram. Deferred to the RESEARCH commit (this file's
  commit) — the section is authored as part of this research.
 - `schemas/README.md` notes `engine: "kyverno"` is shared by the K8s
  adapter and kyverno-json (distinguished by `ruleId` prefix).
 - `modules/STANDARDS.md` gains a "Policy authoring standard" section
  (P4, REQ-307).
 - `docs/METRICS.md` notes the policy engine is swappable (P4, REQ-307).
@@ -0,0 +1,219 @@
 # P05 Final Review + Audit — v1.26 Live Pilot Estate Activation
 > **Phase:** 5 (final review + audit + ship) — review + audit only; the
 > milestone ship (merge to main / tag v1.25.5 / branch deletion) is the
 > orchestrator's next step, deliberately out of scope here.
 > **Branch:** `phase/05-final-review-ship`
 > **Milestone:** `milestone/v1.26-pilot-activation`
 > **Tags so far:** v1.25.0 (P0) → v1.25.1 (P1) → v1.25.2 (P2) →
 > v1.25.3 (P3) → v1.25.4 (P4). P5 ships v1.25.5 (= the v1.26 release).
 > **Date:** 2026-08-19
 ---
 ## 1. Review (ciagent-review equivalent)
 Multi-persona review across P1..P4 (lead-developer coordination;
 correctness / testing / security / maintainability axes). The spot-checks
 below confirm the P3/P4 commits deliver what their messages claim.
 ### Correctness spot-checks (all PASS)
 - **kyverno-json substrate fix (59d837f):** the engine `_translate` parses
  the real `kj` v0.0.3 bare-list output (not the v1.25-assumed
  `{"results":[...]}` dict); `_materialize_yaml_policy_dir` mirrors `.json`
  policies to `.yaml` twins (kj v0.0.3 ignores `.json`); the `validate`
  wrapper was removed from all 16 policies + the check syntax fixed
  (`expression: expected_value`). All 36 kj-dependent tests pass against
  real `kj` (0 skips). The install script fixed
  (`go install .../kyverno-json@latest` + symlink, not the broken
  `cmd/kj@latest`).
 - **outcome backfill (51b886f, REQ-317):** `core/metrics/outcome_backfill.py`
  updates `fact_decision.outcome` pending → succeeded/failed; idempotent +
  terminal (no overwrite of a non-pending outcome); wired into the
  collector. The P4 run evidence (6ced8ed) confirms
  `nova.outcome.backfilled (pending->succeeded)`.
 - **Gitea adapter (P3 W0):** the consumer `deploy.yml` has no cross-repo
  `uses:` — inline `actions/checkout@v4` of `acdl/acdl @ ref: v1.25` into
  `platform/` then `bash platform/scripts/run_platform.sh`. SPEC §10 Q1
  resolved by evidence.
 - **env-JSON state_backend (3300ed2, REQ-319):** the adapter reads
  `env.state_backend.bucket` when present (fallback to the computed
  `nova-tfstate-{account_id}-{region}` for backwards compat). `dev.json`
  bound to `581513795199` + `nova-tfstate-581513795199-us-east-1`;
  qa/prod/dr stay placeholder (account `000000000000` — the pilot-readiness
  policy blocks apply, D-208).
 - **pilot policies (e22661a, REQ-315/320):** `no-placeholder-account.json`
  passes on dev (581513795199), fails on placeholder;
  `all-matches-committed.json` asserts `all_committed == true`. Both run
  against real `kj` (not skipped).
 ### Testing
 - 844 tests collected; **844 pass** (839 fast + 5 slow individually
  re-run: 2 `test_run_local_e2e_*` + 3 `test_verify_regression_mode::*`).
  0 failures, 0 skips that shouldn't skip.
 - New feature coverage confirmed: REQ-317 backfill test
  (`test_outcome_backfill.py`), REQ-318 escalation_reason test
  (`test_confidence_escalation_reason.py`), REQ-315/320 policy tests
  (`test_settlement_finality_policy.py`, `test_pilot_readiness_policy.py`
  — both real-kj), REQ-316 CAP-025 test (`test_regression_pilot.py`), Gitea
  adapter tests (`test_deploy_workflow_invocation.py` +
  `test_deploy_gitea_invocation.py` — assert no cross-repo `uses:`,
  `ref: v1.25`, `secrets: inherit`), rotation workflow test
  (`test_rotate_key_workflow.py`), CAP-025 test
  (`test_deploy_workflow_env_input.py`).
 - The v1.25 `pytest.skip("kj not installed")` skips are gone — `_require_kj`
  no longer skips (kj v0.0.3 installed). All kj-dependent tests exercise
  the real engine.
 ### Security
 - **No `NOVA_AWS_*` secrets in committed files.** `.env.secrets` is
  gitignored and NOT tracked (`git ls-files` confirms). All `NOVA_AWS_*`
  references in committed workflow files are `${{ secrets.* }}` placeholder
  references — the correct pattern. The W6 fix (b237b3e) removed raw
  `NOVA_AWS_*` from the shell env in `run_platform.sh`'s local fallback.
 - **No forge mentions in synced files.** `test_no_forge_mentions` PASS
  (the REQ-230 guard). The W6/W7 fix (03edd82) renamed `NOVA_GITEA_TOKEN`
  → `NOVA_FORGE_TOKEN` (forge-agnostic) after the guard tripped.
 ### Maintainability
 - **No stale `TYPE_MAP` refs in active docs.** The P4 W2 fix (a0799f1)
  fixed the stale `TYPE_MAP`/`INPUT_MAP` references in `adapters/README.md`
  (IDEATE I8). Remaining `TYPE_MAP` mentions are in `.ciagent/archive/`
  (historical, correct) + `.ciagent/{CLARIFY,IDEATE,RESEARCH}.md`
  (decision records, correct context).
 - **No new TODOs/FIXMEs in P3/P4.** `grep` over `core/` for
  `TODO|FIXME|XXX|HACK` returns 0 matches.
 - The P3 W0.5 fix (3735330) resolved pre-existing P2 drift (dynamodb
  `simple.yaml` → `simple.yml`, sync_workflows re-sync, CAP-024 deck path
  → `nova-autonomous-cloud-delivery-marp.md`).
 ### Review verdict
 **0 P0 issues remain** after the one P0 fix applied this phase (see §3).
 **P1+ issues for post-hoc review (none blocking ship):**
 | # | Severity | Issue | Disposition |
 |---|----------|-------|-------------|
 | R-1 | P2 (cosmetic) | `CHECKPOINT.json` `phase_branch` field is stale (`phase/03-pilot-metrics-and-policies`) — should be `phase/04-pilot-run-and-docs` or cleared. | Post-hoc. The orchestrator's ship step overwrites CHECKPOINT entirely (`stage: complete, phase: 5, phase_role: final`), so this field is transient. Not fixed here to avoid touching CHECKPOINT outside the ship step. |
 | R-2 | P3 (historical) | The v1.26 consumer-repo merge commit (78da051) + the P0 merge (d391cdf) use `---/ci---` close markers; the v1.26 platform-repo commits (P3/P4) use `---ci---` only. Minor format inconsistency from the multi-project boundary. | Post-hoc. Cosmetic; both markers are recognized by the audit tooling. |
 | R-3 | P3 (future-hardening) | Single `NOVA_AWS_*` root-equivalent key (D-207). Documented in PLAN.md §Future Hardening — a future milestone should split into `NOVA_BOOTSTRAP_AWS_*` + least-privilege `NOVA_AWS_*` runner key. | Post-hoc. Out of v1.26 scope by design (D-207, G-Q9). |
 ---
 ## 2. Audit (ciagent-audit equivalent)
 ### 2.1 Reconstruction test — **PASS**
 The git log `---ci---` blocks are consistent with the `.ciagent/` file
 states. The last 20 commits on `milestone/v1.26-pilot-activation` show the
 expected phase progression:
 - P0 (`d391cdf`, status: complete) → P1 ship (`2ee541f`) →
  P2 reconcile (`d022ddc`) → P2 complete (`6a3d47e`) →
  P3 W0.5 → W2 → W3 → W4 → W5 → W6 → W6/W7 → verify (`5d1a985`) →
  docs (`732998b`) → merge+complete (`268f695`, `6b60c0c`) →
  P4 W1 (`cec34ab`, `6ced8ed`) → W2 (`a0799f1`) → verify (`074ee05`) →
  merge+complete (`6eb7af2`, `f266dcf`).
 Each phase follows the `execute → verify → complete` lifecycle. The
 CHECKPOINT `current_phase` (phase 4, status complete, tag v1.25.4) matches
 the latest commit (`f266dcf docs(ship): P4 complete → v1.25.4`). The
 `previous_phase` (phase 3, tag v1.25.3, complete) is consistent.
 All 4 merge commits on the milestone branch (d391cdf, 78da051, 268f695,
 6eb7af2) carry `---ci---` blocks with project/phase/milestone/status.
 ### 2.2 `.ciagent/` file discipline — **CLEAN** (after the one P0 fix)
 - **CHECKPOINT.json:** `current_phase` (4/complete/v1.25.4) + `previous_phase`
  (3/complete/v1.25.3) consistent with the git log. `waves` map + `pre_run`
  map + `notes` accurately describe the P4 live apply + outcome backfill.
  One stale field: `phase_branch` (R-1, post-hoc).
 - **REQUIREMENTS.md:** v1.26 traceability table now shows all 13 REQs
  (310..322) complete. **One P0 fix applied:** REQ-316 row corrected from
  "P4 live-verify pending" → "v1.25.4 — live-verify complete" (P4 is
  complete; v1.25.4 tagged; the live apply against 581513795199 succeeded
  per commit 6ced8ed + verify 074ee05). The v1.25 table (REQ-291..309) is
  all-complete + consistent with ROADMAP.
 - **ROADMAP.md:** v1.26 phases P0..P4 marked complete; P5 marked "planned"
  (correct — this phase is in progress, ship is next). v1.25 marked
  complete. The phase descriptions match the commits.
 - **PLAN.md:** the active phase plan covers P0..P5 with wave ordering,
  persona assignment, + the REQ-322→P2 W0 revision. Consistent with what
  shipped.
 - **ARCHITECTURE.md:** §12.8 (Pilot Estate) + §12.9 (rotation) present
  (P4 W2 docs).
 - **PROJECT.md:** v1.26 active milestone noted; multi-project mode
  (`nova-blockchain-exchange`) reflected.
 ### 2.3 Branch hygiene — **CLEAN**
 `git branch -a` (local):
 - `main`
 - `milestone/v1.26-pilot-activation`
 - `phase/05-final-review-ship` (current)
 P1..P4 phase branches are deleted (only milestone + P5 remain, as
 required). Remote: `origin/main` + `origin/milestone/v1.26-pilot-activation`
 mirror the local state.
 Tags: `v1.25` (floating) + `v1.25.0` + `v1.25.1` + `v1.25.2` + `v1.25.3` +
 `v1.25.4` all exist. `v1.25.5` is not yet present (correct — it's the
 orchestrator's ship step).
 ### 2.4 Commit discipline — **CLEAN**
 Every v1.26-scope commit on the milestone branch carries a `---ci---`
 block with `project` + `phase` + `milestone` + `status` (and most carry
 `wave`). The 4 merge commits (d391cdf, 78da051, 268f695, 6eb7af2) all
 carry `---ci---` blocks. (Historical commits from v1.0-v1.18 predate the
 block convention — out of scope for this audit.)
 The consumer-repo merge (78da051) correctly carries
 `project: nova-blockchain-exchange` (multi-project boundary respected);
 the platform commits carry `project: acdl`.
 ### Audit verdict
 | Check | Result | Detail |
 |-------|--------|--------|
 | Reconstruction test | **PASS** | git-log `---ci---` blocks ↔ `.ciagent/` consistent; phase 4/complete/v1.25.4 matches HEAD. |
 | File discipline | **CLEAN** | All 6 `.ciagent/` files consistent after the REQ-316 P0 fix. One stale `phase_branch` field (R-1, post-hoc). |
 | Branch hygiene | **CLEAN** | Only main + milestone + P5; P1-P4 deleted; v1.25.0..v1.25.4 tagged. |
 | Commit discipline | **CLEAN** | All v1.26 commits carry `---ci---` blocks; merge commits included. |
 ---
 ## 3. P0 fixes applied this phase
 | # | File | Fix |
 |---|------|-----|
 | P0-1 | `.ciagent/REQUIREMENTS.md` | REQ-316 traceability row: "P4 live-verify pending" → "v1.25.4 — live-verify complete". P4 is complete (v1.25.4 tagged, live apply against 581513795199 succeeded per commits 6ced8ed + 074ee05); the "pending" text was stale documentation drift that misstated the milestone state. |
 No code-level P0 issues found — the P3/P4 feat/fix commits deliver what
 they claim; the test suite is green; no secrets leaked; no forge mentions;
 no stale active-doc references.
 ---
 ## 4. Overall verdict — **PROCEED to milestone ship**
 - **Review:** 0 P0 issues remain (1 P0 fix applied: REQ-316 doc drift).
  3 P1+ items flagged for post-hoc (R-1 stale CHECKPOINT field, R-2 close-
  marker inconsistency, R-3 future key-split — none block ship).
 - **Audit:** reconstruction PASS; file discipline CLEAN; branch hygiene
  CLEAN; commit discipline CLEAN.
 - **Tests:** 844 passed, 0 failed, 0 unexpected skips (5 slow tests
  individually confirmed green: 2 local-e2e + 3 regression-mode).
 **Decision: PROCEED.** The orchestrator's next step (Wave 3 milestone
 ship: merge `phase/05-final-review-ship` → `milestone/v1.26-pilot-
 activation` → `main`; tag `v1.25.5`; Gitea release; delete milestone
 branches; final CHECKPOINT clear) is unblocked. Per the full-autonomy
 "never halt" directive, even if a P0 had been critical, the ship step
 would still proceed with the issue documented — but here the single P0
 was a cosmetic doc-drift, now fixed.
@@ -0,0 +1,39 @@
 # VERIFY — v1.26 P3 (pilot-metrics-and-policies) PASS
 > Four-layer verification. All gates green.
 ## Structural
 - pilot-readiness/no-placeholder-account.json + settlement-finality/all-matches-committed.json exist (REQ-315/320)
 - core/metrics/outcome_backfill.py + tests exist (REQ-317)
 - escalation_reason emitted on block band (REQ-318) — test_confidence_escalation_reason.py
 - adapters/terraform/adapter.py reads env.state_backend.bucket (REQ-319) — test_adapter_state_backend.py
 - core/environments/dev.json bound to 581513795199 (D-203); qa/prod/dr placeholder (D-208)
 - CAP-025 in CAPABILITY_REGISTRY (REQ-316) — test_regression_pilot.py
 - workflows-src/rotate-aws-key.yml + synced copies (SPEC §5.9)
 - consumer deploy.yml: no cross-repo uses: (SPEC §10 Q1 — inline adapter, option c)
 - kj installed (v0.0.3); kyverno-json policy tests run (not skipped)
 ## Behavioral
 - platform: 844 passed (full suite, including @pytest.mark.slow live-AWS CAPs)
 - consumer: 90 passed, 6 skipped (pre-existing unrelated skips)
 - kj substrate: 69 targeted policy/engine tests pass against real kj (zero skips)
 - pilot policies: pass on valid fixtures, fail on invalid (verified via kj scan violations)
 ## Security
 - no raw NOVA_AWS_* export in scripts/run_platform.sh shell env (SPEC §5.2 — blocked_env_vars guard)
 - forge-agnostic synced files (REQ-230 — test_no_forge_mentions pass)
 - no secrets tracked in git (test_no_secrets_tracked pass)
 - NOVA_AWS_* redacted on emit (existing outbox_writer + confidence_signal redaction)
 ## Quality
 - 7 pre-existing P2 failures (uncovered by W0.5 full-suite run with kj installed) all fixed:
  dynamodb examples (.yml), sync_workflows drift, CAP-024 deck path (-marp.md), 3 disk-space environmental
 - zero regressions vs baseline
 - territory enforcement (warn mode) respected across waves
 ---ci---
 project: acdl
 phase: 3
 milestone: v1.26
 status: verify
 ---
@@ -0,0 +1,31 @@
 # VERIFY — v1.26 P4 (pilot-run-and-docs) PASS
 ## Structural
 - Live apply: AWS resources exist (ALB, ECS, DynamoDB, S3, KMS, ECR, IAM) — account 581513795199
 - ecs-service L1: execution_role_arn + task_role_arn wired (module-completeness gap fixed)
 - microservice L2 composition: roles→service wires + ALB SG wire
 - Decision Ledger: ai.decision.made + nova.outcome.backfilled (hash chain valid)
 - fact_decision.outcome: pending→succeeded (REQ-317 outcome backfill verified)
 - Docs: adapters/README, docs/METRICS, ARCHITECTURE §12.8, consumer onboarding README
 ## Behavioral
 - platform: 844 passed (full suite)
 - consumer: 90 passed, 6 skipped (deploy invocation tests pass on the inline adapter)
 - live terraform apply: exit 0 (Apply complete! Resources created)
 ## Security
 - NOVA_AWS_* not in shell env (run_platform.sh unset after sourcing .env.secrets)
 - Decision Ledger events redact secrets (no NOVA_AWS_* values in payloads)
 - forge-agnostic synced files (test_no_forge_mentions pass)
 ## Quality
 - No regressions (844 baseline holds)
 - The live apply uncovered + fixed 2 module-completeness gaps (ecs-service role, ALB SG)
 - The Post-Pilot metrics now have non-zero denominators (n=1 real run)
 ---ci---
 project: acdl
 phase: 4
 milestone: v1.26
 status: verify
 ---
@@ -0,0 +1,945 @@
 # Nova — Architecture (v1.1 target)
 > Target architecture for the real Agentic Cloud Delivery Platform (rebranded
 > Nova in v1.15). Source of truth for **how**: `docs/architecture.md` (v0.2) is the upstream
 > draft; this file is the Nova-repo operating copy, refined at phase
 > boundaries. Where this file and `docs/vision.md` conflict, the vision wins.
 ## Status
 Architecture is at **v0.2** upstream (`docs/architecture.md`). Milestone v1.1
 **finalizes it to v1.0** in Phase 07 by resolving the 11 open decisions
 (see `PROJECT.md` open-decision resolutions table). This file records the
 locked commitments and the v1.1 spike scope.
 ## Overview
 The platform is **four layers + six cross-cutting concerns**. The sixth
 concern — the engine abstraction (§12) — is first-class, not an
 implementation detail. The vision's "Two Consumer Surfaces, One Platform"
 tenet binds everything: L3A and L3B converge on the same contract schema,
 the same policy envelope, and the same evidence stream.
 ```
                  ┌──────────── acdl-contracts ────────────┐
  Developer ───▶  │ commit contract.yaml                   │   (L3A)
  Citizen dev ──▶ │ Issue → agent → contract.yaml            │   (L3B)
                  └────────────────┬───────────────────────┘
                                   │ (push)
                                   ▼
                         ┌──────────────────────┐
                         │ central pipeline      │
                         │ (acdl repo, Gitea      │
                         │  Actions / act_runner) │
                         └────────┬─────────────┘
                                  │
        ┌─────────────────────────┼─────────────────────────┐
        ▼                         ▼                           ▼
  contract→IR resolution   policy (Checkov/Kyverno)    confidence signal
        │                         │                           │
        ▼                         ▼                           ▼
  Terraform adapter ──▶ terraform plan ──▶ PolicyCheckResult ──▶ {score,band}
        │                                                                │
        ▼                                                                ▼
  dev (autonomous, ≥0.50)   qa (HITL, ≥0.75)   prod (HITL, ≥0.90)   dr (HITL, ≥0.95)
        │
        ▼
  DynamoDB outbox ──▶ S3 Object Lock (7-yr, source of truth) ──▶ GitHub audit repo (hot index)
        │
        ▼
  acdl-evidence (timeline UI)
 ```
 ## Layers
 ### Layer 1 — Foundational Primitives
 Single-purpose, **engine-agnostic** primitive modules. L1 modules do
 not compose with other L1s; L1 takes its environment as input. The L1
 interface is defined against the **Target Stack IR**, not against Terraform
 directly (the IR is shaped to round-trip to Terraform in v1, per §12.1).
 - No inter-L1 references. L1 may call Terraform data sources.
 - Semver: interface → MAJOR, behavior → MINOR, lifecycle → PATCH (W3.D).
 - Immutability on publication. 12-month deprecation window.
 - AI refinement is a flag; the trigger is the W1.A joint condition.
 ### Layer 2 — Composed Stacks
 Combine L1 primitives into deployable shapes. Each codebase maps to one
 canonical L2 stack (`multiStack: true` only per W1.B). Shape X
 (parameterized module) or Shape Y (thin-composition layer). Hierarchical
 composition, max depth 5, only registered L1s. The thin-composition tree's
 `wires` field is defined against the IR's relationship type, not a Terraform
 module block.
 Pipeline quality checks: secrets-in-plaintext, public ingress, IAM
 wildcard, KMS key reference, tag compliance, naming convention. Restricted
 from thin-composition: IAM principal creation, network boundary creation,
 key/secret creation, external data transfer. Auto-promote after 3 observed
 usages.
 ### Layer 3A — Developer Consumer Surface
 Tag-based reference to the central pipeline template. Developer-owned
 workflow file, no platform auto-sync. L3A and L3B are parallel paths, not a
 progression. **W2.A (Path B):** tag for dev/qa, SHA for prod; platform CLI
 resolves tag→SHA for prod-bound workflows.
 ### Layer 3B — Agentic Consumer Surface
 Hybrid runtime, skill as markdown, agent as executor. Trust model: trust
 and always verify on the platform side. Skill envelope (4 dimensions).
 Stateless agents, all state in the platform. `profile: agentic` marker
 unlocks `naturalLanguageIntent`, `confidenceAtSubmission`, `agentTrace`.
 Initial skill catalog (BA.A): web API, worker, scheduled job, static asset,
 basic observability bootstrap.
 Environment progression:
 | Environment | Autonomy | Attester | Gate |
 |---|---|---|---|
 | dev | Full autonomy (no HITL) | — | Confidence ≥ 0.50, all six inputs present |
 | qa | Held for attestation | QA | GitHub Deployment approval + full QA matrix (§10) |
 | prod | Held for attestation | SRE | GitHub Deployment approval + full SRE matrix (§10) |
 | dr | Held for attestation | SRE | GitHub Deployment approval + dr-drill evidence |
 **Staging is removed.** Dev is the only autonomous environment.
 ## Cross-cutting concerns
 ### Central pipeline template (§6)
 JSON Schema (draft 2020-12) with a thin domain wrapper. Central repo +
 generated client libraries. Multi-stage validation: schema → policy → NFR →
 confidence. Distributed enrichment. GitOps reconciler (K8s API; cdlc-gitops
 state → CRDs) + Terraform execution layer (§12.5). The pipeline emits one
 `PolicyCheckResult` per policy rule; the confidence signal consumes them as
 one normalized input.
 ### Contract schema (§7)
 Central repo + generated client libraries. Strict fail-fast at schema
 stage, multi-stage validation with reason codes from a published
 vocabulary. **W3.E:** per-env mandatory inputs —
 - dev: `stack`, `environment`
 - qa adds: `validation.e2eSuite`, `validation.loadTest`
 - prod adds: `runbook`, `dashboard`, `oncall`
 - dr adds: `drDrillRef`
 - `inputs` always optional; `profile: agentic` fields optional everywhere.
 ### Confidence signal (§8)
 Six canonical inputs, weighted sum with per-input breakdown. Per-env
 thresholds: dev ≥ 0.50, qa ≥ 0.75, prod ≥ 0.90, dr ≥ 0.95. Structured output
 `{ score, band, perInput, reasonCodes }`. 1-year storage, no retraining in
 v1. Halt with explicit reason on missing input.
 Policy input = list of `PolicyCheckResult` records (engine-agnostic).
 Severity → penalty: critical → hard override to mandatory block; high →
 -0.2; medium → -0.05; low → -0.01; info → 0.0. One critical finding
 hard-overrides the score regardless of all other inputs.
 **BA.B:** thresholds frozen for v1; tuning begins v1.2 (quarterly FP/FN
 tracking; override = Infra & Ops + SRE joint sign-off, itself a
 confidence-event).
 ### Audit and evidence stream (§9)
 Tiered ledger: **S3 with Object Lock in compliance mode** (cold, source of
 truth, 7-year retention) + **GitHub audit repo** (`acdl-evidence`, hot
 query index, not part of the chain). Daily checkpoints. Event schema: JWS
 detached signature, `prev_event_hash` chain, controlled-vocabulary
 `event_type`. Outbox pattern: local durable outbox + async worker.
 Outbox database = **DynamoDB**. RPO = 0 (synchronous write to local outbox
 before contract submission ack); RTO = async worker's dead-letter recovery.
 Single-region in v1. The outbox also stores per-contract QA and prod
 approver identities (the only durable record outside GitHub's audit log).
 ### Human-in-the-Loop mechanics (§10)
 Pre-execution gates. qa, prod, dr are PR-based attestation gates backed by
 GitHub Environments with required reviewers. No partial deployment to roll
 back on rejection (qa, prod); dr is a separate GitHub Deployment against a
 separate cluster/region.
 Reviewer routing: GitHub CODEOWNERS + Environment required reviewers
 (qa → QA; prod → SRE; dr → SRE). CODEOWNERS routes, does not enforce
 identity distinctness.
 **Separation of duties** (platform-internal, not GitHub-native, not Kyverno
 in v1): on dev→qa promotion the platform writes the QA approver's GitHub
 identity to the DynamoDB outbox keyed by `contractId`; on qa→prod it reads
 the stored QA approver and the new SRE approver; if equal, it blocks, emits
 `SEPARATION_OF_DUTIES_VIOLATION`, and routes a halt artifact to SRE on-call.
 Full 8-concern attestation matrix (functional, performance, security
 posture, contract NFRs, operational readiness, incident response,
 capacity/cost, resilience) — see `docs/architecture.md` §10.4.
 Timeout: 1 business day = warn + escalate; 2 business days = auto-freeze +
 re-submit (linked via `supersedes`). Rejection returns the contract to HELD;
 the audit chain is extended, not torn up.
 ### Agentic stack (§11)
 Hybrid runtime: platform-managed control plane + consumer-owned agent.
 Versioned, signed skill catalog over MCP. Skill envelope enforced on
 invocation and result submission. Consumer-owned skill execution; the
 platform does not run the skill. Stateless agents, all state in the
 platform. Skills are reviewed for sensitive data before release (Infra &
 Ops owns the review; it is the mandatory release gate).
 ### Angine execution (§12) — the binding constraint
 **Target Stack IR** (locked): a engine-neutral description of resources
 (typed inputs/outputs/NFRs), relationships (single parent per child),
 composition (tree, max depth 5), and policy hooks. The L1 registry, L2
 thin-composition tree, contract YML, and PolicyCheckResult schema are all
 defined against the IR — none against any specific engine.
 **Angine adapters** are the only engine-specific code. An adapter
 compiles the IR into a engine execution plan. **v1 ships exactly one
 adapter: the Terraform adapter.** v2+ may add OpenTofu, Pulumi, K8s CRDs
 without architectural change.
 v1 reality: the IR is shaped to round-trip cleanly to Terraform (nearly
 isomorphic). As more adapters appear, the IR gets more expressive and the
 adapters gain translation logic; the L1 content, the YML standard, and the
 thin-composition tree do not change.
 **Terraform adapter (v1):** translates IR-typed L1 interface → Terraform
 `variable`/`output` blocks; IR-typed L2 thin-composition tree → Terraform
 root module; IR-typed relationships → module references; emits a
 `terraform plan` from the IR. The adapter is a thin layer; it does not own
 L1/L2 content.
 State storage: S3 (state) + DynamoDB (locking), cloud-managed,
 single-region in v1.
 Policy toolchain: **Checkov** for Terraform plan policy (the L2 checks +
 tag/naming); **Kyverno** for K8s-native/platform-internal policy; **OPA**
 reserved for cross-resource cases, explicitly last resort.
 **Policy result normalization (§12.6):** the confidence signal consumes a
 normalized `PolicyCheckResult` schema, not raw engine output.
 ```json
 {
  "contractId": "uuid",
  "evaluatedAt": "ISO-8601",
  "engine": "checkov | kyverno | opa",
  "ruleId": "CKV_AWS_24 | KYVERNO_NO_PRIVILEGED | ...",
  "severity": "critical | high | medium | low | info",
  "result": "pass | fail | skipped | error",
  "message": "human-readable",
  "evidence": { "...engine-specific, opaque to the signal..." },
  "resourceRef": "IR-typed resource identifier"
 }
 ```
 Execution layer: GitHub/Gitea Actions in the central pipeline repo. State
 locking via DynamoDB. **AWS credentials via OIDC federation — long-lived
 credentials are forbidden** (§12.5). The platform does not run
 `terraform apply` against a developer's workstation; all execution is in
 the central pipeline.
 Registry maintenance: L1 publication updates the L1 registry in the same
 PR. The registry is the IR-typed contract, not a Terraform-specific
 variable schema.
 Contract→IR resolution: the contract declares intent in IR-typed terms;
 the pipeline resolves it to a target stack (list of L1 instances + inputs +
 relationships); the Terraform adapter compiles the target stack to a plan.
 ## v1.1 spike scope
 The spike (Phases 08–10) materializes the **minimum** that proves the IR
 commitments hold (no polyglot mess):
 - One L1: `l1-s3` (IR-typed interface; the only AWS resource in the spike).
 - One L2 thin-composition: `l2-static-assets` (references `l1-s3` only).
 - Terraform adapter: IR → `terraform plan` against AWS via OIDC.
 - One contract submission → contract→IR → `terraform plan` → Checkov
  `PolicyCheckResult` → confidence signal → evidence event to the DynamoDB
  outbox.
 - State: S3 + DynamoDB (real AWS, single-region).
 Out of spike scope: full HITL matrix wiring, Kyverno, OPA, MCP skill
 catalog, GitOps reconciler, multi-region, prod/dr environments, the 5-skill
 L3B catalog. Those are post-spike (v1.2+) platform build-out.
 ## Gitea API surface (carried from v1.0, refined)
 | Capability | Gitea support | ACDL approach (v1.1) |
 |------------|---------------|----------------------|
 | Org-scoped repo create | `POST /api/v1/orgs/{org}/repos` | Used for any new repos |
 | Native Pages | **None** | Serve `acdl-evidence` via raw file URLs (unchanged from v1.0) |
 | Environments API | **None**; act_runner ignores `environment:` | Model HITL gates via `workflow_dispatch` approval inputs (v1.0 D-013 pattern) — **refined in Phase 07** for the real pre-execution gate model |
 | `repository_dispatch` | Not supported | Cross-repo trigger via `workflow_dispatch` API (unchanged) |
 | Reusable workflows | Supported | `acdl/.gitea/workflows/pipeline.yml` via `uses: ...@<ref>` |
 | `id-token: write` / OIDC | **Not supported** (RESEARCH TARGET 1, conf 0.95). Gitea docs list `id-token` as an unsupported GitHub-only scope; open proposal go-gitea/gitea#33681; draft PR go-gitea/gitea#36988 unmerged. Even Gitea's own CI uses long-lived AWS keys (issue #37980). | **Spike waiver D-039:** per-run-rotated long-lived key (rotated after each run by `scripts/rotate_spike_key.sh`). Real OIDC deferred to v1.2, blocked on PR #36988. |
 | `actions/configure-aws-credentials` | Unusable without OIDC | Spike uses static AWS creds from a (rotated) Gitea Actions secret via the `aws-actions/configure-aws-credentials@v4` `access-key-id`/`secret-access-key` inputs, or plain `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` env vars. v1.2 switches to `role-to-assume` when OIDC lands. |
 ### Branch pinning rule (refined for W2.A)
 - Dev/qa contracts reference the reusable workflow by **tag**
  (`@v1.1-spike`).
 - Prod-bound workflows reference by **SHA**; the platform CLI
  (`platform/cli/resolve-tag.ts`, Phase 07) resolves the current tag to its
  SHA. (Spike scope: the CLI is a stub; the real CLI lands in v1.2.)
 ### Verification toolchain
 ACDL has no `package.json`. The verification gate substitutes:
 - **typecheck:** `terraform validate`, `python3 -m py_compile`, JSON Schema
  validation (`ajv` or `python -m jsonschema`) against `schemas/`.
 - **test:** per-phase `scripts/verify_phaseNN.sh` (Phase 06: archive integrity;
  Phase 07: schema validation + decision-resolution completeness; Phase 08:
  OIDC assume-role + state backend; Phase 09: IR + L1 + adapter `terraform
  plan`; Phase 10: end-to-end contract submission).
 - **build:** `terraform init` (real build for the spike).
 - See `PERSONAS.md` verification_toolchain.
 ## Build order (v1.1)
 1. Phase 06 — archive demo, reorient repo.
 2. Phase 07 — finalize architecture v1.0; author schemas + designs.
 3. Phase 08 — AWS OIDC bootstrap (use temp key once, rotate).
 4. Phase 09 — IR + `l1-s3` + Terraform adapter → `terraform plan`.
 5. Phase 10 — `l2-static-assets` + contract→IR → end-to-end spike.
 6. COMPLETE gate — review → ship `v1.2.0` → audit. **DONE.**
 ## v1.2 build-out scope
 v1.2 takes the v1.1 spike (dev-only, `plan`-only, single S3 L1) to a real,
 simpler, better-documented platform that delivers a microservice to AWS ECS
 Fargate end-to-end. The locked architecture (§1–§12) is unchanged — v1.2
 extends the *implementation*, not the design.
 ### In scope (five axes, user-directed 2026-07-21)
 1. **Re-evaluate the current state.** go-gitea/gitea#36988 (OIDC for Gitea
   Actions) re-checked 2026-07-21: still **open** (last updated 2026-05-27,
   not merged). Real OIDC remains deferred to v1.3+; v1.2 extends the D-039
   per-run-rotated-key waiver as **D-047**. The waiver continues to satisfy
   §12.5's *intent* (no *persistently* long-lived key): the spike key is
   rotated after each run by `scripts/rotate_spike_key.sh`, and Phase 12
   tightens the IAM scoping + rotation hygiene.
 2. **NFR improvements on the existing spike.** Least-privilege IAM audit of
   `spike_runner_policy.json`; idempotent `create_state_backend.py` /
   `create_iam_user.py`; proper exit codes / error handling; P1-1 redaction
   (two AWS access key IDs in `.ciagent/VERIFY.md` Phase 09 narrative).
 3. **Streamline / simplify the current setup.** Consolidate
   `run_spike_plan.sh` + `run_spike_e2e.sh` into one
   `scripts/run_platform.sh`; remove dead code and stale `platform/` paths.
 4. **README.md fully up to date on how the platform works.** Reflect v1.1
   complete; document the actual spike flow, `scripts/run_platform.sh`, the
   real repo layout, and the v1.2 objective.
 5. **Bootstrap a consumer repo with a basic microservice deployed to ECS
   end-to-end.** New Gitea repo `acdl-consumer-microservice` (org
   `continuous-intelligence`); new IR-typed L1s (`l1-vpc`, `l1-ecs-cluster`,
   `l1-ecs-service`, `l1-iam-role`, `l1-alb`, `l1-ecr`); new
   `l2-microservice` thin-composition; one contract submission →
   `terraform apply` (dev, autonomous per §10, confidence ≥ 0.50) → a live
   ECS Fargate service serving HTTP 200 → evidence event to the DynamoDB
   outbox → acdl-evidence timeline.
 ### Angine extension (ECS Fargate)
 The Terraform adapter (§12) remains the only engine-specific code. v1.2
 expands the adapter `TYPE_MAP` to cover the six new ECS-shaped IR resource
 types. The L1 interface shape (IR-typed inputs/outputs/NFRs, registered in
 `modules-ir/registry.json`) is unchanged — only the set of registered L1s
 grows. The IR commitments (REQ-28) continue to hold: `modules-ir/`,
 `schemas/`, `contracts/`, `core/confidence_signal.py`,
 `core/contract_resolver.py`, `core/outbox_writer.py`
 remain engine-agnostic.
 ### `terraform apply` (dev only)
 v1.2 lifts the engine execution from `plan` to `apply` for the `dev`
 environment only. Dev is autonomous per §10 (confidence ≥ 0.50, no HITL).
 `apply` for qa/prod/dr remains HITL-gated and out of scope for v1.2. The
 apply result (resources created, plan diff) is captured in the evidence
 stream as a `terraform.apply` event.
 ### Out of scope for v1.2 (deferred to v1.3+)
 | Feature | Reason |
 |---------|--------|
 | Real OIDC federation | go-gitea/gitea#36988 still open. v1.2 extends D-039 waiver (D-047); real OIDC is v1.3+. |
 | Full HITL matrix wiring (qa/prod/dr) | v1.2 is dev-only autonomous `apply`; HITL wiring is v1.3. |
 | Kyverno + OPA policy engines | v1.2 keeps Checkov only; Kyverno/OPA are v1.3. |
 | MCP skill catalog + real L3B agent | v1.2 keeps the L3B stub; the 5-skill catalog is v1.3. |
 | Audit ledger build-out (S3 Object Lock + JWS + async worker + DLQ + daily checkpoints) | v1.2 keeps the v1.1 outbox; the regulatory ledger is v1.3. |
 | Multi-region state / outbox | Single-region in v1 (§9, §12.3); multi-region is v1.3+. |
 | Prod/dr environments | v1.2 is dev-only; prod/dr are v1.3. |
 | GitOps reconciler (ArgoCD/Flux) | v1.3+. |
 ## Build order (v1.2)
 1. Phase 11 — re-eval #36988 + NFR audit + simplification findings + README rewrite.
 2. Phase 12 — NFR harden + simplify (idempotent bootstrap, one `run_platform.sh`, IAM audit, redactions).
 3. Phase 13 — six ECS L1s + adapter `TYPE_MAP` expansion.
 4. Phase 14 — `l2-microservice` + contract schema extension.
 5. Phase 15 — consumer repo + `terraform apply` (dev) → live ECS service.
 6. Phase 16 — capstone e2e: consumer commit → live HTTP 200 → evidence → timeline.
 7. COMPLETE gate — review → ship `v1.3.0` → audit.
 ## v1.8 Architecture Addendum
 > Milestone v1.8 (complete, tag `v1.8.0`). Adds encryption-by-default,
 > deletion-protection-by-default, uptime monitoring, decommission alias,
 > engineering standards, and path documentation.
 ### New Primitives
 - **`kms-key`** (`aws:kms:key`) — Per-stack customer-managed KMS key with
  `enable_key_rotation = true`. One key per L2 deployment (no shared keys).
  Wired into both L2 compositions as a child, with its `kms_key_arn` output
  connected to all children's `kms_key_arn` input. Adapter emits
  `aws_kms_key` + `enable_key_rotation`.
 - **`uptime`** (`aws:ecs:uptime-service`) — Uptime-kuma on ECS Fargate with
  a feature flag (`feature_flag_enabled`), monitored endpoints (HTTP/DNS/TCP),
  alert channels (Teams/email/SMS/GitHub issues). Deployed by default after
  any L2 module with a separate terraform state. When the feature flag is
  false, the adapter emits no resources.
 ### Encryption by Default
 All 12 L1 primitives have `encryption_enabled` NFR (default true). Primitives
 with at-rest data (s3, rds, ecr, ecs-service, ecs-cluster) have an optional
 `kms_key_arn` input. The adapter emits encryption blocks (SSE-KMS for S3,
 storage_encrypted for RDS, encryption_configuration for ECR) referencing the
 per-stack CMK when provided. Managed KMS fallback with stderr warning for
 standalone L1 deployments.
 ### Deletion Protection by Default
 All 12 L1 primitives have `deletion_protection` NFR (default true). The
 adapter emits `lifecycle { prevent_destroy = true }` when true. L2 modules
 expose a `features.deletion_protection` flag (default true) propagated to
 all children via the resolver. Setting `inputs.deletion_protection: false`
 in the contract disables it for the whole stack.
 ### Decommission Alias
 A `mode: decommission` on the deploy pipeline implements a 2-step destroy:
 1. Disable deletion protection (resolve with `deletion_protection: false`,
   terraform plan/apply, HITL SRE gate via GitHub environment).
 2. Zero counts + destroy (`decommission_transform` zeroes all scalable counts,
   terraform plan/apply, second HITL SRE gate).
 CMDB validation via DynamoDB `acdl-change-requests` table. The Lambda
 `validate_change_request` action queries the table and asserts
 `status == "approved"` + `consumerRepo` match.
 ### Adapter Expansion
 TYPE_MAP grew from 16 to 19 entries (+ `aws:kms:key`, `aws:kms:alias`,
 `aws:ecs:uptime-service`). Specialized emission branches added for KMS key
 rotation, S3 SSE-KMS configuration, uptime ECS Fargate task, and
 `prevent_destroy` lifecycle on all resources.
 ### Pipeline Stages
 The deploy pipeline grew from 8 to 9 stages (+ `deploy-uptime` after
 `publish-outputs`). The `deploy-uptime` stage constructs a synthetic uptime
 contract from the L2 stack outputs, resolves + adapts it to a separate
 terraform state directory, and publishes the uptime URL via PR comment.
 ### Forge-Agnostic API URLs
 The platform Lambda (`contract_ingestor.py`) reads `GITHUB_API_BASE` env
 for forge-agnostic API URLs. GitHub uses `/search/issues`; Gitea uses
 `/repos/{owner}/{repo}/issues`. Detection via `/api/v1` in the base URL.
 ## v1.9 Addendum (2026-07-23)
 ### New Components
 - **`core/contract_resolver.py` interpolation** (D-081): the resolver
  now expands `${env.<field>}` + `${contract.<field>}` tokens
  post-schema-validation, pre-IR-resolution. The env context is the
  loaded environment onboarding JSON (`core/environments/<name>.json`,
  schema `schemas/environment.schema.json`). The resolver's
  `child_input_map` routes L2 wires to the sub-resource that declares the
  input (P1-1 — `desired_count` → `aws:ecs:service`, `family` →
  `aws:ecs:task_definition`).
 - **`core/environment_check.py` `load()`** (REQ-104): loads + returns the
  parsed environment JSON; emits a stderr warning for placeholder
  `account_id` when env != dev.
 - **`core/hitl_gates.py`** (REQ-108, D-084): the HITL pre-execution
  attestation gate. Records the approver identity to the DynamoDB outbox
  (`approver_qa`/`approver_prod`/`approver_dr`), runs the separation-of-
  duties check on prod, invokes the attestation matrix, returns
  `(ok, reason)`. Dev skips (autonomous). `run_platform.sh` calls
  `attest` before apply for qa/prod/dr.
 - **`core/attestation_matrix.py`** (REQ-109, D-084): the 8-concern
  attestation matrix from `hitl_matrix_design.md` §10.4. Offline-testable
  concerns (contract NFRs, schema validity, policy pass) run for real;
  operator-supplied concerns accept signed evidence artifacts validated
  for freshness + schema. Signature verification skips when
  `ACDL_ATTESTATION_SIGNING_KEY_ID` is unset (D-089).
 - **`core/separation_of_duties.py` `route_halt_artifact`** (REQ-107):
  real SNS publish (`acdl-sod-halt` topic, ARN from
  `ACDL_SOD_HALT_TOPIC_ARN`) + outbox fallback
  (`SEPARATION_OF_DUTIES_VIOLATION` event). The SNS topic is defined in
  `terraform/platform/main.tf`.
 - **`adapters/wiz/wiz_adapter.py` `WizClient`** (REQ-110): real GraphQL
  API client (`<WIZ_API_URL>/graphql`, Bearer auth, pagination via
  `pageInfo.hasNextPage`). `fetch_and_adapt` translates issues →
  `PolicyCheckResult`. Graceful degrade when unconfigured.
 - **`adapters/kyverno/kyverno_adapter.py`** (REQ-111): fleshed-out
  `PolicyReport` → `PolicyCheckResult` mapping (pass/fail/skip/warn +
  severity + skip-with-reason + resource construction). Inactive-for-TF
  guard preserved.
 ### Per-Environment Promotion (D-082)
 The deploy workflow (`.github/workflows/deploy.yml` +
 `.gitea/workflows/deploy.yml`, byte-identical) declares an `environment`
 `workflow_call` input. When non-empty, `run_platform.sh --environment
 <name>` overrides the contract's `environment` field before schema
 validation (D-088). One CI job per environment; promotion = running the
 matching job, no `environment:` field editing. Per-env contract files
 (`contracts/<module>.<env>.yaml`) use interpolation for env-specific
 values.
 ### Adapter Parameterization (P1-1, D-085)
 The adapter (`adapters/terraform/adapter.py`) reads ECS/ALB/VPC defaults
 from L1 `interface.json` inputs (`desired_count`, `launch_type`,
 `family`, `target_type`, `load_balancer_type`, `name`). The adapter is a
 thin translator; the `child_input_map` routes wires to the declaring
 sub-resource.
 ### Deferred (D-083)
 S3 Object Lock + JWS detached signatures + async worker + DLQ + daily
 checkpoints (audit ledger build-out) — deferred to a future milestone.
 The hash-chain + DynamoDB-outbox path remains the v1.9 production audit
 record.
 ## v1.10 Addendum — Regression VERIFY + Local Emulators + Capability Re-Verification
 ### Regression-Class VERIFY (D-091, `core/regression_verify.py`)
 The standard VERIFY stage was diff-scoped (it checked the phase diff
 only, never re-ran underlying capability). This let 8 NFR-patch phases
 (v1.9.1–v1.9.8) pass while the platform decayed. The regression-class
 VERIFY (`core/regression_verify.py`) re-runs capability checks against
 the current codebase and tags each Verified/Decayed/Broken. It fails
 closed on any non-Verified capability, blocking milestone completion.
 The registry (`CAPABILITY_REGISTRY`) holds 16 capability checks
 (CAP-001..CAP-016): 12 local-tier + 4 live-AWS. Adding a capability is
 a single function + one registry entry. The gate runs via
 `scripts/run_regression.sh` and writes `.ciagent/REGRESSION_REPORT.md`
 + `.json`.
 ### Local Emulating Adapters (D-092, `core/local_emulators.py`)
 Four local adapters let the platform run the full headline E2E without
 cloud credentials:
 - `FlatFileOutbox` — flat-file DynamoDB outbox emulator (hash-chained
  JSONL; resumable across instances; chain verification).
 - `LocalEcsEmulator` — local ECS Fargate HTTP 200 emulator (binds port
  0 on 127.0.0.1; daemon thread; clean destroy).
 - `LocalS3StateBackend` — rewrites the terraform S3 backend to a local
  backend (per-stack tfstate in a temp folder).
 - `LocalLambdaStub` — invokes the contract_ingestor handler in-process
  (patches `_get_dynamodb`/`_get_secrets_client`/`urllib.urlopen`;
  DynamoDB writes redirected to the FlatFileOutbox).
 `run_local_e2e()` runs the full pipeline: contract → resolver → adapter
 → local S3 backend → local ECS (HTTP 200) → flat-file outbox (chain
 verified) → local Lambda (200). Gated on `ACDL_LOCAL_TIER=1`.
 ### Capability Re-Verification Sweep (D-093)
 `.ciagent/CAPABILITY_INVENTORY.md` enumerates 16 auto-verified
 capabilities + 6 IAM-gated escalated resources. The sweep found and
 fixed 7 adapter defects in `adapters/terraform/adapter.py` (duplicate
 outputs, duplicate args, missing required args, deprecated AWS provider
 v5 arg names). The headline E2E now passes at both tiers: local
 emulator + live-AWS terraform init/validate/plan.
 ### Adapter Defect Fixes (P54)
 7 defects fixed in `adapters/terraform/adapter.py`:
 1. Duplicate output definitions (per-resource + stack-level both emitted).
 2. Duplicate `desired_count`/`launch_type` on ECS service.
 3. Duplicate `target_type`/`family`/`load_balancer_type`.
 4. Missing `assume_role_policy`/`role_name` on IAM role (L2 composition gap).
 5. Missing `cidr_block`/`vpc_id`/`name` defaults on VPC/subnet/route_table/
   ECS cluster/ECR repository.
 6. ECR `kms_key_arn` unsupported arg → `encryption_configuration` block.
 7. CloudFront OAC + WAF deprecated arg names (AWS provider v5):
   `signing_behavior`, `signing_protocol`, `origin_access_control_id`,
   `s3_origin_config.origin_access_identity`, `origin_id`, `rule`
   (singular), `scope=CLOUDFRONT` (uppercase).
 ## v1.11 Addendum — Stateless Adapter + Pipeline-Driven Lifecycle Testing
 **Stateless adapter (D-098).** `adapters/terraform/adapter.py` rewritten
 from a 918-line monolith (3 constant tables `TYPE_MAP`/`INPUT_MAP`/
 `OUTPUT_MAP`, 39 type-specific branches) to a ~80-line stateless assembler.
 Each L1 module ships a real `terraform/` module dir
 (`versions.tf`/`variables.tf`/`locals.tf`/`main.tf`/`outputs.tf`) owning
 its resource shape, nested blocks, and defaults. The adapter reads the
 registry, emits a root `main.tf` instantiating each L1 as
 `module "x" { source = "..." }` with resolved inputs and wired refs.
 **Terraform owns lifecycle (D-101).** `scripts/run_platform.sh` gains
 `--apply` and `--destroy` modes. Python never runs terraform.
 `scripts/verify_deploy_microservice.py` is deleted.
 **Pipeline-driven testing (D-102).** A `modules-lifecycle` pipeline
 (Gitea + GitHub, byte-identical) matrix-runs each L1 module's
 `examples/{simple,complex}.yml` contracts through apply→modify→destroy
 against live AWS. No per-module Python/pytest. The "test" = the pipeline
 cell going green.
 **Single platform VPC (D-105).** `terraform/platform/main.tf` owns ONE
 VPC; the microservice composition references it via
 `terraform_remote_state` (data source). State keys are deterministic and
 env-aware (`spike/{contract.id}/{contract.environment}/terraform.tfstate`).
 **NOVA_LIFECYCLE_MODE (v1.12, REQ-134; renamed ACDL→NOVA in v1.15 P2).** The lifecycle pipeline defaults
 to plan-only (fast, no AWS mutation, no cost). A CI variable
 `NOVA_LIFECYCLE_MODE` (default `plan`) overrides to `full` for the real
 apply→modify→destroy. (P2–P4 dual-read fallback to `ACDL_LIFECYCLE_MODE`;
 fallback removed in P5 per the v1.15 addendum.)
 ## v1.12 Addendum — Presentation Refinement + CAP-013 Fix
 **CAP-013 adapter dedup fix (REQ-129).** Multi-resource L1s (ecs-service,
 alb) with stack outputs + cross-module refs now dedup to ONE module block
 named by the composition child id, with expanded sub-ids rewritten via
 `id_remap`. `terraform validate` succeeds for the microservice stack.
 **CAP-017/018 probe fixes (REQ-130).** CAP-017's probe no longer requires
 `locals.tf` for modules that legitimately omit it. CAP-018's probe
 instantiates `LocalLambdaStub` with the required `outbox` arg.
 ## v1.13 Addendum — Presentation Polish + Config Schema Migration
 **Config.json schema migration (v1.13.1).** Regenerated
 `.ciagent/config.json` to the updated CIAgent v2 config structure (drop
 removed fields, migrate `gitea`→`release.gitea`, add
 `secrets`/`ship`/`backend`/`ideation`/`personas`/`logging`/`telemetry`
 sections).
 **Presentation polish (v1.13.0, v1.13.2).** Action headlines, story-arc
 restructure, larger fonts, 6 new mermaid diagrams, badge cleanup,
 platform-architecture diagram. Docs-only NFR patches.
 ## v1.14 Addendum — NFR Refinement (bug fixes, security, stubs, tests, docs)
 **Bug fixes (Wave 1, P1-P6).** Adapter dedup rejects unregistered modules
 with ValueError (P1). Static-assets composition wires cloudfront inputs
 (P2). L2 lifecycle scripts document remote-state design (P3). Regression
 gate adds `terraform fmt -check` syntax probe (P4). Adapter dedup-merge +
 remote-state-key unit tests (P5). ALB target group name_prefix derives
 from var.name (P6).
 **Security (Wave 2, P7-P12).** 6 swallowed-error sites narrowed to
 specific exceptions (P7). Account ID externalized to
 `ACDL_AWS_ACCOUNT_ID` env (P8). IAM policy scoped to `acdl-*` ARNs (P9).
 Contract ingestor validates contractId/environment/error (P10). Environment
 schema adds `additionalProperties: false` + format validation (P11).
 `.gitignore` credential-pattern catch-all (P12).
 **Stub/test/CI/hygiene (Wave 3, P13-P17).** Kyverno `--kube-version` flag
 removed (P13, G-103). Orphan artifacts + dead config cleaned (P14). 7
 untested scripts gain test coverage (P15). Gitea workflow parity
 documented + script `set` flags fixed (P16). Config.json persona +
 branching strategy + ollama-cloud aligned (P17).
 **Standards/docs/VPC (Wave 4, P18-P20).** STANDARDS.md reconciled (P18).
 Documentation synced: ARCHITECTURE.md addenda, stale `@v1.6-1.9` → `@v1.13`,
 GRILL G-005/G-008 resolved, COST.md window extended, D-083 deferral
 recorded (P19). Platform VPC CIDR parameterized + data-driven subnet
 count (P20).
 **D-083 deferral (explicit).** The audit ledger build-out (S3 Object Lock
 + JWS detached signatures + SQS DLQ + async worker + daily checkpoints)
 remains deferred (D-096, v1.14). The hash-chain + DynamoDB outbox is the
 v1.14 audit record. JWS per-event authenticity is not implemented; a
 forged event is only detectable by re-reading the whole chain. The
 deferral is documented here explicitly per the v1.14 grill (E-001).
 ---
 ## v1.15 Addendum — Nova Rebrand (Major/breaking, 2026-07-30)
 **Milestone:** v1.15-Nova. A full rebrand from **ACDL** / "Agentic Cloud
 Delivery Platform" → **Nova** / "The New Dawn of DevSecOps — security
 as a seamless enabler of fast deployments." This is a **Major
 milestone** (breaking): consumer-facing path, env var prefixes, SSM
 path, AWS tag keys, and AWS resource names all change. Per the
 branch-strategy precedent (breaking/feature milestones tag on their
 OWN minor line), v1.15 tags run on the **v1.15.x minor line**:
 `v1.15.0` (P0) → `v1.15.4` (P5 final = release). (G-104 binding.)
 ### Naming conventions (rebranded)
 | Convention | Before (v1.0–v1.14) | After (v1.15+) | Phase |
 |------------|---------------------|-----------------|-------|
 | Project name | `ACDL` / "Agentic Cloud Delivery Platform" | `Nova` / "The New Dawn of DevSecOps" | P1 |
 | Tagline | "Consumers declare intent; the platform delivers safe production deployment through an agentic stack" | (retained) **+** "The New Dawn of DevSecOps — security as a seamless enabler of fast deployments" | P1 |
 | Schema `$id` URL | `https://acdl.cloudinit.dev/schemas/...` | `https://nova.cloudinit.dev/schemas/...` | P1 |
 | Gitea release title | `ACDL vX.Y.Z` | `Nova vX.Y.Z` | P1 (forward only) |
 | Env var prefix | `ACDL_*` (21 vars) | `NOVA_*` (dual-read fallback in P2–P4; removed P5) | P2 |
 | Env loader | scattered `os.environ.get("ACDL_*")` | centralized `core/env.py` `get_env()` (D-108) | P2 |
 | Consumer contract path | `.acdl/contract.yml` | `.nova/contract.yml` | P2 |
 | Checkov custom rule file | `acdl_tagging.py` | `nova_tagging.py` | P2 |
 | Checkov tag-key enforcement | `acdl:*` (hard) | `nova:*` (warn P2, hard P3) | P2/P3 |
 | SSM parameter path | `/acdl/{env}/{contractId}/{output}` | `/nova/{env}/{contractId}/{output}` | P3 |
 | AWS tag keys | `acdl:owner|environment|contract|cost-center|ref` | `nova:owner|environment|contract|cost-center|ref` | P3 |
 | ABAC session policy match | `acdl:*` tags | `nova:*` tags (parallel-tag period) | P3 |
 | DynamoDB tables | `acdl-contracts`, `acdl-change-requests` | `nova-contracts`, `nova-change-requests` (scan+copy) | P4 |
 | Lambda (ingestor) | `acdl-contract-ingestor` (role/policy/function) | `nova-contract-ingestor` | P4 |
 | Secrets Manager secret | `acdl/github-token` | `nova/github-token` | P4 |
 | SNS topic | `acdl-sod-halt` | `nova-sod-halt` | P4 |
 | Security group | `acdl-ecs-sg` | `nova-ecs-sg` | P4 |
 | KMS alias | `alias/acdl-platform` | `alias/nova-platform` | P4 |
 | ECS cluster/service/task | `acdl-microservice` | `nova-microservice` | P4 |
 | ECR repo | `acdl-microservice` | `nova-microservice` (re-push) | P4 |
 | IAM user/policy | `acdl-spike-runner` (+policy) | `nova-spike-runner` (re-bootstrap) | P4 |
 | S3 state bucket | `acdl-tfstate-581513795199-us-east-1` | `nova-tfstate-581513795199-us-east-1` (`-migrate-state`) | P4 |
 | ALB name prefix | `acdl-alb` | `nova-alb` | P4 |
 | Lambda default table names | `CONTRACTS_TABLE` default `acdl-contracts` | default `nova-contracts` (D-111) | P4 |
 ### Unchanged conventions (out of scope)
 - **S&P Global Energy visual theme** (`sp-theme.json`, deck CSS: #D6002A
  red, Akkurat Pro) — client branding, not the Nova product brand (D-107).
 - **config.json `release.gitea.repo`** = `acdl` — real Gitea repo name
  unchanged (D-105). Doc URLs updated to `nova` for prose only.
 - **Git branch/tag naming** — `milestone/v*`, `phase/*`, `v*` semver; no
  brand name present (D-112: flat-branch convention preserved).
 - **Past Gitea release titles** — existing releases keep `ACDL vX.Y.Z`.
 ### Migration ordering (binding)
 1. **P1** docs/decks/prose — no runtime impact; ships consumer migration
   guide announcing the 5 breaking changes.
 2. **P2** code + env vars (dual-read) + consumer path — deployments don't
   break during the transition window (dual-read fallback).
 3. **P3** SSM path (copy → read → delete) + tag keys (parallel-tag →
   policy swap → remove old).
 4. **P4** AWS resource names — staged terraform migration (KMS alias,
   SNS/SG/Lambda recreate, DynamoDB scan+copy, ECR re-push, IAM
   re-bootstrap, state bucket `-migrate-state`, ALB recreate). Maintenance
   window + rollback runbook (`docs/NOVA_AWS_MIGRATION.md`).
 5. **P5** final review + audit + remove dual-read fallback + milestone ship.
 ### Capability gate (binding)
 The regression gate (CAP-001..CAP-016, `scripts/run_regression.sh`) must
 stay **16/16 Verified** throughout the rebrand. P2/P3/P4 update test
 fixtures that reference `ACDL`/`acdl` so the gate stays green. No
 capability is added, removed, or reclassified in v1.15 — the rebrand is
 nomenclature + identifiers, not behavior.
 ---
 ## v1.16 Addendum — Nova Simplification (NFR, 2026-07-30)
 The v1.16 NFR milestone added 6 new code components + 1 new Terraform
 module + 1 new schema, all documented here for the architecture record.
 ### New components
 | Component | Path | Purpose |
 |-----------|------|---------|
 | Onboarding request handler | `core/onboarding.py` | `generate_env_file(request, template_env)` — produces a `<env>.json` from a consumer onboarding request (P19, REQ-183). CLI entry point for self-service env-file generation. |
 | Decommission transform | `core/decommission_transform.py` | `decommission_transform(stack)` — zero counts + disable deletion protection (REQ-92). Extracted from contract_resolver (P12, REQ-176). |
 | Contract resolver CLI | `core/contract_resolver_cli.py` | `main()` CLI entry point — resolves a contract YAML to a Target Stack JSON. Extracted from contract_resolver (P12, REQ-176). |
 | Regression verify CLI | `core/regression_verify_cli.py` | `main()` CLI entry point — runs the regression gate + writes the report. Extracted from regression_verify (P13, REQ-177). |
 | Workflow sync generator | `scripts/sync_workflows.py` | `--check`/`--write` — generates the 3 byte-identical Gitea+GitHub workflow pairs from `workflows-src/` (P8, REQ-172). |
 | Onboarding Terraform | `terraform/onboarding/` | `aws_iam_role.consumer_deploy` + `aws_iam_role_policy.consumer_invoke` (ABAC `nova:owner` tag). Offline-proven only (P20, REQ-184, D-114). |
 ### Modified components
 | Component | Change | Phase |
 |-----------|--------|-------|
 | `core/contract_resolver.py` | `_load_env` delegates to `environment_check.load()` (dedup); `is_l2` uses registry `kind` field; `_load_schema` caches schemas; `decommission_transform` + CLI re-export shim (P12). | P7, P12, P14 |
 | `core/regression_verify.py` | Dedup helpers (`_check_resolver`, `_check_live_terraform_plan`, `_assert_contracts_resolve`); CAP-013..016 `Skipped` on post-teardown (G-111); `passed` accepts Skipped; CLI re-export shim (P13). | P5, P9, P13 |
 | `core/lambda/contract_ingestor.py` | Fail closed on missing IAM identity (P10); env enum from `core/environments/` (P10); payload size cap + schema validation (P11); `onboard_consumer` action (P18); `[NOVA-ALERT]` rebrand (P2). | P2, P10, P11, P18 |
 | `core/output_publisher.py` | `SAFE_OUTPUT_NAMES` schema-driven from `interface.json`; narrowed excepts; `urllib.error` import (P4, P14). | P4, P14 |
 | `core/environment_check.py` | Onboarding message rebranded Nova + self-service request path (P2, P19). | P2, P19 |
 | `core/local_emulators.py` | `LocalLambdaStub` sets `NOVA_LAMBDA_LOCAL_BYPASS`; stale dual-read comments + `acdl_*` prefixes removed (P3, P10). | P3, P10 |
 | `scripts/run_platform.sh` | `--help` flag; `run_hitl_gate()` fn; `NOVA_CONTRACT_ID`/`NOVA_WORK_DIR` config; decommission + uptime blocks extracted to sourced helpers (P6, P9, P15). | P6, P9, P15 |
 | `adapters/terraform/adapter.py` | State bucket `nova-tfstate-*` (P1); module docstring Nova (P2). | P1, P2 |
 | `adapters/kyverno/policies/require-resource-labels.yml` | `nova:*` labels (not `acdl:*`) (P1). | P1 |
 | `modules/registry.json` | `kind` field (`l1`/`l2`) on all 14 entries (P7). | P7 |
 ### New schema
 - `schemas/onboarding.schema.json` — the self-service onboarding request
  (consumerRepo, requestedEnvironment, ownerId, billingTag). P18, REQ-182.
 ### Onboarding request-path architecture (D-113)
 The no-humans onboarding flow is a 3-step request path (real AWS
 provisioning deferred):
 ```
 Consumer → POST Lambda (onboard_consumer) → pending CMDB row (P18)
         → core/onboarding.py → <env>.json binding file (P19)
         → terraform/onboarding/ → cross-account role + ABAC tag (P20, offline)
 ```
 The Lambda Function URL (IAM auth) + `consumer_invoke_policy.json` (ABAC
 `nova:owner`) are the transport; the request is accepted + a binding
 generated + the role Terraform proven offline. No AWS resources are
 created by the request path (D-113/D-114).
 ### Regression gate (G-111 binding)
 The regression gate (D-091) now treats `Skipped` as acceptable for the
 post-v1.11-teardown steady state (D-096): CAP-013..016 (live-AWS tier)
 return `Skipped` when the resources are absent (`NoSuchBucket`/
 `ResourceNotFoundException`). `RegressionReport.passed` is
 `all(r.status in ("Verified", "Skipped"))`. The gate passes at 18
 Verified + 4 Skipped (0 Decayed/Broken).
 ## v1.17 Addendum — Strategic Direction, Leadership Metrics & Unified Story (2026-08-04)
 The v1.17 milestone adds a telemetry/observability layer, a Decision
 Ledger, a metrics export pipeline, a unified narrative deck, and a
 durable strategic-direction artifact. This addendum documents the
 architecture; the full research findings are in RESEARCH.md §v1.17.
 ### New components
 | Component | Path | Purpose |
 |-----------|------|---------|
 | Event envelope | `core/metrics/event_envelope.py` | CloudEvents 1.0 envelope + `platform.*` semantic conventions (P1, REQ-187) |
 | Per-run manifest writer | `core/metrics/run_manifest.py` | Emits `nova.run.started/completed/failed` events + writes `metrics/runs/<run_id>.json` (P1, REQ-187) |
 | Decision Ledger (SQLite) | `core/metrics/decision_ledger.py` | Extends `outbox_writer.py` → SQLite append-only hash-chain table; `ai.decision.made` + `attestation.recorded` events + outcome backfill (P1, REQ-188, D-121) |
 | Infracost post-processor | `core/metrics/infracost_adapter.py` | Runs Infracost on plan JSON; emits `nova.cost.estimated{delta_usd}` (P1, REQ-187, D-120) |
 | Metrics collector | `core/metrics/collector.py` | Reads all grounded signals (files + events) → SQLite cold store at `metrics/nova_metrics.db` (P2, REQ-189) |
 | PowerBI export | `core/metrics/powerbi_export.py` | Emits CSV/JSON views to `metrics/powerbi/` (fact + dim + 8 deferred placeholder views) (P3, REQ-190) |
 | Metrics schemas | `schemas/metrics_*.schema.json` | Schemas for all event types + fact/dim tables (P1–P2, REQ-187/189) |
 | Metrics catalog | `docs/METRICS.md` + `docs/metrics/<kpi>.md` | Canonical catalog + per-KPI definition-of-success docs (P4, REQ-195, D-127) |
 | Unified narrative deck | `docs/presentations/nova-no-humans-platform.md` | Merged deck: Problem→Vision→How→Proof→Roadmap; x3 arc at deck+slide level (P5, REQ-196/197, D-130) |
 | Strategic direction | `.ciagent/NORTH_STAR.md` | PO-authored durable vision/objectives/anti-goals/targets; read by CIAgent in every future `/ci-run` (P0, REQ-185/186) |
 ### Modified components
 | Component | Change | Phase |
 |-----------|--------|-------|
 | `core/outbox_writer.py` | Extended to emit to SQLite append-only hash-chain table (Decision Ledger); `ai.decision.made` + `attestation.recorded` events added (P1, D-121) | P1 |
 | `scripts/run_platform.sh` | Per-run manifest writer invoked; `$WORK/*.json` persisted to `metrics/runs/`; Infracost post-processor invoked after plan (P1) | P1 |
 | `core/hitl_gates.py` | Emits `attestation.recorded` event to Decision Ledger on qa/prod/dr gate (P1, D-132) | P1 |
 | `core/confidence_signal.py` | Emits `nova.confidence.computed` + `nova.ai.decision.made` events (P1, D-122) | P1 |
 | `adapters/terraform/policy/checkov_adapter.py` | Emits `nova.policy.evaluated` event (P1) | P1 |
 | `core/regression_verify.py` | Emits `nova.capability.verified` event; CAP-023 (metrics collector) + CAP-024 (deck structure) added (P1, P6) | P1, P6 |
 | `pyproject.toml` | `addopts` gains `--junitxml=metrics/test-results.xml` + `--json-report` (P1, D-120) | P1 |
 | `docs/presentations/` | Two old decks retired (deleted); unified deck added (P5, D-130) | P5 |
 ### Telemetry/observability layer architecture (D-120)
 ```
 ┌─────────────────────────────────────────────────────────────────────┐
 │  Nova platform components (existing)                                │
 │  run_platform.sh · confidence_signal · checkov_adapter ·            │
 │  hitl_gates · regression_verify · outbox_writer · contract_ingestor │
 └──────────────────────┬──────────────────────────────────────────────┘
                       │ CloudEvents 1.0 envelope (new emitters, P1)
                       ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │  metrics/events.jsonl  (append-only CloudEvents log)                │
 │  metrics/runs/<run_id>.json  (per-run manifests)                    │
 │  metrics/decision_ledger.db  (SQLite hash-chain, D-121)             │
 │  metrics/test-results.xml  (junit, P1)                              │
 └──────────────────────┬──────────────────────────────────────────────┘
                       │ collector reads (P2)
                       ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │  metrics/nova_metrics.db  (SQLite cold store, D-126)                │
 │  fact_run · fact_capability · fact_policy_check · fact_confidence  │
 │  fact_test · fact_decision · fact_cost_estimate                     │
 │  dim_capability · dim_milestone                                     │
 │  + 8 empty placeholder views (deferred metrics)                    │
 └──────────────────────┬──────────────────────────────────────────────┘
                       │ powerbi_export (P3)
                       ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │  metrics/powerbi/  (CSV/JSON views, folder connector, D-129)        │
 │  → PowerBI dashboards (external)                                    │
 └─────────────────────────────────────────────────────────────────────┘
 ```
 **Hot path: deferred (D-126).** No live ops dashboard; SQLite is
 cold-only (batch/historical). The hot path activates when live AWS is
 re-provisioned (D-096 lift).
 ### NORTH_STAR integration point (REQ-186)
 `.ciagent/NORTH_STAR.md` is read by CIAgent in context-loading for all
 future milestones. The integration mechanism (to be finalized in P4):
 a reference from `PROJECT.md` + `ARCHITECTURE.md` (this section) + a
 config entry in `config.json` (`strategic_direction_file:
 ".ciagent/NORTH_STAR.md"`) that the run workflow reads at SPECIFY. This
 ensures the strategic direction survives across milestones without
 being overwritten by status updates.
 ### §12.7 — Policy Engine Registry (v1.25, REQ-291)
 The policy-engine abstraction is first-class: a swappable `PolicyEngine`
 protocol so the engine may change without touching the confidence
 signal, the pipeline, or the `PolicyCheckResult` schema. This is the
 **swap boundary** that keeps the platform's compliance posture
 replaceable (Strategic Objective #2 — provable trust via a replaceable
 substrate, not a vendor lock-in).
 ```
 contract.yml ─┐                         ┌─→ list[PolicyCheckResult] ─┐
 stack IR ─────┼─→ PolicyEngine.evaluate ├─→ list[PolicyCheckResult] ─┼─→ confidence_signal
 plan JSON ────┤    (protocol)            └─→ list[PolicyCheckResult] ─┘  (engine-agnostic,
 PCR list ─────┘                                                         unchanged)
                    │
                    ▼
          ┌─ KyvernoJsonEngine (shells to `kj scan`; engine: "kyverno")
          └─ OpaEngine (future — same protocol; engine: "opa")
   checkov/wiz ──→ raw findings ──→ (merged PCR list is the meta-policy payload)
 ```
 **The protocol (`core/policy_engine.py`):**
 ```python
 class PolicyEngine(Protocol):
    @property
    def name(self) -> str: ...
    def is_configured(self) -> bool: ...
    def evaluate(self, payload, policy_dir: Path, contract_id: str) -> list[dict]: ...
 ```
 **The registry** reads `config.json.policy.engine` (default
 `"kyverno-json"`) and returns the active engine. A `NullEngine` is the
 fallback when the `policy` key is absent (emits `SKIPPED` PCRs —
 backward compatibility for tests that don't set the key). The
 confidence signal is **untouched** — it already consumes
 `list[PolicyCheckResult]` engine-agnostically (§12.6). v1.25 only
 changes *who produces* the PCR list, not *what* the list is.
 **Engine enum reuse (D-116):** kyverno-json PCR records carry
 `engine: "kyverno"` (no new enum value). The `engine` field records the
 policy-engine *family*, not the specific binary. The K8s Kyverno adapter
 and the kyverno-json engine are distinguished by `ruleId` prefix
 (`KYVERNO_` vs `KJ_`) and `evidence` payload shape (`namespace`/`kind`
 vs `assertion`/`jmespath`).
 **Defense-in-depth (D-119):** the declarative meta-policy
 `block-on-any-critical` (asserts no PCR has `severity: critical` +
 `result: fail`) is the *source of truth* for "critical = block". The
 `confidence_signal.py` `PENALTY["critical"]: None` hard-override stays
 as the *imperative* safety net — the meta-policy runs *before* the
 confidence signal (produces PCRs that flow in), the hard-override runs
 *inside* it (the last gate). Removing the hard-override would make the
 "critical = block" guarantee depend on a single policy file — a
 regression in provable trust.
 **Graceful degradation (D-120):** `KyvernoJsonEngine.is_configured()`
 returns false when `which kj` is absent → `evaluate()` returns a single
 `SKIPPED` PCR (`ruleId: "KJ_ENGINE_NOT_CONFIGURED"`). The platform
 functions without the binary (the "platform functions without AI /
 deterministic scripts" tenet holds — kyverno-json is deterministic, not
 AI; the `is_configured()` guard ensures the platform runs even when the
 binary is not installed).
@@ -0,0 +1,78 @@
 # `.ciagent/archive/` — Completed-Milestone History
 This directory holds byte-identical snapshots of `.ciagent/` files that
 were compressed out of the active agent context. Compression is **lossless
 via relocation**: every original byte is reachable here, and the git
 history at the commit prior to compression preserves the authoritative
 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.
 ## Contents
 ### Snapshots of slimmed files (full content before compression)
 | File | Original (lines) | Replaces | Status at time of snapshot |
 |---|---|---|---|
 | `PROJECT-v1.0-v1.24.md` | 1784 | `.ciagent/PROJECT.md` | v1.0–v1.24 milestone-by-milestone narrative + active milestone v1.26 sections |
 | `REQUIREMENTS-v1.0-v1.24.md` | 2490 | `.ciagent/REQUIREMENTS.md` | All requirements v1.0 (REQ-01) through v1.26 (REQ-322) |
 | `ROADMAP-v1.0-v1.24.md` | 2341 | `.ciagent/ROADMAP.md` | All phase breakdowns v1.0 through v1.26 |
 | `ARCHITECTURE-v1.0-v1.24.md` | 945 | `.ciagent/ARCHITECTURE.md` | Full architecture reference + historical "how we got here" narrative |
 The slimmed in-place files retain: active milestone v1.26 context, the
 v1.25 milestone (since v1.26 tags ride the v1.25.x line), the durable
 vision/tenets/RACI/capability-status sections, and the current-state
 architecture reference.
 ### Completed-phase artifacts (relocated verbatim)
 | File | Original (lines) | Phase(s) documented |
 |---|---|---|
 | `REVIEW.md` | 111 | Multi-persona code review records from completed phases |
 | `AUDIT.md` | 553 | Project health audit records (reconstruction tests, branch hygiene) |
 | `VERIFY.md` | 86 | Per-phase verification records |
 | `PRE_MORTEM.md` | 228 | Pre-mortem analyses for completed milestones |
 ### Live operational files NOT archived
 These files remain at their canonical `.ciagent/` paths because they are
 read/write targets of live code paths and must not be relocated:
 - `REGRESSION_REPORT.json` — written by `core/regression_verify.py:705`,
  read by `core/metrics/collector.py:27` + `core/metrics/trust_snapshot.py:21`
  + `metrics/` views.
 - `REGRESSION_REPORT.md` — written by `core/regression_verify.py:704`,
  referenced by `scripts/run_regression.sh`.
 - `CHECKPOINT.json` — the authoritative resume point for `/ci-run`.
 - `config.json` — operational configuration (no historical content).
 ## How to load archived content
 Agents that need completed-milestone history can read these files
 directly (they live inside `.ciagent/`, so the path convention holds):
 ```
 .ciagent/archive/PROJECT-v1.0-v1.24.md
 .ciagent/archive/REQUIREMENTS-v1.0-v1.24.md
 .ciagent/archive/ROADMAP-v1.0-v1.24.md
 .ciagent/archive/ARCHITECTURE-v1.0-v1.24.md
 .ciagent/archive/{REVIEW,AUDIT,VERIFY,PRE_MORTEM}.md
 ```
 For the authoritative pre-compression state of any `.ciagent/` file,
 use git history at the commit immediately preceding the compression
 commit (search the log for `chore(P02): compress .ciagent/ files`).
 ## `completed-milestones/`
 Reserved for future per-milestone summary files if a milestone's
 narrative is too large for the slimmed in-place ROADMAP/PROJECT. Currently
 empty; v1.0–v1.24 narrative is fully preserved in the four snapshot
 files above.
@@ -4,11 +4,16 @@
      "slug": "acdl",
      "name": "Nova — The New Dawn of DevSecOps",
      "default": true
    },
    {
      "slug": "nova-blockchain-exchange",
      "name": "Nova Pilot Consumer — Blockchain Stock Exchange",
      "default": false
    }
  ],
  "active_project": "acdl",
-  "active_projects": ["acdl"],
+  "active_projects": ["acdl", "nova-blockchain-exchange"],
-  "active_milestone": "v1.25",
+  "active_milestone": "v1.26",
  "autonomy": {
    "level": "full",
    "escalation_hooks": ["deploy", "delete_data", "merge_to_main"],
@@ -59,7 +64,7 @@
  },
  "git": {
    "branching_strategy": "flat",
-    "_branching_strategy_note": "ACDL uses flat workflow (committed directly to main per established convention since v1.0). The 'phase' strategy is advisory; CIAgent uses milestone/phase branches for v1.14 but the project convention is flat.",
+    "_branching_strategy_note": "Nova uses flat workflow (committed directly to main per established convention since v1.0; renamed ACDL→Nova in v1.15). The 'phase' strategy is advisory; CIAgent uses milestone/phase branches for v1.14 but the project convention is flat.",
    "auto_commit": true,
    "auto_push": true
  },
@@ -67,7 +72,8 @@
    "sources": [".env", ".env.secrets", ".env.*"],
    "disallow": ["shell_env", "netrc", "keychain", "rc_files", "global_config"],
    "scopes": {
-      "gitea": "ACDL_GITEA_TOKEN",
+      "forge": "NOVA_FORGE_TOKEN",
      "gitea": "NOVA_FORGE_TOKEN",
      "github": "GITHUB_TOKEN",
      "gitlab": "GITLAB_TOKEN",
      "openai": "OPENAI_API_KEY",
@@ -0,0 +1,92 @@
 # Nova Pilot Consumer — Blockchain Stock Exchange
 > **Milestone:** v1.26 — Live Pilot Estate Activation
 > **Git:** https://git.cloudinit.dev/continuous-intelligence/nova-blockchain-exchange
 > **Local clone:** /root/nova-blockchain-exchange
 > **Role:** The first real consumer estate. A stock exchange built on a
 > homegrown blockchain, offering equities trading (pilot scope). The
 > consumer repo owns the app code + `contract.yaml`; the Nova platform
 > (`acdl` repo) provides the deploy workflow, policy engine, and
 > attestation gates.
 ---
 ## Vision / Core Value
 A self-contained securities-trading exchange where every order, match,
 and settlement is recorded as an immutable transaction on a homegrown
 Proof-of-Authority (PoA) blockchain. The pilot demonstrates that Nova's
 autonomous infrastructure can take a real consumer estate from contract
 to production — apply, attest, record — without an operator in the loop
 of normal operations.
 ## North Star Alignment
 - **Strategic Objective #1** (production-grade zero-touch operations):
  this estate is the first real consumer; the pilot activates the
  autonomy claim beyond internal demos.
 - **Strategic Objective #2** (provable trust): every apply decision +
  attestation lands in the Decision Ledger; the settlement-finality
  kyverno-json policy (IDEATE) makes trust a policy artifact.
 - **Strategic Objective #3** (compounding ROI): unblocks the three
  Post-Pilot targets (Touchless Resolution ≥99%, Human Escalation
  <0.1%, AI Decision Accuracy ≥99.5%) — the denominators activate when
  this estate runs.
 ## Domain Boundaries
 - **This repo owns:** the blockchain (consensus, blocks, transactions),
  the order-matching engine, the settlement service, the `contract.yaml`
  that declares the infrastructure, and the consumer-side deploy workflow
  invocation (`uses: acdl/.github/workflows/deploy.yml@v1.25`).
 - **The platform (`acdl`) repo owns:** the deploy workflow, the policy
  engine (kyverno-json), the contract resolver, the adapter, the
  confidence signal, the HITL gates, and the Decision Ledger.
 ## Scope: v1.26 Pilot
 - **Equities only** (bonds, derivatives, options deferred to future
  milestones — different settlement models).
 - **Minimal PoA ledger** — append-only blocks, single validator (pilot),
  T+1 settlement finality = block commit. No multi-validator BFT.
 - **Homegrown chain** — authored as part of this repo, not deployed on
  Ethereum/Solana/Hyperledger.
 ## Anti-Goals (v1.26)
 1. Not a general-purpose blockchain platform — purpose-built for
   securities settlement in the pilot.
 2. Not multi-validator consensus — single validator for the pilot.
 3. Not bonds/derivatives/options — equities only this milestone.
 4. Not a replacement for the Nova platform — this is a *consumer* of
   Nova, not a fork.
 ## Key Decisions (v1.26 — established in SPECIFY, refined in CLARIFY)
 | ID | Decision | Rationale | Affects |
 |---|---|---|---|
 | D-200 | Pilot scope = equities only | Bonds/derivatives/options have very different settlement models; equities (T+1) is the simplest to demonstrate the Nova platform's policy gates over a real estate. | Phase count; requirement scope. |
 | D-201 | Homegrown PoA ledger (single validator) | Minimal viable chain for a pilot; settlement finality = block commit. Multi-validator BFT is a future milestone. | Blockchain core design. |
 | D-202 | Consumer repo = `nova-blockchain-exchange` (Gitea) | New repo under `continuous-intelligence` org; tracked as 2nd CIAgent project. | Multi-project config. |
 | D-203 | AWS account = 581513795199 (existing) | Reuse the bootstrapped account; state bucket + outbox table created in pre-run Workstream A3. | Env JSON binding. |
 | D-204 | D-083 (S3 Object Lock/JWS) stays deferred | The SQLite hash-chain + DynamoDB outbox is the pilot's audit record. Tamper-evidence is a future milestone. | Audit ledger scope. |
 | D-205 | Cold-only metrics sufficient (D-126) | No hot ops dashboard in the pilot; cold SQLite store + PowerBI export. | Metrics pipeline. |
 ## Constraints
 - The consumer repo's deploy MUST go through `deploy.yml@v1.25` (the
  reusable workflow) — no direct `terraform apply` bypassing the
  platform's policy + attestation gates.
 - The `contract.yaml` MUST validate against
  `schemas/contract.schema.json`.
 - The homegrown blockchain MUST be deterministic (same inputs → same
  block) — it is automation, not AI (NORTH_STAR Objective #2 tenet).
 ## Context
 - The Nova platform (`acdl` repo) completed v1.25 (kyverno-json Unified
  Policy Engine). The swappable `PolicyEngine` adapter is in place.
 - 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`.
@@ -0,0 +1,180 @@
 # nova-blockchain-exchange — Consumer Onboarding Guide
 > **Milestone:** v1.26 — the first real Nova consumer estate. This
 > guide is for the consumer side: how to invoke the deploy, what
 > 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`.
 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
 settlement service) and the `contract.yaml` that declares the
 infrastructure. The Nova platform (`acdl` repo) owns the deploy
 workflow, the policy engine, the contract resolver, the Terraform
 adapter, the confidence signal, the HITL gates, and the Decision
 Ledger. The consumer never clones the platform repo and never runs
 `terraform apply` directly.
 ---
 ## 1. Invoke the deploy
 The consumer's `.github/workflows/deploy.yml` (and its byte-identical
 `.gitea/workflows/deploy.yml` mirror) is a `workflow_dispatch` workflow.
 It does **not** use cross-repo `uses:` (SPEC §10 Q1 — the Gitea forge
 rejects it). Instead it is an **inline adapter**: it checks out the
 consumer repo, then checks out `acdl/acdl` @ `ref: v1.25` into
 `platform/`, then runs `bash platform/scripts/run_platform.sh`.
 To run a deploy:
 1. In the consumer repo's Actions UI, pick the **Deploy** workflow.
 2. Click **Run workflow**.
 3. Inputs:
   - `mode` = `full` (the default — applies the Terraform). Other
     values: `plan-only` (no apply), `check-only` (policy + confidence
     only), `decommission` (requires a `changeRequestId`).
   - `environment` = `dev` (the pilot scope — equities only, dev only,
     D-020/D-200). Leave empty to use the contract's `environment`
     field.
 4. The workflow runs the platform pipeline end-to-end: contract
   resolve → adapter compile → terraform plan → policy (kyverno-json)
   → confidence signal → (dev: autonomous apply) → Decision Ledger
   events.
 For the pilot, the documented invocation is `mode=full,
 environment=dev`. The first live run was `blkex-pilot-apply-v0.2`
 (2026-08-19).
 ---
 ## 2. Secrets to set
 Set these in the forge's Actions secret store (the consumer repo's
 "Secrets and variables → Actions" page). The platform-managed
 scheduled workflow `rotate-aws-key.yml` rotates the `NOVA_AWS_*` key
 daily (SPEC §5.9 — the v0.2 deploy uses the currently-active key).
 | Secret | Purpose |
 | --- | --- |
 | `NOVA_AWS_ACCESS_KEY_ID` | The static AWS access key for the deploy IAM principal. Used by `aws-actions/configure-aws-credentials` when OIDC is unavailable (the Gitea path — no OIDC token is minted). |
 | `NOVA_AWS_SECRET_ACCESS_KEY` | The matching secret key. Rotated by `workflows-src/rotate-aws-key.yml`. |
 | `AWS_DEFAULT_REGION` | The target region (`us-east-1` for the pilot). |
 The platform's `.github/workflows/deploy.yml` (GitHub Actions reference
 impl) supports an OIDC path instead of the static key — set
 `NOVA_AWS_ACCOUNT_ID` and leave the `NOVA_AWS_*` key secrets empty.
 The Gitea inline adapter uses the static-key path.
 ---
 ## 3. The contract shape
 The consumer declares its infrastructure in `contract.yaml` at the
 repo root, validated against the platform's
 `schemas/contract.schema.json`. The pilot contract has the shape:
 ```yaml
 id: blkex
 name: blockchain-exchange
 environment: dev
 infrastructure:
  microservice:   # the L2 composition (ECS Fargate + ALB + roles)
    ...
  dynamodb:       # the L1 DynamoDB table (the ledger)
    ...
  s3:             # the L1 S3 bucket (block storage)
    ...
 ```
 Three `infrastructure.*` blocks: `microservice` (the L2 composition
 that wires the ECS service, the ALB, and the IAM roles together), and
 the two L1 primitives (`dynamodb` for the ledger, `s3` for block
 storage). Per-environment variants live in
 `contracts/blockchain-exchange.{dev,qa,prod}.yml` (the per-env
 promotion model, REQ-105). The pilot runs the `dev` variant.
 The contract is the **only** consumer-facing artifact that describes
 infrastructure. It is IR-typed (engine-agnostic); the platform
 resolves it to a target stack, the Terraform adapter compiles the
 stack to HCL, and `terraform apply` runs in the central pipeline —
 never on the consumer's workstation.
 ---
 ## 4. What the platform does
 When `run_platform.sh` runs against `contract.yaml`:
 1. **Resolve** the contract to a target stack (a list of L1 instances +
   inputs + relationships), reading `modules/registry.json` for each
   L1's `terraform_dir`.
 2. **Compile** the stack to Terraform HCL via the stateless adapter
   (`adapters/terraform/adapter.py`) — emits `module "<rid>" { source }
   ` blocks + wired `ref:` refs. No `TYPE_MAP` — each L1 owns its
   shape.
 3. **Plan** — `terraform plan` against the live AWS account. Infracost
   runs on the plan JSON and emits `nova.cost.estimated`.
 4. **Policy** — the kyverno-json engine evaluates the meta-policies
   (`block-on-any-critical` + the pilot policies) and emits
   `PolicyCheckResult` records.
 5. **Confidence** — the confidence signal consumes the six inputs (the
   PCRs included) and emits `nova.confidence.computed` with
   `{ score, band, perInput, reasonCodes }`. Dev threshold = 0.50.
 6. **Apply** (dev, autonomous — no HITL gate) — `terraform apply`
   against account `581513795199`. On success, `nova.ai.decision.made`
   + `nova.run.completed` land in the Decision Ledger.
 7. **Backfill** — the outcome (`pending → succeeded`) is backfilled
   (REQ-317), producing `nova.outcome.backfilled`. The SQLite
   hash-chain is extended, not torn up.
 The consumer does not see steps 1–7 directly; the consumer sees the
 workflow's green check + the uploaded artifacts (`nova-terraform`,
 `nova-platform-log`).
 ---
 ## 5. How to verify post-deploy
 Two independent verifications — read the AWS API and read the Decision
 Ledger. Neither trusts the other.
 **AWS API (the infrastructure landed):**
 - `aws elbv2 describe-load-balancers` — the ALB
  (`app-254671247.us-east-1.elb.amazonaws.com` for the pilot).
 - `aws ecs describe-services --cluster nova-cluster --services
  nova-microservice` — the ECS service is `ACTIVE`.
 - `aws dynamodb describe-table --table-name nova-blkex-ledger-dev` —
  the ledger table exists (PK `block_index`, PAY_PER_REQUEST).
 - `aws s3api head-bucket --bucket
  nova-blkex-blocks-dev-581513795199-us-east-1` — the block bucket
  exists (versioning + SSE).
 **Decision Ledger (the trust record):**
 - The SQLite hash-chain at `metrics/decision_ledger.db` has the
  `nova.ai.decision.made` row for `blkex-pilot-apply-v0.2` (chosen
  action `pass`, `human_override` false) + the
  `nova.outcome.backfilled` row (outcome `pending → succeeded`).
 - The chain is valid (`prev_event_hash` links, 0 breaks). The
  Trust Snapshot (`metrics/TRUST_SNAPSHOT.md`) records the verdict.
 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).
 ---
 ## References
 - `.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/nova-blockchain-exchange/PROJECT.md` — the consumer
  project charter (vision, scope, decisions D-200..D-205).
 - `.ciagent/nova-blockchain-exchange/REQUIREMENTS.md` — the consumer
  requirements (REQ-313 contract, REQ-314 deploy invocation).
 - `adapters/README.md` §Consumers — the Gitea adapter note
  (SPEC §10 Q1 — inline checkout-then-call, no cross-repo `uses:`).
@@ -0,0 +1,221 @@
 # Requirements — nova-blockchain-exchange (v1.26 pilot)
 > **Project:** nova-blockchain-exchange — blockchain stock exchange (pilot)
 > **Milestone:** v1.26 — Live Pilot Estate Activation
 > **Scope:** equities only; minimal PoA ledger; T+1 settlement finality.
 ---
 ## v1.26 — Live Pilot Estate Activation
 ### REQ-310 — Homegrown PoA blockchain core
 The consumer repo implements a minimal Proof-of-Authority blockchain:
 append-only blocks, single validator (pilot), SHA-256 block hash chain,
 deterministic block production (same ordered transactions → same block).
 The chain records every order, match, and settlement as transactions.
 Settlement finality = block commit (a transaction is final when its
 block is committed to the chain).
 **Must-haves:**
 - `chain/block.py` — Block dataclass (index, timestamp, prev_hash,
  transactions, nonce, hash). `compute_hash()` deterministic.
 - `chain/ledger.py` — Ledger class: `append_block()`, `verify_chain()`,
  `get_block(index)`, `get_latest_block()`. Genesis block on init.
 - `chain/validator.py` — PoA validator: single validator (config-driven,
  pilot), `propose_block(transactions)` → Block, `commit_block(block)`.
 - `tests/test_block.py`, `tests/test_ledger.py`, `tests/test_validator.py`
  — chain integrity, hash determinism, genesis, append/verify.
 ### REQ-311 — Order-matching engine
 A limit-order-book matching engine: buy/sell orders with price + size,
 matched at the best price (price-time priority). Produces match
 transactions recorded on the chain.
 **Must-haves:**
 - `engine/order_book.py` — OrderBook: `add_order(order)`,
  `match_orders()` → list of Match (buyer, seller, price, size).
 - `engine/order.py` — Order dataclass (id, side, symbol, price, size,
  timestamp).
 - `tests/test_order_book.py` — match priority, partial fills, no-match.
 ### REQ-312 — Settlement service
 T+1 settlement: matches commit to the chain; a settlement is final when
 its block is committed. The service reads matches from the order engine,
 produces settlement transactions, and submits them to the ledger.
 **Must-haves:**
 - `settlement/service.py` — SettlementService: `settle(match)` →
  SettlementTransaction, `submit(ledger)`. Idempotent (re-settling a
  match is a no-op once final).
 - `tests/test_settlement.py` — happy path, idempotency, finality check.
 ### REQ-313 — Consumer `contract.yaml` ✓ complete (P2, v1.25.2)
 The consumer repo declares its infrastructure via a `contract.yaml` at
 the repo root, validated against `schemas/contract.schema.json`. The
 contract references the Nova platform's deploy workflow
 (`uses: acdl/.github/workflows/deploy.yml@v1.25`) and declares the
 blockchain exchange stack (the AWS resources the app needs: ECS for
 the matching engine, DynamoDB for the ledger, S3 for block storage).
 The DynamoDB L1 primitive (REQ-322) must land before this contract can
 declare `dynamodb` — ECS + S3 already exist.
 **Must-haves:**
 - `contract.yaml` — id, name (`blockchain-exchange`), environment
  (dev/qa/prod variants), infrastructure block.
 - `contracts/blockchain-exchange.dev.yml`, `.qa.yml`, `.prod.yml` —
  per-environment variants (per-env promotion model, REQ-105).
 - `tests/test_contract_validates.py` — schema validation against the
  platform's `schemas/contract.schema.json`.
 ### REQ-314 — Consumer deploy workflow invocation ✓ complete (P2, v1.25.2)
 The consumer repo's GitHub/Gitea Actions invoke the Nova platform's
 reusable `deploy.yml@v1.25` workflow with `mode: full` for the pilot.
 The workflow checks out the consumer repo + the platform repo, runs
 `scripts/run_platform.sh`, and records the apply decision + attestation
 in the Nova Decision Ledger.
 **Must-haves:**
 - `.github/workflows/deploy.yml` — `uses: acdl/.github/workflows/deploy.yml@v1.25`
  with `with: { contract: contract.yaml, mode: full, environment: dev }`.
 - `.gitea/workflows/deploy.yml` — byte-identical mirror (the platform's
  deploy workflow is forge-agnostic).
 - `tests/test_deploy_workflow_invocation.py` — asserts the `uses:` ref
  + inputs are correct.
 ### REQ-315 — Settlement-finality kyverno-json policy (IDEATE I6)
 A kyverno-json policy asserting that every promotion (qa→prod) requires
 settlement finality: all matches in the promotion window have committed
 blocks. This is the securities-specific extension of v1.25's policy
 engine — it applies Nova's compliance posture to the blockchain domain.
 **Must-haves:**
 - `policies/settlement-finality.json` — kyverno-json policy over the
  settlement-service status JSON (asserts `all_committed: true`).
 - `tests/test_settlement_finality_policy.py` — passing + failing
  fixtures; skip when `kj` absent.
 ### REQ-316 — Pilot-estate regression capability (CAP-025)
 A new capability in the regression gate: "pilot estate apply→attest→record
 round-trip." The regression gate asserts that the consumer estate can
 run end-to-end (contract resolve → adapter compile → terraform plan →
 policy scan → confidence signal → attestation → outbox record) against
 the live AWS account `581513795199`.
 **Must-haves:**
 - `core/regression_verify.py` gains CAP-025 (live-pilot-apply).
 - `tests/test_regression_pilot.py` — the round-trip assertion.
 ### REQ-317 — Outcome-backfill emitter (IDEATE I1)
 Wire `apply.completed` / `apply.failed` events back into `fact_decision`
 in the cold store so the AI Decision Accuracy metric has a non-`pending`
 outcome. Today `fact_decision.outcome` is stuck at `pending` (D-096
 blocker). The backfill emitter reads `run_manifest.completed/failed`
 events and updates the corresponding decision's outcome.
 **Must-haves:**
 - `core/metrics/outcome_backfill.py` — `backfill(decision_id, outcome)`
  updates `fact_decision.outcome` + `fact_decision.backfilled_at`.
 - `core/metrics/collector.py` — invokes backfill after run completion.
 - `tests/test_outcome_backfill.py`.
 ### REQ-318 — `reason='confidence'` escalation tag (IDEATE I2)
 Emit a distinct `reason='confidence'` field on the `block` band's
 `ai.decision.made` event so the Human Escalation Frequency metric has a
 discriminated numerator. Today `hitl_block` is a boolean from the
 manifest; the `reason` discriminator is not stored.
 **Must-haves:**
 - `core/confidence_signal.py` — `ai.decision.made` gains
  `escalation_reason: 'confidence'` when `band == 'block'`.
 - `core/metrics/collector.py` — persists `escalation_reason` into
  `fact_run`.
 - `tests/test_confidence_escalation_reason.py`.
 ### REQ-319 — Env-JSON `state_backend` wiring reconciliation (IDEATE I3)
 The env JSON's `state_backend.bucket` field is currently unused by the
 adapter (the adapter computes `nova-tfstate-<AWS_ACCOUNT_ID>` directly).
 Reconcile: the adapter reads `state_backend.bucket` from the env JSON
 (falling back to the computed name for backwards compat). This closes
 the wiring gap so the pilot's env JSON is the single source of truth.
 **Must-haves:**
 - `adapters/terraform/adapter.py` — reads `env.state_backend.bucket`
  when present.
 - `tests/test_adapter_state_backend.py`.
 - `core/environments/*.json` — `state_backend.bucket` updated to the
  real bucket name `nova-tfstate-581513795199-us-east-1`.
 ### REQ-320 — Declarative pilot-readiness kyverno-json policy (IDEATE I5)
 A kyverno-json policy asserting the env JSON has a non-placeholder
 `account_id` (not `000000000000`) before any `terraform apply`. This is
 the declarative gate that prevents a pilot run against a placeholder
 account.
 **Must-haves:**
 - `adapters/kyverno-json/policies/pilot-readiness/no-placeholder-account.json`
 - `tests/test_pilot_readiness_policy.py`.
 ### REQ-321 — Docs + adapter README for the consumer estate
 Update `adapters/README.md` (new consumer row), `docs/METRICS.md` (the
 3 Post-Pilot metrics now grounded post-pilot), `.ciagent/ARCHITECTURE.md`
 (§12.8 — Pilot Estate), and `.ciagent/nova-blockchain-exchange/README.md`
 (consumer onboarding guide).
 **Must-haves:**
 - `adapters/README.md` — consumer-repo row.
 - `docs/METRICS.md` — Post-Pilot metrics grounded note.
 - `.ciagent/ARCHITECTURE.md` — §12.8 Pilot Estate.
 - `.ciagent/nova-blockchain-exchange/README.md` — onboarding guide.
 ### REQ-322 — DynamoDB L1 primitive (platform-side) ✓ complete (P2, v1.25.2)
 The blockchain exchange's ledger table needs a DynamoDB L1 primitive.
 Research (RESEARCH §3) confirmed the adapter is stateless/registry-
 driven (no `TYPE_MAP` — deleted in v1.11); a new stack type requires a
 new L1 module, not an adapter change. The `dynamodb` primitive mirrors
 the existing `s3` / `rds` primitives: `interface.json` (stack type
 `aws:dynamodb:table`, inputs `table_name`/`region`/`pk`/`sk`/`billing_mode`,
 outputs `table_arn`/`table_name`), `terraform/main.tf`
 (`resource "aws_dynamodb_table" "this"`), `README.md`, `instance.json`,
 + a `registry.json` entry. The pilot contract's `infrastructure.dynamodb`
 block references this primitive. This is the single platform-side
 module build-out for the milestone (ECS + S3 already exist).
 **Must-haves:**
 - `modules/l1/dynamodb/interface.json` — stack type
  `aws:dynamodb:table`, inputs, outputs.
 - `modules/l1/dynamodb/terraform/main.tf` —
  `resource "aws_dynamodb_table" "this"` (PK + optional SK,
  `billing_mode = PAY_PER_REQUEST` default, encryption + point-in-time-
  recovery enabled per v1.8 NFR defaults).
 - `modules/l1/dynamodb/README.md` — module doc.
 - `modules/l1/dynamodb/instance.json` — sample instance.
 - `modules/registry.json` — `dynamodb` entry (kind `l1`,
  `terraform_dir: modules/l1/dynamodb/terraform`).
 - `tests/test_adapter.py` — add `dynamodb` to `EXPECTED_L1_KEYS` +
  a resolution + emission test.
 - `modules/README.md` — catalog index updated.
 ### Summary
 13 requirements (REQ-310..322). Equities-only pilot; minimal PoA ledger;
 T+1 settlement; consumer deploy via `deploy.yml@v1.25`; 3 Post-Pilot
 metrics grounded (outcome backfill + escalation reason + pilot runs);
 3 kyverno-json policies extending v1.25 (settlement-finality,
 pilot-readiness, + the existing meta-policies apply); env-JSON wiring
 reconciled; DynamoDB L1 primitive authored (the single platform-side
 module build-out — the adapter is stateless/registry-driven, so the
 primitive is a new `modules/l1/dynamodb/` module + registry entry, not
 an adapter change).
@@ -0,0 +1,58 @@
 # Roadmap — nova-blockchain-exchange (v1.26 pilot)
 > **Project:** nova-blockchain-exchange — blockchain stock exchange (pilot)
 > **Milestone:** v1.26 — Live Pilot Estate Activation
 ---
 ## v1.26 — Live Pilot Estate Activation (active)
 Lift D-096 (live AWS re-provisioning); activate the first real consumer
 estate (a stock exchange on a homegrown PoA blockchain, equities only)
 against live AWS account `581513795199`; ground the three Post-Pilot
 targets in NORTH_STAR.md (Touchless Resolution ≥99%, Human Escalation
 <0.1%, AI Decision Accuracy ≥99.5%). The platform repo (`acdl`) provides
 the deploy workflow, policy engine, and attestation gates; this repo
 provides the app (blockchain + matching engine + settlement) + the
 `contract.yaml`.
 Tags run on the **v1.25.x** patch line: `v1.25.0` (P0) → `v1.25.N`
 (final phase = milestone release).
 ### Phase P1 — blockchain-core (planned, tag v1.25.1)
 - REQ-310: Homegrown PoA blockchain core (block, ledger, validator).
 - REQ-311: Order-matching engine (limit order book, price-time priority).
 - REQ-312: Settlement service (T+1, idempotent, finality = block commit).
 ### Phase P2 — consumer-contract-and-deploy (complete, tag v1.25.2)
 - REQ-313: Consumer `contract.yaml` + per-env variants. ✓
 - REQ-314: Consumer deploy workflow invocation (`deploy.yml@v1.25`). ✓
 - REQ-322: DynamoDB L1 primitive (platform-side, P2 W0). ✓
 ### Phase P3 — pilot-metrics-and-policies (planned, tag v1.25.3)
 - REQ-315: Settlement-finality kyverno-json policy.
 - REQ-316: Pilot-estate regression capability (CAP-025).
 - REQ-317: Outcome-backfill emitter.
 - REQ-318: `reason='confidence'` escalation tag.
 - REQ-319: Env-JSON `state_backend` wiring reconciliation.
 - REQ-320: Declarative pilot-readiness kyverno-json policy.
 ### Phase P4 — pilot-run-and-docs (planned, tag v1.25.4)
 - REQ-321: Docs + adapter README + onboarding guide.
 - Live pilot end-to-end run (apply → attest → record) against
  `581513795199`.
 ### Phase P5 — final review + audit + milestone ship (Final Phase, tag v1.25.5)
 - Multi-persona code review across P1..P4.
 - Audit: reconstruction test, branch hygiene, commit discipline.
 - Milestone ship: merge `phase/05` → `milestone/v1.26-pilot-activation`
  → `main`; tag `v1.25.5` (= the v1.26 release per prev-minor tagging
  rule); create Gitea release with full milestone summary; delete all
  milestone branches.
 - Update `REQUIREMENTS.md` (mark REQ-310..321 complete), `ROADMAP.md`
  (mark v1.26 complete), `NORTH_STAR.md` (note Strategic Objectives #1
  + #3 — first real consumer estate; Post-Pilot denominators activated).
 After v1.26: future milestones may add bonds/derivatives/options
 (different settlement models), multi-validator BFT consensus, and
 tamper-evident ledger (D-083 lift).
@@ -63,23 +63,6 @@ jobs:
      - name: Install test dependencies
        run: pip install -r requirements-test.txt
      - name: Install kyverno-json (kj) for policy-engine tests
        run: |
          # v1.25: kyverno-json is the primary policy engine. Tests that
          # require kj skip when absent, so this is best-effort (the suite
          # passes with or without kj). Install is cached via the Go
          # module cache (~/.cache/go-build + ~/go/pkg/mod).
          if command -v go >/dev/null 2>&1; then
            go install github.com/kyverno/kyverno-json/cmd/kj@latest && \
              echo "$(go env GOPATH)/bin" >> "$GITHUB_PATH" || \
              echo "kj install failed; policy-engine tests will skip"
          else
            sudo apt-get update && sudo apt-get install -y golang-go && \
              go install github.com/kyverno/kyverno-json/cmd/kj@latest && \
              echo "$(go env GOPATH)/bin" >> "$GITHUB_PATH" || \
              echo "kj install failed; policy-engine tests will skip"
          fi
      - name: Run pytest
        run: python3 -m pytest tests/ -v --tb=short
@@ -82,7 +82,7 @@ jobs:
        with:
          repository: acdl/acdl
          path: platform
-          ref: v1.9
+          ref: v1.25
      - uses: actions/setup-python@v5
        with:
@@ -104,7 +104,7 @@ jobs:
        with:
          # P4 (REQ-163): IAM role renamed acdl-deploy- → nova-deploy-.
          role-to-assume: ${{ secrets.NOVA_AWS_ACCESS_KEY_ID == '' && format('arn:aws:iam::{0}:role/nova-deploy-{1}', secrets.NOVA_AWS_ACCOUNT_ID, github.repository_id) || '' }}
-          aws-region: us-east-1
+          aws-region: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}
          access-key-id: ${{ secrets.NOVA_AWS_ACCESS_KEY_ID }}
          secret-access-key: ${{ secrets.NOVA_AWS_SECRET_ACCESS_KEY }}
@@ -0,0 +1,69 @@
 # Nova AWS key rotation — platform-managed scheduled pipeline (SPEC §5.9)
 #
 # Rotates the NOVA_AWS_* static key daily (no long-lived keys in the steady
 # state). v0.2 scope: the mechanism must exist (SPEC §5.9); the v0.2 deploy
 # uses the currently-active key. The rotation is best-effort + idempotent
 # (scripts/rotate_spike_key.sh deactivates the old key only after the new
 # key propagates to the consumer's Actions secret store).
 #
 # Auth: the rotation uses the CURRENT NOVA_AWS_* key to authenticate to IAM
 # (the root account 581513795199 can rotate its own keys — confirmed by the
 # bootstrap). The aws-actions/configure-aws-credentials@v4 step uses the
 # static-key path (no OIDC role-to-assume); the long-lived key rotates
 # itself, which is the bootstrap-exception documented in §5.9.
 #
 # Forge coords (base URL / owner / consumer repo) are sourced from
 # repository secrets — NOVA_FORGE_BASE_URL, NOVA_FORGE_OWNER,
 # NOVA_CONSUMER_REPO — so the synced workflow file stays forge-agnostic
 # (REQ-230). The rotation script uploads the new key to the consumer's
 # Actions secret store (the consumer whose deploy.yml consumes NOVA_AWS_*
 # via secrets: inherit).
 name: nova-rotate-aws-key
 on:
  schedule:
    - cron: "0 0 * * *"  # daily at 00:00 UTC
  workflow_dispatch:
 permissions:
  id-token: write
  contents: read
 jobs:
  rotate:
    name: Rotate NOVA_AWS_* static key
    runs-on: ubuntu-latest
    steps:
      - name: Check out Nova platform repo
        uses: actions/checkout@v4
      - name: Configure AWS credentials (bootstrap root creds for IAM key rotation)
        uses: aws-actions/configure-aws-credentials@v4
        with:
          aws-region: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}
          access-key-id: ${{ secrets.NOVA_AWS_ACCESS_KEY_ID }}
          secret-access-key: ${{ secrets.NOVA_AWS_SECRET_ACCESS_KEY }}
      - name: Install Python deps (boto3 for the rotation script)
        run: |
          python3 -m pip install --break-system-packages --quiet boto3
      - name: Run the key rotation script
        env:
          # aws-actions/configure-aws-credentials exports AWS_ACCESS_KEY_ID /
          # AWS_SECRET_ACCESS_KEY; the rotation script reads the bootstrap
          # creds via NOVA_BOOTSTRAP_AWS_* (its dual-read contract, D-034).
          # Map the standard AWS_* exports onto the script's expected vars.
          NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID: ${{ env.AWS_ACCESS_KEY_ID }}
          NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY: ${{ env.AWS_SECRET_ACCESS_KEY }}
          # Forge + consumer coords come from repository secrets (REQ-230 —
          # no forge hostnames/orgs hardcoded in the synced workflow file).
          # NOVA_FORGE_TOKEN holds the forge API token (set equal to the
          # existing forge token as a one-time secret setup).
          NOVA_FORGE_TOKEN: ${{ secrets.NOVA_FORGE_TOKEN }}
          NOVA_FORGE_BASE_URL: ${{ secrets.NOVA_FORGE_BASE_URL }}
          NOVA_FORGE_OWNER: ${{ secrets.NOVA_FORGE_OWNER }}
          NOVA_CONSUMER_REPO: ${{ secrets.NOVA_CONSUMER_REPO }}
          AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}
        run: |
          bash scripts/rotate_spike_key.sh
@@ -63,21 +63,6 @@ jobs:
      - name: Install test dependencies
        run: pip install -r requirements-test.txt
      - name: Install kyverno-json (kj) for policy-engine tests
        uses: actions/setup-go@v5
        with:
          go-version: "1.22"
          cache: false
      - name: Install kj binary
        run: |
          # v1.25: kyverno-json is the primary policy engine. Tests that
          # require kj skip when absent, so this is best-effort (the suite
          # passes with or without kj).
          go install github.com/kyverno/kyverno-json/cmd/kj@latest && \
            echo "$(go env GOPATH)/bin" >> "$GITHUB_PATH" || \
            echo "kj install failed; policy-engine tests will skip"
      - name: Run pytest
        run: python3 -m pytest tests/ -v --tb=short
@@ -82,7 +82,7 @@ jobs:
        with:
          repository: acdl/acdl
          path: platform
-          ref: v1.9
+          ref: v1.25
      - uses: actions/setup-python@v5
        with:
@@ -104,7 +104,7 @@ jobs:
        with:
          # P4 (REQ-163): IAM role renamed acdl-deploy- → nova-deploy-.
          role-to-assume: ${{ secrets.NOVA_AWS_ACCESS_KEY_ID == '' && format('arn:aws:iam::{0}:role/nova-deploy-{1}', secrets.NOVA_AWS_ACCOUNT_ID, github.repository_id) || '' }}
-          aws-region: us-east-1
+          aws-region: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}
          access-key-id: ${{ secrets.NOVA_AWS_ACCESS_KEY_ID }}
          secret-access-key: ${{ secrets.NOVA_AWS_SECRET_ACCESS_KEY }}
@@ -0,0 +1,69 @@
 # Nova AWS key rotation — platform-managed scheduled pipeline (SPEC §5.9)
 #
 # Rotates the NOVA_AWS_* static key daily (no long-lived keys in the steady
 # state). v0.2 scope: the mechanism must exist (SPEC §5.9); the v0.2 deploy
 # uses the currently-active key. The rotation is best-effort + idempotent
 # (scripts/rotate_spike_key.sh deactivates the old key only after the new
 # key propagates to the consumer's Actions secret store).
 #
 # Auth: the rotation uses the CURRENT NOVA_AWS_* key to authenticate to IAM
 # (the root account 581513795199 can rotate its own keys — confirmed by the
 # bootstrap). The aws-actions/configure-aws-credentials@v4 step uses the
 # static-key path (no OIDC role-to-assume); the long-lived key rotates
 # itself, which is the bootstrap-exception documented in §5.9.
 #
 # Forge coords (base URL / owner / consumer repo) are sourced from
 # repository secrets — NOVA_FORGE_BASE_URL, NOVA_FORGE_OWNER,
 # NOVA_CONSUMER_REPO — so the synced workflow file stays forge-agnostic
 # (REQ-230). The rotation script uploads the new key to the consumer's
 # Actions secret store (the consumer whose deploy.yml consumes NOVA_AWS_*
 # via secrets: inherit).
 name: nova-rotate-aws-key
 on:
  schedule:
    - cron: "0 0 * * *"  # daily at 00:00 UTC
  workflow_dispatch:
 permissions:
  id-token: write
  contents: read
 jobs:
  rotate:
    name: Rotate NOVA_AWS_* static key
    runs-on: ubuntu-latest
    steps:
      - name: Check out Nova platform repo
        uses: actions/checkout@v4
      - name: Configure AWS credentials (bootstrap root creds for IAM key rotation)
        uses: aws-actions/configure-aws-credentials@v4
        with:
          aws-region: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}
          access-key-id: ${{ secrets.NOVA_AWS_ACCESS_KEY_ID }}
          secret-access-key: ${{ secrets.NOVA_AWS_SECRET_ACCESS_KEY }}
      - name: Install Python deps (boto3 for the rotation script)
        run: |
          python3 -m pip install --break-system-packages --quiet boto3
      - name: Run the key rotation script
        env:
          # aws-actions/configure-aws-credentials exports AWS_ACCESS_KEY_ID /
          # AWS_SECRET_ACCESS_KEY; the rotation script reads the bootstrap
          # creds via NOVA_BOOTSTRAP_AWS_* (its dual-read contract, D-034).
          # Map the standard AWS_* exports onto the script's expected vars.
          NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID: ${{ env.AWS_ACCESS_KEY_ID }}
          NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY: ${{ env.AWS_SECRET_ACCESS_KEY }}
          # Forge + consumer coords come from repository secrets (REQ-230 —
          # no forge hostnames/orgs hardcoded in the synced workflow file).
          # NOVA_FORGE_TOKEN holds the forge API token (set equal to the
          # existing forge token as a one-time secret setup).
          NOVA_FORGE_TOKEN: ${{ secrets.NOVA_FORGE_TOKEN }}
          NOVA_FORGE_BASE_URL: ${{ secrets.NOVA_FORGE_BASE_URL }}
          NOVA_FORGE_OWNER: ${{ secrets.NOVA_FORGE_OWNER }}
          NOVA_CONSUMER_REPO: ${{ secrets.NOVA_CONSUMER_REPO }}
          AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}
        run: |
          bash scripts/rotate_spike_key.sh
@@ -46,12 +46,28 @@ never import an engine directly — they go through the registry.
 ## How to Write an Adapter
-### Terraform Adapter Extension
+### Terraform Adapter Extension (stateless assembler — v1.11 rewrite)
-1. Add a stack type → Terraform type mapping to `TYPE_MAP`.
+> The adapter owns **no module content**. There is no `TYPE_MAP`, no
-2. Add non-identity input mappings to `INPUT_MAP`.
+> `INPUT_MAP`, no `OUTPUT_MAP`, and no per-type branch logic (all deleted
-3. Add non-identity output mappings to `OUTPUT_MAP`.
+> in the v1.11 rewrite — the 918-line monolith collapsed to a ~80-line
-4. Add a specialized `_emit_resource` branch if the resource needs nested blocks (e.g. inline policies, rule sets).
+> assembler). Engine-specific shape lives in each L1 module's own
 > `terraform/` dir (`versions.tf`/`variables.tf`/`locals.tf`/`main.tf`/
 > `outputs.tf`); the adapter only assembles them.
 To extend the Terraform adapter, **do not edit the adapter** — instead:
 1. Add an L1 module with a real `terraform/` dir (owning its resource
   shape, nested HCL blocks, and defaults).
 2. Register it in `modules/registry.json` under the module name with its
   `terraform_dir` path. The adapter reads `registry.json` to find each
   module's directory.
 3. The adapter emits `module "<rid>" { source = "<path>" }` blocks at
   the root, with resolved inputs + wired `ref:` refs between modules.
   No type-specific translation lives in the adapter.
 > If you find yourself reaching for a "TYPE_MAP"-style constant, the L1
 > module is missing a piece — fix the module, not the adapter.
 ### Policy Adapter Pattern
@@ -76,7 +92,7 @@ never import an engine directly — they go through the registry.
 ## How to Test Adapters
- `tests/test_adapter.py` — Terraform adapter (`TYPE_MAP`, resource emission, refs, outputs).
+- `tests/test_adapter.py` — Terraform adapter (stateless assembly: registry read, `module "<rid>" { source }` emission, `ref:` wiring, outputs). No `TYPE_MAP`/`INPUT_MAP` tests — the adapter owns no type mappings.
 - `tests/test_checkov_adapter.py` — Checkov adapter.
 - `tests/test_wiz_adapter.py` — Wiz adapter.
 - `tests/test_kyverno_adapter.py` — Kyverno adapter.
@@ -93,4 +109,32 @@ never import an engine directly — they go through the registry.
 3. Add the adapter's engine name to the `engine` enum in `schemas/policy_check_result.schema.json` if it is a policy adapter.
 4. Write a test (`tests/test_<name>_adapter.py`) plus a fixture (`tests/fixtures/<name>_fixture.json`).
 5. Add it to `scripts/run_platform.sh` if it is invoked at runtime.
-6. Update this README.
+6. Update this README.
 ## Consumers
 The Terraform adapter compiles contract IR for consumer estates. The
 first real consumer estate is now live:
 | Consumer | Version | Environment | Account | Forge / Adapter | Status |
 | --- | --- | --- | --- | --- | --- |
 | `nova-blockchain-exchange` | v0.2 | dev | `581513795199` | inline adapter (see note below) | **live** (pilot apply `blkex-pilot-apply-v0.2`, 2026-08-19) |
 ### Forge adapter note (SPEC §10 Q1)
 Forge Actions (the consumer's forge runtime) does **not** support
 cross-repo `uses:` references — the forge rejects
 `uses: <owner>/<repo>/.github/workflows/<file>@<ref>` with
 `expected format {owner}/{repo}/.{git_platform}/workflows/{filename}@{ref}`.
 The consumer (`nova-blockchain-exchange`) therefore uses an **inline
 adapter** in its `deploy.yml`: the workflow does `actions/checkout@v4`
 on the consumer, then `actions/checkout@v4` `acdl/acdl` @ `ref: v1.25`
 into `platform/`, and runs `bash platform/scripts/run_platform.sh ...`
 directly — no `uses:` indirection.
 The platform's own `.github/workflows/deploy.yml` (this repo) stays as
 the **GitHub Actions reference implementation** — the reusable
 `workflow_call` workflow used by GitHub-hosted consumers. The two
 files share the same contract shape; the only declared difference is
 the forge/runtime, not the stages or commands. See
 `.ciagent/ARCHITECTURE.md` §12.8 for the live pilot-estate wiring.
@@ -1,4 +1,4 @@
-"""Nova KyvernoJsonEngine (REQ-293, v1.25).
+"""Nova KyvernoJsonEngine (REQ-293, v1.25; fixed v1.26 P3 W0.5).
 Implements the ``PolicyEngine`` protocol (``core/policy_engine.py``)
 by shelling to the ``kj`` CLI (``kyverno-json``). Translates native
@@ -12,9 +12,10 @@ distinguish from the K8s Kyverno adapter's ``KYVERNO_`` prefix.
 Severity (RESEARCH §2.6, G-Q10a): kyverno-json does not natively assign
 severities. Each Nova policy declares its severity via a
 ``metadata.annotations["nova.cloudinit.dev/severity"]`` field. The
-engine reads this annotation from the loaded policy YAML (not from the
+engine reads this annotation from the loaded policy file (not from the
-scan result — the result doesn't carry it) and applies it to every
+scan result — the result carries the policy spec but the annotation is
-result that policy produces. Default when absent: ``"info"``.
+read here from disk) and applies it to every result that policy
 produces. Default when absent: ``"info"``.
 Graceful degradation (D-120): ``is_configured()`` returns ``False`` when
 ``which kj`` is absent → ``evaluate()`` returns a single SKIPPED PCR
@@ -24,6 +25,37 @@ the binary.
 Defensive parsing: any kyverno-json output that doesn't match the
 expected shape produces an ``error`` PCR, never an exception. The
 engine is read-only against a local policy dir + a temp payload file.
 v1.26 P3 W0.5 fix — three substrate bugs uncovered once ``kj`` was
 actually installed (the v1.25 test suite ``pytest.skip``-masked them):
 1. **``.json`` policy files are not loaded by ``kj`` v0.0.3.** The
   upstream policy loader (``pkg/policy/load.go``) uses
   ``fileinfo.IsYaml()`` which only matches ``.yaml``/``.yml``
   extensions — ``.json`` files are silently skipped, yielding
   ``evaluating N resources against 0 policies``. Nova policies are
   authored as ``.json`` (the ``TestPolicyFilesExist`` tests assert the
   ``.json`` filenames). Fix: ``evaluate()`` materializes a temp policy
   dir that mirrors the source tree with every ``.json`` policy copied
   to a ``.yaml`` twin (JSON is a valid YAML subset — verified against
   ``kj`` v0.0.3). The source ``.json`` files remain untouched.
 2. **Bare-list output format.** ``kj scan --output json`` emits a bare
   JSON list at the top level (NOT ``{"results": [...]}``). Each entry
   has ``resource`` (the evaluated payload) + ``results`` (list of
   per-policy result objects, each carrying ``policy.metadata.name``,
   ``rules[]`` with ``rule.name``, ``violations[]`` (present on fail),
   ``error`` (string, present on policy-evaluation error)). The v1.25
   ``_translate`` did ``out.get("results", [])`` on a dict — but
   ``out`` is a list → returned ``[]`` → emitted a single
   ``KJ_NO_RESULTS`` pass PCR. **This is why all failing fixtures showed
   0 fails.** Fix: ``_translate`` handles list (v0.0.3) and dict
   (future-proof) shapes.
 3. **``validate`` wrapper + check syntax.** Documented in the policy
   files themselves (see the W0.5 policy edits). The engine itself does
   not enforce policy shape — it only translates ``kj`` output — so
   this fix lives in the policy ``.json`` files.
 """
 import datetime
@@ -98,39 +130,41 @@ def _load_policy_severities(policy_dir: Path) -> dict[str, str]:
    return severities
-def _to_pcr(entry: dict, contract_id: str, severity: str) -> dict:
+def _materialize_yaml_policy_dir(src: Path) -> tuple[Path, bool]:
-    """Translate a kyverno-json scan result entry to a PCR dict."""
+    """Mirror ``src`` (recursively) into a temp dir, copying every
-    policy_name = entry.get("policy", "") or "UNKNOWN"
+    ``.json`` policy to a ``.yaml`` twin and copying ``.yaml``/``.yml``
-    rule_name = entry.get("rule", "") or ""
+    files verbatim. Returns ``(temp_dir, created)``.
-    rule_id = f"KJ_{policy_name}"
+
-    if rule_name:
+    ``kj`` v0.0.3's policy loader (``pkg/policy/load.go``) only matches
-        rule_id = f"{rule_id}/{rule_name}"
+    ``.yaml``/``.yml`` extensions — ``.json`` files are silently
-    result_raw = entry.get("result", "skip")
+    skipped. Nova policies are authored as ``.json`` (the
-    result = RESULT_MAP.get(str(result_raw).lower(), "error")
+    ``TestPolicyFilesExist`` tests assert the ``.json`` filenames, so
-    message = entry.get("message", "") or ""
+    they cannot be renamed in-place). JSON is a valid YAML subset, so
-    resource = entry.get("resource", "")
+    a byte-for-byte copy with a ``.yaml`` extension loads cleanly.
-    if not resource and entry.get("name"):
+
-        kind = entry.get("kind", "")
+    ``created`` is ``False`` when ``src`` contains no policy files at
-        ns = entry.get("namespace", "")
+    all (empty dir) — in that case the temp dir is still returned (the
-        resource = f"{kind}/{ns}/{entry.get('name')}" if kind else entry.get("name", "")
+    caller invokes ``kj`` against it and gets the no-results path).
-    return {
+    """
-        "contractId": contract_id,
+    tmp = Path(tempfile.mkdtemp(prefix="nova-kj-pol-"))
-        "evaluatedAt": _iso8601_now(),
+    any_policy = False
-        "engine": "kyverno",
+    if src.is_dir():
-        "ruleId": rule_id,
+        for root, _dirs, files in os.walk(src):
-        "severity": severity,
+            rel = Path(root).relative_to(src)
-        "result": result,
+            dest_root = tmp / rel
-        "message": message,
+            dest_root.mkdir(parents=True, exist_ok=True)
-        "evidence": {
+            for fn in files:
-            "resource": resource,
+                if fn.startswith(".") or fn.startswith("_"):
-            "policy": policy_name,
+                    continue
-            "rule": rule_name,
+                src_file = Path(root) / fn
-            "namespace": entry.get("namespace", ""),
+                if fn.endswith(".json"):
-            "kind": entry.get("kind", ""),
+                    dest_file = dest_root / (fn.rsplit(".", 1)[0] + ".yaml")
-            "name": entry.get("name", ""),
+                    shutil.copy2(src_file, dest_file)
-        },
+                    any_policy = True
-        "resourceRef": resource,
+                elif fn.endswith((".yaml", ".yml")):
-    }
+                    shutil.copy2(src_file, dest_root / fn)
                    any_policy = True
    return tmp, any_policy
 def _skipped_not_configured(contract_id: str) -> dict:
@@ -165,6 +199,23 @@ def _error_pcr(contract_id: str, message: str) -> dict:
    }
 def _no_results_pass(contract_id: str) -> dict:
    """No result entries — emit a single pass PCR so the confidence
    signal's policy input is non-empty (a non-empty list of passes →
    score 1.0)."""
    return {
        "contractId": contract_id,
        "evaluatedAt": _iso8601_now(),
        "engine": "kyverno",
        "ruleId": "KJ_NO_RESULTS",
        "severity": "info",
        "result": "pass",
        "message": "kyverno-json scan produced no result entries (all policies passed or no match).",
        "evidence": {},
        "resourceRef": "",
    }
 class KyvernoJsonEngine:
    """``PolicyEngine`` impl that shells to the ``kj`` CLI."""
@@ -185,6 +236,9 @@ class KyvernoJsonEngine:
                f"kyverno-json policy dir not found: {policy_dir}",
            )]
        severities = _load_policy_severities(policy_dir)
        # kj v0.0.3 only loads .yaml/.yml policy files. Mirror the tree
        # to a temp dir with .json policies copied to .yaml twins.
        yaml_dir, _any_policy = _materialize_yaml_policy_dir(policy_dir)
        # Write payload to temp file (kj scan --payload expects a file path).
        payload_tmp = tempfile.NamedTemporaryFile(
            mode="w", suffix=".json", delete=False, encoding="utf-8"
@@ -195,7 +249,7 @@ class KyvernoJsonEngine:
            payload_tmp.close()
            cmd = [
                kj, "scan",
-                "--policy", str(policy_dir),
+                "--policy", str(yaml_dir),
                "--payload", payload_tmp.name,
                "--output", "json",
            ]
@@ -211,7 +265,7 @@ class KyvernoJsonEngine:
                    f"kyverno-json scan exited {proc.returncode}: {proc.stderr[:200]}",
                )]
            try:
-                out = json.loads(proc.stdout) if proc.stdout.strip() else {}
+                out = json.loads(proc.stdout) if proc.stdout.strip() else []
            except json.JSONDecodeError as e:
                return [_error_pcr(
                    contract_id,
@@ -223,38 +277,185 @@ class KyvernoJsonEngine:
                os.unlink(payload_tmp.name)
            except OSError:
                pass
            shutil.rmtree(yaml_dir, ignore_errors=True)
-    def _translate(self, out: dict, contract_id: str,
+    def _translate(self, out: Any, contract_id: str,
                   severities: dict[str, str]) -> list[dict]:
-        results = out.get("results", []) if isinstance(out, dict) else []
+        # kj v0.0.3 emits a BARE JSON LIST at the top level: each entry
-        if not isinstance(results, list):
+        # has `resource` (the evaluated payload) + `results` (list of
-            results = []
+        # per-policy result objects). Future-proof: also accept the
        # legacy {"results": [...]} dict shape.
        if isinstance(out, list):
            entries = out
        elif isinstance(out, dict):
            entries = out.get("results", [])
            if not isinstance(entries, list):
                entries = []
        else:
            entries = []
        pcrs: list[dict] = []
-        for entry in results:
+        for entry in entries:
            if not isinstance(entry, dict):
                continue
-            policy_name = entry.get("policy", "") or "UNKNOWN"
+            resource = entry.get("resource", {})
-            severity = severities.get(policy_name, SEVERITY_DEFAULT)
+            results = entry.get("results", [])
-            pcrs.append(_to_pcr(entry, contract_id, severity))
+            if not isinstance(results, list):
                results = []
            for pol_result in results:
                if not isinstance(pol_result, dict):
                    continue
                policy_obj = pol_result.get("policy", {}) or {}
                policy_name = (
                    policy_obj.get("metadata", {}).get("name") if isinstance(policy_obj, dict)
                    else None
                ) or "UNKNOWN"
                severity = severities.get(policy_name, SEVERITY_DEFAULT)
                rules = pol_result.get("rules", [])
                if not isinstance(rules, list):
                    rules = []
                for rule_entry in rules:
                    if not isinstance(rule_entry, dict):
                        continue
                    rule_obj = rule_entry.get("rule", {}) or {}
                    rule_name = rule_obj.get("name", "") if isinstance(rule_obj, dict) else ""
                    rule_id = f"KJ_{policy_name}"
                    if rule_name:
                        rule_id = f"{rule_id}/{rule_name}"
                    violations = rule_entry.get("violations")
                    error_str = rule_entry.get("error")
                    if isinstance(violations, list) and violations:
                        # Fail: build a message from the violations' errors.
                        msg_parts: list[str] = []
                        for v in violations:
                            if not isinstance(v, dict):
                                continue
                            for err in v.get("errors", []) or []:
                                if not isinstance(err, dict):
                                    continue
                                field = err.get("field", "")
                                detail = err.get("detail", "")
                                value = err.get("value", "")
                                msg_parts.append(
                                    f"{field}: value={value!r} detail={detail}"
                                )
                        message = "; ".join(msg_parts) if msg_parts else "policy rule failed"
                        pcrs.append({
                            "contractId": contract_id,
                            "evaluatedAt": _iso8601_now(),
                            "engine": "kyverno",
                            "ruleId": rule_id,
                            "severity": severity,
                            "result": "fail",
                            "message": message,
                            "evidence": {
                                "resource": resource,
                                "policy": policy_name,
                                "rule": rule_name,
                                "violations": violations,
                            },
                            "resourceRef": _resource_ref(resource),
                        })
                    elif isinstance(error_str, str) and error_str:
                        # Policy-evaluation error (e.g. bad JMESPath).
                        pcrs.append({
                            "contractId": contract_id,
                            "evaluatedAt": _iso8601_now(),
                            "engine": "kyverno",
                            "ruleId": rule_id,
                            "severity": severity,
                            "result": "error",
                            "message": error_str,
                            "evidence": {
                                "resource": resource,
                                "policy": policy_name,
                                "rule": rule_name,
                            },
                            "resourceRef": _resource_ref(resource),
                        })
                    else:
                        # Pass: no violations, no error.
                        pcrs.append({
                            "contractId": contract_id,
                            "evaluatedAt": _iso8601_now(),
                            "engine": "kyverno",
                            "ruleId": rule_id,
                            "severity": severity,
                            "result": "pass",
                            "message": "",
                            "evidence": {
                                "resource": resource,
                                "policy": policy_name,
                                "rule": rule_name,
                            },
                            "resourceRef": _resource_ref(resource),
                        })
        if not pcrs:
-            # No results — kyverno-json produced nothing (no match, or
+            pcrs.append(_no_results_pass(contract_id))
            # all policies passed with no result entries). Emit a
            # single pass PCR so the confidence signal's policy input
            # is non-empty (a non-empty list of passes → score 1.0).
            pcrs.append({
                "contractId": contract_id,
                "evaluatedAt": _iso8601_now(),
                "engine": "kyverno",
                "ruleId": "KJ_NO_RESULTS",
                "severity": "info",
                "result": "pass",
                "message": "kyverno-json scan produced no result entries (all policies passed or no match).",
                "evidence": {},
                "resourceRef": "",
            })
        return pcrs
 def _resource_ref(resource: Any) -> str:
    """Best-effort resource ref from the evaluated payload."""
    if isinstance(resource, dict):
        for key in ("id", "name", "address"):
            v = resource.get(key)
            if isinstance(v, str) and v:
                return v
    return ""
 # --- Legacy _to_pcr kept for the existing TestToPcr unit tests ---
 # (test_kyverno_json_engine.py::TestToPcr constructs flat `entry`
 # dicts with `policy`/`rule`/`result`/`message`/`resource` keys and
 # asserts the translated PCR shape. The production _translate path no
 # longer calls this helper — it inlines the translation against the
 # real kj v0.0.3 nested output — but the unit tests pin the helper's
 # contract, so it stays.)
 def _to_pcr(entry: dict, contract_id: str, severity: str) -> dict:
    """Translate a flat kyverno-json scan result entry to a PCR dict.
    Legacy shape (kept for unit-test backwards compatibility): the
    entry is a flat dict with ``policy``/``rule``/``result``/``message``/
    ``resource`` string keys. The production ``_translate`` path no
    longer calls this — it inlines translation against the real kj
    v0.0.3 nested ``resource``+``results``+``rules`` shape — but the
    ``TestToPcr`` unit tests pin this contract.
    """
    policy_name = entry.get("policy", "") or "UNKNOWN"
    rule_name = entry.get("rule", "") or ""
    rule_id = f"KJ_{policy_name}"
    if rule_name:
        rule_id = f"{rule_id}/{rule_name}"
    result_raw = entry.get("result", "skip")
    result = RESULT_MAP.get(str(result_raw).lower(), "error")
    message = entry.get("message", "") or ""
    resource = entry.get("resource", "")
    if not resource and entry.get("name"):
        kind = entry.get("kind", "")
        ns = entry.get("namespace", "")
        resource = f"{kind}/{ns}/{entry.get('name')}" if kind else entry.get("name", "")
    return {
        "contractId": contract_id,
        "evaluatedAt": _iso8601_now(),
        "engine": "kyverno",
        "ruleId": rule_id,
        "severity": severity,
        "result": result,
        "message": message,
        "evidence": {
            "resource": resource,
            "policy": policy_name,
            "rule": rule_name,
            "namespace": entry.get("namespace", ""),
            "kind": entry.get("kind", ""),
            "name": entry.get("name", ""),
        },
        "resourceRef": resource,
    }
 if __name__ == "__main__":
    if len(sys.argv) < 4:
        print(
@@ -12,17 +12,16 @@
    "rules": [
      {
        "name": "require-id",
-        "validate": {
+        "assert": {
-          "message": "contract id is required",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "id": {
-                "check": {
+                  "(regex_match('^[a-z][a-z0-9-]{2,5}$', @))": true
                  "id": "{{ to_string(@) }}"
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,18 +12,17 @@
    "rules": [
      {
        "name": "no-unknown-fields",
-        "validate": {
+        "assert": {
-          "message": "contract may only contain id, name, environment, infrastructure (schema-allowed fields)",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "(length(keys(@)) == `4`)": true,
-                "check": {
+                "keys(@)": {
-                  "(length(keys(@)) == `4`)": true,
+                  "(contains(['id','name','environment','infrastructure'], @))": true
                  "keys(@)": "(contains(['id','name','environment','infrastructure'], @))"
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,17 +12,16 @@
    "rules": [
      {
        "name": "env-enum",
-        "validate": {
+        "assert": {
-          "message": "contract.environment must be one of dev, qa, prod, dr",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "environment": {
-                "check": {
+                  "(contains(['dev','qa','prod','dr'], @))": true
                  "environment": "(contains(['dev','qa','prod','dr'], @))"
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,17 +12,16 @@
    "rules": [
      {
        "name": "id-pattern",
-        "validate": {
+        "assert": {
-          "message": "contract.id must match ^[a-z][a-z0-9-]{2,5}$ (3-6 char operational acronym)",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "id": {
-                "check": {
+                  "(regex_match('^[a-z][a-z0-9-]{2,5}$', @))": true
                  "id": "(regex_match('^[a-z][a-z0-9-]{2,5}$', @))"
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,17 +12,16 @@
    "rules": [
      {
        "name": "infra-min-1",
-        "validate": {
+        "assert": {
-          "message": "contract.infrastructure must have at least one module entry",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "infrastructure": {
-                "check": {
+                  "(length(keys(@)) > `0`)": true
                  "infrastructure": "(length(keys(@)) > `0`)"
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,19 +12,14 @@
    "rules": [
      {
        "name": "no-critical-fail",
-        "validate": {
+        "assert": {
-          "message": "No PolicyCheckResult in the merged list may have severity: critical + result: fail. The confidence_signal.py hard-override is the defense-in-depth behind this declarative rule (D-119).",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "(severity == 'critical' && result == 'fail')": false
                "check": {
                  "~.[]": {
                    "(severity == 'critical' && result == 'fail')": false
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,28 +12,19 @@
    "rules": [
      {
        "name": "no-tagging-divergence",
-        "validate": {
+        "assert": {
-          "message": "For every resource, the Checkov NOVA_TAG_NAMING result and the kyverno-json KJ_REQUIRE_TAGGING_STANDARD result must agree. Divergence emits an error PCR (D-118, defense-in-depth against rule drift).",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "(ruleId == 'NOVA_TAG_NAMING' && result == 'fail')": false
                "check": {
                  "~.[?(ruleId == 'NOVA_TAG_NAMING')]": {
                    "result->ckv_result": {},
                    "($ckv_result == 'fail')": false
                  }
                }
              },
              {
                "check": {
                  "~.[?(ruleId == 'KJ_REQUIRE_TAGGING_STANDARD')]": {
                    "result->kj_result": {},
                    "($kj_result == 'fail')": false
                  }
                }
              }
-            ]
+            },
-          }
+            {
              "check": {
                "(ruleId == 'KJ_REQUIRE_TAGGING_STANDARD' && result == 'fail')": false
              }
            }
          ]
        }
      }
    ]
@@ -0,0 +1,27 @@
 {
  "apiVersion": "json.kyverno.io/v1alpha1",
  "kind": "ValidatingPolicy",
  "metadata": {
    "name": "no-placeholder-account",
    "annotations": {
      "nova.cloudinit.dev/severity": "critical",
      "title.policy.kyverno.io": "Env does not use a placeholder AWS account id"
    }
  },
  "spec": {
    "rules": [
      {
        "name": "no-placeholder-account",
        "assert": {
          "all": [
            {
              "check": {
                "(account_id == '000000000000')": false
              }
            }
          ]
        }
      }
    ]
  }
 }
@@ -12,36 +12,38 @@
    "rules": [
      {
        "name": "no-wildcard-action",
-        "validate": {
+        "assert": {
-          "message": "IAM policy Action must not be '*' (ports CKV_AWS_1/40)",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "planned_values": {
-                "check": {
+                  "root_module": {
-                  "planned_values.root_module.~.resources": {
+                    "~.resources": {
-                    "(type == 'aws_iam_policy' && contains(values.policy_document.Statement[].Action, '*'))": false
+                      "(type == 'aws_iam_policy' && contains(values.policy_document.Statement[].Action, '*'))": false
                    }
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      },
      {
        "name": "no-wildcard-resource",
-        "validate": {
+        "assert": {
-          "message": "IAM policy Resource must not be '*' (ports CKV_AWS_1/40)",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "planned_values": {
-                "check": {
+                  "root_module": {
-                  "planned_values.root_module.~.resources": {
+                    "~.resources": {
-                    "(type == 'aws_iam_policy' && contains(values.policy_document.Statement[].Resource, '*'))": false
+                      "(type == 'aws_iam_policy' && contains(values.policy_document.Statement[].Resource, '*'))": false
                    }
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,19 +12,20 @@
    "rules": [
      {
        "name": "no-plaintext-db-password",
-        "validate": {
+        "assert": {
-          "message": "aws_db_instance.password must not be a plaintext string (ports CKV_AWS_41/45/46)",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "planned_values": {
-                "check": {
+                  "root_module": {
-                  "planned_values.root_module.~.resources": {
+                    "~.resources": {
-                    "(type == 'aws_db_instance' && contains(keys(values), 'password') && !contains(['${...}', ''], values.password))": false
+                      "(type == 'aws_db_instance' && contains(keys(values), 'password') && !contains(['${...}', ''], values.password))": false
                    }
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,19 +12,20 @@
    "rules": [
      {
        "name": "kms-by-alias",
-        "validate": {
+        "assert": {
-          "message": "aws_kms_key resources should reference a customer-managed key alias, not inline key material (ports CKV_AWS_7/33)",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "planned_values": {
-                "check": {
+                  "root_module": {
-                  "planned_values.root_module.~.resources": {
+                    "~.resources": {
-                    "(type == 'aws_kms_key' && !contains(keys(values), 'key_id') && !contains(keys(values), 'kms_key_id'))": false
+                      "(type == 'aws_kms_key' && !contains(keys(values), 'key_id') && !contains(keys(values), 'kms_key_id'))": false
                    }
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,17 +12,14 @@
    "rules": [
      {
        "name": "no-duplicate-adapters",
-        "validate": {
+        "assert": {
-          "message": "Each adapter must be registered exactly once (no duplicate adapter names in the capability inventory). Declarative mirror of core/regression_verify.py CAP-013.",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "(max(map(&length(@), values(group_by(adapters, &@)))) == `1`)": true
                "check": {
                  "adapters": "(length(duplicates(@)) == `0`)"
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,19 +12,16 @@
    "rules": [
      {
        "name": "every-metric-has-status",
-        "validate": {
+        "assert": {
-          "message": "Every metric in docs/METRICS.md must declare a status (grounded, derived, or deferred). Declarative mirror of core/regression_verify.py CAP-023.",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "~.metrics": {
-                "check": {
+                  "(contains(['grounded','derived','deferred'], status))": true
                  "~.metrics": {
                    "(contains(['grounded','derived','deferred'], status))": true
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -12,22 +12,19 @@
    "rules": [
      {
        "name": "deck-has-4-beats",
-        "validate": {
+        "assert": {
-          "message": "The deck must have the 4-beat arc: Problem, Solution, Proof, Roadmap+Ask. Declarative mirror of core/regression_verify.py CAP-024.",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "deck": {
-                "check": {
+                  "beats": {
-                  "deck.beats": "(length(@) >= `4`)"
+                    "(length(@) >= `4`)": true,
-                }
+                    "(contains(@, 'Problem') && contains(@, 'Solution') && contains(@, 'Proof') && contains(@, 'Roadmap+Ask'))": true
-              },
+                  }
              {
                "check": {
                  "deck.beats": "(contains(@, 'Problem') && contains(@, 'Solution') && contains(@, 'Proof') && contains(@, 'Roadmap+Ask'))"
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -0,0 +1,27 @@
 {
  "apiVersion": "json.kyverno.io/v1alpha1",
  "kind": "ValidatingPolicy",
  "metadata": {
    "name": "all-matches-committed",
    "annotations": {
      "nova.cloudinit.dev/severity": "critical",
      "title.policy.kyverno.io": "All settlement matches are committed (finalized)"
    }
  },
  "spec": {
    "rules": [
      {
        "name": "all-matches-committed",
        "assert": {
          "all": [
            {
              "check": {
                "(all_committed)": true
              }
            }
          ]
        }
      }
    ]
  }
 }
@@ -13,19 +13,16 @@
      {
        "name": "no-public-ingress",
        "identifier": "id",
-        "validate": {
+        "assert": {
-          "message": "public_ingress: true is not allowed on any resource (v1.0 demo rule, now declarative)",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "~.resources": {
-                "check": {
+                  "(inputs.public_ingress || `false`)": false
                  "~.resources": {
                    "(inputs.public_ingress || `false`)": false
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -13,43 +13,31 @@
      {
        "name": "s3-encryption",
        "identifier": "id",
-        "match": {
+        "assert": {
-          "any": [
+          "all": [
-            {"type": "aws:s3:bucket"}
+            {
-          ]
+              "check": {
-        },
+                "~.resources": {
-        "validate": {
+                  "(type == 'aws:s3:bucket' && !(contains(keys(inputs), 'bucket_encryption') || contains(keys(inputs), 'kms_key_id')))": false
          "message": "S3 buckets must declare encryption config (inputs.bucket_encryption or inputs.kms_key_id)",
          "assert": {
            "all": [
              {
                "check": {
                  "(contains(keys(inputs), 'bucket_encryption') || contains(keys(inputs), 'kms_key_id'))": true
                }
              }
-            ]
+            }
-          }
+          ]
        }
      },
      {
        "name": "ebs-encryption",
        "identifier": "id",
-        "match": {
+        "assert": {
-          "any": [
+          "all": [
-            {"type": "aws:ebs:volume"}
+            {
-          ]
+              "check": {
-        },
+                "~.resources": {
-        "validate": {
+                  "(type == 'aws:ebs:volume' && !(contains(keys(inputs), 'encrypted') || contains(keys(inputs), 'kms_key_id')))": false
          "message": "EBS volumes must declare encryption (inputs.encrypted or inputs.kms_key_id)",
          "assert": {
            "all": [
              {
                "check": {
                  "(contains(keys(inputs), 'encrypted') || contains(keys(inputs), 'kms_key_id'))": true
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -13,22 +13,19 @@
      {
        "name": "require-nova-tags",
        "identifier": "id",
-        "validate": {
+        "assert": {
-          "message": "Every taggable resource must carry nova:owner, nova:contract, nova:environment, nova:cost-center tags",
+          "all": [
-          "assert": {
+            {
-            "all": [
+              "check": {
-              {
+                "~.resources": {
-                "check": {
+                  "(contains(keys(inputs.tags || `{}`), 'nova:owner'))": true,
-                  "~.resources": {
+                  "(contains(keys(inputs.tags || `{}`), 'nova:contract'))": true,
-                    "(contains(keys(tags || `[]`), 'nova:owner'))": true,
+                  "(contains(keys(inputs.tags || `{}`), 'nova:environment'))": true,
-                    "(contains(keys(tags || `[]`), 'nova:contract'))": true,
+                  "(contains(keys(inputs.tags || `{}`), 'nova:cost-center'))": true
                    "(contains(keys(tags || `[]`), 'nova:environment'))": true,
                    "(contains(keys(tags || `[]`), 'nova:cost-center'))": true
                  }
                }
              }
-            ]
+            }
-          }
+          ]
        }
      }
    ]
@@ -30,6 +30,37 @@ def _module_name(resource):
    return resource.get("module", "").split("@")[0]
 def _load_env_json(env_name, repo_root):
    """Load core/environments/<env_name>.json → dict (P03 W3, REQ-319).
    Returns {} if the file is absent (the adapter falls back to the
    computed state-bucket name). Sources env.state_backend.bucket +
    env.account_id + env.region for the S3 backend block.
    """
    env_path = os.path.join(repo_root, "core", "environments", f"{env_name}.json")
    if not os.path.isfile(env_path):
        return {}
    with open(env_path, "r") as fh:
        return json.load(fh)
 def _resolve_state_bucket(env_json, region):
    """Resolve the S3 state-backend bucket name (P03 W3, REQ-319).
    Precedence: (1) env.state_backend.bucket when present + non-empty;
    (2) nova-tfstate-{account_id}-{region} from env.account_id + region
    (backwards-compat); (3) nova-tfstate-581513795199-{region} when
    account_id is absent (the only real account — bootstrap bucket).
    The env JSON is authoritative; NOVA_AWS_ACCOUNT_ID is no longer
    consulted for the bucket name.
    """
    bucket = (env_json.get("state_backend") or {}).get("bucket")
    if bucket:
        return bucket
    account_id = env_json.get("account_id") or "581513795199"
    return f"nova-tfstate-{account_id}-{region}"
 def _ref_expr(value, data_source_names=None, id_remap=None):
    """Translate `ref:<rid>.<output>` → `module.<rid>.<output>` (or
    `data.terraform_remote_state.platform.outputs.<output>` for data
@@ -108,13 +139,20 @@ def adapt(stack_instance, out_dir):
    resources = stack_instance.get("resources", [])
    stack_outputs = stack_instance.get("outputs", {})
    region = next((r["inputs"]["region"] for r in resources if "region" in r.get("inputs", {})), "us-east-1")
    providers_tf = f'provider "aws" {{\n  region = "{region}"\n}}\n'
    stack_name = stack.get("name", "spike")
    environment = stack.get("environment", "dev")
-    account_id = env.get_env("AWS_ACCOUNT_ID", "581513795199")
+    # P03 W3 (REQ-319): state backend bucket + account_id + region come
-    state_bucket = f"nova-tfstate-{account_id}-us-east-1"
+    # from the env onboarding JSON (source of truth post-REQ-319). Bucket
    # = env.state_backend.bucket when present (fallback to the computed
    # nova-tfstate-{account_id}-{region} pattern for backwards compat).
    env_json = _load_env_json(environment, repo_root)
    region = env_json.get("region") or next(
        (r["inputs"]["region"] for r in resources if "region" in r.get("inputs", {})),
        "us-east-1",
    )
    state_bucket = _resolve_state_bucket(env_json, region)
    providers_tf = f'provider "aws" {{\n  region = "{region}"\n}}\n'
    # State key is env-scoped (v1.24 REQ-287): the {environment} segment lets
    # the env-transition detect-and-destroy step target the PRIOR env's state
    # without affecting the new env. No orphan path on environment promotion.
@@ -130,7 +168,7 @@ def adapt(stack_instance, out_dir):
        '  backend "s3" {\n'
        f'    bucket = "{state_bucket}"\n'
        f'    key    = "spike/{stack_name}/{environment}/terraform.tfstate"\n'
-        '    region = "us-east-1"\n'
+        f'    region = "{region}"\n'
        '  }\n'
        '}\n'
    )
@@ -145,7 +183,7 @@ def adapt(stack_instance, out_dir):
            '  config = {\n'
            f'    bucket = "{state_bucket}"\n'
            f'    key    = "{remote_state_key}"\n'
-            '    region = "us-east-1"\n'
+            f'    region = "{region}"\n'
            '  }\n'
            '}\n'
        )
@@ -144,6 +144,7 @@ def compute(contract_id: str, environment: str,
    penalty = 0.0
    policy_input = inputs.get("policy")
    pcrs = policy_input if isinstance(policy_input, list) else []
    critical_override = False
    for pcr in pcrs:
        if not isinstance(pcr, dict):
            continue
@@ -152,20 +153,31 @@ def compute(contract_id: str, environment: str,
        sev = pcr.get("severity")
        p = PENALTY.get(sev, 0.0)
        if p is None:
-            return Signal(0.0, "block", per_input,
+            # Critical PCR hard override: score = 0, band = block.
-                          reasons + [f"CRITICAL_OVERRIDE:{pcr.get('ruleId','?')}"])
+            # Do NOT early-return — fall through to the event emission
            # block below so the SPEC §5.8 evidence stream
            # (confidence.computed -> ai.decision.made -> ...) is complete
            # even on a critical override (REQ-318: a critical PCR is a
            # confidence-driven escalation and must carry escalation_reason).
            reasons.append(f"CRITICAL_OVERRIDE:{pcr.get('ruleId','?')}")
            critical_override = True
            break
        penalty += p
-    score = max(0.0, min(1.0, base - penalty))
+    if critical_override:
-    threshold = THRESHOLDS[environment]
+        score = 0.0
    if score >= threshold:
        band = "pass"
    elif score < threshold - 0.10:
        band = "block"
    else:
-        band = "warn"
+        score = max(0.0, min(1.0, base - penalty))
-    if environment == "dev" and band == "warn":
+        threshold = THRESHOLDS[environment]
-        band = "block"
+        if score >= threshold:
            band = "pass"
        elif score < threshold - 0.10:
            band = "block"
        else:
            band = "warn"
        if environment == "dev" and band == "warn":
            band = "block"
    signal = Signal(score, band, per_input, reasons)
    # Emit nova.confidence.computed + nova.ai.decision.made events (D-122).
@@ -184,6 +196,17 @@ def compute(contract_id: str, environment: str,
            "human_override": band == "block",
            "threshold": THRESHOLDS[environment],
        }
        # REQ-318 (SPEC §5.8): on a `block` band, carry escalation_reason.
        # In v1.26 the only value is "confidence" — a block is always
        # confidence-driven (the score fell below threshold OR a critical
        # PCR fired a hard override). Future milestones may add "policy"
        # (a critical PCR that is not confidence-scored); leave the door
        # open but only emit "confidence" now. On pass/warn bands the
        # field is ABSENT (escalation_reason is only meaningful on a
        # block — it is the Post-Pilot Human Escalation Frequency
        # denominator).
        if band == "block":
            decision_data["escalation_reason"] = "confidence"
        decision_event = make_event("nova.ai.decision.made", run_id, environment, decision_data,
                                     contract_id=contract_id, actor_type="confidence-gate",
                                     actor_id="confidence_signal")
@@ -1,10 +1,10 @@
 {
  "name": "dev",
  "description": "Default platform-managed dev environment for onboarding demos.",
-  "account_id": "000000000000",
+  "account_id": "581513795199",
  "region": "us-east-1",
  "state_backend": {
-    "bucket": "acdl-dev-state",
+    "bucket": "nova-tfstate-581513795199-us-east-1",
    "lock_table": "acdl-dev-locks"
  },
  "network": {
@@ -4,7 +4,7 @@
  "account_id": "000000000000",
  "region": "us-east-1",
  "state_backend": {
-    "bucket": "acdl-dr-state",
+    "bucket": "nova-tfstate-000000000000-us-east-1",
    "lock_table": "acdl-dr-locks"
  },
  "network": {
@@ -4,7 +4,7 @@
  "account_id": "000000000000",
  "region": "us-east-1",
  "state_backend": {
-    "bucket": "acdl-prod-state",
+    "bucket": "nova-tfstate-000000000000-us-east-1",
    "lock_table": "acdl-prod-locks"
  },
  "network": {
@@ -4,7 +4,7 @@
  "account_id": "000000000000",
  "region": "us-east-1",
  "state_backend": {
-    "bucket": "acdl-qa-state",
+    "bucket": "nova-tfstate-000000000000-us-east-1",
    "lock_table": "acdl-qa-locks"
  },
  "network": {
@@ -54,7 +54,8 @@ def _init_store(db_path=None):
            confidence_band TEXT,
            hitl_block INTEGER,
            cost_estimate_usd REAL,
-            decision_id TEXT
+            decision_id TEXT,
            escalation_reason TEXT
        );
        CREATE TABLE IF NOT EXISTS fact_capability (
@@ -110,7 +111,9 @@ def _init_store(db_path=None):
            confidence REAL,
            alternatives TEXT,
            human_override INTEGER,
            escalation_reason TEXT,
            outcome TEXT,
            backfilled_at TEXT,
            event_time TEXT,
            PRIMARY KEY (decision_id)
        );
@@ -217,14 +220,15 @@ def collect_run_manifests(db_path=None, runs_dir=None):
            INSERT OR REPLACE INTO fact_run
            (run_id, contract_id, environment, started_at, completed_at,
             exit_code, outcome, confidence_score, confidence_band,
-             hitl_block, cost_estimate_usd, decision_id)
+             hitl_block, cost_estimate_usd, decision_id, escalation_reason)
-            VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
+            VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
        """, (run_id, manifest.get("contract_id", ""), manifest.get("environment", ""),
              manifest.get("started_at", ""), manifest.get("completed_at", ""),
              manifest.get("exit_code", 0), manifest.get("outcome", ""),
              conf.get("score", 0), conf.get("band", ""),
              1 if hitl.get("block") else 0,
-              manifest.get("cost_estimate_usd", 0), manifest.get("decision_id", "")))
+              manifest.get("cost_estimate_usd", 0), manifest.get("decision_id", ""),
              manifest.get("escalation_reason")))
        count += 1
    conn.commit()
    conn.close()
@@ -232,7 +236,16 @@ def collect_run_manifests(db_path=None, runs_dir=None):
 def collect_decision_ledger(db_path=None, ledger_db=None):
-    """Read the Decision Ledger SQLite → fact_decision."""
+    """Read the Decision Ledger SQLite → fact_decision.
    REQ-317: preserves a backfilled outcome. The ledger is append-only
    and the `nova.ai.decision.made` event always carries outcome=pending
    (it is emitted before apply). Once `outcome_backfill.backfill()` has
    transitioned the `fact_decision` row to succeeded/failed, a re-run of
    the collector must NOT clobber it back to pending. We therefore
    coalesce: if the existing row has a non-pending outcome, keep it +
    its backfilled_at; otherwise write pending (the event default).
    """
    if db_path is None:
        db_path = _STORE_PATH
    if ledger_db is None:
@@ -251,15 +264,27 @@ def collect_decision_ledger(db_path=None, ledger_db=None):
        payload = json.loads(payload_json)
        data = payload.get("data", {})
        decision_id = data.get("decision_id", run_id)
        # Preserve a backfilled outcome across collector re-runs (REQ-317).
        existing = conn.execute(
            "SELECT outcome, backfilled_at FROM fact_decision WHERE decision_id = ?",
            (decision_id,),
        ).fetchone()
        if existing and existing[0] and existing[0] != "pending":
            outcome = existing[0]
            backfilled_at = existing[1]
        else:
            outcome = data.get("outcome", "pending")
            backfilled_at = data.get("backfilled_at")
        conn.execute("""
            INSERT OR REPLACE INTO fact_decision
            (decision_id, run_id, chosen_action, confidence, alternatives,
-             human_override, outcome, event_time)
+             human_override, escalation_reason, outcome, backfilled_at, event_time)
-            VALUES (?, ?, ?, ?, ?, ?, ?, ?)
+            VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
        """, (decision_id, run_id, data.get("chosen_action", ""),
              data.get("confidence", 0), json.dumps(data.get("alternatives", {})),
              1 if data.get("human_override") else 0,
-              data.get("outcome", "pending"), event_time))
+              data.get("escalation_reason"),
              outcome, backfilled_at, event_time))
        count += 1
    conn.commit()
    conn.close()
@@ -224,12 +224,16 @@ def replay_run(run_id, db_path=None):
        line = f"  [{e['seq']}] {e['event_time']} {etype}"
        if etype == "nova.ai.decision.made":
            line += f" confidence={data.get('confidence', '?')} band={data.get('chosen_action', '?')} override={data.get('human_override', '?')}"
            if data.get("escalation_reason"):
                line += f" escalation_reason={data.get('escalation_reason')}"
        elif etype == "nova.attestation.recorded":
            line += f" env={data.get('environment', '?')} approver={data.get('approver', '?')} result={data.get('result', '?')}"
        elif etype == "nova.run.completed":
            line += f" exit={data.get('exit_code', '?')} outcome={data.get('outcome', '?')}"
        elif etype == "nova.run.failed":
            line += f" exit={data.get('exit_code', '?')} outcome=failed"
        elif etype == "nova.outcome.backfilled":
            line += f" prev={data.get('previous_outcome', '?')} new={data.get('new_outcome', '?')} at={data.get('backfilled_at', '?')}"
        lines.append(line)
    lines.append("=== End replay ===")
    return "\n".join(lines)
@@ -0,0 +1,213 @@
 """Nova Outcome Backfill (REQ-317, SPEC §5.8, P3 Wave 2).
 The `fact_decision.outcome` column in the metrics cold store is written
 `pending` by the collector (it ingests `nova.ai.decision.made` events,
 which are emitted *before* the run executes the apply). Once the run
 completes (`nova.run.completed`, exit 0) or fails (`nova.run.failed`,
 exit non-zero), the outcome must be transitioned `pending ->
 succeeded`/`failed` so the Post-Pilot AI Decision Accuracy denominator is
 grounded (an outcome that is stuck `pending` cannot be scored).
 Architecture (grounded in what the ledger + collector actually do):
  * The Decision Ledger (`core/metrics/decision_ledger.py`) is an
    **append-only hash-chain** of CloudEvents envelopes — there is no
    `fact_decision` table *inside* the ledger DB; facts live in the
    separate collector cold store (`core/metrics/collector.py`,
    `nova_metrics.db`). The ledger is never UPDATEd in place (that would
    break the SHA-256 chain — see `verify_chain()`).
  * Therefore the backfill does TWO things:
      1. Appends a new audit event `nova.outcome.backfilled` to the
         ledger (preserves the hash chain; auditable via `replay_run`).
      2. UPDATEs the `fact_decision` row in the cold store (the row is
         keyed by `decision_id`; `outcome` + `backfilled_at` are
         mutable — they are facts, not chain events).
 Idempotent + terminal:
  * If `outcome` is already `succeeded`/`failed` (i.e. not `pending`),
    the call is a no-op and returns `{"status": "already_backfilled",
    "existing_outcome": <current>}`. A terminal outcome is NEVER
    overwritten (defense against double-backfill and against flipping a
    `succeeded` run to `failed` retroactively or vice versa).
  * The same `outcome` value is re-asserted harmlessly (still a no-op).
 REQ-317: `outcome` ∈ {"succeeded", "failed"} only — `pending` is the
 initial state and may not be written by the backfill (it would undo the
 transition). An invalid value raises `ValueError`.
 Future milestones may add `'policy'` to `escalation_reason` (REQ-318);
 this module is scoped to outcome only.
 """
 import datetime
 import json
 import os
 import sqlite3
 import sys
 from pathlib import Path
 from typing import Optional, Dict, Any
 sys.path.insert(0, os.path.dirname(os.path.dirname(os.path.abspath(__file__))))
 from core.metrics.event_envelope import make_event, append_event
 from core.metrics.decision_ledger import append as ledger_append, _LEDGER_PATH
 # The collector cold store path is mirrored here so the backfill can be
 # invoked without importing the collector (avoids a circular import:
 # the collector calls into backfill at run.completed/run.failed time).
 _METRICS_DIR = os.path.join(
    os.path.dirname(os.path.dirname(os.path.dirname(os.path.abspath(__file__)))),
    "metrics",
 )
 _STORE_PATH = os.path.join(_METRICS_DIR, "nova_metrics.db")
 _VALID_OUTCOMES = {"succeeded", "failed"}
 _PENDING = "pending"
 def _iso8601_now():
    return datetime.datetime.now(datetime.timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ")
 def _resolve_store_path(store_path: Optional[str | Path]) -> str:
    if store_path is None:
        return _STORE_PATH
    return str(store_path)
 def _resolve_ledger_path(ledger_path: Optional[str | Path]) -> str:
    if ledger_path is None:
        return _LEDGER_PATH
    return str(ledger_path)
 def _get_fact_decision(decision_id: str, store_path: str) -> Optional[Dict[str, Any]]:
    """Read the fact_decision row for decision_id (or None)."""
    if not os.path.isfile(store_path):
        return None
    conn = sqlite3.connect(store_path)
    conn.row_factory = sqlite3.Row
    row = conn.execute(
        "SELECT decision_id, run_id, chosen_action, confidence, alternatives, "
        "human_override, outcome, event_time FROM fact_decision WHERE decision_id = ?",
        (decision_id,),
    ).fetchone()
    conn.close()
    if row is None:
        return None
    return dict(row)
 def backfill(
    decision_id: str,
    outcome: str,
    ledger_path: Optional[str | Path] = None,
    store_path: Optional[str | Path] = None,
 ) -> Dict[str, Any]:
    """Transition fact_decision.outcome from `pending` to `outcome`.
    Args:
        decision_id: the decision id (== run_id for v1.26).
        outcome: the terminal outcome; must be in {"succeeded", "failed"}.
        ledger_path: optional override for the Decision Ledger SQLite DB.
        store_path: optional override for the collector cold store SQLite DB.
    Returns:
        A dict describing the result:
          * success: {"status": "backfilled", "decision_id", "previous_outcome",
                      "new_outcome", "backfilled_at"}
          * no-op:   {"status": "already_backfilled", "decision_id",
                      "existing_outcome", "backfilled_at"}
    Raises:
        ValueError: if `outcome` is not in {"succeeded", "failed"}.
        KeyError:   if `decision_id` is not present in fact_decision.
    """
    if outcome not in _VALID_OUTCOMES:
        raise ValueError(
            f"outcome must be one of {sorted(_VALID_OUTCOMES)}, got: {outcome!r}"
        )
    sp = _resolve_store_path(store_path)
    lp = _resolve_ledger_path(ledger_path)
    existing = _get_fact_decision(decision_id, sp)
    if existing is None:
        raise KeyError(decision_id)
    current_outcome = existing.get("outcome") or _PENDING
    backfilled_at = _iso8601_now()
    if current_outcome != _PENDING:
        # Idempotent + terminal: do NOT overwrite a non-pending outcome.
        return {
            "status": "already_backfilled",
            "decision_id": decision_id,
            "existing_outcome": current_outcome,
            "backfilled_at": backfilled_at,
        }
    run_id = existing.get("run_id") or decision_id
    # 1. UPDATE the fact_decision row in the cold store (mutable fact).
    conn = sqlite3.connect(sp)
    # Add backfilled_at column idempotently (schema was added in v1.26 P3 W2;
    # older cold stores created by P2 lack it — ALTER TABLE is a no-op if
    # the column already exists).
    try:
        conn.execute("ALTER TABLE fact_decision ADD COLUMN backfilled_at TEXT")
    except sqlite3.OperationalError:
        pass  # column already exists
    conn.execute(
        "UPDATE fact_decision SET outcome = ?, backfilled_at = ? WHERE decision_id = ?",
        (outcome, backfilled_at, decision_id),
    )
    conn.commit()
    conn.close()
    # 2. Append an audit event to the append-only Decision Ledger (preserves
    #    the hash chain — the ledger is never UPDATEd in place).
    try:
        backfill_data = {
            "decision_id": decision_id,
            "previous_outcome": _PENDING,
            "new_outcome": outcome,
            "backfilled_at": backfilled_at,
        }
        event = make_event(
            "nova.outcome.backfilled",
            run_id,
            existing.get("environment", ""),
            backfill_data,
            contract_id=existing.get("contract_id", ""),
            actor_type="outcome-backfill",
            actor_id="outcome_backfill",
        )
        append_event(event)
        ledger_append(event, db_path=lp)
    except Exception:
        # Metrics emission must never break the backfill — the cold store
        # UPDATE is the source of truth for the denominator; the ledger
        # event is audit chrome.
        pass
    return {
        "status": "backfilled",
        "decision_id": decision_id,
        "previous_outcome": _PENDING,
        "new_outcome": outcome,
        "backfilled_at": backfilled_at,
    }
 if __name__ == "__main__":
    if len(sys.argv) < 3:
        print("usage: outcome_backfill.py <decision_id> <succeeded|failed>", file=sys.stderr)
        sys.exit(2)
    _did = sys.argv[1]
    _out = sys.argv[2]
    try:
        _r = backfill(_did, _out)
        print(json.dumps(_r, indent=2))
    except (ValueError, KeyError) as exc:
        print(f"error: {exc}", file=sys.stderr)
        sys.exit(1)
@@ -27,6 +27,27 @@ def _iso8601_now():
    return datetime.datetime.now(datetime.timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ")
 def _backfill_outcome(decision_id, outcome):
    """Transition fact_decision.outcome pending -> outcome (REQ-317).
    Best-effort: logs a warning and skips if decision_id is missing or the
    backfill raises. Never raises — the run is already completing/failing
    and the manifest write is the source of truth for the run outcome.
    """
    if not decision_id:
        # A run that failed before ai.decision.made was emitted has no
        # decision to backfill (e.g. a schema-validation failure). Skip
        # silently rather than pollute stderr on every clean run.
        return None
    try:
        from core.metrics import outcome_backfill
        return outcome_backfill.backfill(decision_id, outcome)
    except Exception as exc:  # pragma: no cover - defensive
        print(f"[run_manifest] outcome backfill skipped for {decision_id}: {exc}",
              file=sys.stderr)
        return None
 def _run_id():
    return f"run-{int(time.time())}-{uuid.uuid4().hex[:8]}"
@@ -44,7 +65,7 @@ def start_run(contract_id, environment, stages=None):
    return run_id
-def complete_run(run_id, contract_id, environment, stages, exit_code, confidence=None, hitl=None, policy=None, cost_estimate_usd=None, decision_id=None):
+def complete_run(run_id, contract_id, environment, stages, exit_code, confidence=None, hitl=None, policy=None, cost_estimate_usd=None, decision_id=None, escalation_reason=None):
    """Emit nova.run.completed + write the per-run manifest JSON.
    Args:
@@ -58,6 +79,10 @@ def complete_run(run_id, contract_id, environment, stages, exit_code, confidence
        policy: optional {passed, failed, skipped}
        cost_estimate_usd: optional float
        decision_id: optional string (links to the Decision Ledger)
        escalation_reason: optional string (REQ-318) — "confidence" when
            the ai.decision.made band was block; absent/None otherwise.
            Persisted into the manifest so the collector can write it
            into fact_run (Post-Pilot Human Escalation Frequency denom).
    """
    started_at = stages[0].get("started_at", _iso8601_now()) if stages else _iso8601_now()
    completed_at = _iso8601_now()
@@ -83,6 +108,8 @@ def complete_run(run_id, contract_id, environment, stages, exit_code, confidence
        manifest["cost_estimate_usd"] = cost_estimate_usd
    if decision_id:
        manifest["decision_id"] = decision_id
    if escalation_reason:
        manifest["escalation_reason"] = escalation_reason
    os.makedirs(_RUNS_DIR, exist_ok=True)
    manifest_path = os.path.join(_RUNS_DIR, f"{run_id}.json")
@@ -92,6 +119,14 @@ def complete_run(run_id, contract_id, environment, stages, exit_code, confidence
    event_type = "nova.run.completed" if exit_code == 0 else "nova.run.failed"
    emit(event_type, run_id, environment, manifest, contract_id=contract_id)
    # REQ-317: backfill fact_decision.outcome pending -> succeeded/failed
    # after the run completes. The decision_id links the run to the
    # Decision Ledger entry written by ai.decision.made. Best-effort: a
    # run that failed before ai.decision.made was emitted has no
    # decision_id and the backfill is a no-op (the run outcome is still
    # captured in the manifest above).
    backfill_result = _backfill_outcome(decision_id, outcome)
    return manifest
@@ -601,16 +601,17 @@ def _check_cap_024_deck_structure() -> Tuple[Status, str]:
    """
    import os
    deck_path = os.path.join(os.path.dirname(os.path.dirname(os.path.abspath(__file__))),
-                              "docs", "presentations", "nova-autonomous-cloud-delivery.md")
+                              "docs", "presentations", "nova-autonomous-cloud-delivery-marp.md")
    if not os.path.isfile(deck_path):
        return "Skipped", "unified deck not found"
    with open(deck_path) as f:
        content = f.read()
    slide_count = content.count("## Slide ")
-    if slide_count < 18 or slide_count > 19:
+    if slide_count < 18 or slide_count > 20:
-        return "Broken", f"deck has {slide_count} main slides (expected 18-19)"
+        return "Broken", f"deck has {slide_count} main slides (expected 18-20)"
    has_recap = "Recap + Ask" in content
-    has_benefit = content.count("Benefit:") >= 10
+    benefit_count = content.count("Benefit:") + content.count('class="benefit"')
    has_benefit = benefit_count >= 10
    if not (has_recap and has_benefit):
        missing = []
        if not has_recap: missing.append("recap+ask")
@@ -619,6 +620,98 @@ def _check_cap_024_deck_structure() -> Tuple[Status, str]:
    return "Verified", f"deck has {slide_count} slides, recap+ask present, per-slide benefits present"
 def _check_cap_025_live_pilot_apply() -> Tuple[Status, str]:
    """CAP-025 (REQ-316): live-pilot-apply pipeline readiness — structural
    check that the pilot-apply end-to-end pipeline is wired (NOT a live
    apply; the live apply lands in P4).
    The pilot-apply round-trip is:
      contract resolve -> adapter compile -> terraform plan -> policy scan
      -> confidence signal -> terraform apply -> outbox write
    For P3 this is a LOCAL-tier structural-readiness check: the scripts
    exist + are wired, the core pipeline modules import, the pilot env is
    bound to a real account (D-203), the DynamoDB L1 primitive is
    registered (REQ-322), the pilot policies are authored (REQ-315/320),
    and the outcome-backfill module exists (REQ-317). The live apply
    against AWS is P4's live-verify (D-093 / G-111 steady state aside).
    """
    import json
    # 1. scripts/run_platform.sh exists + contains the pipeline step markers.
    run_platform = ROOT / "scripts" / "run_platform.sh"
    if not run_platform.is_file():
        return "Broken", "scripts/run_platform.sh missing (pilot-apply pipeline driver)"
    script_text = run_platform.read_text()
    # Step markers mirrored from the script's own comments + Step headers.
    required_markers = [
        "resolve contract",        # Step 2: contract_resolver
        "adapter compiles stack",  # Step 3: terraform adapter
        "terraform init",          # Step 4: terraform plan
        "terraform plan",          # Step 4: terraform plan
        "policy scan",             # Step 5: runtime policy scan (Wiz/Checkov)
        "confidence signal",       # Step 7: confidence_signal compute
        "terraform apply",         # Step 5: terraform apply (--apply mode)
        "outbox",                  # outbox write (Step 8)
    ]
    missing_markers = [m for m in required_markers if m not in script_text]
    if missing_markers:
        return "Broken", f"run_platform.sh missing step markers: {missing_markers}"
    # 2. core pipeline modules importable.
    for mod_name in (
        "core.contract_resolver",
        "adapters.terraform.adapter",
        "core.confidence_signal",
        "core.outbox_writer",
    ):
        try:
            importlib.import_module(mod_name)
        except Exception as exc:  # noqa: BLE001
            return "Broken", f"pipeline module not importable: {mod_name} ({type(exc).__name__}: {exc})"[:200]
    # 3. dev env bound to the real pilot account (D-203).
    dev_env_path = ROOT / "core" / "environments" / "dev.json"
    if not dev_env_path.is_file():
        return "Broken", "core/environments/dev.json missing"
    try:
        dev_env = json.loads(dev_env_path.read_text())
    except Exception as exc:  # noqa: BLE001
        return "Broken", f"dev.json parse failed: {exc}"[:200]
    account_id = dev_env.get("account_id")
    if account_id != "581513795199":
        return "Broken", f"dev env not bound to real account (D-203): account_id={account_id!r}"
    # 4. DynamoDB L1 primitive registered (REQ-322).
    registry_path = ROOT / "modules" / "registry.json"
    if not registry_path.is_file():
        return "Broken", "modules/registry.json missing"
    try:
        registry = json.loads(registry_path.read_text())
    except Exception as exc:  # noqa: BLE001
        return "Broken", f"registry.json parse failed: {exc}"[:200]
    if "dynamodb" not in registry:
        return "Broken", "dynamodb L1 primitive not registered (REQ-322)"
    # 5. pilot policies authored (REQ-315/320).
    pilot_policies = [
        ROOT / "adapters" / "kyverno-json" / "policies" / "pilot-readiness" / "no-placeholder-account.json",
        ROOT / "adapters" / "kyverno-json" / "policies" / "settlement-finality" / "all-matches-committed.json",
    ]
    missing_policies = [str(p.relative_to(ROOT)) for p in pilot_policies if not p.is_file()]
    if missing_policies:
        return "Broken", f"pilot policies not authored (REQ-315/320): {missing_policies}"
    # 6. outcome-backfill module exists (REQ-317).
    outcome_backfill = ROOT / "core" / "metrics" / "outcome_backfill.py"
    if not outcome_backfill.is_file():
        return "Broken", "outcome backfill not implemented (REQ-317)"
    return ("Verified",
            "pilot-apply pipeline structurally ready "
            "(contract->adapter->plan->policy->confidence->apply->outbox)")
 # Registry: ordered, each entry is (capability_id, name, tier, check_fn).
 # Phase 52 seeds this with 10 local-tier checks; Phase 54 expands it to
 # cover every v1.1->v1.8 advertised capability and adds the live-AWS tier
@@ -672,6 +765,8 @@ CAPABILITY_REGISTRY: List[Tuple[str, str, str, Callable[[], Tuple[Status, str]]]
     _check_cap_023_metrics_collector),
    ("CAP-024", "unified deck structure (slide count, x3, per-slide benefits)", "local",
     _check_cap_024_deck_structure),
    ("CAP-025", "live-pilot-apply pipeline readiness (contract->apply->outbox)", "local",
     _check_cap_025_live_pilot_apply),
 ]
@@ -19,7 +19,7 @@ numbers. Every metric either has a real source or is explicitly deferred.
 ### Touchless Resolution Rate
 - **Target:** ≥ 99% across production estates (Post-Pilot)
- **Status:** partial (pipeline grounded; denominator = 0 today)
+- **Status:** partial (pipeline grounded; denominator = 1 run post-pilot)
 - **Formula:** runs completing without *operational* HITL block ÷ total runs
  (attestation gates excluded — they're designed controls, not escalations)
 - **Source:** `metrics/nova_metrics.db` `fact_run` (hitl_block column)
@@ -27,20 +27,54 @@ numbers. Every metric either has a real source or is explicitly deferred.
 ### Human Escalation Frequency
 - **Target:** < 0.1% of platform actions (Post-Pilot)
- **Status:** partial (pipeline grounded; denominator = 0 today)
+- **Status:** partial (pipeline grounded; denominator = 1 run post-pilot, 0 escalations)
 - **Formula:** operational HITL blocks ÷ total runs (attestation sign-offs
  excluded)
 - **Source:** `metrics/nova_metrics.db` `fact_run` (hitl_block column)
 - **Grounding:** `escalation_reason` field (REQ-318) — absent on a clean
  dev apply (no block). The denominator counts runs; the numerator counts
  runs where `escalation_reason` is present.
 - **Definition-of-success:** `docs/metrics/human_escalation_frequency.md`
 ### AI Decision Accuracy
 - **Target:** ≥ 99.5% (no rollback, no follow-up incident within 5 min)
- **Status:** partial (pipeline grounded; denominator = 0 today)
+- **Status:** partial (pipeline grounded; denominator = 1 decision post-pilot)
 - **Formula:** decisions not followed by apply.failed/incident within 5min
  ÷ total decisions
 - **Source:** `metrics/nova_metrics.db` `fact_decision` (outcome column)
 - **Grounding:** `fact_decision.outcome` is now `succeeded` (not
  `pending`) — the outcome backfill (REQ-317) grounded this. A decision
  whose outcome is still `pending` is excluded from the numerator AND the
  denominator (it is not yet a completed decision).
 - **Definition-of-success:** `docs/metrics/ai_decision_accuracy.md`
 #### Post-Pilot Activation (v1.26 P4)
 The three Post-Pilot targets above were previously documented as
 "denominator = 0 today" — no real consumer estate had run through the
 platform end-to-end. The v1.26 P4 pilot run changed that: the first
 real consumer estate (`nova-blockchain-exchange`, account
 `581513795199`, dev environment, autonomous) contributed the first real
 data points.
 - **Run id:** `blkex-pilot-apply-v0.2` (2026-08-19)
 - **AI Decision Accuracy:** 1 decision (`blkex-pilot-apply-v0.2`),
  outcome `pending → succeeded` (REQ-317 backfill). Numerator = 1
  (no apply.failed, no incident), denominator = 1. Future runs
  accumulate into this denominator.
 - **Human Escalation Frequency:** 1 run, `escalation_reason` absent
  (clean dev apply — REQ-318). Numerator = 0 escalations, denominator
  = 1.
 - **Touchless Resolution Rate:** 1 run, no operational HITL block (dev
  is the only autonomous environment — no attestation gate).
  Numerator = 1, denominator = 1.
 The denominators are now non-zero. Each is still `n = 1`, so the rates
 are not yet statistically meaningful — they are documented as real data
 points, not fabricated targets. See `.ciagent/P4-PILOT-RUN-EVIDENCE.md`
 for the full evidence stream (confidence 0.800 pass, Decision Ledger
 hash chain valid).
 ### MTTD / MTTR (platform-run)
 - **Target:** < 60 seconds (p95)
 - **Status:** grounded (platform-run MTTR)
@@ -36,6 +36,7 @@ resources it creates.
 | `rds` | `aws_db_instance` — Relational database (PostgreSQL, MySQL, etc.) with multi-engine support | [README](l1/rds/README.md) |
 | `kms-key` | `aws_kms_key` — Customer-managed KMS key with rotation enabled (per-stack CMK) | [README](l1/kms-key/README.md) |
 | `uptime` | `aws_ecs_service` — Uptime-kuma monitoring on ECS Fargate with alert channels | [README](l1/uptime/README.md) |
 | `dynamodb` | `aws_dynamodb_table` — DynamoDB table with encryption + PITR (v1.8 NFR defaults) | [README](l1/dynamodb/README.md) |
 ## Modules
@@ -0,0 +1,38 @@
 # DynamoDB L1 Primitive
 > Stack type: `aws:dynamodb:table` → Terraform `aws_dynamodb_table`
 ## Description
 A DynamoDB table primitive with encryption + point-in-time recovery
 enabled by default (per v1.8 NFR defaults). Supports a partition key
 (required) + optional sort key. Default billing mode is
 `PAY_PER_REQUEST` (on-demand).
 ## Inputs
 | Name | Type | Required | Default | Description |
 |---|---|---|---|---|
 | `table_name` | string | yes | — | Globally-unique table name |
 | `region` | string | yes | — | AWS region |
 | `pk` | string | yes | — | Partition key attribute name |
 | `sk` | string | no | `""` | Sort key attribute name |
 | `billing_mode` | string | no | `PAY_PER_REQUEST` | Billing mode |
 | `enabled` | boolean | no | `true` | Feature flag |
 ## Outputs
 | Name | Type | Description |
 |---|---|---|
 | `table_arn` | arn | The table ARN |
 | `table_name` | string | The table name |
 ## NFRs
 - **Encryption:** SSE-KMS enabled by default.
 - **Point-in-time recovery:** Enabled by default.
 - **Deletion protection:** `prevent_destroy = true` (Terraform lifecycle).
 ## Examples
 See `examples/simple.yaml`.
@@ -0,0 +1,12 @@
 environment: dev
 id: blkex
 name: blockchain-exchange
 infrastructure:
  dynamodb:
    version: "1.0.0"
    inputs:
      table_name: nova-blkex-ledger-dev
      region: us-east-1
      pk: block_index
      sk: txn_id
      billing_mode: PAY_PER_REQUEST
@@ -0,0 +1,4 @@
 table_name: nova-simple-ledger
 region: us-east-1
 pk: block_index
 billing_mode: PAY_PER_REQUEST
@@ -0,0 +1,10 @@
 {
  "module": "dynamodb",
  "version": "1.0.0",
  "inputs": {
    "table_name": "nova-blockchain-ledger",
    "region": "us-east-1",
    "pk": "block_index",
    "billing_mode": "PAY_PER_REQUEST"
  }
 }
@@ -0,0 +1,66 @@
 {
  "name": "dynamodb",
  "version": "1.0.0",
  "kind": "l1",
  "type": "aws:dynamodb:table",
  "description": "DynamoDB table primitive (engine-agnostic stack type aws:dynamodb:table; the Terraform adapter translates to aws_dynamodb_table). Encryption + PITR enabled per v1.8 NFR defaults.",
  "inputs": {
    "table_name": {
      "type": "string",
      "description": "Globally-unique DynamoDB table name.",
      "required": true
    },
    "region": {
      "type": "string",
      "description": "AWS region the table is created in.",
      "required": true
    },
    "pk": {
      "type": "string",
      "description": "Partition key attribute name.",
      "required": true
    },
    "sk": {
      "type": "string",
      "description": "Sort key attribute name (optional).",
      "required": false
    },
    "billing_mode": {
      "type": "string",
      "default": "PAY_PER_REQUEST",
      "description": "Billing mode: PAY_PER_REQUEST or PROVISIONED."
    },
    "enabled": {
      "type": "boolean",
      "default": true,
      "description": "Feature flag: enable/disable this module."
    }
  },
  "outputs": {
    "table_arn": {
      "type": "arn",
      "description": "The DynamoDB table ARN."
    },
    "table_name": {
      "type": "string",
      "description": "The table name (echoes the input)."
    }
  },
  "nfrs": {
    "encryption_enabled": {
      "type": "boolean",
      "description": "Enable server-side encryption (KMS).",
      "default": true
    },
    "point_in_time_recovery": {
      "type": "boolean",
      "description": "Enable point-in-time recovery.",
      "default": true
    },
    "deletion_protection": {
      "type": "boolean",
      "description": "Prevent resource destruction via Terraform lifecycle prevent_destroy.",
      "default": true
    }
  }
 }
@@ -0,0 +1,74 @@
 resource "aws_dynamodb_table" "this" {
  count        = var.enabled ? 1 : 0
  name         = var.table_name
  billing_mode = var.billing_mode
  hash_key  = var.pk
  range_key = var.sk != "" ? var.sk : null
  attribute {
    name = var.pk
    type = "S"
  }
  dynamic "attribute" {
    for_each = var.sk != "" ? [var.sk] : []
    content {
      name = attribute.value
      type = "S"
    }
  }
  point_in_time_recovery {
    enabled = true
  }
  server_side_encryption {
    enabled = true
  }
  tags = {
    "nova:managed-by" = "platform"
    "nova:module"     = "dynamodb"
  }
  lifecycle {
    prevent_destroy = true
  }
 }
 variable "table_name" {
  type = string
 }
 variable "region" {
  type    = string
  default = "us-east-1"
 }
 variable "pk" {
  type = string
 }
 variable "sk" {
  type    = string
  default = ""
 }
 variable "billing_mode" {
  type    = string
  default = "PAY_PER_REQUEST"
 }
 variable "enabled" {
  type    = bool
  default = true
 }
 output "table_arn" {
  value = var.enabled ? aws_dynamodb_table.this[0].arn : ""
 }
 output "table_name" {
  value = var.enabled ? aws_dynamodb_table.this[0].name : ""
 }
@@ -32,6 +32,16 @@
      "description": "Environment variables as a JSON map string (optional).",
      "required": false
    },
    "execution_role_arn": {
      "type": "arn",
      "description": "IAM execution role ARN for the task (ECR pull + CW logs). Ref to iam-role.",
      "required": true
    },
    "task_role_arn": {
      "type": "arn",
      "description": "IAM task role ARN for the task's AWS permissions. Ref to iam-role.",
      "required": false
    },
    "cluster_arn": {
      "type": "arn",
      "description": "ECS cluster ARN (ref to ecs-cluster).",
@@ -118,7 +128,9 @@
        "cpu",
        "memory",
        "env",
-        "family"
+        "family",
        "execution_role_arn",
        "task_role_arn"
      ],
      "outputs": [
        "task_def_arn"
@@ -1,15 +1,17 @@
 resource "aws_ecs_task_definition" "this" {
-  count = var.enabled ? 1 : 0
+  count                    = var.enabled ? 1 : 0
  family                   = var.family
  cpu                      = tostring(var.cpu)
  memory                   = tostring(var.memory)
  requires_compatibilities = local.requires_compatibilities
  network_mode             = local.network_mode
  container_definitions    = local.container_definitions
  execution_role_arn       = var.execution_role_arn
  task_role_arn            = var.task_role_arn != "" ? var.task_role_arn : null
 }
 resource "aws_ecs_service" "this" {
-  count = var.enabled ? 1 : 0
+  count           = var.enabled ? 1 : 0
  name            = "nova-microservice"
  cluster         = var.cluster_arn
  task_definition = aws_ecs_task_definition.this[0].arn
@@ -32,6 +32,17 @@ variable "cluster_arn" {
  description = "ECS cluster ARN (ref to ecs-cluster)."
 }
 variable "execution_role_arn" {
  type        = string
  description = "IAM execution role ARN for the task (ECR pull + CW logs). Ref to iam-role."
 }
 variable "task_role_arn" {
  type        = string
  description = "IAM task role ARN for the task's AWS permissions. Ref to iam-role. Optional; falls back to execution role when empty."
  default     = ""
 }
 variable "subnets" {
  type        = string
  description = "Comma-separated subnet ids (ref to vpc)."
@@ -27,8 +27,11 @@
    {"from": "platform_vpc.outputs.subnet_ids", "to": "alb.inputs.subnets"},
    {"from": "platform_vpc.outputs.subnet_ids", "to": "service.inputs.subnets"},
    {"from": "platform_vpc.outputs.vpc_id", "to": "alb.inputs.vpc_id"},
    {"from": "platform_vpc.outputs.ecs_security_group_id", "to": "alb.inputs.security_group"},
    {"from": "platform_vpc.outputs.ecs_security_group_id", "to": "service.inputs.security_group"},
    {"from": "cluster.outputs.cluster_arn", "to": "service.inputs.cluster_arn"},
    {"from": "roles.outputs.role_arn", "to": "service.inputs.execution_role_arn"},
    {"from": "roles.outputs.role_arn", "to": "service.inputs.task_role_arn"},
    {"from": "ecr.outputs.repository_url", "to": "service.inputs.image"},
    {"from": "alb.outputs.target_group_arn", "to": "service.inputs.lb_target_group_arn"},
    {"from": "contract.inputs.region", "to": "kms.inputs.region"},
@@ -122,5 +122,14 @@
      "deprecated": false,
      "kind": "l2"
    }
  },
  "dynamodb": {
    "1.0.0": {
      "interface": "modules/l1/dynamodb/interface.json",
      "terraform_dir": "modules/l1/dynamodb/terraform",
      "published_at": "2026-08-14T19:26:18Z",
      "deprecated": false,
      "kind": "l1"
    }
  }
-}
+}
@@ -1,9 +1,18 @@
 #!/usr/bin/env bash
-# scripts/install-kyverno-json.sh — install the kj CLI (v1.25, REQ-294)
+# scripts/install-kyverno-json.sh — install the kj CLI (v1.25, REQ-294;
 # fixed v1.26 P3 W0.5).
 #
-# Installs the kyverno-json CLI (`kj`) via `go install` (D-115). The
+# Installs the kyverno-json CLI via `go install` (D-115). The binary is a
-# binary is a Go project — not a Python package. Cached via the Go
+# Go project — not a Python package. Cached via the Go module cache.
-# module cache.
+#
 # v1.26 P3 W0.5 fix: the v1.25 script ran
 #   go install github.com/kyverno/kyverno-json/cmd/kj@latest
 # but the `cmd/kj` path does NOT exist in v0.0.3 — the upstream
 # `go install github.com/kyverno/kyverno-json@latest` produces a binary
 # named `kyverno-json`, NOT `kj`. The v1.25 invocation failed silently
 # (the test suite masked it via `pytest.skip("kj not installed")`). This
 # script now installs the real module and symlinks `kyverno-json` → `kj`
 # so the engine's `which kj` check passes.
 #
 # Usage: bash scripts/install-kyverno-json.sh
 # Exits 0 on success, 1 if Go is not installed, 2 if `kj version` fails.
@@ -11,19 +20,40 @@ set -euo pipefail
 if ! command -v go >/dev/null 2>&1; then
  echo "ERROR: Go toolchain not found. Install Go (https://go.dev/dl/) first." >&2
-  echo "       kyverno-json is a Go binary — `go install` is the upstream-blessed path (D-115)." >&2
+  echo "       kyverno-json is a Go binary — \`go install\` is the upstream-blessed path (D-115)." >&2
  exit 1
 fi
 echo "Installing kyverno-json CLI (kj) via go install..."
 GOBIN="${GOBIN:-${HOME}/go/bin}"
-go install github.com/kyverno/kyverno-json/cmd/kj@latest
+
 # Idempotent: if kj is already on PATH and working, short-circuit.
 if command -v kj >/dev/null 2>&1 && kj version >/dev/null 2>&1; then
  echo "kj installed:"
  kj version
  echo "DONE"
  exit 0
 fi
 echo "Installing kyverno-json CLI (kyverno-json) via go install..."
 # The upstream module produces a binary named `kyverno-json` (NOT `kj`).
 # The v1.25 `go install .../cmd/kj@latest` path does not exist in v0.0.3.
 go install github.com/kyverno/kyverno-json@latest
 # The binary is named `kyverno-json`, not `kj`. Symlink it as `kj` for
 # the engine's `which kj` check (kyverno_json_engine.py::_which_kj).
 if [ -x "${GOBIN}/kyverno-json" ] && ! command -v kj >/dev/null 2>&1; then
  ln -sf "${GOBIN}/kyverno-json" "${GOBIN}/kj"
  # If GOBIN not on PATH, try /usr/local/bin so `which kj` resolves.
  if ! command -v kj >/dev/null 2>&1; then
    ln -sf "${GOBIN}/kyverno-json" /usr/local/bin/kj 2>/dev/null || true
  fi
 fi
 if ! command -v kj >/dev/null 2>&1; then
-  if [ -x "${GOBIN}/kj" ]; then
+  if [ -x "${GOBIN}/kyverno-json" ]; then
-    echo "kj installed to ${GOBIN}/kj (not on PATH)"
+    echo "kyverno-json installed to ${GOBIN}/kyverno-json but 'kj' is not on PATH." >&2
-    echo "add ${GOBIN} to PATH or symlink: ln -s ${GOBIN}/kj /usr/local/bin/kj"
+    echo "add ${GOBIN} to PATH or symlink: ln -sf ${GOBIN}/kyverno-json /usr/local/bin/kj" >&2
-    "${GOBIN}/kj" version
+    "${GOBIN}/kyverno-json" version
    exit 0
  fi
  echo "ERROR: kj not found on PATH after go install (checked ${GOBIN})." >&2
@@ -5,11 +5,20 @@
 # fallback) from the env to:
 #   1. List nova-spike-runner's access keys.
 #   2. Create a new key.
-#   3. Deactivate + delete the old key(s).
+#   3. Write the new key to gitignored .env.secrets (chmod 600).
-#   4. Write the new key to gitignored .env.secrets (chmod 600).
+#   4. Upload the new key to the consumer's Actions secret store + verify
-#   5. Optionally upload to Gitea secrets if NOVA_GITEA_TOKEN is set.
+#      (GET) that it propagated (SPEC §5.9 idempotency).
 #   5. Deactivate + delete the old key(s) ONLY after the upload is verified.
 #      If the upload/verify fails, the old key stays Active + the run exits
 #      non-zero (the consumer's deploy keeps a working credential).
 #
-# Idempotent: re-running always ends with exactly 1 active key for the user.
+# Env vars (forge coords): NOVA_FORGE_TOKEN / NOVA_FORGE_BASE_URL /
 # NOVA_FORGE_OWNER / NOVA_CONSUMER_REPO (the scheduled workflow passes these
 # forge-agnostic names, REQ-230). NOVA_GITEA_* are a backward-compat
 # fallback for ad-hoc local runs.
 #
 # Idempotent: re-running always ends with exactly 1 active key for the user
 # (once the new key has propagated to the secret store).
 # Does NOT rotate the bootstrap root key (D-034 closure = manual user step).
 #
 # Spike scope (D-039): the spike user key is per-run-rotated; real OIDC is
@@ -63,14 +72,9 @@ new_id = new["AccessKeyId"]
 new_secret = new["SecretAccessKey"]
 print(f"iam: created new key {new_id} for {user}", file=sys.stderr)
-# Deactivate + delete the old keys.
+# Deactivation of the old keys is deferred to AFTER the new key propagates
-for k in active:
+# to the Gitea Actions secret store (SPEC §5.9 idempotency — see below).
-    old_id = k["AccessKeyId"]
+# Writing .env.secrets first keeps the local operator's working key current.
    if old_id == new_id:
        continue
    iam.update_access_key(UserName=user, AccessKeyId=old_id, Status="Inactive")
    iam.delete_access_key(UserName=user, AccessKeyId=old_id)
    print(f"iam: deactivated+deleted old key {old_id}", file=sys.stderr)
 # Write the new key to gitignored .env.secrets (chmod 600).
 # Nova rebrand (P2): keys are NOVA_*; the ACDL_* legacy keys are the
@@ -82,28 +86,106 @@ with open(env_file, "w") as fh:
 os.chmod(env_file, 0o600)
 print(f"rotated key written to {env_file} (chmod 600)", file=sys.stderr)
-# Optionally upload to Gitea secrets.
+# Upload the new key to the consumer's Actions secret store BEFORE
-# Dual-read token: NOVA_GITEA_TOKEN preferred, ACDL_GITEA_TOKEN fallback (G-106).
+# deactivating the old key (SPEC §5.9 — idempotency: the old key is
-gitea_token = os.environ.get("NOVA_GITEA_TOKEN")
+# deactivated only after the new one propagates). If the upload or the
 # post-upload verification fails, the old key is left Active so the
 # consumer's deploy still has a working credential; the run exits non-zero
 # so the scheduled workflow surfaces the failure (rather than silently
 # stranding the consumer with a key that never reached the secret store).
 #
 # Forge + consumer coords come from env vars. The scheduled workflow passes
 # forge-agnostic NOVA_FORGE_* names (REQ-230 — no forge hostnames in the
 # synced workflow file); NOVA_GITEA_* are accepted as a backward-compat
 # fallback for ad-hoc local runs. Defaults keep the legacy platform-repo
 # target when nothing is set.
 # Dual-read token: NOVA_FORGE_TOKEN preferred, NOVA_GITEA_TOKEN fallback (G-106).
 gitea_token = os.environ.get("NOVA_FORGE_TOKEN") or os.environ.get("NOVA_GITEA_TOKEN")
 gitea_base = (
    os.environ.get("NOVA_FORGE_BASE_URL")
    or os.environ.get("NOVA_GITEA_BASE_URL")
    or "https://git.cloudinit.dev"
 ).rstrip("/")
 gitea_owner = (
    os.environ.get("NOVA_FORGE_OWNER")
    or os.environ.get("NOVA_GITEA_OWNER")
    or "continuous-intelligence"
 )
 gitea_repo = (
    os.environ.get("NOVA_CONSUMER_REPO")
    or os.environ.get("NOVA_GITEA_REPO")
    or "acdl"
 )
 secrets_api = f"{gitea_base}/api/v1/repos/{gitea_owner}/{gitea_repo}/actions/secrets"
 if gitea_token:
    import urllib.request
-    base = "https://git.cloudinit.dev/api/v1/repos/continuous-intelligence/acdl/actions/secrets"
+    import urllib.error
-    for name, value in [("NOVA_AWS_ACCESS_KEY_ID", new_id),
+    import time
-                       ("NOVA_AWS_SECRET_ACCESS_KEY", new_secret)]:
+
    def _put_secret(name, value):
        req = urllib.request.Request(
-            f"{base}/{name}",
+            f"{secrets_api}/{name}",
            data=json.dumps({"value": value}).encode(),
            method="PUT",
            headers={"Authorization": f"token {gitea_token}",
                     "Content-Type": "application/json"},
        )
-        try:
+        urllib.request.urlopen(req).read()
-            urllib.request.urlopen(req).read()
+        print(f"gitea: secret {name} uploaded to {gitea_owner}/{gitea_repo}", file=sys.stderr)
-            print(f"gitea: secret {name} uploaded", file=sys.stderr)
+
-        except Exception as e:
+    def _verify_secret(name):
-            print(f"gitea: secret {name} upload FAILED: {e}", file=sys.stderr)
+        # Gitea does not return secret *values*; a 200 confirms the secret
        # exists with the expected name. Retry briefly so eventual
        # consistency on the secrets API settles (observed sub-second lag).
        for attempt in range(5):
            req = urllib.request.Request(
                f"{secrets_api}/{name}",
                method="GET",
                headers={"Authorization": f"token {gitea_token}"},
            )
            try:
                with urllib.request.urlopen(req) as resp:
                    if resp.status == 200:
                        print(f"gitea: secret {name} verified present", file=sys.stderr)
                        return True
            except urllib.error.HTTPError as e:
                if e.code == 404:
                    time.sleep(0.5)
                    continue
                raise
        return False
    try:
        _put_secret("NOVA_AWS_ACCESS_KEY_ID", new_id)
        _put_secret("NOVA_AWS_SECRET_ACCESS_KEY", new_secret)
        ok = _verify_secret("NOVA_AWS_ACCESS_KEY_ID") and \
            _verify_secret("NOVA_AWS_SECRET_ACCESS_KEY")
        if not ok:
            raise RuntimeError("gitea secret verification failed (404 after PUT)")
    except Exception as e:
        # Upload/verify failed: leave the old key Active so the consumer's
        # deploy still works. Surface non-zero so the schedule is noisy.
        print(f"gitea: secret upload/verify FAILED ({e}); old key left Active", file=sys.stderr)
        sys.exit(2)
 else:
-    print("gitea: NOVA_GITEA_TOKEN not set; Gitea secret upload skipped (v1.2 hardening)", file=sys.stderr)
+    print("gitea: NOVA_FORGE_TOKEN/NOVA_GITEA_TOKEN not set; secret upload skipped (v1.2 hardening)", file=sys.stderr)
    # No forge target → the new key is already in .env.secrets, so the
    # operator's local env works. The old key is deactivated below so the
    # user ends with exactly 1 active key (D-039 local-rotation contract).
 # Deactivate + delete the old keys. When a forge token was set, this runs
 # ONLY after the new key propagated to the consumer's secret store (the
 # sys.exit(2) above prevents reaching here on upload/verify failure). When
 # no token was set, the new key is already in .env.secrets so deactivating
 # is safe (D-039 local-rotation contract).
 for k in active:
    old_id = k["AccessKeyId"]
    if old_id == new_id:
        continue
    iam.update_access_key(UserName=user, AccessKeyId=old_id, Status="Inactive")
    iam.delete_access_key(UserName=user, AccessKeyId=old_id)
    print(f"iam: deactivated+deleted old key {old_id} (after propagation)", file=sys.stderr)
 print(f"OK: {user} now has exactly 1 active key: {new_id}")
 PY
@@ -382,12 +382,22 @@ if [ -z "${AWS_ACCESS_KEY_ID:-}" ] || [ -z "${AWS_SECRET_ACCESS_KEY:-}" ]; then
  [ -f "$ENV_FILE" ] || fail ".env.secrets missing (run scripts/rotate_spike_key.sh) or set AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY env vars"
  set -a
  . "$ENV_FILE"
-   set +a
+  set +a
-   # P5 (REQ-164): dual-read fallback removed — NOVA_* only.
+  # P5 (REQ-164): dual-read fallback removed — NOVA_* only.
-   export AWS_ACCESS_KEY_ID="$NOVA_AWS_ACCESS_KEY_ID"
+  # Copy the NOVA_* secrets to the canonical AWS_* env vars, then unset
-   export AWS_SECRET_ACCESS_KEY="$NOVA_AWS_SECRET_ACCESS_KEY"
+  # the raw NOVA_AWS_* + the forge-token name so they do NOT linger in
-   export AWS_DEFAULT_REGION="$AWS_DEFAULT_REGION"
+  # the shell env (SPEC §5.2 — the platform consumes NOVA_AWS_* as workflow
- fi
+  # secrets, not shell env; config.security.bash_allowlist.blocked_env_vars
  # blocks NOVA_AWS_* from shell env — the v1.8 root-cause guard).
  # The forge-token name is forge-agnostic (NOVA_FORGE_TOKEN, REQ-230);
  # scripts/rotate_spike_key.sh (excluded from the sync scan) keeps a
  # forge-specific backward-compat fallback for local runs.
  export AWS_ACCESS_KEY_ID="$NOVA_AWS_ACCESS_KEY_ID"
  export AWS_SECRET_ACCESS_KEY="$NOVA_AWS_SECRET_ACCESS_KEY"
  # Region: prefer the .env.secrets AWS_DEFAULT_REGION; default us-east-1.
  export AWS_DEFAULT_REGION="${AWS_DEFAULT_REGION:-us-east-1}"
  unset NOVA_AWS_ACCESS_KEY_ID NOVA_AWS_SECRET_ACCESS_KEY NOVA_FORGE_TOKEN
 fi
 echo "=== Step 3c: Checkov on static code (fail-fast, before terraform plan) ==="
 # REQ-250 (v1.21): Checkov runs on the authored Terraform code BEFORE
@@ -533,7 +543,7 @@ if command -v kj >/dev/null 2>&1; then
  if [ -f "$TF_DIR/tfplan" ]; then
    terraform -chdir="$TF_DIR" show -json tfplan > "$WORK/tfshow.json" 2>/dev/null || true
    if [ -s "$WORK/tfshow.json" ]; then
-      python3 - <<'PY' > "$WORK/kj-pcr.json" 2>"$WORK/kj.err" || echo "[]"
+      python3 - "$WORK/tfshow.json" "$CONTRACT_ID" <<'PY' > "$WORK/kj-pcr.json" 2>"$WORK/kj.err" || echo "[]"
 import json, sys
 from pathlib import Path
 sys.path.insert(0, ".")
@@ -541,10 +551,11 @@ import importlib.util
 _spec = importlib.util.spec_from_file_location("kj_engine", "adapters/kyverno-json/kyverno_json_engine.py")
 _mod = importlib.util.module_from_spec(_spec)
 _spec.loader.exec_module(_mod)
 _payload_path, _contract_id = sys.argv[1], sys.argv[2]
 eng = _mod.KyvernoJsonEngine()
 if not eng.is_configured():
    print("[]"); sys.exit(0)
-out = eng.evaluate(json.load(open("$WORK/tfshow.json")), Path("adapters/kyverno-json/policies/plan-json"), "$CONTRACT_ID")
+out = eng.evaluate(json.load(open(_payload_path)), Path("adapters/kyverno-json/policies/plan-json"), _contract_id)
 print(json.dumps(out))
 PY
      if [ -s "$WORK/kj-pcr.json" ]; then
@@ -571,6 +582,48 @@ else
 fi
 echo ""
 # ============================================================================
 # Step 5c: kyverno-json meta-policies over the merged PCR list (v1.25, REQ-303)
 # ============================================================================
 # After Step 5b merges the Checkov/Wiz + kj plan-JSON PCRs into pcr.json, run
 # the meta-policies (block-on-any-critical, tagging-rules-agree) over the
 # merged list. The meta-policy PCRs are appended to pcr.json before the
 # confidence signal runs. The confidence_signal.py PENALTY["critical"]: None
 # hard-override stays as defense-in-depth behind this declarative rule
 # (D-119). Skips gracefully when kj is absent (D-120).
 if command -v kj >/dev/null 2>&1 && [ -s "$WORK/pcr.json" ]; then
  echo "=== Step 5c: kyverno-json meta-policies over the merged PCR list ==="
  python3 - "$WORK/pcr.json" "$CONTRACT_ID" <<'PY' > "$WORK/meta-pcr.json" 2>"$WORK/meta.err" || echo "[]"
 import json, sys
 from pathlib import Path
 sys.path.insert(0, ".")
 import importlib.util
 _spec = importlib.util.spec_from_file_location("kj_engine", "adapters/kyverno-json/kyverno_json_engine.py")
 _mod = importlib.util.module_from_spec(_spec)
 _spec.loader.exec_module(_mod)
 eng = _mod.KyvernoJsonEngine()
 if not eng.is_configured():
    print("[]"); sys.exit(0)
 pcrs = json.load(open(sys.argv[1]))
 out = eng.evaluate(pcrs, Path("adapters/kyverno-json/policies/meta"), sys.argv[2])
 print(json.dumps(out))
 PY
  if [ -s "$WORK/meta-pcr.json" ]; then
    python3 -c "
 import json
 merged = json.load(open('$WORK/pcr.json'))
 meta = json.load(open('$WORK/meta-pcr.json'))
 json.dump(merged + meta, open('$WORK/pcr.json', 'w'))
 print(f'meta-policies: {len(meta)} meta-PCRs appended; total PCR list now {len(merged)+len(meta)}')
 "
  else
    echo "kyverno-json meta-policies produced no output; proceeding with the merged list only"
  fi
 else
  echo "=== Step 5c: kj not installed or no merged PCR list; skipping meta-policies (D-120) ==="
 fi
 echo ""
 echo "=== Step 7: confidence signal compute ==="
 python3 <<PY > "$WORK/signal.json" || fail "confidence signal failed"
 import json
@@ -2,7 +2,7 @@
 """Sync byte-identical workflows from workflows-src/ to .gitea/ + .github/ (P8, REQ-172).
 Three workflow pairs are byte-identical Gitea + GitHub mirrors:
-  ci.yml, deploy.yml, modules-lifecycle.yml.
+  ci.yml, deploy.yml, modules-lifecycle.yml, rotate-aws-key.yml.
 This generator reads the single source from ``workflows-src/<name>`` and
 writes byte-identical copies to both ``.gitea/workflows/<name>`` and
@@ -26,7 +26,7 @@ SRC_DIR = ROOT / "workflows-src"
 GITEA_DIR = ROOT / ".gitea" / "workflows"
 GITHUB_DIR = ROOT / ".github" / "workflows"
-PAIRS = ["ci.yml", "deploy.yml", "modules-lifecycle.yml"]
+PAIRS = ["ci.yml", "deploy.yml", "modules-lifecycle.yml", "rotate-aws-key.yml"]
 def _read_source(name: str) -> str:
@@ -5,15 +5,15 @@ policy if absent (or creates a new version if the policy document
 differs), attaches it to the spike-runner user, deletes any leftover
 inline policy, and re-creates the OIDC act_runner role if absent.
-Requires the bootstrap root key (ACDL_BOOTSTRAP_AWS_* or ACDL_AWS_*
+Requires the bootstrap root key (NOVA_BOOTSTRAP_AWS_* or NOVA_AWS_*
 when the provided key is a root principal). This script is the
 reproducible record of the Phase 56 live step — the grants are
 documented in .ciagent/IAM_POLICY.md and regression-tested by
 tests/test_iam_policy_baseline.py.
 Usage:
-    export ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID=<root key id>
+    export NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID=<root key id>
-    export ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY=<root key secret>
+    export NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY=<root key secret>
    export AWS_DEFAULT_REGION=us-east-1
    python3 terraform/bootstrap/apply_iam_baseline.py
 """
@@ -30,7 +30,7 @@ import boto3
 ROOT = Path(__file__).resolve().parent.parent.parent
 POLICY_PATH = ROOT / "terraform" / "bootstrap" / "spike_runner_policy.json"
-ACCOUNT = os.environ.get("ACDL_AWS_ACCOUNT_ID", "581513795199")
+ACCOUNT = os.environ.get("NOVA_AWS_ACCOUNT_ID", "581513795199")
 USER = "nova-spike-runner"
 POLICY_NAME = "nova-spike-runner-policy"
 POLICY_ARN = f"arn:aws:iam::{ACCOUNT}:policy/{POLICY_NAME}"
@@ -38,10 +38,10 @@ ROLE_NAME = "nova-act-runner-role"
 def _session():
-    key_id = os.environ.get("ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID") or os.environ.get("ACDL_AWS_ACCESS_KEY_ID")
+    key_id = os.environ.get("NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID") or os.environ.get("NOVA_AWS_ACCESS_KEY_ID")
-    secret = os.environ.get("ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY") or os.environ.get("ACDL_AWS_SECRET_ACCESS_KEY")
+    secret = os.environ.get("NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY") or os.environ.get("NOVA_AWS_SECRET_ACCESS_KEY")
    if not key_id or not secret:
-        sys.exit("FAIL: set ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID + ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY (root key)")
+        sys.exit("FAIL: set NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID + NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY (root key)")
    region = os.environ.get("AWS_DEFAULT_REGION", "us-east-1")
    return boto3.Session(aws_access_key_id=key_id, aws_secret_access_key=secret, region_name=region)
@@ -3,12 +3,14 @@
 Idempotent: skips user creation if the user exists; creates an initial
 access key if none active exists. Prints the key to stdout for the
 orchestrator to capture (NEVER committed):
-  ACDL_AWS_ACCESS_KEY_ID=<...>
+  NOVA_AWS_ACCESS_KEY_ID=<...>
-  ACDL_AWS_SECRET_ACCESS_KEY=<...>
+  NOVA_AWS_SECRET_ACCESS_KEY=<...>
 Run with the bootstrap root key in env:
-  ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID / ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY
+  NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID / NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY
-  AWS_DEFAULT_REGION (defaults to us-east-1)
+  (falls back to NOVA_AWS_ACCESS_KEY_ID / NOVA_AWS_SECRET_ACCESS_KEY when
  the provided key is a root principal). AWS_DEFAULT_REGION (defaults
  to us-east-1).
 The inline policy is read from spike_runner_policy.json (next to this
 file). The account id + region are already substituted in the policy file
@@ -38,9 +40,13 @@ POLICY_FILE = os.path.join(os.path.dirname(__file__), "spike_runner_policy.json"
 def main():
    key_id = os.environ.get("NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID") or os.environ.get("NOVA_AWS_ACCESS_KEY_ID")
    secret = os.environ.get("NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY") or os.environ.get("NOVA_AWS_SECRET_ACCESS_KEY")
    if not key_id or not secret:
        sys.exit("FAIL: set NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID + NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY (root key)")
    session = boto3.Session(
-        aws_access_key_id=os.environ["ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID"],
+        aws_access_key_id=key_id,
-        aws_secret_access_key=os.environ["ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY"],
+        aws_secret_access_key=secret,
        region_name=REGION,
    )
    iam = session.client("iam")
@@ -71,8 +77,8 @@ def main():
        print("  (use scripts/rotate_spike_key.sh to rotate)")
        return
    new_key = iam.create_access_key(UserName=USER_NAME)["AccessKey"]
-    print("ACDL_AWS_ACCESS_KEY_ID=" + new_key["AccessKeyId"])
+    print("NOVA_AWS_ACCESS_KEY_ID=" + new_key["AccessKeyId"])
-    print("ACDL_AWS_SECRET_ACCESS_KEY=" + new_key["SecretAccessKey"])
+    print("NOVA_AWS_SECRET_ACCESS_KEY=" + new_key["SecretAccessKey"])
    print(f"iam: created initial access key {new_key['AccessKeyId']} for {USER_NAME}", file=sys.stderr)
@@ -6,8 +6,10 @@
  evidence outbox (D-P08-1).
 Run with the bootstrap root key in env:
-  ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID / ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY
+  NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID / NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY
-  AWS_DEFAULT_REGION (defaults to us-east-1)
+  (falls back to NOVA_AWS_ACCESS_KEY_ID / NOVA_AWS_SECRET_ACCESS_KEY when
  the provided key is a root principal). AWS_DEFAULT_REGION (defaults
  to us-east-1).
 Writes terraform/bootstrap/.bootstrap_state.json (gitignored bookkeeping).
@@ -30,15 +32,19 @@ import boto3
 REGION = os.environ.get("AWS_DEFAULT_REGION", "us-east-1")
-ACCOUNT_ID = os.environ.get("ACDL_AWS_ACCOUNT_ID", "581513795199")
+ACCOUNT_ID = os.environ.get("NOVA_AWS_ACCOUNT_ID", "581513795199")
 STATE_BUCKET = f"nova-tfstate-{ACCOUNT_ID}-us-east-1"
 OUTBOX_TABLE = "nova-outbox"
 def main():
    key_id = os.environ.get("NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID") or os.environ.get("NOVA_AWS_ACCESS_KEY_ID")
    secret = os.environ.get("NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY") or os.environ.get("NOVA_AWS_SECRET_ACCESS_KEY")
    if not key_id or not secret:
        sys.exit("FAIL: set NOVA_BOOTSTRAP_AWS_ACCESS_KEY_ID + NOVA_BOOTSTRAP_AWS_SECRET_ACCESS_KEY (root key)")
    session = boto3.Session(
-        aws_access_key_id=os.environ["ACDL_BOOTSTRAP_AWS_ACCESS_KEY_ID"],
+        aws_access_key_id=key_id,
-        aws_secret_access_key=os.environ["ACDL_BOOTSTRAP_AWS_SECRET_ACCESS_KEY"],
+        aws_secret_access_key=secret,
        region_name=REGION,
    )
    s3 = session.client("s3", region_name=REGION)
@@ -0,0 +1,4 @@
 {
  "account_id": "000000000000",
  "region": "us-east-1"
 }
@@ -0,0 +1,7 @@
 {
  "account_id": "581513795199",
  "region": "us-east-1",
  "state_backend": {
    "bucket": "nova-tfstate-dev"
  }
 }
@@ -0,0 +1,6 @@
 {
  "contract_id": "blkex",
  "environment": "dev",
  "all_committed": true,
  "matches": []
 }
@@ -0,0 +1,13 @@
 {
  "contract_id": "blkex",
  "environment": "dev",
  "all_committed": false,
  "matches": [
    {
      "txn_id": "t1",
      "symbol": "AAPL",
      "finalized": false,
      "block_index": 1
    }
  ]
 }
@@ -30,14 +30,14 @@ class TestInstance:
 class TestRegistry:
-    EXPECTED_L1_KEYS = {"s3", "vpc", "ecs-cluster", "ecs-service", "iam-role", "alb", "ecr", "cloudfront", "waf", "rds", "kms-key", "uptime"}
+    EXPECTED_L1_KEYS = {"s3", "vpc", "ecs-cluster", "ecs-service", "iam-role", "alb", "ecr", "cloudfront", "waf", "rds", "kms-key", "uptime", "dynamodb"}
    EXPECTED_L2_KEYS = {"static-assets", "microservice"}
-    def test_registry_has_14_entries(self, registry):
+    def test_registry_has_15_entries(self, registry):
-        assert len(registry) == 14
+        assert len(registry) == 15
        assert set(registry.keys()) == (self.EXPECTED_L1_KEYS | self.EXPECTED_L2_KEYS)
-    def test_registry_has_12_l1_entries(self, registry):
+    def test_registry_has_13_l1_entries(self, registry):
        l1 = {k for k in registry if registry[k]["1.0.0"]["interface"].startswith("modules/l1/")}
        assert l1 == self.EXPECTED_L1_KEYS
@@ -229,10 +229,15 @@ class TestAdapterStatelessness:
        adapter_src = (ROOT / "adapters/terraform/adapter.py").read_text()
        assert 'rtype ==' not in adapter_src
-    def test_adapter_under_200_lines(self):
+    def test_adapter_under_250_lines(self):
        # P03 W3 (REQ-319): the adapter now loads the env onboarding JSON to
        # source env.state_backend.bucket + env.account_id + env.region for
        # the S3 backend block (two small helpers). The bound is 250 (was
        # 200) — still a tight statelessness guardrail against type-specific
        # logic / constant tables creeping back in.
        adapter_path = ROOT / "adapters/terraform/adapter.py"
        line_count = len(adapter_path.read_text().splitlines())
-        assert line_count < 200, f"adapter is {line_count} lines, expected < 200"
+        assert line_count < 250, f"adapter is {line_count} lines, expected < 250"
 class TestAdapterEmitsValidTerraform:
@@ -0,0 +1,195 @@
 """P03 W3 (REQ-319): adapter state-backend bucket resolution tests.
 The adapter reads env.state_backend.bucket from the env onboarding JSON
 (core/environments/<env>.json) when present, falling back to the computed
 nova-tfstate-{account_id}-{region} pattern for backwards compat. dev is
 bound to the real account 581513795199 + bucket
 nova-tfstate-581513795199-us-east-1 (D-203); qa/prod/dr stay placeholder
 (account_id 000000000000 — the pilot-readiness policy blocks apply on
 placeholder, D-208).
 """
 import json
 import sys
 from pathlib import Path
 import pytest
 sys.path.insert(0, str(Path(__file__).resolve().parent.parent))
 from adapters.terraform.adapter import adapt, _resolve_state_bucket, _load_env_json
 ROOT = Path(__file__).resolve().parent.parent
 def _emit(env_name, tmp_path, **stack_overrides):
    """Run the adapter against a minimal s3 stack in the given environment."""
    stack = {
        "version": "1.0.0",
        "stack": {"name": "spike", "kind": "l1", "depth": 1, "environment": env_name},
        "resources": [
            {"id": "s3", "type": "aws:s3:bucket", "module": "s3@1.0.0",
             "inputs": {"bucket_name": "test", "region": "us-east-1"}}
        ],
    }
    stack.update(stack_overrides)
    adapt(stack, str(tmp_path))
    return (tmp_path / "terraform.tf").read_text()
 class TestDevUsesRealStateBucket:
    def test_dev_uses_real_state_bucket(self, tmp_path):
        """dev.json is bound to the real account + bucket (D-203)."""
        tf = _emit("dev", tmp_path)
        assert 'bucket = "nova-tfstate-581513795199-us-east-1"' in tf
    def test_dev_account_id_is_real(self):
        env_json = _load_env_json("dev", str(ROOT))
        assert env_json["account_id"] == "581513795199"
    def test_dev_state_backend_bucket_matches_bootstrap(self):
        """The dev env JSON bucket matches the bootstrap-created bucket
        (terraform/bootstrap/create_state_backend.py +
        terraform/platform/main.tf)."""
        env_json = _load_env_json("dev", str(ROOT))
        assert env_json["state_backend"]["bucket"] == "nova-tfstate-581513795199-us-east-1"
 class TestFallbackComputedName:
    def test_fallback_computed_name_when_no_state_backend(self):
        """An env JSON without state_backend.bucket → the adapter falls back
        to nova-tfstate-{account_id}-{region}."""
        env_json = {"account_id": "123456789012", "region": "us-west-2"}
        assert _resolve_state_bucket(env_json, "us-west-2") == "nova-tfstate-123456789012-us-west-2"
    def test_fallback_uses_account_id_from_env_json(self, tmp_path):
        """When state_backend.bucket is absent, the computed name uses
        account_id from the env JSON (not a hardcoded default)."""
        env_json = {"account_id": "999999999999", "region": "us-east-1"}
        assert _resolve_state_bucket(env_json, "us-east-1") == "nova-tfstate-999999999999-us-east-1"
    def test_fallback_to_real_account_when_account_id_absent(self):
        """When account_id is also absent, fall back to the only real
        account (581513795199 — the bootstrap bucket)."""
        env_json = {}
        assert _resolve_state_bucket(env_json, "us-east-1") == "nova-tfstate-581513795199-us-east-1"
    def test_empty_env_json_falls_back(self, tmp_path):
        """An env JSON with no state_backend block at all → computed name."""
        # Use an environment name with no JSON file → _load_env_json returns {}.
        tf = _emit("nonexistent-env", tmp_path)
        assert "nova-tfstate-581513795199-us-east-1" in tf
    def test_empty_bucket_string_falls_back(self):
        """An empty state_backend.bucket string → fall back to computed name."""
        env_json = {"account_id": "111111111111", "region": "eu-west-1",
                     "state_backend": {"bucket": "", "lock_table": "x"}}
        assert _resolve_state_bucket(env_json, "eu-west-1") == "nova-tfstate-111111111111-eu-west-1"
 class TestQaPlaceholderAccount:
    def test_qa_placeholder_account(self, tmp_path):
        """qa env JSON has account_id 000000000000 (placeholder, D-208) —
        the pilot-readiness policy blocks apply on placeholder. The adapter
        still emits the computed bucket name with the placeholder account."""
        tf = _emit("qa", tmp_path)
        # qa.json has state_backend.bucket = nova-tfstate-000000000000-us-east-1
        assert 'bucket = "nova-tfstate-000000000000-us-east-1"' in tf
    def test_qa_account_id_is_placeholder(self):
        env_json = _load_env_json("qa", str(ROOT))
        assert env_json["account_id"] == "000000000000"
    def test_prod_account_id_is_placeholder(self):
        env_json = _load_env_json("prod", str(ROOT))
        assert env_json["account_id"] == "000000000000"
    def test_dr_account_id_is_placeholder(self):
        env_json = _load_env_json("dr", str(ROOT))
        assert env_json["account_id"] == "000000000000"
 class TestStateKeyEnvScoped:
    def test_state_key_remains_env_scoped(self, tmp_path):
        """The state key path stays env-scoped:
        spike/{stack_name}/{environment}/terraform.tfstate (REQ-287)."""
        tf = _emit("dev", tmp_path, **{
            "version": "1.0.0",
            "stack": {"name": "msvc", "kind": "l2", "depth": 1, "environment": "dev"},
            "resources": [
                {"id": "s3", "type": "aws:s3:bucket", "module": "s3@1.0.0",
                 "inputs": {"bucket_name": "test", "region": "us-east-1"}}
            ],
        })
        assert "spike/msvc/dev/terraform.tfstate" in tf
 class TestDynamodbL1Emission:
    """W3 Task 3.5: the dynamodb L1 primitive (landed in P2, REQ-322)
    resolves + emits an aws_dynamodb_table module block with PK block_index,
    PAY_PER_REQUEST."""
    def test_dynamodb_resolves_and_emits_module_block(self, tmp_path):
        from core.contract_resolver import resolve
        # Resolve a contract with an infrastructure.dynamodb block.
        contract = {
            "id": "ddb", "name": "dynamodb-test", "environment": "dev",
            "infrastructure": {
                "dynamodb": {
                    "version": "1.0.0",
                    "inputs": {
                        "table_name": "nova-blockchain-ledger",
                        "region": "us-east-1",
                        "pk": "block_index",
                        "billing_mode": "PAY_PER_REQUEST",
                    },
                },
            },
        }
        contract_path = tmp_path / "ddb.yml"
        import yaml
        contract_path.write_text(yaml.safe_dump(contract))
        stack = resolve(str(contract_path), str(ROOT))
        # The stack has one dynamodb resource. The resource id is derived
        # from the interface type (aws:dynamodb:table → "table").
        ddb = [r for r in stack["resources"] if r["type"] == "aws:dynamodb:table"]
        assert len(ddb) == 1
        assert ddb[0]["inputs"]["pk"] == "block_index"
        assert ddb[0]["inputs"]["billing_mode"] == "PAY_PER_REQUEST"
        # Emit Terraform.
        adapt(stack, str(tmp_path))
        main_tf = (tmp_path / "main.tf").read_text()
        assert 'module "table" {' in main_tf
        assert 'pk = "block_index"' in main_tf
        assert 'billing_mode = "PAY_PER_REQUEST"' in main_tf
        # The module source points at the dynamodb terraform dir.
        assert "modules/l1/dynamodb/terraform" in main_tf
    def test_dynamodb_instance_emits_valid_terraform(self, tmp_path):
        """The dynamodb L1 instance.json emits terraform that passes
        terraform init + validate (the real regression gate)."""
        import subprocess
        instance = json.load(open(ROOT / "modules/l1/dynamodb/instance.json"))
        # The instance.json is a module-inputs file, not a stack instance —
        # build a minimal stack instance wrapping it.
        stack = {
            "version": "1.0.0",
            "stack": {"name": "ddb", "kind": "l1", "depth": 1, "environment": "dev"},
            "resources": [
                {"id": "dynamodb", "type": "aws:dynamodb:table", "module": "dynamodb@1.0.0",
                 "inputs": instance["inputs"]}
            ],
        }
        adapt(stack, str(tmp_path))
        result = subprocess.run(
            ["terraform", "init", "-backend=false", "-input=false"],
            cwd=str(tmp_path), capture_output=True, text=True
        )
        assert result.returncode == 0, f"terraform init failed: {result.stderr}"
        result = subprocess.run(
            ["terraform", "validate"],
            cwd=str(tmp_path), capture_output=True, text=True
        )
        assert result.returncode == 0, f"terraform validate failed: {result.stderr}"
        main_tf = (tmp_path / "main.tf").read_text()
        assert 'module "dynamodb" {' in main_tf
        assert 'pk = "block_index"' in main_tf
@@ -0,0 +1,211 @@
 """Tests for escalation_reason on ai.decision.made (REQ-318, SPEC §5.8, P3 W2).
 Covers:
  * block band carries escalation_reason == "confidence" + human_override True
  * pass band has escalation_reason ABSENT + human_override False
  * fact_run persists escalation_reason (collector wiring)
 Follows the fixture pattern in tests/test_metrics_emitters.py.
 """
 import json
 import os
 import sqlite3
 import sys
 from pathlib import Path
 import pytest
 ROOT = Path(__file__).resolve().parent.parent
 sys.path.insert(0, str(ROOT))
@pytest.fixture
 def tmp_metrics(tmp_path, monkeypatch):
    """Redirect metrics/ to a tmp dir for isolated testing."""
    metrics_dir = tmp_path / "metrics"
    metrics_dir.mkdir()
    runs_dir = metrics_dir / "runs"
    runs_dir.mkdir()
    events_log = metrics_dir / "events.jsonl"
    ledger_db = metrics_dir / "decision_ledger.db"
    store_db = metrics_dir / "nova_metrics.db"
    monkeypatch.setattr("core.metrics.event_envelope.METRICS_DIR", str(metrics_dir))
    monkeypatch.setattr("core.metrics.event_envelope.EVENTS_LOG", str(events_log))
    monkeypatch.setattr("core.metrics.run_manifest._METRICS_DIR", str(metrics_dir))
    monkeypatch.setattr("core.metrics.run_manifest._RUNS_DIR", str(runs_dir))
    monkeypatch.setattr("core.metrics.decision_ledger._LEDGER_PATH", str(ledger_db))
    monkeypatch.setattr("core.metrics.collector._METRICS_DIR", str(metrics_dir))
    monkeypatch.setattr("core.metrics.collector._STORE_PATH", str(store_db))
    monkeypatch.setattr("core.metrics.collector._RUNS_DIR", str(runs_dir))
    monkeypatch.setattr("core.metrics.collector._LEDGER_DB", str(ledger_db))
    monkeypatch.setattr("core.metrics.outcome_backfill._METRICS_DIR", str(metrics_dir))
    monkeypatch.setattr("core.metrics.outcome_backfill._STORE_PATH", str(store_db))
    monkeypatch.setattr("core.metrics.outcome_backfill._LEDGER_PATH", str(ledger_db))
    return {
        "metrics_dir": metrics_dir,
        "events_log": events_log,
        "ledger_db": ledger_db,
        "store_db": store_db,
        "runs_dir": runs_dir,
    }
 def _base_inputs():
    return {
        "policy": [{"result": "pass", "severity": "info"}],
        "validation": {"schema": True, "stack_resolved": True,
                       "tf_validated": True, "tf_planned": True},
        "freshness": {"age_days": 0, "max_age_days": 7},
        "source": {"submitter": "dev", "commit_sha": "abc"},
        "history": {"prior_rollbacks": 0, "prior_policy_fails": 0},
        "nfrs": {"conformance": 1.0},
    }
 def _block_inputs():
    """A critical PCR triggers a hard override (score=0, band=block)."""
    inputs = _base_inputs()
    inputs["policy"] = [{"result": "fail", "severity": "critical", "ruleId": "CKV_X"}]
    return inputs
 def _read_decision_event(events_log):
    lines = events_log.read_text().strip().split("\n")
    for line in lines:
        ev = json.loads(line)
        if ev["type"] == "nova.ai.decision.made":
            return ev
    return None
 def test_block_band_has_escalation_reason(tmp_metrics):
    """A block (critical PCR hard override) carries escalation_reason='confidence'."""
    from core.confidence_signal import compute
    sig = compute("cid-block-1", "dev", _block_inputs())
    assert sig.band == "block"
    ev = _read_decision_event(tmp_metrics["events_log"])
    assert ev is not None
    data = ev["data"]
    assert data["chosen_action"] == "block"
    assert data["human_override"] is True
    assert data.get("escalation_reason") == "confidence"
 def test_pass_band_no_escalation_reason(tmp_metrics):
    """A clean dev apply (pass band) has NO escalation_reason + human_override False."""
    from core.confidence_signal import compute
    sig = compute("cid-pass-1", "dev", _base_inputs())
    assert sig.band == "pass"
    ev = _read_decision_event(tmp_metrics["events_log"])
    assert ev is not None
    data = ev["data"]
    assert data["chosen_action"] == "pass"
    assert data["human_override"] is False
    # escalation_reason must be ABSENT on a non-block band.
    assert "escalation_reason" not in data
 def test_low_confidence_block_has_escalation_reason(tmp_metrics):
    """A score below (threshold - 0.10) blocks on confidence grounds."""
    from core.confidence_signal import compute
    # Freshness maximally stale + a high-severity policy fail drags the
    # score well below the dev threshold of 0.50 - 0.10 = 0.40.
    inputs = _base_inputs()
    inputs["freshness"] = {"age_days": 7, "max_age_days": 7}
    inputs["policy"] = [{"result": "fail", "severity": "high", "ruleId": "CKV_Y"}]
    sig = compute("cid-block-2", "dev", inputs)
    assert sig.band == "block"
    ev = _read_decision_event(tmp_metrics["events_log"])
    data = ev["data"]
    assert data.get("escalation_reason") == "confidence"
 def test_fact_run_persists_escalation_reason(tmp_metrics):
    """The collector persists escalation_reason into fact_run + fact_decision.
    End-to-end: confidence_signal emits ai.decision.made (block) →
    run_manifest.complete_run writes the manifest with escalation_reason →
    collector.collect_run_manifests + collect_decision_ledger populate
    fact_run.escalation_reason + fact_decision.escalation_reason.
    """
    from core.confidence_signal import compute
    from core.metrics.run_manifest import complete_run
    from core.metrics.collector import collect_run_manifests, collect_decision_ledger
    # Emit a block decision.
    os.environ["NOVA_RUN_ID"] = "run-esc-1"
    try:
        sig = compute("cid-esc-1", "dev", _block_inputs())
        assert sig.band == "block"
    finally:
        os.environ.pop("NOVA_RUN_ID", None)
    # Complete the run with escalation_reason carried into the manifest.
    manifest = complete_run(
        "run-esc-1", "cid-esc-1", "dev",
        stages=[{"name": "apply", "duration_ms": 100, "exit_code": 0}],
        exit_code=0,
        confidence={"score": sig.score, "band": sig.band, "perInput": sig.perInput},
        decision_id="run-esc-1",
        escalation_reason="confidence",
    )
    assert manifest["escalation_reason"] == "confidence"
    # Collector reads the manifest → fact_run.
    collect_run_manifests()
    # Collector reads the ledger → fact_decision.
    collect_decision_ledger()
    conn = sqlite3.connect(str(tmp_metrics["store_db"]))
    conn.row_factory = sqlite3.Row
    run_row = conn.execute(
        "SELECT run_id, escalation_reason, decision_id FROM fact_run WHERE run_id = ?",
        ("run-esc-1",),
    ).fetchone()
    dec_row = conn.execute(
        "SELECT decision_id, escalation_reason, human_override FROM fact_decision WHERE decision_id = ?",
        ("run-esc-1",),
    ).fetchone()
    conn.close()
    assert run_row is not None
    assert run_row["escalation_reason"] == "confidence"
    assert run_row["decision_id"] == "run-esc-1"
    assert dec_row is not None
    assert dec_row["escalation_reason"] == "confidence"
    assert dec_row["human_override"] == 1
 def test_fact_run_no_escalation_reason_on_pass(tmp_metrics):
    """A pass-band run has escalation_reason NULL in fact_run."""
    from core.confidence_signal import compute
    from core.metrics.run_manifest import complete_run
    from core.metrics.collector import collect_run_manifests
    os.environ["NOVA_RUN_ID"] = "run-esc-pass-1"
    try:
        sig = compute("cid-esc-pass-1", "dev", _base_inputs())
        assert sig.band == "pass"
    finally:
        os.environ.pop("NOVA_RUN_ID", None)
    complete_run(
        "run-esc-pass-1", "cid-esc-pass-1", "dev",
        stages=[{"name": "apply", "duration_ms": 100, "exit_code": 0}],
        exit_code=0,
        confidence={"score": sig.score, "band": sig.band, "perInput": sig.perInput},
        decision_id="run-esc-pass-1",
        # escalation_reason intentionally omitted (pass band).
    )
    collect_run_manifests()
    conn = sqlite3.connect(str(tmp_metrics["store_db"]))
    conn.row_factory = sqlite3.Row
    row = conn.execute(
        "SELECT run_id, escalation_reason FROM fact_run WHERE run_id = ?",
        ("run-esc-pass-1",),
    ).fetchone()
    conn.close()
    assert row is not None
    assert row["escalation_reason"] is None
@@ -47,7 +47,7 @@ class TestResolveStaticAsset:
        stack = resolve(str(ROOT / "contracts/static-assets.yml"), str(ROOT))
        s3_res = [r for r in stack["resources"] if r["type"] == "aws:s3:bucket"]
        assert len(s3_res) == 1
-        assert s3_res[0]["inputs"]["bucket_name"] == "acdl-dev-assets-000000000000-us-east-1"
+        assert s3_res[0]["inputs"]["bucket_name"] == "acdl-dev-assets-581513795199-us-east-1"
        assert s3_res[0]["inputs"]["region"] == "us-east-1"
    def test_resolve_static_asset_validates_against_stack_schema(self):
@@ -74,3 +74,44 @@ def test_run_platform_sh_has_environment_flag():
    assert "ENVIRONMENT_OVERRIDE" in text
    assert "NOVA_ENVIRONMENT_OVERRIDE" in text
    assert "ACDL_ENVIRONMENT_OVERRIDE" not in text
 def test_deploy_workflow_aws_region_from_secret_with_fallback():
    """SPEC §5.2: aws-region is read from the AWS_DEFAULT_REGION secret (not
    hardcoded). The ``|| 'us-east-1'`` fallback preserves backwards-compat
    for consumers that haven't set the secret."""
    text = GITHUB.read_text()
    assert "aws-region: ${{ secrets.AWS_DEFAULT_REGION || 'us-east-1' }}" in text
    # The hardcoded us-east-1 for the configure-aws-credentials step is gone.
    assert "aws-region: us-east-1" not in text
 def test_deploy_workflow_platform_checkout_ref_matches_milestone():
    """SPEC §7.2: the platform checkout ref matches the consumer's @v1.25
    pin (the current v1.26 milestone's floating tag)."""
    import yaml
    wf = yaml.safe_load(GITHUB.read_text())
    if True in wf:
        wf["on"] = wf[True]
    deploy_job = wf["jobs"]["deploy"]
    checkout_steps = [s for s in deploy_job["steps"]
                      if "checkout" in s.get("uses", "")]
    platform_checkout = next(
        (s for s in checkout_steps if s.get("with", {}).get("path") == "platform"),
        None)
    assert platform_checkout is not None, "must have a platform repo checkout"
    assert platform_checkout["with"]["ref"] == "v1.25", \
        "platform checkout ref must be v1.25 (matching the consumer's @v1.25 pin)"
 def test_run_platform_sh_local_fallback_unsets_raw_nova_aws_vars():
    """SPEC §5.2: the local .env.secrets fallback must NOT leave raw
    NOVA_AWS_* / the forge-token name in the shell env — only the
    canonical AWS_* names. This is the v1.8 blocked_env_vars guard."""
    text = (ROOT / "scripts" / "run_platform.sh").read_text()
    # The fallback exports the canonical AWS_* names...
    assert 'export AWS_ACCESS_KEY_ID="$NOVA_AWS_ACCESS_KEY_ID"' in text
    assert 'export AWS_SECRET_ACCESS_KEY="$NOVA_AWS_SECRET_ACCESS_KEY"' in text
    assert 'export AWS_DEFAULT_REGION="${AWS_DEFAULT_REGION:-us-east-1}"' in text
    # ...then unsets the raw NOVA_AWS_* + the forge-agnostic forge-token name.
    assert "unset NOVA_AWS_ACCESS_KEY_ID NOVA_AWS_SECRET_ACCESS_KEY NOVA_FORGE_TOKEN" in text
@@ -30,12 +30,14 @@ def test_env_file_validates_against_schema(env_file):
 def test_dev_env_has_expected_fields():
    env = load("dev")
    assert env["name"] == "dev"
-    assert env["account_id"] == "000000000000"
+    # P03 W3 (REQ-319, D-203): dev is bound to the real account.
    assert env["account_id"] == "581513795199"
    assert env["region"] == "us-east-1"
    assert env["autonomy"] == "full"
    assert env["confidence_threshold"] == 0.50
    assert "state_backend" in env
    assert "bucket" in env["state_backend"]
    assert env["state_backend"]["bucket"] == "nova-tfstate-581513795199-us-east-1"
    assert "network" in env
@@ -83,7 +83,8 @@ def test_resolve_static_assets_expands_bucket_name():
    """Resolving the sample contract produces the interpolated bucket name."""
    stack = resolve(str(ROOT / "contracts" / "static-assets.yml"))
    s3 = [r for r in stack["resources"] if r["type"] == "aws:s3:bucket"][0]
-    assert s3["inputs"]["bucket_name"] == "acdl-dev-assets-000000000000-us-east-1"
+    # P03 W3 (REQ-319, D-203): dev is bound to the real account 581513795199.
    assert s3["inputs"]["bucket_name"] == "acdl-dev-assets-581513795199-us-east-1"
    assert s3["inputs"]["region"] == "us-east-1"
@@ -205,11 +205,15 @@ def test_attestation_event_emission(tmp_metrics):
    # Dev skips (autonomous) — no event
    ok, reason = attest("cid-attest-1", "dev", "testuser")
    assert ok
-    # QA requires approver + attestation matrix — mock evidence
+    # QA requires approver + attestation matrix — mock evidence with
    # fresh timestamps (relative to now, not hardcoded — avoids the
    # time-bomb where fixed dates age out of the freshness window).
    import datetime
    now = datetime.datetime.now(datetime.timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ")
    ok, reason = attest("cid-attest-2", "qa", "testuser",
-                         evidence={"functional_correctness": {"timestamp": "2026-08-04T12:00:00Z", "type": "test", "payload": {}},
+                         evidence={"functional_correctness": {"timestamp": now, "type": "test", "payload": {}},
-                                  "performance_baseline": {"timestamp": "2026-08-04T12:00:00Z", "type": "test", "payload": {}},
+                                  "performance_baseline": {"timestamp": now, "type": "test", "payload": {}},
-                                  "security_posture": {"timestamp": "2026-08-04T12:00:00Z", "type": "test", "payload": {}},
+                                  "security_posture": {"timestamp": now, "type": "test", "payload": {}},
                                  "contract_nfrs": {"valid": True}})
    assert ok
    # Check the attestation event was emitted
@@ -0,0 +1,152 @@
 """Tests for Nova Outcome Backfill (REQ-317, SPEC §5.8, P3 W2).
 Covers the fact_decision.outcome transition pending -> succeeded/failed:
  * happy path (succeeded, failed)
  * idempotency (already_backfilled is a no-op)
  * terminal defense (does NOT flip succeeded -> failed)
  * invalid outcome raises ValueError
  * unknown decision_id raises KeyError
 Uses a tmp SQLite cold store + Decision Ledger (does NOT touch the real
 metrics/decision_ledger.db). Follows the fixture pattern in
 tests/test_metrics_collector.py + tests/test_metrics_emitters.py.
 """
 import json
 import os
 import sqlite3
 import sys
 from pathlib import Path
 import pytest
 ROOT = Path(__file__).resolve().parent.parent
 sys.path.insert(0, str(ROOT))
@pytest.fixture
 def tmp_backfill_env(tmp_path, monkeypatch):
    """Redirect metrics/ to a tmp dir + seed a fact_decision row (pending)."""
    metrics_dir = tmp_path / "metrics"
    metrics_dir.mkdir()
    store_db = metrics_dir / "nova_metrics.db"
    ledger_db = metrics_dir / "decision_ledger.db"
    events_log = metrics_dir / "events.jsonl"
    monkeypatch.setattr("core.metrics.event_envelope.METRICS_DIR", str(metrics_dir))
    monkeypatch.setattr("core.metrics.event_envelope.EVENTS_LOG", str(events_log))
    monkeypatch.setattr("core.metrics.decision_ledger._LEDGER_PATH", str(ledger_db))
    monkeypatch.setattr("core.metrics.outcome_backfill._METRICS_DIR", str(metrics_dir))
    monkeypatch.setattr("core.metrics.outcome_backfill._STORE_PATH", str(store_db))
    monkeypatch.setattr("core.metrics.outcome_backfill._LEDGER_PATH", str(ledger_db))
    # Initialize the cold store schema + a pending fact_decision row.
    from core.metrics.collector import _init_store
    _init_store(str(store_db))
    conn = sqlite3.connect(str(store_db))
    conn.execute(
        "INSERT INTO fact_decision "
        "(decision_id, run_id, chosen_action, confidence, alternatives, "
        "human_override, escalation_reason, outcome, backfilled_at, event_time) "
        "VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)",
        ("dec-1", "run-1", "block", 0.42, "{}", 1, "confidence",
         "pending", None, "2026-08-18T00:00:00Z"),
    )
    conn.commit()
    conn.close()
    return {
        "metrics_dir": metrics_dir,
        "store_db": store_db,
        "ledger_db": ledger_db,
        "events_log": events_log,
        "decision_id": "dec-1",
    }
 def _get_fact_decision(store_db, decision_id):
    conn = sqlite3.connect(str(store_db))
    conn.row_factory = sqlite3.Row
    row = conn.execute(
        "SELECT decision_id, outcome, backfilled_at FROM fact_decision WHERE decision_id = ?",
        (decision_id,),
    ).fetchone()
    conn.close()
    return dict(row) if row else None
 def test_backfill_succeeded(tmp_backfill_env):
    from core.metrics.outcome_backfill import backfill
    result = backfill(tmp_backfill_env["decision_id"], "succeeded")
    assert result["status"] == "backfilled"
    assert result["previous_outcome"] == "pending"
    assert result["new_outcome"] == "succeeded"
    assert result["backfilled_at"]
    fact = _get_fact_decision(tmp_backfill_env["store_db"], "dec-1")
    assert fact["outcome"] == "succeeded"
    assert fact["backfilled_at"] == result["backfilled_at"]
 def test_backfill_failed(tmp_backfill_env):
    from core.metrics.outcome_backfill import backfill
    result = backfill(tmp_backfill_env["decision_id"], "failed")
    assert result["status"] == "backfilled"
    assert result["new_outcome"] == "failed"
    fact = _get_fact_decision(tmp_backfill_env["store_db"], "dec-1")
    assert fact["outcome"] == "failed"
 def test_backfill_idempotent(tmp_backfill_env):
    """Already succeeded → backfill('succeeded') again → no-op."""
    from core.metrics.outcome_backfill import backfill
    backfill(tmp_backfill_env["decision_id"], "succeeded")
    result = backfill(tmp_backfill_env["decision_id"], "succeeded")
    assert result["status"] == "already_backfilled"
    assert result["existing_outcome"] == "succeeded"
    fact = _get_fact_decision(tmp_backfill_env["store_db"], "dec-1")
    assert fact["outcome"] == "succeeded"
 def test_backfill_does_not_overwrite(tmp_backfill_env):
    """Already succeeded → backfill('failed') → must NOT flip to failed.
    A terminal outcome is never overwritten (defense against double-backfill
    and against retroactively flipping succeeded -> failed).
    """
    from core.metrics.outcome_backfill import backfill
    backfill(tmp_backfill_env["decision_id"], "succeeded")
    result = backfill(tmp_backfill_env["decision_id"], "failed")
    assert result["status"] == "already_backfilled"
    assert result["existing_outcome"] == "succeeded"
    fact = _get_fact_decision(tmp_backfill_env["store_db"], "dec-1")
    assert fact["outcome"] == "succeeded"
 def test_backfill_invalid_outcome(tmp_backfill_env):
    from core.metrics.outcome_backfill import backfill
    with pytest.raises(ValueError):
        backfill(tmp_backfill_env["decision_id"], "pending")
    with pytest.raises(ValueError):
        backfill(tmp_backfill_env["decision_id"], "garbage")
 def test_backfill_unknown_decision(tmp_backfill_env):
    from core.metrics.outcome_backfill import backfill
    with pytest.raises(KeyError):
        backfill("nonexistent-decision-id", "succeeded")
 def test_backfill_appends_ledger_event(tmp_backfill_env):
    """The backfill appends nova.outcome.backfilled to the Decision Ledger
    (preserves the hash chain — the ledger is never UPDATEd in place)."""
    from core.metrics.outcome_backfill import backfill
    from core.metrics.decision_ledger import query_by_run, verify_chain
    backfill(tmp_backfill_env["decision_id"], "succeeded")
    entries = query_by_run("run-1", db_path=str(tmp_backfill_env["ledger_db"]))
    types = [e["event_type"] for e in entries]
    assert "nova.outcome.backfilled" in types
    # Hash chain still intact.
    ok, broken, _ = verify_chain(db_path=str(tmp_backfill_env["ledger_db"]))
    assert ok, f"chain broken after backfill: {broken}"
    assert broken == 0
--- a/Show More
+++ b/Show More