diff --git a/.ciagent/PROJECT.md b/.ciagent/PROJECT.md
index 07c5df4..204182d 100644
--- a/.ciagent/PROJECT.md
+++ b/.ciagent/PROJECT.md
@@ -58,6 +58,103 @@ traceable to a human attestation and an immutable evidence stream.
boundary. The platform validates, enriches with operational standards,
and reconciles the target state.
+## Scope: Nova is Downstream of PDLC
+
+> **Promoted from Core Tenet #2 + Anti-Goal #1 (v1.18, REQ-216).** This
+> is the unmissable scope statement — the PDLC is upstream, Nova is
+> downstream.
+
+The **Product Development Lifecycle (PDLC)** — product backlog, code
+authorship, IDE workflows, sprint planning, application business logic —
+is **upstream** of Nova. Nova never penetrates the PDLC. Nova's domain is
+**infrastructure + delivery only**: environment progression, cloud
+resource lifecycle, operational security/observability NFRs, policy
+enforcement, immutable audit lineage, and the two consumer surfaces
+(technical developer + agentic).
+
+Integration between the PDLC and Nova is **only** through the validated,
+published contract boundary (`schemas/contract.schema.json` +
+`schemas/submission-readiness.schema.json`). The citizen developer's AI
+coding agent, an upstream agentic SDLC platform, or any upstream
+development platform may all produce submissions — the source does not
+matter because all are subject to the same compliance standards (the
+submission-readiness gate, D-133). Nova validates, enriches with
+operational standards, and reconciles the target state. Nova never
+authors application code, manages product backlogs, or provides IDE
+workflows.
+
+```
+PDLC (upstream) Nova (downstream)
+───────────────── ─────────────────
+product backlog contract ingestion
+code authorship (AI agent / IDE / SDLC) → submission-readiness gate
+sprint planning → policy enforcement
+application business logic → cloud resource lifecycle
+ → environment progression (dev→qa→prod→dr)
+ → immutable audit + attestation
+```
+
+## RACI Matrix
+
+> **Source of truth (v1.18, REQ-215, D-139).** Three roles clarify who
+> owns what across the Nova delivery lifecycle. The matrix is the
+> authoritative version; `docs/raci.md` is the citizen-developer-facing
+> copy.
+
+### Roles
+
+- **Citizen Developer (CD)** — the consumer (technical developer L3A or
+ non-technical L3B). Responsible for all **Functional Requirements (FRs)**
+ and **User Acceptance Testing (UAT)**. The FRs + UAT are produced via
+ the citizen developer's AI coding agent, an upstream agentic SDLC, or
+ an upstream development platform — **the source does not matter as all
+ are subject to the same compliance standards** (the submission-readiness
+ gate, D-133).
+- **Platform** — Nova. Responsible for all **Non-Functional Requirements
+ (NFRs)**, **Infrastructure** (cloud resource lifecycle, state, IAM),
+ **QA** (the platform-side quality checks: policy, confidence, schema),
+ and **Production deployments to cloud** (the apply path, the pipeline,
+ the release).
+- **Release Management (RM)** — **co-owned**. QA + SRE attestations are
+ required by the actual release. The attestations are performed
+ agentically (the platform runs the checks), but the release is
+ **overseen and triggered by the Citizen Developer** — the human
+ attestation at the stage gate (D-042, hitl_gates.py). The platform
+ performs; the citizen developer authorizes.
+
+### Matrix
+
+| Work Category | Citizen Developer | Platform | Release Management |
+|---|---|---|---|
+| **Functional Requirements (FRs)** | **R/A** | C | I |
+| **User Acceptance Testing (UAT)** | **R/A** | C | I |
+| **Non-Functional Requirements (NFRs)** | I | **R/A** | C |
+| **Infrastructure (cloud, state, IAM)** | I | **R/A** | C |
+| **QA (policy, confidence, schema checks)** | C | **R/A** | I |
+| **Production deployment to cloud** | I | **R/A** | C |
+| **Release attestation (QA + SRE sign-off)** | **A** | R | **R** |
+
+**Key: R** = Responsible (does the work) · **A** = Accountable (owns the
+outcome, sign-off) · **C** = Consulted · **I** = Informed.
+
+**Compliance-standard equivalence note:** the citizen developer's FRs +
+UAT may originate from any upstream source — an AI coding agent, an
+agentic SDLC platform, or a traditional development platform. All are
+subject to the same compliance standards: the submission-readiness gate
+(`schemas/submission-readiness.schema.json`), the contract schema, the
+policy envelope, and the immutable audit stream. The platform does not
+differentiate by upstream source; it validates the submission, not the
+author.
+
+**Co-ownership of Release Management:** the release is co-owned. The
+platform performs the QA + SRE attestations agentically (confidence signal,
+policy checks, separation-of-duties). The citizen developer oversees and
+triggers the actual release — the human attestation at the stage gate is
+the citizen developer's authorization, recorded with approver identity
+(D-042). The platform runs the checks; the citizen developer authorizes
+the promotion. This is the "autonomy in operations, human at stage gates"
+model from the NORTH_STAR.
+
## Capability Status (Re-Verified 2026-07-27)
> Source of truth: `.ciagent/CAPABILITY_INVENTORY.md` (Phase 54, D-093).
diff --git a/docs/presentations/nova-no-humans-platform-marp.md b/docs/presentations/nova-no-humans-platform-marp.md
index 458d540..f43994f 100644
--- a/docs/presentations/nova-no-humans-platform-marp.md
+++ b/docs/presentations/nova-no-humans-platform-marp.md
@@ -34,7 +34,7 @@ style: |
**Shifting from Operational Overhead to Strategic Value**
-v1.17 — Strategic Direction, Leadership Metrics & Unified Story
+v1.18 — Citizen Developer & Production-Grade Guidance
---
@@ -49,7 +49,7 @@ v1.17 — Strategic Direction, Leadership Metrics & Unified Story
2. **Vision** — Nova's strategic direction (NORTH_STAR)
3. **How** — the pipeline, Decision Ledger, attestation gates
4. **Proof** — grounded metrics that make the claim defensible
-5. **Roadmap** — deferred metrics with unblock paths + the ask
+5. **Roadmap** — deferred metrics with unblock paths + the ask + scope + RACI
**Benefit:** you leave knowing which claims are proven today, which are pipeline-ready, and which are deferred with a documented unblock path — no marketing, just grounded evidence.
@@ -301,6 +301,42 @@ From `docs/METRICS_DEFERRED_ROADMAP.md`.
---
+## Slide 17 — Scope: Downstream of PDLC
+
+**Nova governs infrastructure + delivery. The PDLC (product backlog, code authorship, IDE) is upstream — Nova never penetrates it.**
+
+- **The PDLC is upstream:** product backlog, code authorship (AI agent / IDE / agentic SDLC), sprint planning, application business logic
+- **Nova is downstream:** contract ingestion → submission-readiness gate → policy → cloud lifecycle → environment progression → audit + attestation
+- **Integration is only through the contract boundary:** the citizen developer's AI coding agent, an upstream agentic SDLC, or any dev platform may all produce submissions — the source does not matter as all are subject to the same compliance standards
+- Nova validates the submission, not the author
+- Cites `docs/scope.md` + `PROJECT.md` § Scope
+
+**Benefit:** you now know the scope boundary — Nova is purpose-built for infrastructure operations, not product development; integration is through one validated contract.
+
+---
+
+## Slide 18 — RACI: Who Owns What
+
+**Three roles, one matrix — the citizen developer owns FRs + UAT, the platform owns NFRs + infra + QA + prod deploy, release management is co-owned.**
+
+| Work Category | Citizen Dev | Platform | Release Mgmt |
+|---|---|---|---|
+| Functional Requirements (FRs) | **R/A** | C | I |
+| User Acceptance Testing (UAT) | **R/A** | C | I |
+| Non-Functional Requirements (NFRs) | I | **R/A** | C |
+| Infrastructure (cloud, state, IAM) | I | **R/A** | C |
+| QA (policy, confidence, schema) | C | **R/A** | I |
+| Production deployment to cloud | I | **R/A** | C |
+| Release attestation (QA + SRE) | **A** | R | **R** |
+
+- **Compliance-standard equivalence:** FRs + UAT may come from any upstream source (AI agent, agentic SDLC, dev platform) — all pass the same submission-readiness gate
+- **Release co-ownership:** the platform runs the attestations agentically; the citizen developer oversees and triggers the actual release (human at the stage gate)
+- Cites `docs/raci.md` + `PROJECT.md` § RACI Matrix
+
+**Benefit:** you now know exactly what you bring (FRs + UAT), what Nova provides (NFRs + infra + QA + prod deploy), and what you co-own (the release attestation).
+
+---
+
diff --git a/docs/presentations/nova-no-humans-platform-talking-points.md b/docs/presentations/nova-no-humans-platform-talking-points.md
index 6c35dbd..b273d10 100644
--- a/docs/presentations/nova-no-humans-platform-talking-points.md
+++ b/docs/presentations/nova-no-humans-platform-talking-points.md
@@ -103,6 +103,20 @@
- "Pipeline-ready" → "production-proven" is the value proposition
- **Key takeaway:** approve a pilot + the ledger build-out to move from pipeline-ready to production-proven
+### Slide 17 — Scope: Downstream of PDLC
+- Nova governs infra + delivery only; the PDLC (product backlog, code authorship, IDE) is upstream
+- Integration is only through the validated contract boundary
+- Any upstream source (AI agent, agentic SDLC, dev platform) may produce submissions — all subject to the same compliance standards
+- Nova validates the submission, not the author
+- **Key takeaway:** Nova is purpose-built for infrastructure operations, not product development; the scope boundary is clean
+
+### Slide 18 — RACI: Who Owns What
+- Citizen Developer owns FRs + UAT (via any upstream source — AI agent, SDLC, dev platform — all pass the same gate)
+- Platform owns NFRs + infra + QA + prod deploy
+- Release Management is co-owned: platform runs attestations agentically, citizen developer oversees + triggers the release (human at stage gate)
+- The compliance-standard equivalence is the key: the source does not matter; the submission does
+- **Key takeaway:** you bring FRs + UAT; Nova provides NFRs + infra + QA + prod deploy; the release is co-owned with you at the stage gate
+
### Appendix A1 — Metrics Glossary
- Reference for every metric mentioned in the deck
- Use if the audience asks "what does X mean?"
diff --git a/docs/presentations/nova-no-humans-platform.html b/docs/presentations/nova-no-humans-platform.html
index f3dfa5c..94c6501 100644
--- a/docs/presentations/nova-no-humans-platform.html
+++ b/docs/presentations/nova-no-humans-platform.html
@@ -51,7 +51,7 @@ img { display: block; margin: 0 auto; max-height: 320px; }
Nova — The No-Humans Infrastructure Platform
Shifting from Operational Overhead to Strategic Value
-
v1.17 — Strategic Direction, Leadership Metrics & Unified Story