diff --git a/docs/presentations/assets/nova-sp-theme.css b/docs/presentations/assets/nova-sp-theme.css index 8434bf9..b268b48 100644 --- a/docs/presentations/assets/nova-sp-theme.css +++ b/docs/presentations/assets/nova-sp-theme.css @@ -1,3 +1,8 @@ +/* RETAINED AS REFERENCE ONLY — not loaded at render time. + * The live deck uses Marp `default` theme + an inline `style:` block in + * the -marp.md frontmatter. This file is kept for future styling work + * reference. Do NOT pass via `--theme`; it is not in the render path. + */ /* @theme nova-sp */ /* Nova — S&P Global Energy theme for Marp decks. * diff --git a/docs/presentations/nova-autonomous-cloud-delivery-marp.md b/docs/presentations/nova-autonomous-cloud-delivery-marp.md index 2c92531..74ef110 100644 --- a/docs/presentations/nova-autonomous-cloud-delivery-marp.md +++ b/docs/presentations/nova-autonomous-cloud-delivery-marp.md @@ -1,9 +1,29 @@ --- marp: true -theme: nova-sp +theme: default paginate: true size: 16x9 footer: 'Nova — The Autonomous Cloud Delivery Platform' +style: | + section { font-family: "Akkurat Pro", "Helvetica Neue", "Arial", sans-serif; font-size: 22px; color: #1B1B1B; padding: 48px 56px 40px; overflow: auto; } + h1 { color: #D6002A; font-size: 34px; margin-bottom: 0.3em; } + h2 { color: #D6002A; font-size: 26px; margin-bottom: 0.2em; } + h3 { color: #D6002A; font-size: 22px; margin-bottom: 0.2em; } + section.title { background: #1B1B1B; color: #fff; border-top: 8px solid #D6002A; } + section.title h1, section.title h2 { color: #fff; } + section.title header, section.title footer { display: none; } + table { font-size: 18px; width: 100%; border-collapse: collapse; } + th { background: #F0F0F0; border-bottom: 2px solid #D6002A; padding: 4px 8px; text-align: left; } + td { border-bottom: 1px solid #F0F0F0; padding: 4px 8px; } + blockquote { border-left: 4px solid #D6002A; color: #2E2E2E; font-size: 20px; padding-left: 12px; } + pre { background: #1B1B1B; color: #fff; border-radius: 4px; padding: 12px; font-size: 16px; } + code { background: #F0F0F0; color: #1B1B1B; border-radius: 2px; padding: 1px 4px; font-size: 18px; } + pre code { background: transparent; color: inherit; } + img { display: block; margin: 0 auto; max-width: 100%; max-height: 380px; object-fit: contain; } + strong { color: #D6002A; } + .benefit { margin-top: 0.6em; padding-top: 0.4em; border-top: 1px solid #D6002A; color: #1B1B1B; font-size: 20px; font-style: italic; } + section.title .benefit { color: #fff; } + @media print { section { overflow: hidden; } } --- @@ -28,7 +48,7 @@ Product Development & Citizen Developer Overview Every hour a developer spends writing, deploying, fixing, or remediating infrastructure is an hour not spent releasing features to production. -**Benefit:** the answer is an autonomous cloud delivery platform that encodes discipline as policy, scans proactively, remediates rapidly, and makes operations visible to leadership rather than hidden in tribal knowledge. +
the answer is an autonomous cloud delivery platform that encodes discipline as policy, scans proactively, remediates rapidly, and makes operations visible to leadership rather than hidden in tribal knowledge.
@@ -44,7 +64,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast - **Provable, not promised** — trust established by deterministic scripts that calculate a score; the platform functions without AI - **Autonomy in operations, human at stage gates** — QA signs off for production; SRE greenlights operational readiness -**Benefit:** the destination is autonomous operations with provable trust — security, remediation velocity, reliability, and lead time made visible to leadership, not promised to them. +
the destination is autonomous operations with provable trust — security, remediation velocity, reliability, and lead time made visible to leadership, not promised to them.
@@ -61,7 +81,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast - **Lead Time** (PR → Production) · **Infrastructure Vulnerability Count** (trend) · **MTTR** · **Cloud Spend Reduction** 4. **Integrate with externally owned development platforms — regardless of source** — PDLC, SDLC, Agentic, or Citizen Developer; Nova provides skills + MCP endpoints; all prod intents go through the same controls and quality gates -**Benefit:** the scope is explicit — Nova governs infrastructure and delivery, integrates with any upstream source through one validated contract, and measures success on four metrics a CTO can repeat back. +
the scope is explicit — Nova governs infrastructure and delivery, integrates with any upstream source through one validated contract, and measures success on four metrics a CTO can repeat back.
@@ -76,7 +96,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast 3. Not an upstream development platform (no product backlogs, IDE, code authorship) 4. Not a replacement for the Product Development Lifecycle (PDLC) -**Benefit:** the boundaries are explicit — Nova is purpose-built for infrastructure operations and delivery, not a general-purpose AI agent or an upstream development platform. +
the boundaries are explicit — Nova is purpose-built for infrastructure operations and delivery, not a general-purpose AI agent or an upstream development platform.
@@ -93,7 +113,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast - **The integration point is one contract** — any upstream source (AI agent, agentic SDLC, dev platform) produces submissions subject to the same compliance standards - **Nova validates the submission, not the author** — the audit trail, the policy envelope, and the evidence stream are the same regardless of source -**Benefit:** a clean scope boundary — Nova is purpose-built for infrastructure operations and integrates with any upstream source through one validated contract, so the platform team's surface area stays bounded. +
a clean scope boundary — Nova is purpose-built for infrastructure operations and integrates with any upstream source through one validated contract, so the platform team's surface area stays bounded.
@@ -118,7 +138,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast **R**=Responsible · **A**=Accountable (sign-off) · **C**=Consulted · **I**=Informed. Production readiness is co-owned: the platform runs attestations agentically; the citizen developer authorizes the promotion at the stage gate. -**Benefit:** every party knows what they bring, what the platform provides, what quality engineering guards, and where SRE signs off — accountability is explicit, never diffuse. +
every party knows what they bring, what the platform provides, what quality engineering guards, and where SRE signs off — accountability is explicit, never diffuse.
@@ -136,7 +156,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast - **Fail-fast, quick feedback** — Checkov runs on the authored Terraform code before `terraform plan` so developers get immediate policy feedback - **Wiz on the plan when configured; Checkov as a drop-in otherwise** — Wiz scans the plan output; when Wiz credentials are absent, Checkov runs against the plan. **Wiz and Checkov are never both run on the plan.** -**Benefit:** two layers of scanning, zero operator involvement in normal operations — fast deterministic feedback at authoring time and a runtime scan on the resolved plan. +
two layers of scanning, zero operator involvement in normal operations — fast deterministic feedback at authoring time and a runtime scan on the resolved plan.
@@ -152,7 +172,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast - **"AI decisions" are really automated decisions** — made by deterministic scripts that calculate a score and a band; the platform functions without AI. When an LLM planner is added later, it will emit richer alternatives without breaking the schema. - **The value is accountability, not the storage engine** — the ledger is append-only and tamper-evident; every decision is queryable for auditing, traceable to an outcome, and impossible to rewrite after the fact. -**Benefit:** "autonomous" is defensible because every decision is immutable, queryable, and accountable — and the audience knows exactly what "automated" means here: deterministic scoring, not a black-box LLM. +
"autonomous" is defensible because every decision is immutable, queryable, and accountable — and the audience knows exactly what "automated" means here: deterministic scoring, not a black-box LLM.
@@ -170,7 +190,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast | Performance baseline | qa | 7d | The deployment meets its performance envelope vs. the agreed baseline. | | Security posture | qa | 24h | The deployment's security findings have been reviewed and accepted. | -**Benefit:** QA signs off on quality before any promotion — the gate is explicit, not implicit. +
QA signs off on quality before any promotion — the gate is explicit, not implicit.
@@ -194,7 +214,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast Separation-of-duties on prod: the approver cannot be the same person who built the deployment. -**Benefit:** the gate model is explicit — autonomy in operations, human in accountability, by design. The matrix is what makes autonomous operations safe enough to trust in production. +
the gate model is explicit — autonomy in operations, human in accountability, by design. The matrix is what makes autonomous operations safe enough to trust in production.
@@ -212,7 +232,7 @@ Separation-of-duties on prod: the approver cannot be the same person who built t - **The live ops dashboard (PowerBI)** surfaces the four CTO-grade metrics (Lead Time, Vulnerability Count, MTTR, Cloud Spend) alongside trust metrics (Decision Ledger coverage, Attestation coverage) and efficiency metrics (touchless resolution, escalation frequency) - **Every number is traceable to a signal** — when a CFO asks "where does this number come from?", the answer is a query against the cold store, not a Slack thread -**Benefit:** the architecture is the trust substrate — leadership sees the same numbers the platform produces, in PowerBI, with full traceability. Operations become visible. +
the architecture is the trust substrate — leadership sees the same numbers the platform produces, in PowerBI, with full traceability. Operations become visible.
@@ -229,7 +249,7 @@ Separation-of-duties on prod: the approver cannot be the same person who built t - **No change to production without both** — the ledger entry and the human attestation are mandatory, enforced by the pipeline, not by policy - **Full traceability** — a production change is traceable from the contract that declared intent, through the policy scan, the confidence score, the attestation, to the applied outcome -**Benefit:** trust is provable — not a marketing claim, a queryable record. An auditor answers "who approved this, when, on what evidence?" in one query; a CTO answers "how many of last quarter's prod changes were touchless?" in one query. +
trust is provable — not a marketing claim, a queryable record. An auditor answers "who approved this, when, on what evidence?" in one query; a CTO answers "how many of last quarter's prod changes were touchless?" in one query.
@@ -247,7 +267,7 @@ Separation-of-duties on prod: the approver cannot be the same person who built t - **The four CTO-grade metrics are the ROI proof:** Lead Time (PR → Prod), Infrastructure Vulnerability Count (trend), MTTR, Cloud Spend Reduction — all flow into PowerBI - **Honest caveat:** derived metrics are computed on internal runs today; the production-denominator activates when a pilot estate runs. The formula is grounded; the production numbers are not yet. -**Benefit:** the ROI is not a black box — the formula is shown, the four metrics are committed, and the production-denominator caveat is stated up front. The CFO sees exactly what is real today and what activates with a pilot. +
the ROI is not a black box — the formula is shown, the four metrics are committed, and the production-denominator caveat is stated up front. The CFO sees exactly what is real today and what activates with a pilot.
@@ -270,7 +290,7 @@ To be clear: these deferrals are *measurement infrastructure*, not the autonomy | 5 | Live cost reconciliation | Live AWS re-provisioning + actual-spend feed | | 6 | Predictive vs reactive ratio | ML anomaly-forecasting service (not yet built) | -**Benefit:** the boundaries are explicit — what Nova measures today, and exactly what blocks the rest. The autonomy is real; the measurement gaps are documented with the work that unblocks each one. +
the boundaries are explicit — what Nova measures today, and exactly what blocks the rest. The autonomy is real; the measurement gaps are documented with the work that unblocks each one.
@@ -293,7 +313,7 @@ To be clear: these deferrals are *measurement infrastructure*, not the autonomy Re-evaluation triggers: each blocking piece of work lifts on its own schedule; the metrics layer evolves as each one lands. -**Benefit:** every deferred metric has an unblock path — nothing is hand-waved; everything has a plan and a timeframe. +
every deferred metric has an unblock path — nothing is hand-waved; everything has a plan and a timeframe.
@@ -314,7 +334,7 @@ Re-evaluation triggers: each blocking piece of work lifts on its own schedule; t Grounded in the four strategic objectives (autonomy, provable trust, ROI, integration) and the deferred-metric unblock paths. -**Benefit:** the 12-month product arc — each quarter activates a strategic objective and its corresponding board-level metric, from pilot activation through integration leadership. +
the 12-month product arc — each quarter activates a strategic objective and its corresponding board-level metric, from pilot activation through integration leadership.
@@ -333,7 +353,7 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr **Month-18 destination:** *"Nova is the layer enterprise leadership points to when they say 'we don't have an infrastructure ops team anymore, and the audit trail is stronger than it ever was.'"* -**Benefit:** each quarter has a concrete deliverable, a target metric grounded in a strategic objective, and a path from "honestly deferred" to "shipped and measured." +
each quarter has a concrete deliverable, a target metric grounded in a strategic objective, and a path from "honestly deferred" to "shipped and measured."
@@ -349,7 +369,7 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr - **MCP server** — a plugin-registry, stdio server exposing four tools: `lookup_principle`, `list_domains`, `matrix_lookup`, `validate_against_principles`. The developer's AI agent (or any agentic SDLC platform) calls these tools to look up the principles that apply to its submission - **The integration point is the same regardless of source** — whether the submission comes from an AI coding agent, an agentic SDLC platform, or a traditional IDE, the same skills and MCP server apply. This is how Nova makes the citizen developer production-grade without owning the PDLC -**Benefit:** the citizen developer's AI agent is not unguided — Nova provides production-grade engineering principles as skills and as an MCP surface, so submissions arrive at the contract boundary already aligned with the platform's standards. +
the citizen developer's AI agent is not unguided — Nova provides production-grade engineering principles as skills and as an MCP surface, so submissions arrive at the contract boundary already aligned with the platform's standards.
@@ -365,7 +385,7 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr - **Agentic validation, not a second policy engine** — the MCP server gives the AI agent the principles to validate against; the agent does the validation. The agent reasons about the submission against the principles, not a second static scan - **Vendored for audit reproducibility** — Atelier is vendored at a pinned tag. A validation result is replayable against the exact principles that produced it, so an audit can reproduce a validation months later, not just trust a log line -**Benefit:** the citizen developer's submission is checked for engineering discipline, not just policy compliance — and the check is reproducible for audit. That is what makes the submission production-grade, regardless of which upstream platform produced it. +
the citizen developer's submission is checked for engineering discipline, not just policy compliance — and the check is reproducible for audit. That is what makes the submission production-grade, regardless of which upstream platform produced it.
@@ -385,7 +405,7 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr **The ask:** "Approve a pilot estate to activate the production-denominator metrics (Lead Time, Vulnerability Count, MTTR, Cloud Spend), and approve the tamper-evident ledger build-out to move from the local hash-chain to S3 Object Lock + signed checkpoints. These two decisions move Nova from 'pipeline-ready' to 'production-proven.'" -**Benefit:** a clear business decision — approve a pilot and the ledger build-out — with the confidence that every claim in this deck is grounded, derived, or honestly deferred. +
a clear business decision — approve a pilot and the ledger build-out — with the confidence that every claim in this deck is grounded, derived, or honestly deferred.
@@ -413,6 +433,6 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr | Attestation Coverage | prod/dr attested ÷ total prod/dr | grounded | | Policy Compliance Rate | 1 − failed_assets ÷ total | grounded | -**Benefit:** a reference for every metric mentioned in the deck. +
a reference for every metric mentioned in the deck.
\ No newline at end of file diff --git a/docs/presentations/nova-autonomous-cloud-delivery.html b/docs/presentations/nova-autonomous-cloud-delivery.html index fdf7d8f..97ee68e 100644 --- a/docs/presentations/nova-autonomous-cloud-delivery.html +++ b/docs/presentations/nova-autonomous-cloud-delivery.html @@ -1,11 +1,96 @@ -Nova — The Autonomous Cloud Delivery Platform
+Nova — The Autonomous Cloud Delivery Platform

Nova — The Autonomous Cloud Delivery Platform

Shifting from Operational Overhead to Strategic Value

Product Development & Citizen Developer Overview

Nova — The Autonomous Cloud Delivery Platform
-
+

Slide 1 — The Problem

Product teams now own their cloud infrastructure — but ownership without discipline is destroying value.

    @@ -15,10 +100,48 @@
  • Tribal knowledge and the rockstar-operator problem. Operations depend on a handful of administrators; when they leave, the knowledge leaves with them. The platform should encode the discipline, not the person.

Every hour a developer spends writing, deploying, fixing, or remediating infrastructure is an hour not spent releasing features to production.

-

Benefit: the answer is an autonomous cloud delivery platform that encodes discipline as policy, scans proactively, remediates rapidly, and makes operations visible to leadership rather than hidden in tribal knowledge.

+
the answer is an autonomous cloud delivery platform that encodes discipline as policy, scans proactively, remediates rapidly, and makes operations visible to leadership rather than hidden in tribal knowledge.
Nova — The Autonomous Cloud Delivery Platform
-
+

Slide 2 — Nova's Vision

Infrastructure operations become visible. Every environment provisioned, every incident healed, every risk remediated — by an autonomous system whose trustworthiness is provable, not promised. Human attestation remains required at stage gates; the operator is never in the loop of normal operations.

@@ -28,10 +151,48 @@
  • Provable, not promised — trust established by deterministic scripts that calculate a score; the platform functions without AI
  • Autonomy in operations, human at stage gates — QA signs off for production; SRE greenlights operational readiness
  • -

    Benefit: the destination is autonomous operations with provable trust — security, remediation velocity, reliability, and lead time made visible to leadership, not promised to them.

    +
    the destination is autonomous operations with provable trust — security, remediation velocity, reliability, and lead time made visible to leadership, not promised to them.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 3 — Strategic Objectives

    4 Strategic Objectives:

      @@ -44,10 +205,48 @@
    1. Integrate with externally owned development platforms — regardless of source — PDLC, SDLC, Agentic, or Citizen Developer; Nova provides skills + MCP endpoints; all prod intents go through the same controls and quality gates
    -

    Benefit: the scope is explicit — Nova governs infrastructure and delivery, integrates with any upstream source through one validated contract, and measures success on four metrics a CTO can repeat back.

    +
    the scope is explicit — Nova governs infrastructure and delivery, integrates with any upstream source through one validated contract, and measures success on four metrics a CTO can repeat back.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 4 — Anti-Goals (What Nova Is NOT)

    1. Not a general-purpose AI agent platform
    2. @@ -55,10 +254,48 @@
    3. Not an upstream development platform (no product backlogs, IDE, code authorship)
    4. Not a replacement for the Product Development Lifecycle (PDLC)
    -

    Benefit: the boundaries are explicit — Nova is purpose-built for infrastructure operations and delivery, not a general-purpose AI agent or an upstream development platform.

    +
    the boundaries are explicit — Nova is purpose-built for infrastructure operations and delivery, not a general-purpose AI agent or an upstream development platform.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 5 — Scope: Downstream of PDLC

    Nova governs infrastructure and delivery. The PDLC is upstream — Nova never penetrates it. Integration is through one validated contract.

      @@ -67,10 +304,48 @@
    • The integration point is one contract — any upstream source (AI agent, agentic SDLC, dev platform) produces submissions subject to the same compliance standards
    • Nova validates the submission, not the author — the audit trail, the policy envelope, and the evidence stream are the same regardless of source
    -

    Benefit: a clean scope boundary — Nova is purpose-built for infrastructure operations and integrates with any upstream source through one validated contract, so the platform team's surface area stays bounded.

    +
    a clean scope boundary — Nova is purpose-built for infrastructure operations and integrates with any upstream source through one validated contract, so the platform team's surface area stays bounded.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 6 — RACI: Who Owns What

    Four roles, one matrix — citizen developer owns FRs + UAT, platform owns NFRs + infra, quality engineering owns the gate evidence, SRE owns operational readiness.

    @@ -143,10 +418,48 @@

    R=Responsible · A=Accountable (sign-off) · C=Consulted · I=Informed. Production readiness is co-owned: the platform runs attestations agentically; the citizen developer authorizes the promotion at the stage gate.

    -

    Benefit: every party knows what they bring, what the platform provides, what quality engineering guards, and where SRE signs off — accountability is explicit, never diffuse.

    +
    every party knows what they bring, what the platform provides, what quality engineering guards, and where SRE signs off — accountability is explicit, never diffuse.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 7 — The Platform Pipeline

    How intent becomes verified infrastructure — fail-fast policy scanning before the plan, runtime scanning after it.

    class:tall

    @@ -155,10 +468,48 @@
  • Fail-fast, quick feedback — Checkov runs on the authored Terraform code before terraform plan so developers get immediate policy feedback
  • Wiz on the plan when configured; Checkov as a drop-in otherwise — Wiz scans the plan output; when Wiz credentials are absent, Checkov runs against the plan. Wiz and Checkov are never both run on the plan.
  • -

    Benefit: two layers of scanning, zero operator involvement in normal operations — fast deterministic feedback at authoring time and a runtime scan on the resolved plan.

    +
    two layers of scanning, zero operator involvement in normal operations — fast deterministic feedback at authoring time and a runtime scan on the resolved plan.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 8 — The Decision Ledger

    Every automated decision is captured, immutable, queryable — and accountable.

      @@ -166,10 +517,48 @@
    • "AI decisions" are really automated decisions — made by deterministic scripts that calculate a score and a band; the platform functions without AI. When an LLM planner is added later, it will emit richer alternatives without breaking the schema.
    • The value is accountability, not the storage engine — the ledger is append-only and tamper-evident; every decision is queryable for auditing, traceable to an outcome, and impossible to rewrite after the fact.
    -

    Benefit: "autonomous" is defensible because every decision is immutable, queryable, and accountable — and the audience knows exactly what "automated" means here: deterministic scoring, not a black-box LLM.

    +
    "autonomous" is defensible because every decision is immutable, queryable, and accountable — and the audience knows exactly what "automated" means here: deterministic scoring, not a black-box LLM.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 9 — Attestation Matrix: QA

    The designed controls that keep humans at stage gates — QA concerns, freshness-validated.

    @@ -202,10 +591,48 @@
    -

    Benefit: QA signs off on quality before any promotion — the gate is explicit, not implicit.

    +
    QA signs off on quality before any promotion — the gate is explicit, not implicit.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 10 — Attestation Matrix: Prod/DR

    Production and DR controls — operational readiness, resilience, and disaster recovery.

    @@ -263,10 +690,48 @@

    Separation-of-duties on prod: the approver cannot be the same person who built the deployment.

    -

    Benefit: the gate model is explicit — autonomy in operations, human in accountability, by design. The matrix is what makes autonomous operations safe enough to trust in production.

    +
    the gate model is explicit — autonomy in operations, human in accountability, by design. The matrix is what makes autonomous operations safe enough to trust in production.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 11 — Telemetry & Live Ops

    Every metric in this deck is traceable to a real emitted signal — the live-ops dashboard makes operations visible in PowerBI.

    class:tall

    @@ -275,10 +740,48 @@
  • The live ops dashboard (PowerBI) surfaces the four CTO-grade metrics (Lead Time, Vulnerability Count, MTTR, Cloud Spend) alongside trust metrics (Decision Ledger coverage, Attestation coverage) and efficiency metrics (touchless resolution, escalation frequency)
  • Every number is traceable to a signal — when a CFO asks "where does this number come from?", the answer is a query against the cold store, not a Slack thread
  • -

    Benefit: the architecture is the trust substrate — leadership sees the same numbers the platform produces, in PowerBI, with full traceability. Operations become visible.

    +
    the architecture is the trust substrate — leadership sees the same numbers the platform produces, in PowerBI, with full traceability. Operations become visible.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 12 — Decision Ledger + Attestation Coverage

    By design, no change reaches production without a ledger entry and a human attestation — both queryable for auditing, with full traceability.

      @@ -287,10 +790,48 @@
    • No change to production without both — the ledger entry and the human attestation are mandatory, enforced by the pipeline, not by policy
    • Full traceability — a production change is traceable from the contract that declared intent, through the policy scan, the confidence score, the attestation, to the applied outcome
    -

    Benefit: trust is provable — not a marketing claim, a queryable record. An auditor answers "who approved this, when, on what evidence?" in one query; a CTO answers "how many of last quarter's prod changes were touchless?" in one query.

    +
    trust is provable — not a marketing claim, a queryable record. An auditor answers "who approved this, when, on what evidence?" in one query; a CTO answers "how many of last quarter's prod changes were touchless?" in one query.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 13 — Cost & ROI

    The ROI formula and the cost estimates — grounded, with the production denominator honestly flagged.

      @@ -300,10 +841,48 @@
    • The four CTO-grade metrics are the ROI proof: Lead Time (PR → Prod), Infrastructure Vulnerability Count (trend), MTTR, Cloud Spend Reduction — all flow into PowerBI
    • Honest caveat: derived metrics are computed on internal runs today; the production-denominator activates when a pilot estate runs. The formula is grounded; the production numbers are not yet.
    -

    Benefit: the ROI is not a black box — the formula is shown, the four metrics are committed, and the production-denominator caveat is stated up front. The CFO sees exactly what is real today and what activates with a pilot.

    +
    the ROI is not a black box — the formula is shown, the four metrics are committed, and the production-denominator caveat is stated up front. The CFO sees exactly what is real today and what activates with a pilot.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 14 — What's Deferred — and Why

    Honesty about what is not measured yet — and the blocking work for each.

    To be clear: these deferrals are measurement infrastructure, not the autonomy itself. The platform runs without an operator in the loop of normal operations. What is deferred is the evidence pipeline for certain metrics — not the autonomy.

    @@ -348,10 +927,48 @@ -

    Benefit: the boundaries are explicit — what Nova measures today, and exactly what blocks the rest. The autonomy is real; the measurement gaps are documented with the work that unblocks each one.

    +
    the boundaries are explicit — what Nova measures today, and exactly what blocks the rest. The autonomy is real; the measurement gaps are documented with the work that unblocks each one.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 15 — Roadmap to the North Star

    The path from the grounded metrics to the 12–18 month targets — each deferred metric has an unblock path and a timeframe.

    @@ -396,10 +1013,48 @@

    Re-evaluation triggers: each blocking piece of work lifts on its own schedule; the metrics layer evolves as each one lands.

    -

    Benefit: every deferred metric has an unblock path — nothing is hand-waved; everything has a plan and a timeframe.

    +
    every deferred metric has an unblock path — nothing is hand-waved; everything has a plan and a timeframe.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 16 — 12-Month Product Roadmap

    The product arc from pilot activation to integration — four quarters, four outcomes.

    @@ -434,10 +1089,48 @@

    Grounded in the four strategic objectives (autonomy, provable trust, ROI, integration) and the deferred-metric unblock paths.

    -

    Benefit: the 12-month product arc — each quarter activates a strategic objective and its corresponding board-level metric, from pilot activation through integration leadership.

    +
    the 12-month product arc — each quarter activates a strategic objective and its corresponding board-level metric, from pilot activation through integration leadership.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 17 — Quarter-by-Quarter Outcomes

    @@ -476,10 +1169,48 @@

    Month-18 destination: "Nova is the layer enterprise leadership points to when they say 'we don't have an infrastructure ops team anymore, and the audit trail is stronger than it ever was.'"

    -

    Benefit: each quarter has a concrete deliverable, a target metric grounded in a strategic objective, and a path from "honestly deferred" to "shipped and measured."

    +
    each quarter has a concrete deliverable, a target metric grounded in a strategic objective, and a path from "honestly deferred" to "shipped and measured."
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 18 — Production-Grade Guidance via Atelier (1/2)

    Nova instructs the citizen developer's AI agent on production-grade engineering — a set of skills and an MCP server.

      @@ -487,10 +1218,48 @@
    • MCP server — a plugin-registry, stdio server exposing four tools: lookup_principle, list_domains, matrix_lookup, validate_against_principles. The developer's AI agent (or any agentic SDLC platform) calls these tools to look up the principles that apply to its submission
    • The integration point is the same regardless of source — whether the submission comes from an AI coding agent, an agentic SDLC platform, or a traditional IDE, the same skills and MCP server apply. This is how Nova makes the citizen developer production-grade without owning the PDLC
    -

    Benefit: the citizen developer's AI agent is not unguided — Nova provides production-grade engineering principles as skills and as an MCP surface, so submissions arrive at the contract boundary already aligned with the platform's standards.

    +
    the citizen developer's AI agent is not unguided — Nova provides production-grade engineering principles as skills and as an MCP surface, so submissions arrive at the contract boundary already aligned with the platform's standards.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 19 — Production-Grade Guidance via Atelier (2/2)

    Agentic validation catches engineering-discipline gaps that deterministic scanners miss — and the validation is reproducible.

      @@ -498,10 +1267,48 @@
    • Agentic validation, not a second policy engine — the MCP server gives the AI agent the principles to validate against; the agent does the validation. The agent reasons about the submission against the principles, not a second static scan
    • Vendored for audit reproducibility — Atelier is vendored at a pinned tag. A validation result is replayable against the exact principles that produced it, so an audit can reproduce a validation months later, not just trust a log line
    -

    Benefit: the citizen developer's submission is checked for engineering discipline, not just policy compliance — and the check is reproducible for audit. That is what makes the submission production-grade, regardless of which upstream platform produced it.

    +
    the citizen developer's submission is checked for engineering discipline, not just policy compliance — and the check is reproducible for audit. That is what makes the submission production-grade, regardless of which upstream platform produced it.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Slide 20 — Recap + Ask

    The 4-beat recap + the business decision.

    Recap:

    @@ -512,10 +1319,48 @@
  • Roadmap: deferred metrics have unblock paths; the 12-month product arc activates one strategic objective per quarter
  • The ask: "Approve a pilot estate to activate the production-denominator metrics (Lead Time, Vulnerability Count, MTTR, Cloud Spend), and approve the tamper-evident ledger build-out to move from the local hash-chain to S3 Object Lock + signed checkpoints. These two decisions move Nova from 'pipeline-ready' to 'production-proven.'"

    -

    Benefit: a clear business decision — approve a pilot and the ledger build-out — with the confidence that every claim in this deck is grounded, derived, or honestly deferred.

    +
    a clear business decision — approve a pilot and the ledger build-out — with the confidence that every claim in this deck is grounded, derived, or honestly deferred.
    Nova — The Autonomous Cloud Delivery Platform
    -
    +

    Appendix A1 — Metrics Glossary

    @@ -593,7 +1438,7 @@
    -

    Benefit: a reference for every metric mentioned in the deck.

    +
    a reference for every metric mentioned in the deck.
    Nova — The Autonomous Cloud Delivery Platform