Jon Chery
cc4c27c8ab
---ci--- project: acdl phase: 10 milestone: v1.1 status: plan plan: waves: 5 tasks: 9 requirements: [REQ-25, REQ-27, REQ-28] ---/ci--- Phase 10 plan (milestone capstone). 5 waves, 9 files: - Wave 1 (platform): L2 composition + registry + adapter L2 extension (D-P10-1) - Wave 2 (backend): contract spike.yaml + contract_resolver.py + outbox_writer.py - Wave 3 (backend+security+platform): run_spike_e2e.sh (10-step pipeline) - Wave 4 (lead): verify_phase10.sh (incl. REQ-28 substrate-agnostic grep) - Wave 5 (EXECUTE-only): run e2e against real AWS + verify + ship Key decisions: D-P10-1 (adapter consumes resolved IR instance; L2 root module = L1 resource for depth-1), D-P10-2 (YAML contract + JSON Schema validation), D-P10-3 (single CONFIDENCE_COMPUTED event; GENESIS chain). REQ-28 binding claim: only adapters/ files contain aws_s3_bucket / aws_ Terraform-specific terms; modules-ir/ schemas/ contracts/ acdl_platform/ are substrate-agnostic.
ACDL — Agentic Cloud Delivery Platform
Consumers declare intent; the platform delivers safe production deployment through an agentic stack — automatically, safely, and with a complete audit trail. A merged change progresses through lower environments end-to-end without a platform engineer joining a thread; a non-technical consumer ships a production deployment by declaring intent, without authoring a workflow, a configuration file, or a Terraform module.
- Vision (the why):
docs/vision.md - Architecture (the how):
docs/architecture.md - Decisions:
.ciagent/PROJECT.md - Target architecture:
.ciagent/ARCHITECTURE.md - Phase plan:
.ciagent/ROADMAP.md
Status
- v1.1 (active): architecture finalization + v1 spike. Finalize the
architecture to v1.0 (resolve the 11 open design decisions) and prove the
locked commitments with one end-to-end implementation spike
(
l1-s3+l2-static-asset+ Terraform adapter → realterraform planagainst AWS). - v1.0 demo (complete, archived): tag
v1.1.0. The 30-minute stub-driven executive demo is preserved underdemo/as the intent reference; it is not the platform.
Repository layout
| Path | Purpose | Populated |
|---|---|---|
acdl_platform/ |
Platform code: confidence signal, contract resolver, outbox, HITL/ledger designs (renamed from platform/ in Phase 08 to avoid shadowing the stdlib platform module) |
Phase 07+ |
schemas/ |
JSON Schemas: IR, PolicyCheckResult, contract | Phase 07 |
adapters/ |
Substrate adapters (Terraform adapter in v1; the only substrate-specific code per §12) | Phase 09 |
terraform/ |
State backend + provider config (S3 state + DynamoDB lock) | Phase 08+ |
modules-ir/ |
IR-typed L1/L2 modules (l1-s3, l2-static-asset) |
Phase 09–10 |
scripts/ |
v1.1 verify scripts (verify_phaseNN.sh) |
Phase 06+ |
demo/ |
Archived v1.0 executive demo (tag v1.1.0); runs locally via demo/scripts/run_demo.sh --no-upload |
complete |
.ciagent/ |
CIAgent metadata (plans, decisions, personas, roadmap, research) | active |
docs/ |
Upstream vision + architecture sources | active |
Running the archived demo
The v1.0 demo is an archived artifact. To re-run it locally:
bash demo/scripts/run_demo.sh --no-upload
The demo deck is at demo/ACDL_DEMO.md. The demo runs
entirely on local stubs — no AWS, no AI — and shows intent and safety
behavior rather than provisioning real cloud resources. It is the reference
of intent for the real platform; it is not the platform itself.