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
**4 Anti-Goals (what Nova is NOT):**
**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.
---
## Slide 4 — Anti-Goals (What Nova Is NOT)
1. Not a general-purpose AI agent platform
2. Not a system that removes humans from accountability — only from normal operations
3. Not an upstream development platform (no product backlogs, IDE, code authorship)
4. Not a replacement for the Product Development Lifecycle (PDLC)
**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.
**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.
---
## Slide 4 — Scope: Downstream of PDLC
## 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.**
@@ -77,7 +81,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast
@@ -98,7 +102,7 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast
---
## Slide 6 — The Platform Pipeline
## Slide 7 — The Platform Pipeline
**How intent becomes verified infrastructure — fail-fast policy scanning before the plan, runtime scanning after it.**
@@ -107,13 +111,12 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast
- **Contract → resolver → adapter → Checkov on static code (before plan) → terraform plan → Wiz on the plan → confidence signal → stage gate → apply → evidence + ledger**
- **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.**
- **Dev is autonomous** (no stage gate); **qa/prod/dr require human attestation** (QA for quality, SRE for production readiness)
**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.
---
## Slide 7 — The Decision Ledger
## Slide 8 — The Decision Ledger
**Every automated decision is captured, immutable, queryable — and accountable.**
@@ -125,15 +128,26 @@ Every hour a developer spends writing, deploying, fixing, or remediating infrast
---
## Slide 8 — The Attestation Matrix
## Slide 9 — Attestation Matrix: QA
**The designed controls that keep humans at stage gates — structured, freshness-validated, separation-of-duties-enforced.**
**The designed controls that keep humans at stage gates — QA concerns, freshness-validated.**
| Concern | Env | Freshness | Description |
|---------|-----|-----------|-------------|
| Functional correctness | qa | 24h | The application behaves as specified; evidence accepted from the consumer's UAT. |
| 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.
---
## Slide 10 — Attestation Matrix: Prod/DR
**Production and DR controls — operational readiness, resilience, and disaster recovery.**
| Concern | Env | Freshness | Description |
|---------|-----|-----------|-------------|
| Operational readiness | prod | 30d | SRE confirms the deployment is operable: runbooks, dashboards, on-call. |
| Incident response | prod | 90d | The on-call path has been exercised; a working incident-response plan exists. |
| Capacity & cost | prod | 30d | Capacity headroom and monthly cost are within the agreed envelope. |
@@ -148,7 +162,7 @@ Separation-of-duties on prod: the approver cannot be the same person who built t
---
## Slide 9 — Telemetry & Live Ops
## 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.**
@@ -156,28 +170,26 @@ Separation-of-duties on prod: the approver cannot be the same person who built t
- **Platform components → CloudEvents envelope → event log + decision ledger + run records → collector → cold store → PowerBI views → live ops dashboard**
- **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)
- **Deliberately minimal** — Nova-native envelopes; no Kafka, no Prometheus, no ClickHouse. The cold store handles batch and historical analysis; the live-ops surface is built in PowerBI on the exported views
- **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.
**By design, no change reaches production without a ledger entry and a human attestation — both queryable for auditing, with full traceability.**
- **Decision Ledger coverage: 100%** — every platform run emits a decision record with outcome backfill; no automated decision is ever lost
- **Attestation coverage: 100%** — every prod/dr promotion is attested by a human (QA for quality, SRE for production readiness), recorded with approver identity, separation-of-duties check, and the evidence matrix
- **No change to production without both** — the ledger entry and the human attestation are mandatory, enforced by the pipeline, not by policy
- **Easily queried for auditing** — queryable by run, by environment, by approver, and by outcome; the audit trail is a query, not a forensic exercise
- **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.
---
## Slide 11 — Cost & ROI
## Slide 13 — Cost & ROI
**The ROI formula and the cost estimates — grounded, with the production denominator honestly flagged.**
@@ -191,7 +203,7 @@ Separation-of-duties on prod: the approver cannot be the same person who built t
---
## Slide 12 — What's Deferred — and Why
## Slide 14 — What's Deferred — and Why
**Honesty about what is not measured yet — and the blocking work for each.**
@@ -199,20 +211,18 @@ To be clear: these deferrals are *measurement infrastructure*, not the autonomy
| # | Deferred metric | Blocking work |
|---|-----------------|---------------|
| 1 | Live infrastructure health | Live AWS re-provisioning (currently torn down to zero-cost steady state) |
| 2 | Live outbox write rate | Live AWS re-provisioning |
| 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.
---
## Slide 13 — Roadmap to the North Star
## 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.**
@@ -231,7 +241,7 @@ Re-evaluation triggers: each blocking piece of work lifts on its own schedule; t
---
## Slide 14 — 12-Month Product Roadmap
## Slide 16 — 12-Month Product Roadmap
**The product arc from pilot activation to integration — four quarters, four outcomes.**
@@ -248,14 +258,14 @@ 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.'"*
@@ -263,7 +273,7 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr
---
## Slide 16 — Production-Grade Guidance via Atelier (1/2)
## 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.**
@@ -275,7 +285,7 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr
---
## Slide 17 — Production-Grade Guidance via Atelier (2/2)
## Slide 19 — Production-Grade Guidance via Atelier (2/2)
**Agentic validation catches engineering-discipline gaps that deterministic scanners miss — and the validation is reproducible.**
@@ -287,7 +297,7 @@ Grounded in the four strategic objectives (autonomy, provable trust, ROI, integr
f"expected 18 main slides, found {len(main_slides)}: {slide_headings}"
assertlen(main_slides)==20, \
f"expected 20 main slides, found {len(main_slides)}: {slide_headings}"
assertlen(appendix_slides)==1, \
f"expected 1 appendix slide, found {len(appendix_slides)}"
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Jon Chery