Jon Chery 247a225d54 feat(P03): Phase 03 verification script (T-3.10)
---ci---
phase: 3
milestone: v1.0
status: execute
persona: lead-developer
task: T-3.10
requirements:
  covered: [REQ-04, REQ-05, REQ-06, REQ-07, REQ-08, REQ-11]
---/ci---

Wave 3, task T-3.10. scripts/verify_phase03.sh checks: (1) 4 L2 folders
with exact names; (2) each L2 manifest.yaml structure + 5 existing L1
references + inputs maps; (3) typecheck (bash -n + py_compile + yaml load);
(4) policy_checker D-025 (pass/fail); (5) confidence_signal D-024
(score 0.90/0.40, exit 0 always); (6) evidence_writer D-023 hash chain
(genesis + 3 events, prev_hash links, SHA-256 recompute); (7) mock_executor
D-022 state.json (l2 + 5 l1s all exit 0 + contract); (8) l3b_agent_stub
D-008 keyword map (Act 3 example + 4 keyword cases + fallback). All 18
checks pass. Uses 'set -uo pipefail' (no set -e) so intentional
non-zero exits (policy_checker failure case) can be captured without
killing the script.
2026-07-21 13:30:55 +00:00

ACDL — Agentic Cloud Delivery Platform

A 30-minute executive demo proving that infrastructure can be delivered automatically, safely, and with a complete audit trail — without the usual weeks of manual tickets, reviews, and copy-pasted configuration.

The demo runs entirely on local stubs (no AWS/GCP/Azure, no external LLM APIs). It shows intent and safety behavior rather than provisioning real cloud resources.

Four acts

  1. Act 1 — The Friction: the old manual 2-week deployment process.
  2. Act 2 — Developer Self-Service: commit a valid contract.yaml for l2-commodity-price-feed, watch Dev auto-run, QA + Prod approval gates, then the evidence timeline.
  3. Act 3 — Citizen Developer: open a GitHub/Gitea Issue with natural- language intent; the Python keyword parser generates the same contract.yaml and triggers the identical pipeline.
  4. Act 4 — The Safety Net: commit a malicious contract.yaml (public-ingress: true) for l2-regulatory-reporting; the pipeline halts in Dev because the confidence signal drops below 0.50, and the rejection is visible on the evidence stream.

Repositories

All under the continuous-intelligence Gitea org at https://git.cloudinit.dev:

  • acdl (this repo) — platform + stubs + reusable workflows
  • acdl-contracts — developer surface (contract.yaml + issue trigger)
  • acdl-evidence — audit timeline (served via raw file URLs; Gitea has no native Pages — see .ciagent/ARCHITECTURE.md Gitea API Surface table)

Project metadata

See .ciagent/PROJECT.md for the full spec, .ciagent/ROADMAP.md for the 5-phase breakdown, .ciagent/REQUIREMENTS.md for traceable requirements, and .ciagent/PERSONAS.md for the active persona roster.

Phase 01 verification

After running scripts/gitea_setup.sh (which creates acdl-contracts and acdl-evidence in the org and pushes the placeholder index.html), run:

ACDL_GITEA_TOKEN=<token> scripts/verify_phase01.sh

The script confirms:

  • both new repos exist via the Gitea API
  • the raw index.html URL on acdl-evidence returns HTTP 200
  • the qa and prod branches exist on acdl-contracts

Exit 0 = Phase 01 success criteria met.

S
Description
Nova — The New Dawn of DevSecOps. Autonomous infrastructure delivery: consumers declare intent, the platform ships safely with an immutable audit trail.
Readme 69 MiB
Languages
Python 87.2%
Shell 8.6%
HCL 4.2%