Jon Chery
68d90c08a7
---ci--- project: acdl phase: 7 milestone: v1.1 status: plan-as-execute persona: backend-engineer+security-engineer task: T-7.9 requirements.covered: [REQ-19] ---/ci--- Wave 4 (co-authored): platform/confidence_signal.py (REQ-19). backend-engineer: 6-input weighted sum (WEIGHTS = policy 0.30, validation 0.25, freshness 0.10, source 0.15, history 0.10, nfrs 0.10 per D-040; sums to 1.0), per-env thresholds (dev 0.50, qa 0.75, prod 0.90, dr 0.95), _per_input_score rules, compute() orchestration, Signal dataclass, dev-warn->block flip (autonomous, no reviewer). security-engineer: PENALTY dict (critical=None hard-override sentinel, high 0.20, medium 0.05, low 0.01, info 0.0), critical-override short-circuit return in compute(), severity penalty loop over the policy input's failing PolicyCheckResult records. Verified: missing input -> block + INPUT_MISSING:<name>; critical fail -> 0.0 block + CRITICAL_OVERRIDE:<ruleId>; cold-start spike dev (ACDL _TAG_NAMING skipped, all validation true, nfrs neutral 0.5) -> 0.95 pass. stdlib only.
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 |
|---|---|---|
platform/ |
Platform code: confidence signal, contract resolver, outbox, HITL/ledger designs | 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.