Files

T

Jon Chery 0d2cbdb423 feat(P1): remove gitea/gitlab from synced files + simplify docs (REQ-230,231,232)

Genericize forge-detection code: gitea→forge/generic_forge, GITEA_ACTOR→FORGE_ACTOR.
Drop .gitea byte-identity test assertions (keep GitHub-side + contract conformance).
Add test_no_forge_mentions.py guard test (REQ-230).
Delete completed migration docs (NOVA_MIGRATION.md, NOVA_AWS_MIGRATION.md).
Move NO_HUMANS_THESIS.md to .ciagent/ (internal artifact).
Strip ciagent-internal provenance from synced docs (REQ-/D-/P-/CAP- IDs,
milestone headers, .ciagent/PROJECT.md citations).
Trim README.md (reusable deploy section, local key rotation paragraph).
Fix version-tag drift (@v1.13→@v1.19, acdl/→nova/).

---ci---
project: acdl
phase: 1
milestone: v1.20
status: execute
requirements: [REQ-230, REQ-231, REQ-232]
---/ci---

2026-08-07 18:20:29 +00:00

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

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.

2.6 KiB Raw Blame History