diff --git a/docs/presentations/nova-leadership-deck-marp.md b/docs/presentations/nova-leadership-deck-marp.md
index 2af7634..92eebf9 100644
--- a/docs/presentations/nova-leadership-deck-marp.md
+++ b/docs/presentations/nova-leadership-deck-marp.md
@@ -14,6 +14,11 @@
   Vision grounding: [1] citations in slides 3, 5, 7 speaker notes
   resolve to docs/vision.md (the spec's acdl-vision.md reference).
 
+  Diagrams: 7 S&P-themed mermaid diagrams (D-246), one per slide,
+  rendered via scripts/render_leadership_diagrams.sh (mmdc + vendored
+  Chromium libs). Sources: assets/mmd/leadership-slide-N.mmd.
+  PNGs: assets/png/leadership-slide-N.png.
+
   Render: python3 scripts/render_pptx.py docs/presentations/nova-leadership-deck-marp.md \
           --output docs/presentations/nova-leadership-deck.pptx
   Smoke test: bash scripts/check_leadership_deck.sh
@@ -42,7 +47,10 @@ style: |
   @media print { section { overflow: hidden; } }
 ---
 
-## The friction every delivery team lives today
+<!-- _class: title -->
+<!-- _paginate: false -->
+
+# The friction every delivery team lives today
 
 > *Velocity is up; the coordination surface around each change is up faster.*
 
@@ -52,6 +60,8 @@ style: |
 
 > *Nova absorbs all three — owned building blocks, separation of concerns, attested compliance up front.*
 
+![diagram](assets/png/leadership-slide-1.png)
+
 <!--
 Three patterns drive the friction every delivery team lives today, and all three trace back to one binding constraint: software delivery scales with the coordination surface around it, not the engineering inside it [1]. That is the claim the vision document opens with, and it is the lens for everything Nova does.
 
@@ -70,13 +80,11 @@ Nova absorbs all three. Owned building blocks, separation of concerns, attested
 
 > *You already recognize this pattern.*
 
-Every Central IT team curates a golden image for Windows, for Linux, for macOS. They own it. They patch it. They ship it. Consumers consume it without thinking about what's inside.
+![diagram](assets/png/leadership-slide-2.png)
 
-Nova plays the same role one layer up — for everything that runs your cloud. S3 buckets with SSE-KMS posture. RDS instances with deletion protection and PITR. Lambda containers with static ABAC binaries. ALBs, ECS services, KMS keys, DynamoDB tables. Each one is owned by the platform team, patched by the platform team, attested by the platform team, and consumed by anyone who declares a contract.
+Central IT curates the golden image; Nova curates the cloud infrastructure. Owned, patched, attested, consumed by contract.
 
-The difference: every primitive is versioned, tested across its entire lifecycle, and bounded by policy before any consumer ever touches it.
-
-> *Nova's lane is the infrastructure beneath the application. AppSec, dependency review, and runtime application security stay where they have always been — with the application team.*
+> *Nova's lane is the infrastructure beneath the application. AppSec stays with the application team.*
 
 <!--
 The Central IT golden-image pattern is one every leadership team already recognizes. Central IT curates the Windows image, the Linux image, the macOS image. They own it, they patch it, they ship it, and consumers consume it without thinking about what is inside. That trade — per-application control for uniform operability — is a trade every enterprise has already made at the OS layer.
@@ -92,13 +100,13 @@ And the lane stays narrow. Nova's lane is the infrastructure beneath the applica
 
 ## Two principles that organize everything else
 
-> *The architecture is principled, not improvised. Two tenets discipline every other decision.*
+> *Two tenets discipline every other decision.*
 
-**Sovereign boundary.** Nova governs the delivery lifecycle; it does not reach upstream into product or software development [1]. Integration with SDLC and PDLC partners happens exclusively through the validated, published contract surface. What lives outside the contract is not Nova's domain.
+![diagram](assets/png/leadership-slide-3.png)
 
-**Lower autonomous · higher attested.** Lower environments proceed through agentic automation. Promotion to higher environments requires deliberate human attestation — not as a rubber stamp, but as policy-mandated accountability [1]. The compute the platform makes; the choice the human keeps.
+**Sovereign boundary** — Nova governs the delivery lifecycle; it does not reach upstream [1]. Integration with SDLC and PDLC happens exclusively through the contract surface.
 
-> *Everything else in the architecture inherits from these two.*
+**Lower autonomous · higher attested** — lower environments proceed through agentic automation; promotion requires deliberate human attestation [1]. The compute the platform makes; the choice the human keeps.
 
 <!--
 The architecture is principled, not improvised. Two tenets discipline every other decision the platform makes, and both come straight from the vision document [1].
@@ -114,14 +122,13 @@ And the point for this room: these two tenets are not aspirational. They are loa
 
 ## Live · Attested · Stays human
 
-**Live today**
-41 capabilities across 12 domains. Contract ingestor, audit outbox, state buckets, and the live pilot run have been operating in our AWS estate since v1.7; pilot evidence at v1.26 returned confidence 0.800. DORA + adoption + policy-conformance metrics flow to PowerBI from the same audit stream as the lineage. Every finding carries one owner, one patch state, one audit entry — one pane, no second source of truth. A POC is production-grade by construction: there is no "POC that became prod" surprise.
+![diagram](assets/png/leadership-slide-4.png)
 
-**Attested on promotion**
-qa, prod, and dr require a named human approver distinct from the PR author. Rubber stamps cannot be silently issued.
+**Live today** — 41 capabilities across 12 domains; pilot confidence 0.800. One pane, no second source of truth.
 
-**Stays human — by design**
-Confidence below the autonomy threshold at qa, prod, or dr triggers human escalation [1]. Some categories of decision are preserved for human judgment, and the platform says so out loud.
+**Attested on promotion** — qa, prod, dr require a named human approver distinct from the PR author.
+
+**Stays human — by design** — confidence below the autonomy threshold triggers human escalation [1].
 
 <!--
 Three columns, three claims, one disambiguation. The claims are real, observable, and disciplined — and the distinction matters for this room.
@@ -137,20 +144,13 @@ Disciplined: attested on promotion, stays human by design. qa, prod, and dr requ
 
 ## The boundary keeps us honest
 
-> *Nova stays where it belongs.*
+![diagram](assets/png/leadership-slide-5.png)
 
-**In Nova's lane**
-- → Infrastructure primitives: S3, RDS, Lambda, ECS, DynamoDB, KMS, CloudFront.
-- → Operational guardrails: confidence, policy, attestation, audit lineage.
-- → CVE response at the infrastructure layer.
+**In Nova's lane** — infrastructure primitives, operational guardrails, CVE response at the infra layer.
 
-**Outside Nova's lane**
-- → Application business logic.
-- → IDE, sprint, author workflows [1].
-- → Application-layer security: AppSec, dependency review, runtime threat modeling.
-- → VM, bare-metal, OS lifecycles [1].
+**Outside Nova's lane** — application business logic, IDE & sprint workflows [1], AppSec, VM/bare-metal/OS lifecycles [1].
 
-> *The line is the contract. Everything below the contract is Nova. Everything above it stays where it has always been.*
+> *The line is the contract. Everything below it is Nova. Everything above it stays where it has always been.*
 
 <!--
 The boundary is not a defensive posture. It is an operating principle — and it is the principle that keeps the architecture honest [1].
@@ -168,13 +168,12 @@ The line is the contract. Everything below the contract is Nova. Everything abov
 
 > *Where CDLC meets SDLC + PDLC — through the contract surface, not above it.*
 
-**α (now → Q4'26) — Operating model + federated governance.** A named platform-ops body owns the platform; SLAs on every L2 are ratifiable by platform + consumer. The operating model is published; integration surfaces for SDLC and PDLC harnesses are documented at the contract boundary.
+![diagram](assets/png/leadership-slide-6.png)
 
-**β (Q1'27) — Auto-published infra observability.** Every consumer stack ships with CloudWatch dashboards, uptime-kuma monitors, and alert routing on apply — infrastructure primitives publish observability as a property, no per-team authoring required.
-
-**γ (Q2'27) — Runbook generation from telemetry.** Every L1 primitive ships with an auto-generated incident runbook derived from observed patterns. SREs get a starting runbook, not a blank page.
-
-**δ (Q3'27 → Q4'27) — Audit ledger, tamper-resistant + externally addressable.** The SQLite hash-evidence stream migrates to S3 Object Lock + JWS signatures. External counsel verifies any production change back to a named human attestation.
+**α (now → Q4'26)** Operating model + federated governance.
+**β (Q1'27)** Auto-published infra observability.
+**γ (Q2'27)** Runbook generation from telemetry.
+**δ (Q3'27 → Q4'27)** Audit ledger, tamper-resistant.
 
 > *Nova absorbs no IDE, no editor, no sprint tool, no agent harness.*
 
@@ -196,23 +195,22 @@ Nova absorbs no IDE, no editor, no sprint tool, no agent harness. The contract s
 
 ## What we ask · What comes back
 
-**What we ask.**
-Architecture endorsement. Runway to the next milestone.
+![diagram](assets/png/leadership-slide-7.png)
 
-**Why now.**
-Agentic SDLC is reshaping the delivery curve. What is barely keepable today — incident response, compliance reconciliation, security remediation — does not compress at the same rate as the velocity it has to keep pace with. By the end of 2027, the gap between delivery acceleration and operational absorption is the structural risk.
+**What works now.** Deploying L1 & L2 stacks works today in the sandbox AWS account — 13 L1 primitives and 2 L2 modules, live-applied at confidence 0.800. Next steps: ingest greenfield pilot projects, promote from sandbox to production, integrate with the SPGE constitutional library, and serve as the infrastructure layer.
 
-**What comes back.**
-The infrastructure foundation that absorbs the velocity. Metrics that tell us where to push next. Audit lineage that closes the regulatory question. The next milestone, **by November 2026**.
+**What we ask.** Architecture endorsement. Runway to the next milestone.
+
+**Why now.** Agentic SDLC is reshaping the delivery curve. What is barely keepable today — incident response, compliance reconciliation, security remediation — does not compress at the same rate as the velocity it has to keep pace with. By the end of 2027, the gap between delivery acceleration and operational absorption is the structural risk.
+
+**What comes back.** The infrastructure foundation that absorbs the velocity. Metrics that tell us where to push next. Audit lineage that closes the regulatory question. The next milestone, **by November 2026**.
 
 > *What we do not ask for: an IDE, a sprint tool, an author workflow, an upstream pipeline. Nova stays in its lane [1].*
 
 <!--
-This is presented to Infrastructure and Operations leadership in August 2026. The ask is two things: architecture endorsement, and runway to the next milestone by November 2026.
+This is presented to Infrastructure and Operations leadership in August 2026. What works now: deploying L1 and L2 stacks works today. 13 L1 primitives and 2 L2 modules are live in the registry; the pilot ran a live terraform apply against the dev AWS account at v1.26 and returned confidence 0.800 — a measured number, not a forecast. We refer to the dev account colloquially as the sandbox. Next steps: ingest greenfield pilot projects (greenfield consumers with no legacy to reconcile), promote from sandbox to production (the promotion path with HITL gates exists; the pilot was dev-only, so activating qa, prod, dr is the next step), integrate with the SPGE constitutional library (an external governance system the audience recognizes; the platform meets it at the contract surface), and serve as the infrastructure layer.
 
-Why now. Agentic SDLC is reshaping the delivery curve. The velocity is up, and it is going to keep going up. What is barely keepable today — incident response, compliance reconciliation, security remediation — does not compress at the same rate as the velocity it has to keep pace with. The operational absorption side of the curve is steeper than the delivery acceleration side, and the gap between them is the structural risk. By the end of 2027, that gap is the thing that breaks cadence. Internal directional target: a 60% reduction in the operational absorption gap is the goal we are holding ourselves to — not a sourced claim, a directional target, and the metrics the platform already produces will tell us whether we are closing it.
+The ask is architecture endorsement and runway to the next milestone by November 2026. Why now: agentic SDLC is reshaping the delivery curve. What is barely keepable today — incident response, compliance reconciliation, security remediation — does not compress at the same rate as the velocity. By end of 2027, the gap between delivery acceleration and operational absorption is the structural risk. Internal directional target: a 60% reduction in that gap — not a sourced claim, a directional target the platform's metrics will track.
 
-What comes back. The infrastructure foundation that absorbs the velocity. Metrics that tell us where to push next. Audit lineage that closes the regulatory question. And the next milestone, by November 2026. That is the runway ask: not a budget, not a headcount, not a re-org. Runway to land the architecture endorsement and demonstrate the next milestone.
-
-What we do not ask for: an IDE, a sprint tool, an author workflow, an upstream pipeline. Nova stays in its lane [1]. The sovereign boundary is the discipline that makes the ask small and the return large. Use the runway to land the architecture endorsement.
+What comes back: the infrastructure foundation that absorbs the velocity, metrics that tell us where to push next, audit lineage that closes the regulatory question, and the next milestone by November 2026. Not a budget, not a headcount — runway to land the architecture endorsement. What we do not ask for: an IDE, a sprint tool, an author workflow, an upstream pipeline. Nova stays in its lane [1]. The sovereign boundary makes the ask small and the return large.
 -->
\ No newline at end of file