Jon Chery
b953fd4a8e
---ci--- phase: 1 milestone: v1.0 status: complete requirements: covered: [REQ-01, REQ-09] partial: [REQ-10, REQ-12] ---/ci--- Squash merge of phase/01-repo-scaffolding into milestone/v1.0-initial. Phase 01 ships the three-repo scaffold (acdl, acdl-contracts, acdl-evidence), the placeholder index.html on acdl-evidence (D-012/D-016 raw-URL substitute for unsupported Gitea Pages), the qa + prod branches on acdl-contracts (D-013 stand-in for unsupported Gitea environments), the workflow skeletons (pipeline.yml + issue-to-contract.yml), and the idempotent setup + verify scripts. REQ-10/12 remain partial pending Phase 04 full implementation.
55 lines
2.2 KiB
Markdown
55 lines
2.2 KiB
Markdown
# 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
|
|
|
|
1. **Act 1 — The Friction:** the old manual 2-week deployment process.
|
|
2. **Act 2 — Developer Self-Service:** commit a valid `contract.yaml` for
|
|
`l2-commodity-price-feed`, watch Dev auto-run, QA + Prod approval gates,
|
|
then the evidence timeline.
|
|
3. **Act 3 — Citizen Developer:** open a GitHub/Gitea Issue with natural-
|
|
language intent; the Python keyword parser generates the same
|
|
`contract.yaml` and triggers the identical pipeline.
|
|
4. **Act 4 — The Safety Net:** commit a malicious `contract.yaml`
|
|
(`public-ingress: true`) for `l2-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 workflows
|
|
- `acdl-contracts` — developer surface (`contract.yaml` + issue trigger)
|
|
- `acdl-evidence` — audit timeline (served via raw file URLs; Gitea has no
|
|
native Pages — see `.ciagent/ARCHITECTURE.md` Gitea 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:
|
|
|
|
```bash
|
|
ACDL_GITEA_TOKEN=<token> scripts/verify_phase01.sh
|
|
```
|
|
|
|
The script confirms:
|
|
- both new repos exist via the Gitea API
|
|
- the raw `index.html` URL on `acdl-evidence` returns HTTP 200
|
|
- the `qa` and `prod` branches exist on `acdl-contracts`
|
|
|
|
Exit 0 = Phase 01 success criteria met. |