Jon Chery
ab69d1069f
---ci--- project: acdl phase: 0 milestone: v1.1 status: complete audit_hygiene: - P1-A: config.json status specify -> complete - P1-B: PERSONAS.md 6 stale platform/ territory paths -> acdl_platform/ - P1-D: ROADMAP.md audit pending -> audit CLEAN ---/ci--- v1.1 milestone COMPLETE + audit CLEAN. Applied 3 audit-hygiene fixes (P1-A/B/D from AUDIT.md): - config.json: status specify -> complete (milestone shipped). - PERSONAS.md: 6 territory paths + 1 verification toolchain command updated platform/ -> acdl_platform/ (the Phase 08 prep rename). - ROADMAP.md: audit pending -> audit CLEAN. Remaining post-hoc P1s (non-blocking, v1.2 cleanup): - P1-1: redact two AWS access key IDs in .ciagent/VERIFY.md Phase 09 narrative (public identifiers, not secret pairs). - P1-C: document v1.1.0 tag-placement guidance in run.md (the tag is on the v1.0 Phase 05 traceability commit, causing 3 pre-specify no-ci commits to fall in the v1.1.0..HEAD range).
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.