docs(P55): rewrite PROJECT/ROADMAP/decks to verified reality; unfreeze decks
PROJECT.md gains a 'Capability Status (Re-Verified 2026-07-27)' section after Domain Boundaries: decay disclosure, the 16 auto-verified capabilities table, the 6 IAM-gated escalated resources, and the regression-gate note. ROADMAP.md v1.9.8 entry annotated 'Last deck-polish phase before the v1.10 deck-freeze'; new v1.10 overview entry noting v1.9.1-v1.9.8 are 'superseded-by-reverification'. Both leadership decks disclose the 2026-07-27 re-verification in their maturity-framing headers, citing .ciagent/CAPABILITY_INVENTORY.md as the source of truth. No 'shipped'/'Available today' claims remain that aren't backed by a Verified capability or an explicit escalation note. The 6 IAM-gated cloud resources (contracts table, Lambda, ECS service, CloudFront stack, uptime-kuma, OIDC role) are explicitly listed as escalated, not silently omitted. Decks unfrozen. v1.10.0 ready to tag. ---ci--- project: acdl phase: 55 milestone: v1.10 status: verify requirements: covered: [REQ-115] partial: [] decisions: [D-094] ---/ci---
This commit is contained in:
@@ -5,6 +5,7 @@
|
||||
> **Length:** ~15 minutes · 10 main + 6 appendix = 16 slides
|
||||
> **Purpose:** Sell the platform's value to tech leadership — zero-trust, security, observability, auditability, and the shift from "operators guess" to "the platform computes safety."
|
||||
> **Maturity framing:** "Testing" = works internally, dev pilot-ready. "Planned" = on the roadmap, not yet implemented. "Agentic" = involves AI agents or autonomous decision-making.
|
||||
> **Re-verification (2026-07-27):** Every "Testing" claim in this deck was re-verified in v1.10 Phase 54 (D-093). The headline E2E (contract → resolver → adapter → terraform init/validate/plan) passes against the live AWS account; the local emulating tier (Phase 53) runs the full E2E with no cloud credentials. 16/16 auto-verifiable capabilities Verified; 6 IAM-gated cloud resources are escalated (require an admin principal the spike-runner lacks). See `.ciagent/CAPABILITY_INVENTORY.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@
|
||||
> **Length:** ~15 minutes · 10 main + 6 appendix = 16 slides
|
||||
> **Purpose:** Sell the developer experience and the citizen developer experience to tech leadership — velocity without sacrificing safety, and security/observability/compliance as platform defaults rather than per-team effort.
|
||||
> **Maturity framing:** "Testing" = works internally, dev pilot-ready. "Planned" = on the roadmap. "Agentic" = involves AI agents or autonomous decision-making.
|
||||
> **Re-verification (2026-07-27):** Every "Testing" claim in this deck was re-verified in v1.10 Phase 54 (D-093). The headline E2E (contract → resolver → adapter → terraform init/validate/plan) passes against the live AWS account; the local emulating tier (Phase 53) runs the full E2E with no cloud credentials. 16/16 auto-verifiable capabilities Verified; 6 IAM-gated cloud resources are escalated (require an admin principal the spike-runner lacks). See `.ciagent/CAPABILITY_INVENTORY.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user