diff --git a/.ciagent/CHECKPOINT.json b/.ciagent/CHECKPOINT.json index db4aa13..305a3f4 100644 --- a/.ciagent/CHECKPOINT.json +++ b/.ciagent/CHECKPOINT.json @@ -1,12 +1,12 @@ { - "phase": 3, + "phase": 4, "stage": "complete", "milestone": "v1.22", "phase_role": "execution", "attempts": 0, - "updated_at": "2026-08-11T14:55:00Z", + "updated_at": "2026-08-11T15:00:00Z", "milestone_complete": false, - "tag": "v1.21.3", - "requirements": ["REQ-259","REQ-260"], - "notes": "v1.22 P3 complete. Tag v1.21.3. Both mermaid diagrams re-rendered at 2x transparent. telemetry-live-ops: TB, 0.63 aspect. platform-pipeline: TB 4-node, 0.49 aspect. Marp deck directives updated to h:480. Proceeding to P4 (deck content)." + "tag": "v1.21.4", + "requirements": ["REQ-261"], + "notes": "v1.22 P4 complete. Tag v1.21.4. 8 overflowing slides trimmed/split. Header removed from frontmatter. Slide count 18->20 main + 1 appendix. 23 slide tests pass. Proceeding to P5 (re-render + tests)." } \ 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 46365e3..3701597 100644 --- a/docs/presentations/nova-autonomous-cloud-delivery.html +++ b/docs/presentations/nova-autonomous-cloud-delivery.html @@ -1,14 +1,11 @@ -Nova — The Autonomous Cloud Delivery Platform
-
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
-
-
Nova — The Autonomous Cloud Delivery Platform
+

Slide 1 — The Problem

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

    @@ -21,8 +18,7 @@

    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.

    Nova — The Autonomous Cloud Delivery Platform
-
-
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.

@@ -35,9 +31,8 @@

Benefit: 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
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 3 — Strategic Objectives + Anti-Goals

+
+

Slide 3 — Strategic Objectives

4 Strategic Objectives:

  1. Zero-touch operations — autonomy as the default, not the demo; stage-gate attestation (QA, SRE) remains human by design
    2. @@ -49,19 +44,22 @@
  2. 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.

+
Nova — The Autonomous Cloud Delivery Platform
+
+
+

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.

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery 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.

  • The PDLC is upstream: product backlog, code authorship (AI agent, IDE, agentic SDLC), sprint planning, application business logic
    • @@ -72,9 +70,8 @@

    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.

    Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 5 — RACI: Who Owns What

+
+

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.

@@ -149,23 +146,20 @@

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.

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

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.

-

+

  • 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.

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 7 — The Decision Ledger

+
+

Slide 8 — The Decision Ledger

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

  • What is captured: the chosen action, the confidence score, the alternatives considered, whether a human overrode it, and the outcome (backfilled once the apply completes). Every stage-gate attestation (QA, SRE) is captured with approver identity and the evidence presented.
    • @@ -175,10 +169,9 @@

    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.

    Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 8 — The Attestation Matrix

-

The designed controls that keep humans at stage gates — structured, freshness-validated, separation-of-duties-enforced.

+
+

Slide 9 — Attestation Matrix: QA

+

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

@@ -207,6 +200,24 @@ + +
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.

+
Nova — The Autonomous Cloud Delivery Platform
+
+
+

Slide 10 — Attestation Matrix: Prod/DR

+

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

+ + + + + + + + + + @@ -255,37 +266,32 @@

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.

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

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.

-

+

  • 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.

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 10 — Decision Ledger + Attestation Coverage

+
+

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.

  • 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.

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 11 — Cost & ROI

+
+

Slide 13 — Cost & ROI

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

  • Cost estimates are pre-apply and offline — the platform reads the terraform plan and estimates cost before anything is applied; a cost regression is caught before the spend happens
    • @@ -297,9 +303,8 @@

    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.

    Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

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.

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.

ConcernEnvFreshnessDescription
Operational readiness prod
@@ -313,41 +318,31 @@ - + - - - - - - + - + - + - - - - - - + @@ -356,9 +351,8 @@

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.

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

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.

1Live infrastructure healthLive infra health, outbox write rate, SLA Live AWS re-provisioning (currently torn down to zero-cost steady state)
2Live outbox write rateLive AWS re-provisioning
3 Tamper-evident ledger checkpoints Audit-ledger build-out (Object Lock + signed checkpoints)
43 Onboarding funnel (requested → granted) Auto-grant implementation
54 Drift auto-reversal Drift-detection scheduler (not yet built)
65 Live cost reconciliation Live AWS re-provisioning + actual-spend feed
7SLA / unplanned downtimeLive AWS re-provisioning
86 Predictive vs reactive ratio ML anomaly-forecasting service (not yet built)
@@ -405,9 +399,8 @@

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

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 14 — 12-Month Product Roadmap

+
+

Slide 16 — 12-Month Product Roadmap

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

@@ -444,9 +437,8 @@

Benefit: 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
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 15 — Quarter-by-Quarter Outcomes

+
+

Slide 17 — Quarter-by-Quarter Outcomes

@@ -454,7 +446,6 @@ - @@ -463,28 +454,24 @@ - - - -
Product theme Key deliverable Target metricGrounding
Pilot Activation Re-provision live AWS; activate first pilot estate; onboarding auto-grant Touchless ≥ 99% · Escalation < 0.1% · Accuracy ≥ 99.5%Objective #1 — autonomy as the default
Q2 Provable Trust Tamper-evident ledger (Object Lock + signed checkpoints); daily checkpoints; live cost reconciliation Decision Ledger Coverage 100% · Cost Savings ≥ 25%Objective #2 — trust is the moat
Q3 Compounding ROI + Drift Drift-detection scheduler; auto-reversal; pre-apply → actual-spend reconciliation on the pilot estate Drift Auto-Reversal ≥ 95% · Spend Reduction ≥ 25%Objective #3 — CFO-pointable numbers
Q4 Integration + Predictive ML anomaly-forecasting; AI-agent intent surface; multi-cloud (Azure/GCP) preview Predictive:Reactive ≥ 3:1 · AI-Agent Intent Share (first measurement)Objective #4 — default substrate for agents
@@ -492,9 +479,8 @@

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."

Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

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.

  • Skills — markdown files keyed to production-grade engineering domains (API, security, data, testing, observability, errors, DevOps, infrastructure-as-code, compliance); the skills extend the baseline catalog with Nova-specific production-grade principles
    • @@ -504,9 +490,8 @@

    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.

    Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

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.

  • Beyond deterministic scanners — Wiz, Checkmarx, and Mend check policy and secrets; they do not check engineering discipline. The Atelier MCP server catches correctness, clarity, and observability gaps that deterministic tools cannot: "is this service observable?", "is this error path handled?", "is this API contract clear?"
    • @@ -516,9 +501,8 @@

    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.

    Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
-

Slide 18 — Recap + Ask

+
+

Slide 20 — Recap + Ask

The 4-beat recap + the business decision.

Recap:

    @@ -531,9 +515,7 @@

    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.

    Nova — The Autonomous Cloud Delivery Platform
-
-
Nova — The Autonomous Cloud Delivery Platform
- +

Appendix A1 — Metrics Glossary

diff --git a/docs/presentations/nova-autonomous-cloud-delivery.pptx b/docs/presentations/nova-autonomous-cloud-delivery.pptx index 312fc64..0773f02 100644 Binary files a/docs/presentations/nova-autonomous-cloud-delivery.pptx and b/docs/presentations/nova-autonomous-cloud-delivery.pptx differ diff --git a/tests/test_slides_pipeline.py b/tests/test_slides_pipeline.py index e9964dd..61099a3 100644 --- a/tests/test_slides_pipeline.py +++ b/tests/test_slides_pipeline.py @@ -267,4 +267,107 @@ def test_source_md_no_badges(): """REQ-252: no maturity badges in the source-of-truth markdown.""" text = SOURCE_MD.read_text() assert "badge" not in text.lower(), \ - "Source markdown still contains badge spans" \ No newline at end of file + "Source markdown still contains badge spans" + + +# --- v1.22 layout/aspect-ratio/theme-structural tests (REQ-262) --- + +def test_theme_css_has_section_padding(): + """REQ-254: theme CSS has a section padding rule (root cause fix).""" + css = THEME_CSS.read_text() + assert "padding:" in css, "theme CSS has no padding rule" + # The section rule must have padding (not just table/td padding) + assert re.search(r"section\s*\{[^}]*padding:", css, re.DOTALL), \ + "theme CSS has no padding on the section rule" + + +def test_theme_css_suppresses_title_chrome(): + """REQ-256: title slides suppress header/footer chrome.""" + css = THEME_CSS.read_text() + assert "section.title header" in css, \ + "theme CSS does not suppress title-slide header" + assert "section.title footer" in css, \ + "theme CSS does not suppress title-slide footer" + assert "display: none" in css, \ + "theme CSS does not set display:none on title chrome" + + +def test_theme_css_has_aspect_ratio_aware_images(): + """REQ-255: image rules use object-fit + max-width (not blunt max-height only).""" + css = THEME_CSS.read_text() + assert "object-fit" in css, \ + "theme CSS does not use object-fit for images" + assert "max-width" in css, \ + "theme CSS does not set max-width for images" + + +def test_png_aspect_ratios_sane(): + """REQ-259/260: PNGs referenced in the marp deck have aspect ratios + in [0.4, 4.0] (suitable for 16:9 slides with img.tall/img.wide classes). + Only checks PNGs actually referenced in the current marp deck — + legacy/unused PNGs are not checked (GRILL revision 1).""" + import struct + deck_text = MARP_DECK.read_text() + # Extract all referenced PNG paths: ![...](assets/png/X.png) + referenced = re.findall(r'!\[[^\]]*\]\(assets/png/([^)]+\.png)\)', deck_text) + assert referenced, "no PNGs referenced in the marp deck" + for png_name in referenced: + png_path = ASSETS / "png" / png_name + assert png_path.is_file(), f"referenced PNG not found: {png_name}" + with open(png_path, "rb") as fh: + data = fh.read(24) + assert data[:8] == b"\x89PNG\r\n\x1a\n", f"{png_name} is not a PNG" + w = struct.unpack(">I", data[16:20])[0] + h = struct.unpack(">I", data[20:24])[0] + ar = w / h + assert 0.4 <= ar <= 4.0, \ + f"{png_name} aspect ratio {ar:.2f} outside [0.4, 4.0] ({w}x{h})" + + +def test_render_slides_has_2x_scale(): + """REQ-258: render_slides.sh uses -s 2 (2x scale) and -b transparent.""" + text = RENDER_SCRIPT.read_text() + assert "-s 2" in text, "render_slides.sh does not use -s 2 (2x scale)" + assert "-b transparent" in text, \ + "render_slides.sh does not use -b transparent" + + +def test_render_slides_pins_cli_versions(): + """REQ-257: render_slides.sh pins marp-cli and mermaid-cli versions + (no @latest).""" + text = RENDER_SCRIPT.read_text() + assert "marp-cli@" in text, "render_slides.sh does not pin marp-cli" + assert "mermaid-cli@" in text, \ + "render_slides.sh does not pin mermaid-cli" + assert "@latest" not in text, \ + "render_slides.sh still uses @latest (not pinned)" + + +def test_render_deck_removed(): + """REQ-257: render_deck.sh has been deleted (produced unthemed output).""" + old_script = ROOT / "scripts" / "render_deck.sh" + assert not old_script.exists(), \ + "render_deck.sh still exists (should be deleted — produced unthemed output)" + + +def test_html_embeds_theme(): + """REQ-262: the committed HTML embeds the S&P theme (--sp-red + padding + in the inline