Jon Chery
9d35c0756c
---ci---
phase: 2
milestone: v1.0
status: clarify
decisions:
- id: D-017
decision: L1 manifest.yaml declares a flat inputs: map of named string keys + descriptions; no nested types
rationale: REQ-02/03 say 'declared inputs'; spec forbids composition and cloud-specific types
confidence: 0.90
alternatives: [JSON-schema-validated nested types, omit inputs entirely]
- id: D-018
decision: L1 mock_apply.sh reads its own manifest.yaml for self-identification but ignores the input values
rationale: D-007 mandates uniform echo + 1s sleep + exit 0; inputs are declared for traceability not consumed
confidence: 0.85
alternatives: [have mock_apply echo the input values back, parameterize sleep duration]
- id: D-019
decision: 8 L1 names fixed per REQ-02 literal
rationale: REQ-02 enumerates them; no naming freedom
confidence: 0.99
alternatives: []
---/ci---
Phase 02 ambiguities are minor (the spec is explicit). Three clarifications
logged: D-017 manifest schema (flat string map), D-018 mock_apply ignores
inputs (uniform stub), D-019 fixed L1 names.
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.