Jon Chery
327ba1de75
---ci--- project: acdl phase: 9 milestone: v1.1 status: plan plan: waves: 5 tasks: 9 requirements: [REQ-24, REQ-26] ---/ci--- Phase 09 plan authored by ci-planner. 5 waves, 9 files: - Wave 1 (platform): T-9.1 interface.json, T-9.2 spike_instance.json, T-9.3 registry.json, T-9.4 README.md (parallel) - Wave 2 (platform): T-9.5 adapters/terraform/adapter.py - Wave 3 (platform): T-9.6 generated terraform/spike/*.tf, T-9.7 run_spike_plan.sh, T-9.9 .gitignore (parallel) - Wave 4 (lead): T-9.8 verify_phase09.sh - Wave 5 (lead, EXECUTE-only): run real terraform plan + verify + tag Key decisions: - D-P09-1: spike runs terraform plan -lock=false (outbox table PK is contractId not LockID; plan-only doesn't write state; v1.2 creates proper acdl-tflock table) - D-P09-2: interface.json (typed contract) vs spike_instance.json (IR- schema-valid instance) - cleanly separates declaration from materialization (resolved the IR schema's inputs-are-values friction) - D-P09-3: registry at modules-ir/registry.json (co-located with L1s) - D-P09-4: generated TF committed + verify regenerates into temp + diffs
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.