Jon Chery
288607b3fa
---ci--- project: acdl phase: 0 milestone: v1.1 status: specify decisions: - D-034 temporary long-lived AWS key waiver (used once in Phase 08, rotated) - D-035 milestone v1.1 (feature), ship tag v1.2.0 - D-036 spike picks l1-s3 + l2-static-asset - D-037 demo archived to demo/ - D-038 open decisions resolved (accept recommendations + decide rest) ---/ci--- Ingest docs/vision.md (6 tenets, anti-goals, signals of success) and docs/architecture.md v0.2 (4 layers + 6 cross-cutting concerns incl. the substrate abstraction) as the source of truth for why/how. Reframe the project from the v1.0 stub demo (tag v1.1.0, archived to demo/ in Phase 06) to the real Agentic Cloud Delivery Platform. - config.json: milestone v1.1, status specify - PROJECT.md: vision + 4-layer/6-concern model + 11 open-decision resolutions (W1.A/B, W2.A, BA.A accepted; W3.D/E, BA.B-F, OpenTofu decided) + D-034..D-038 - ARCHITECTURE.md: target architecture (IR, confidence, ledger, HITL, SoD, substrate abstraction) + v1.1 spike scope (l1-s3 + l2-static-asset) - REQUIREMENTS.md: add REQ-16..REQ-28 + traceability - ROADMAP.md: add v1.1 Phases 06-10 (archive, arch-finalize, OIDC, IR+L1, L2+contract-e2e) - PERSONAS.md: add platform-engineer + security-engineer (custom), retire infra-stub-engineer, update territories + verification toolchain (terraform validate + jsonschema) - PLAN.md: v1.1 specify plan
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.