Jon Chery
0a1ed28c50
---ci---
phase: 5
milestone: v1.0
status: plan
plan:
waves: 3
wave_1_frontend: [T-5.1 evidence-ui/index.html]
wave_2_backend: [T-5.2 scripts/run_demo.sh 4-act simulation]
wave_3_coordination: [T-5.3 verify_phase05.sh, T-5.4 traceability]
requirements_covered: [REQ-13, REQ-14, REQ-15]
must_haves: 6
verification:
typecheck: bash -n + py_compile
test: scripts/verify_phase05.sh (with + without Gitea token)
---/ci---
PLAN.md replaced with Phase 05 plan. Wave 1 (frontend-engineer
REACTIVATED) builds evidence-ui/index.html. Wave 2 (backend-engineer)
builds scripts/run_demo.sh (4-act local simulation + upload). Wave 3
(lead-developer) verifies + traceability. Phase 05 is the milestone
capstone; COMPLETE gate follows.
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
- Act 1 — The Friction: the old manual 2-week deployment process.
- Act 2 — Developer Self-Service: commit a valid
contract.yamlforl2-commodity-price-feed, watch Dev auto-run, QA + Prod approval gates, then the evidence timeline. - Act 3 — Citizen Developer: open a GitHub/Gitea Issue with natural-
language intent; the Python keyword parser generates the same
contract.yamland triggers the identical pipeline. - Act 4 — The Safety Net: commit a malicious
contract.yaml(public-ingress: true) forl2-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 workflowsacdl-contracts— developer surface (contract.yaml+ issue trigger)acdl-evidence— audit timeline (served via raw file URLs; Gitea has no native Pages — see.ciagent/ARCHITECTURE.mdGitea 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.htmlURL onacdl-evidencereturns HTTP 200 - the
qaandprodbranches exist onacdl-contracts
Exit 0 = Phase 01 success criteria met.