Files

T

Nova Slides Render / render (push) Failing after 1m4s

Details

docs(P1): strategic docs — thesis rename + NORTH_STAR objectives + RACI restructure

AUTONOMY_THESIS.md (git mv from NO_HUMANS_THESIS.md): reframe from
'removing humans' to 'autonomy in operations, human at stage gates'.
Drop D-### citations + internal file paths; keep anti-claims, reworded.
Anti-claim #1 now: 'decisions are NOT made by an LLM — deterministic
scripts calculate a score; the platform functions without AI'.

NORTH_STAR.md:
- Vision: 'invisible' → 'visible' (operations become visible — recurring
  theme); polish for technical audience (security, remediation velocity,
  reliability, lead time).
- Objective #2: 'provable trust in AI decisions' → 'provable trust in
  automated decisions' (deterministic scripts calculate a score;
  platform functions without AI).
- Objective #3: four CTO-grade metrics (Lead Time PR→Prod, Infra Vuln
  Count trend, MTTR, Cloud Spend Reduction) → all flow into PowerBI.
- Objective #4: 'default substrate for agentic consumption' → integrate
  with externally owned PDLC/SDLC/Agentic/Citizen Developer platforms
  regardless of source; Nova provides skills + MCP endpoints; all prod
  intents go through the same controls + quality gates.
- Anti-goals: drop #1 (hyperscaler competitor), #4 (legacy untagged),
  #5 (sold to operators). Add: 'not an upstream development platform',
  'not a replacement for the PDLC'. Reword #3 (no 'removes humans').

docs/raci.md: 3 roles → 4 roles. Add Quality Engineering column. Rename
Release Management → SRE. Split release attestation into Quality
attestation (QA) + Production readiness (SRE). Platform no longer holds
A for attestation — reassigned to QE/SRE.

docs/scope.md: add integration framing (skills + MCP endpoints, all
sources go through same controls).

Render scripts: default deck name → nova-autonomous-cloud-delivery.
ONBOARDING + terraform/onboarding: 'no-humans' → 'autonomous'.

---ci---
project: acdl
phase: 1
milestone: v1.21
status: execute
phase_role: execution
---/ci---

2026-08-11 13:55:53 +00:00

3.0 KiB

Raw Blame History

Scope — Nova is Downstream of PDLC

This page is the citizen-developer-facing copy.

The Boundary

The Product Development Lifecycle (PDLC) is upstream of Nova. The PDLC includes:

Product backlog / roadmap planning
Code authorship (via AI coding agent, IDE, or agentic SDLC platform)
Sprint planning / issue tracking
Application business logic
IDE workflows / developer experience

Nova never penetrates the PDLC. Nova's domain is infrastructure + delivery only. Nova integrates with externally owned PDLC, SDLC, Agentic, and Citizen Developer platforms with no regard for the source of the intent: Nova provides a set of skills and MCP endpoints that help the developer or AI agent make their application production-grade, and all intents to deploy to production go through the same rigorous controls, quality gates, attestation, and evidence stream.

What Nova Does

Nova governs the downstream half:

Contract ingestion — the validated entry point
Submission-readiness gate — what is acceptable to start (schemas/submission-readiness.schema.json)
Policy enforcement — the confidence signal, Checkov, tagging
Cloud resource lifecycle — Terraform plan/apply, state, IAM
Environment progression — dev (autonomous) → qa (QA attestation) → prod (SRE attestation) → dr (SRE attestation)
Immutable audit + attestation — the Decision Ledger, the evidence stream, the HITL gates

The Integration Point

Integration between the PDLC and Nova is only through the validated, published contract boundary:

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

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 — all are subject to the same compliance standards. Nova validates the submission, not the author.

What Nova is Not

Not an upstream development platform (no product backlogs, IDE, code authorship).
Not a general-purpose AI agent platform (autonomy is narrow, bounded by policy envelopes).
Not a legacy infrastructure bridge (no VMs/bare metal/OS).
Not a permissive delivery highway (no escape hatches past confidence or HITL).
Not a mutable audit log (VCS history ≠ regulatory evidence).

These anti-goals (from docs/vision.md §7 and Core Tenet #2) are promoted here from buried tenets to an unmissable scope statement.

3.0 KiB Raw Blame History