Jon Chery
41e5aaef59
---ci--- phase: 5 milestone: v1.0 status: execute persona: lead-developer task: T-5.3 requirements: covered: [REQ-13, REQ-14, REQ-15] ---/ci--- Wave 3, task T-5.3 + T-5.4. scripts/verify_phase05.sh checks: (1) evidence-ui/index.html structure (inline CSS/JS, fetch ./audit.json, no external refs, refresh button, 8134 bytes); (2) run_demo.sh syntax + --no-upload flag; (3) run_demo.sh --no-upload (4 acts, exit 0, audit.json written); (4) audit.json content (11 events + Act 1/2/3/4 + Act 4 POLICY_VIOLATION rejection); (5) hash chain integrity; (6) no stray state.json/contracts in repo root; (7) REAL upload + raw URL fetch (audit.json 200 with 11 events, index.html 200 with ACDL Evidence markers). All 13 checks PASS. The demo is live at: https://git.cloudinit.dev/continuous-intelligence/acdl-evidence/raw/branch/main/index.html Traceability: REQ-13/14/15 -> covered (pending VERIFY). ROADMAP Phase 05 -> executing.
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.