docs(init): validate specification — REQ-372 leadership deck (v1.30)

---ci---
project: acdl
phase: 0
milestone: v1.30
status: specify
---/ci---
This commit is contained in:
CIAgent
2026-08-20 13:14:14 +00:00
parent adf3b1c02f
commit 65bf3d84e9
3 changed files with 543 additions and 6 deletions
+184 -1
View File
@@ -853,4 +853,187 @@ M1/M1.5/M2 cutover gates documented in the operator guide.
> gates in `nova-platform-ops` CI (out-of-band). The operator attests
> the results in `docs/operator-guide-platform-ops.md` §18 "Cutover
> Gates" Result column. P6 audit verifies the template + Result column
> exist; the live-green attestation is out-of-band (grill CF-1/CF-2).
> exist; the live-green attestation is out-of-band (grill CF-1/CF-2).
## v1.30 — Single-shot Leadership Deck (active milestone)
> **Feature milestone — single-shot PPTX leadership deck.** Ships
> REQ-372.1 through REQ-372.12 in one execution phase. Tags run on the
> **v1.29.x** line (milestone v1.30 → tags v1.29.1..v1.29.3). Tag
> `v1.29.3` = the milestone release. The deck is a discrete artifact,
> hand-authored (NOT a compression of the existing citizen-developer
> pitch per D-241), scoped to a single live presentation to
> Infrastructure & Operations leadership in August 2026, securing
> architecture endorsement and a November 2026 runway.
>
> Source: `docs/presentations/nova-leadership-deck-marp.md` (authored
> against the Slide Content Map in `.ciagent/PROJECT.md` §v1.30 spec).
> Rendered via the existing `scripts/render_pptx.py` (narrowly extended
> per D-242 to accept an explicit source path + custom output filename
> and to add a per-slide footer textbox). Smoke test:
> `scripts/check_leadership_deck.sh` (runnable on demand; NOT a CI gate
> per the single-shot constraint). Vision grounding `[1]` citations
> resolve to `docs/vision.md` (the spec's `acdl-vision.md` reference).
### Decisions (locked in CLARIFY, full autonomy — load-bearing for v1.30)
- **D-241 (Q3 override):** The leadership deck is a **discrete,
hand-authored artifact** — NOT a compression of the existing
23-slide citizen-developer pitch
(`nova-autonomous-cloud-delivery-marp.md`). This overrides the
post-v1.29 STATE.md intake assumption 3 ("is a compression, not a
rewrite"). The existing citizen-developer deck remains untouched.
Rationale: the spec §2.2 + cover note forbid compression/mirroring;
the Slide Content Map is hand-authored content, not derived.
- **D-242 (render pipeline):** The existing `scripts/render_pptx.py`
is narrowly extended to (a) accept an explicit source `.md` path +
custom output `.pptx` filename (the cover note's invocation
`scripts/render_pptx.py docs/presentations/nova-leadership-deck.md`
is honoured via a path-aware argv), and (b) render a right-aligned
footer textbox on every slide with the exact string
`Nova Platform - Infrastructure & Operations` (the python-pptx
renderer does not read the Marp `footer:` directive; REQ-372.5
requires the footer on every rendered slide). This extension is a
non-REQ-372 prerequisite per spec §3.3 Edge 2 ("scope narrowly and
update `render_pptx.py` separately"). The source file is authored as
`nova-leadership-deck-marp.md` to fit the existing `-marp.md`
pipeline convention; the output is `nova-leadership-deck.pptx` per
spec REQ-372.2.
- **D-243 (date anchor):** August 2026 is a month-only presentation
anchor (no specific day); November 2026 is the runway anchor
(~90 days). Slide 7 references "Infrastructure & Operations
leadership" without naming a specific day. Resolves spec §7 Q1.
### Requirements
#### REQ-372.1 — Source markdown exists and is parseable
**Priority:** High · **Journey:** J1
**Given** the deck initiative is scoped, **when**
`docs/presentations/nova-leadership-deck-marp.md` is read, **then** the
file exists, parses as valid Marp markdown, contains exactly 7 slides
delimited by `---`, and the file header carries the related-artifacts
comment (per REQ-372.9).
#### REQ-372.2 — PPTX render via existing pipeline
**Priority:** High · **Journey:** J1
**Given** the source markdown exists (REQ-372.1), **when**
`scripts/render_pptx.py` is invoked against the leadership deck source,
**then** `docs/presentations/nova-leadership-deck.pptx` is written with
7 slides and python-pptx raised no exceptions.
#### REQ-372.3 — Slide count is exactly 7
**Priority:** High · **Journey:** J1
**Given** the source markdown, **when** slide boundaries are counted,
**then** the count equals 7.
#### REQ-372.4 — Speaker notes depth per slide
**Priority:** High · **Journey:** J1
**Given** the source markdown, **when** speaker notes (HTML comments)
are extracted per slide, **then** per-slide word counts fall within:
slides 1/2/4/6 in 150300; slides 3/5 in 250400; slide 7 in 200300.
Smoke test exits non-zero on violation.
#### REQ-372.5 — Footer on every slide
**Priority:** High · **Journey:** J1
**Given** the source markdown's Marp frontmatter `footer:` directive +
the python-pptx renderer extension (D-242), **when** the PPTX is
rendered, **then** every slide carries the right-aligned footer
`Nova Platform - Infrastructure & Operations`.
#### REQ-372.6 — S&P theme tokens are the only colors used
**Priority:** High · **Journey:** J1
**Given** the source markdown, **when** color values are extracted
(Marp directives + inline overrides), **then** the only hex colors
present are `#D6002A`, `#1B1B1B`, `#FFFFFF`, `#F0F0F0`.
#### REQ-372.7 — Slide-by-slide content traceability
**Priority:** High · **Journey:** J1
**Given** the rendered PPTX, **when** any slide N ∈ [1, 7] is opened,
**then** its content matches the **Slide Content Map** in
`.ciagent/PROJECT.md` §v1.30 spec. Any deviation from the map requires
`CLARIFY` before ship. Smoke test does not assert content strings
verbatim (brittle); audit verifies by visual review against the map.
#### REQ-372.8 — Smoke test exits 0 on pass
**Priority:** High · **Journey:** J1
**Given** `scripts/check_leadership_deck.sh` exists, **when** invoked
from the repo root, **then** the script asserts: (a) source file
exists, (b) slide count = 7, (c) per-slide word counts in band, (d)
footer string present in source, (e) only S&P hex colors used, (f)
PPTX file exists. Exits 0 on pass, non-zero on fail. Runnable on
demand; not wired as a CI gate.
#### REQ-372.9 — Related-artifacts comment in source header
**Priority:** Med · **Journey:** J1
**Given** the source markdown, **when** the file header is inspected,
**then** a comment exists that (i) names this deck as the leadership
artifact for Infrastructure & Operations, (ii) names August 2026 as
the presentation date, (iii) names
`nova-autonomous-cloud-delivery-marp.md` as a related-but-distinct
artifact and notes that this deck does not compress or modify it.
#### REQ-372.10 — CAP-042 appended to STATE.md at ship
**Priority:** Med · **Journey:** J1
**Given** the deck has shipped, **when** STATE.md is updated at the
v1.30 milestone ship wave, **then** a CAP-042 row exists capturing
artifact paths (`nova-leadership-deck-marp.md`,
`nova-leadership-deck.pptx`), audience (Infrastructure & Operations
leadership), single-shot intent, presentation month (August 2026).
#### REQ-372.11 — D-241 recorded in PROJECT.md at ship
**Priority:** Med · **Journey:** J1
**Given** the deck has shipped, **when** PROJECT.md is updated at the
v1.30 milestone ship wave, **then** a `D-241` entry exists capturing:
(a) single-shot nature of the deck, (b) audience (Infrastructure &
Operations leadership), (c) August 2026 anchor + November 2026 runway,
(d) explicit decision not to compress the existing citizen-developer
deck.
#### REQ-372.12 — Vision grounding citations in architecture-load slides
**Priority:** Med · **Journey:** J1
**Given** the source markdown, **when** the speaker notes are
inspected, **then** at least one `[1]` citation appears in slides 3,
5, and 7 — the three architecture-load slides — grounding the
principles, anti-goals, and integration-boundary claims to
`docs/vision.md` (the spec's `acdl-vision.md` reference [1]).
### v1.30 Traceability (live — see CHECKPOINT.json for authoritative state)
| REQ | Phase | Status |
|-----|-------|--------|
| REQ-372.1 | P1 | planned |
| REQ-372.2 | P1 | planned |
| REQ-372.3 | P1 | planned |
| REQ-372.4 | P1 | planned |
| REQ-372.5 | P1 | planned |
| REQ-372.6 | P1 | planned |
| REQ-372.7 | P1 | planned (visual review) |
| REQ-372.8 | P1 | planned |
| REQ-372.9 | P1 | planned |
| REQ-372.10 | P1 | planned |
| REQ-372.11 | P1 | planned |
| REQ-372.12 | P1 | planned |