docs(P03): clarify — D-244 (cover), D-245 (slide 7 content), D-246 (mermaid diagrams)
---ci--- project: acdl phase: 3 milestone: v1.30 status: clarify decisions: [D-244, D-245, D-246] ---/ci---
This commit is contained in:
CIAgent
+12
-22
@@ -1,37 +1,27 @@
|
||||
{
|
||||
"phase": 2,
|
||||
"stage": "complete",
|
||||
"phase": 3,
|
||||
"stage": "clarify",
|
||||
"milestone": "v1.30",
|
||||
"phase_role": "final",
|
||||
"phase_role": "execution",
|
||||
"attempts": 0,
|
||||
"updated_at": "2026-08-20T14:40:00Z",
|
||||
"updated_at": "2026-08-20T15:00:00Z",
|
||||
"project": "acdl",
|
||||
"projects": ["acdl", "nova-blockchain-exchange"],
|
||||
"active_milestone": "v1.30",
|
||||
"milestone_branch": null,
|
||||
"phase_branch": null,
|
||||
"milestone_branch": "milestone/v1.30-leadership-deck",
|
||||
"phase_branch": "phase/03-deck-polish",
|
||||
"tag_line": "v1.29.x",
|
||||
"phase_name": "final-review-ship",
|
||||
"phase_name": "deck-polish",
|
||||
"milestone_type": "feature",
|
||||
"reqs_covered": ["REQ-372.1","REQ-372.2","REQ-372.3","REQ-372.4","REQ-372.5","REQ-372.6","REQ-372.7","REQ-372.8","REQ-372.9","REQ-372.10","REQ-372.11","REQ-372.12"],
|
||||
"reqs_partial": [],
|
||||
"previous_milestone": {
|
||||
"milestone": "v1.30",
|
||||
"tag": "v1.29.3",
|
||||
"milestone": "v1.29",
|
||||
"tag": "v1.28.6",
|
||||
"complete": true,
|
||||
"merged_to_main": "96765fe",
|
||||
"merged_to_main": "9dc5669",
|
||||
"branches_deleted": true,
|
||||
"releases_created": true,
|
||||
"release_ids": [811, 812, 813]
|
||||
"releases_created": true
|
||||
},
|
||||
"ship": {
|
||||
"tag": "v1.29.3",
|
||||
"release_id": 813,
|
||||
"release_url": "https://git.cloudinit.dev/continuous-intelligence/acdl/releases/tag/v1.29.3",
|
||||
"merged_to_main": true,
|
||||
"merge_commit": "96765fe",
|
||||
"branches_deleted": ["phase/02-final-review-ship", "milestone/v1.30-leadership-deck"],
|
||||
"local_only": false
|
||||
},
|
||||
"notes": "v1.30 MILESTONE COMPLETE. Tag v1.29.3 (milestone release), Gitea release id=813. Merged to main 96765fe. All milestone branches deleted (local + remote). REQ-372.1..12 all complete. CAP-042 + D-241..D-243 recorded. 3 Gitea releases: 811 (P0 v1.29.1), 812 (P1 v1.29.2), 813 (P2 v1.29.3). Checkpoint cleared — next run starts a new milestone."
|
||||
"notes": "v1.30 P3 (deck-polish) CLARIFY complete. D-244 (cover slide, overrides G-1), D-245 (slide 7 what-works-now content + SPGE external + sandbox colloquial), D-246 (7 mermaid diagrams, vendored Chromium libs). Local mmdc render verified. Next: EXECUTE (W1 renderer polish, W2 diagrams, W3 source, W4 render+verify)."
|
||||
}
|
||||
+113
-3
@@ -206,8 +206,118 @@ at the v1.30 ship wave (CAP-042 row + intake assumption correction).
|
||||
|
||||
---
|
||||
|
||||
## Polish-phase decisions (D-244, D-245, D-246 — full autonomy)
|
||||
|
||||
The first draft (v1.29.3) passed all 12 REQs but the rendered PPTX
|
||||
has 7 polish issues (vertical imbalance, text clipping, double bullet
|
||||
markers, no visual variety, near-invisible footer, slide-6 red wall,
|
||||
blockquote grey). The user requested: (1) polish all 7 issues, (2)
|
||||
add a "What works now" emphasis to slide 7, (3) generate mermaid
|
||||
diagrams for every slide. These decisions record the deviations from
|
||||
prior binding decisions.
|
||||
|
||||
### D-244 — Slide 1 becomes a black-background cover (overrides grill G-1)
|
||||
|
||||
**Polish issue #4.** Grill G-1 locked "all 7 slides as white content
|
||||
slides." The user approved making slide 1 a black-background cover
|
||||
(strong opener for a live leadership presentation) while keeping
|
||||
slides 2-7 as white content slides. The on-slide body text from the
|
||||
Slide Content Map is preserved verbatim — only the visual treatment
|
||||
(background + text color) changes. REQ-372.7's "deviation requires
|
||||
CLARIFY" clause applies to *content* deviations; this is a
|
||||
presentation polish, not a content change. The source change: slide
|
||||
1's `## The friction...` → `# The friction...` (H1) + `<!-- _class:
|
||||
title -->` directive, which triggers `render_title_slide` (black bg,
|
||||
red top bar, white text).
|
||||
**Confidence:** 1.0 (user-confirmed).
|
||||
|
||||
### D-245 — Slide 7 "What works now" content addition (deviation from Slide Content Map)
|
||||
|
||||
**User request.** A new "What works now" block is added to slide 7's
|
||||
on-slide body, before the existing "What we ask" block. This is a
|
||||
*content* deviation — the Slide Content Map specifies slide 7 as:
|
||||
What we ask / Why now / What comes back + closer. The new block
|
||||
emphasizes what's proven today (L1/L2 stack deployment works, live
|
||||
apply to the sandbox/dev AWS account, confidence 0.800) and the
|
||||
next-steps arc (ingest greenfield pilot projects → promote from
|
||||
sandbox to production → integrate with the SPGE constitutional
|
||||
library → serve as the infrastructure layer).
|
||||
|
||||
**Factual grounding (verified in RESEARCH):**
|
||||
- 13 L1 primitives + 2 L2 modules in `modules/registry.json` (all at
|
||||
`1.0.0`): alb, cloudfront, dynamodb, ecr, ecs-cluster, ecs-service,
|
||||
iam-role, kms-key, rds, s3, uptime, vpc, waf + microservice, static-
|
||||
assets.
|
||||
- CAP-031: live `terraform apply` against AWS account `581513795199`
|
||||
(the dev environment, `mode: full`, dev-only per D-209), producing
|
||||
real ARNs (ALB, ECS, DynamoDB, S3, KMS) at confidence 0.800. This is
|
||||
a **live AWS apply**, NOT "tested locally" and NOT a "sandbox"
|
||||
account (the codebase has no sandbox account; the pilot-readiness
|
||||
policy D-208 blocks placeholder accounts).
|
||||
|
||||
**"sandbox" colloquial term note:** The user explicitly chose to keep
|
||||
"sandbox" as a colloquial term for the dev AWS account after I flagged
|
||||
that the codebase fact is "dev account `581513795199`, live apply."
|
||||
The slide uses "sandbox" (colloquial); the speaker notes carry the
|
||||
precise facts (dev account, live apply, confidence 0.800).
|
||||
|
||||
**"SPGE constitutional library" unverified-in-repo note:** "SPGE"
|
||||
and "constitutional library" appear nowhere in the codebase (0
|
||||
matches across all `.md`/`.py`/`.json`/`.yml`). The user confirmed it
|
||||
is an external system the audience recognizes. The slide includes it
|
||||
as a named next-step integration target, not as a current capability.
|
||||
The speaker notes do not assert it exists in the codebase.
|
||||
|
||||
The Slide Content Map in PROJECT.md is updated to reflect the new
|
||||
slide 7 structure.
|
||||
**Confidence:** 0.90.
|
||||
|
||||
### D-246 — Mermaid diagrams on all 7 slides
|
||||
|
||||
**User request.** Each of the 7 slides gets a leader-friendly,
|
||||
non-technical mermaid diagram covering its core concept. Different
|
||||
mermaid shapes per slide for visual variety.
|
||||
|
||||
**Render path (verified):** The local `mmdc` (mermaid-cli) is blocked
|
||||
by missing Chromium shared libraries (10+ system libs absent, no
|
||||
root). Resolution: 24 Debian bookworm `.deb` packages fetched from the
|
||||
Debian mirror, `.so` files extracted to `/home/opencode/tmp/so2/`,
|
||||
`LD_LIBRARY_PATH` set to include them. Chromium (puppeteer cache at
|
||||
`/home/opencode/.cache/puppeteer/chrome/.../chrome`) launches with
|
||||
the vendored libs; `mmdc` renders with the S&P theme (`sp-theme.json`)
|
||||
+ 2x scale + transparent background. Verified: test diagram renders
|
||||
to a valid PNG with all 4 S&P colors present. The `.mmd` source files
|
||||
+ rendered PNGs are committed for reproducibility; a future
|
||||
environment with system Chromium can re-render via the existing
|
||||
`scripts/render_slides.sh` mermaid step.
|
||||
|
||||
**Theme:** Inline `%%{init: {...}}%%` directive in each `.mmd` with
|
||||
S&P theme variables (`primaryColor:#1B1B1B`, `primaryBorderColor:
|
||||
#D6002A`, `primaryTextColor:#fff`, `secondaryColor:#fff`,
|
||||
`tertiaryColor:#F0F0F0`, `lineColor:#1B1B1B`) — only the 4 S&P tokens.
|
||||
Transparent background. No component names, no technical jargon —
|
||||
concepts only (leader-friendly).
|
||||
|
||||
**Diagram-type-per-slide mapping:**
|
||||
1. flowchart LR — 3 frictions → Nova absorbs them
|
||||
2. flowchart TB — Central IT golden image → Nova one layer up
|
||||
3. flowchart LR with subgraphs — two principles → everything inherits
|
||||
4. flowchart LR (3 columns) — Live · Attested · Stays human
|
||||
5. flowchart LR (two halves) — In Nova's lane / Outside Nova's lane
|
||||
6. timeline — the 18-month shape (α→β→γ→δ)
|
||||
7. flowchart LR — what works now → next steps arc
|
||||
|
||||
The Slide Content Map in PROJECT.md is updated to include a "Diagram"
|
||||
field per slide.
|
||||
**Confidence:** 0.88.
|
||||
|
||||
---
|
||||
|
||||
## Requirements impact
|
||||
|
||||
No requirements are added, removed, or re-scoped by these decisions.
|
||||
D-241–D-243 are load-bearing context for executing REQ-372.1–.12 as
|
||||
written. The spec is locked (v1.0, 2026-08-20); no spec text changes.
|
||||
No requirements are added, removed, or re-scoped by D-241–D-243.
|
||||
D-244–D-246 are polish-phase decisions that record deviations from
|
||||
prior binding decisions (G-1) and the Slide Content Map (slide 7).
|
||||
The spec is locked (v1.0, 2026-08-20); no spec text changes. The
|
||||
Slide Content Map in PROJECT.md is updated to reflect D-245 (slide 7
|
||||
structure) and D-246 (diagram field per slide).
|
||||
Reference in New Issue
Block a user