Jon Chery
b927f9026a
---ci--- project: acdl phase: 6 milestone: v1.1 status: plan plan: waves: 3 tasks: 6 requirements: [] # repo hygiene; no new REQ ---/ci--- Phase 06 plan authored by ci-planner. 3 waves (strictly ordered): - Wave 1 (lead-developer): T-6.1 git mv demo dirs, T-6.2 scaffold new dirs, T-6.3 write scripts/verify_phase06.sh at top-level, T-6.4 rewrite README + .gitignore - Wave 2 (frontend-engineer): T-6.5 confirm demo/evidence-ui/ moved cleanly (confirm-only) - Wave 3 (lead-developer): T-6.6 run verify_phase06.sh + typecheck gate Key design: v1.1 verify scripts live at a new top-level scripts/ (not demo/scripts/ which holds the archived v1.0 verify scripts). All git mv commands enumerated verbatim in T-6.1, cross-checked against RESEARCH.md TARGET 10.
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.