docs(review): P1 fixes — sync slide-count metadata + README directory layout
Review of P71 (v1.13) flagged 2 P1 documentation-metadata drift items: 1. Source .md length headers undercounted by 1 (excluded Appendix TOC slide) 2. README.md drifted — missing 12 new asset files + stale slide/section counts Fixes: - how-the-platform-works.md: 18 -> 19 slides (10 main + TOC + 8 appendix) - the-developer-experience.md: 17 -> 18 slides (10 main + TOC + 7 appendix) - both *-talking-points.md companion headers updated to match - README.md directory layout: added 6 new .mmd + 6 new .png files - README.md appendix convention: "10 main + 6 appendix (17 total)" -> per-deck counts (A1-A8 platform, A1-A7 developer, both with TOC) - README.md current-decks table: slide counts updated to 19/18 - README.md talking-points structure: "10 main + 7 appendix" -> TOC-aware No factual/capability claim changes. 16 docs tests pass. ---ci--- project: acdl phase: 71 milestone: v1.13 status: verify lessons: - P1 fix: sync slide-count metadata across source .md, talking-points, README ---/ci---
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
> **Subtitle:** Agentic Cloud Delivery Platform
|
||||
> **Audience:** Senior Leadership, CTO, Head of Cloud, Head of Infrastructure, Head of DevOps
|
||||
> **Length:** ~15 minutes · 10 main + 7 appendix = 17 slides
|
||||
> **Length:** ~15 minutes · 10 main + Appendix TOC + 7 appendix = 18 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-29):** Every "Testing" claim in this deck was re-verified in v1.10 Phase 54 (D-093) and again in v1.11 via the pipeline-driven lifecycle tests (P59–P62). 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. **22/22 auto-verifiable capabilities Verified** (CAP-013 fixed in v1.12 P67 — the adapter's multi-resource L1 dedup defect is closed). The v1.11 lifecycle pipeline ran apply→modify→destroy against live AWS and was then torn down to zero-cost (D-096). See `.ciagent/CAPABILITY_INVENTORY.md` and `.ciagent/PRE_MORTEM.md`.
|
||||
|
||||
Reference in New Issue
Block a user