Jon Chery
faea213a4c
docs(P16): post-ship traceability + roadmap update (v1.2.6)
...
---ci---
project: acdl
phase: 16
milestone: v1.2
status: shipped
---/ci---
Post-ship: ROADMAP.md Phase 16 -> complete (v1.2.6); REQUIREMENTS.md
REQ-35 -> partial (v1.2.6, IAM-blocked). All 6 v1.2 phases shipped.
2026-07-21 22:24:48 +00:00
Jon Chery
3cca5bb43f
docs(P15): post-ship traceability + roadmap update (v1.2.5, PARTIAL)
...
---ci---
project: acdl
phase: 15
milestone: v1.2
status: shipped
---/ci---
Post-ship: ROADMAP.md Phase 15 -> complete (v1.2.5, PARTIAL); REQUIREMENTS.md
REQ-33 -> partial (IAM-blocked), REQ-34 -> complete (v1.2.5).
2026-07-21 22:22:03 +00:00
Jon Chery
d5cc01edbd
docs(P14): post-ship traceability + roadmap update (v1.2.4)
...
---ci---
project: acdl
phase: 14
milestone: v1.2
status: shipped
---/ci---
Post-ship: ROADMAP.md Phase 14 -> complete (v1.2.4); REQUIREMENTS.md
REQ-32 -> complete (v1.2.4).
2026-07-21 21:12:33 +00:00
Jon Chery
7c6b8c8c84
docs(P13): post-ship traceability + roadmap update (v1.2.3)
...
---ci---
project: acdl
phase: 13
milestone: v1.2
status: shipped
---/ci---
Post-ship: ROADMAP.md Phase 13 -> complete (v1.2.3); REQUIREMENTS.md
REQ-31 -> complete (v1.2.3).
2026-07-21 21:06:08 +00:00
Jon Chery
4c8de8e962
docs(P12): post-ship traceability + roadmap update (v1.2.2)
...
---ci---
project: acdl
phase: 12
milestone: v1.2
status: shipped
---/ci---
Post-ship: ROADMAP.md Phase 12 -> complete (v1.2.2); REQUIREMENTS.md
REQ-30 -> complete (v1.2.2).
2026-07-21 21:02:08 +00:00
Jon Chery
7ee57aa6c7
docs(P11): post-ship traceability + roadmap update (v1.2.1)
...
---ci---
project: acdl
phase: 11
milestone: v1.2
status: shipped
---/ci---
Post-ship: ROADMAP.md Phase 11 -> complete (v1.2.1); REQUIREMENTS.md
REQ-29 -> complete (v1.2.1).
2026-07-21 20:58:01 +00:00
Jon Chery
9504782a77
docs(specify): open v1.2 milestone — platform hardening + ECS microservice
...
---ci---
project: acdl
phase: 0
milestone: v1.2
status: specify
decisions:
- id: D-047
decision: Extend D-039 per-run-rotated-key waiver for v1.2; real OIDC deferred to v1.3+
rationale: go-gitea/gitea#36988 still open (re-checked 2026-07-21, last updated 2026-05-27, not merged)
confidence: 0.95
alternatives: []
---/ci---
Open the v1.2 milestone: platform hardening + first real consumer deployment.
5 scope axes (user-directed): re-eval #36988 , NFR improvements, simplify
the setup, README rewrite, bootstrap a consumer repo with a basic
microservice deployed to ECS Fargate end-to-end.
Files:
- config.json: milestone v1.1 -> v1.2, status complete -> specify
- PROJECT.md: v1.1 objective -> prior (complete); new v1.2 objective +
6-phase table (11-16) + REQ-29..35 summary + D-047
- REQUIREMENTS.md: v1.1 -> prior (complete); new v1.2 section with
REQ-29..35 + traceability (planned)
- ROADMAP.md: v1.1 -> complete (tag v1.2.0, Gitea release 202); new v1.2
section with 6 phases (status planned, ship v1.3.0)
- ARCHITECTURE.md: new "v1.2 build-out scope" section (5 axes, substrate
extension, terraform apply dev-only, out-of-scope deferrals) + build
order
Ship tag at milestone COMPLETE: v1.3.0 (feature milestone, next minor
per ship.md — v1.1 shipped v1.2.0). Phase patches v1.2.1..v1.2.6.
2026-07-21 20:54:55 +00:00
Jon Chery
d3aa960eb8
docs(P10): post-ship traceability + roadmap update (v1.1.5)
...
---ci---
project: acdl
phase: 10
milestone: v1.1
status: shipped
requirements:
complete: [REQ-25, REQ-27, REQ-28]
release:
tag: v1.1.5
---/ci---
ROADMAP Phase 10 -> complete (v1.1.5). REQUIREMENTS REQ-25/27/28 -> complete.
The end-to-end spike pipeline succeeds: contract -> IR -> terraform plan
(real AWS) -> Checkov -> confidence (pass) -> outbox. REQ-28 verified: the
adapter is the only substrate-specific code (the IR commitments hold).
2026-07-21 19:39:19 +00:00
Jon Chery
4c9314710b
docs(P09): post-ship traceability + roadmap update (v1.1.4)
...
---ci---
project: acdl
phase: 9
milestone: v1.1
status: shipped
requirements:
complete: [REQ-24, REQ-26]
release:
tag: v1.1.4
---/ci---
ROADMAP Phase 09 -> complete (v1.1.4). REQUIREMENTS REQ-24/26 -> complete.
The IR-typed L1 module l1-s3 + the Terraform adapter compile to a real
terraform plan against AWS (plan-only, -lock=false per D-P09-1, rotated
spike key per D-039).
2026-07-21 19:17:30 +00:00
Jon Chery
96ab42fde1
docs(P08): post-ship traceability + roadmap update (v1.1.3)
...
---ci---
project: acdl
phase: 8
milestone: v1.1
status: shipped
requirements:
complete: [REQ-23]
release:
tag: v1.1.3
---/ci---
ROADMAP Phase 08 -> complete (v1.1.3). REQUIREMENTS REQ-23 -> complete.
S3 state bucket + DynamoDB outbox table + IAM user acdl-spike-runner
with least-privilege scoped policy + rotated spike key all created and
verified. D-034 closure: user must manually rotate the root key now.
2026-07-21 19:02:26 +00:00
Jon Chery
412e1ef62e
phase: 7, status: plan-as-execute, persona: lead-developer, task: T-7.10
...
---ci---
project: acdl
phase: 7
milestone: v1.1
status: plan-as-execute
persona: lead-developer
task: T-7.10
---/ci---
Wave 5: scripts/verify_phase07.sh + traceability.
verify_phase07.sh asserts all 9 deliverable files exist, 3 JSON Schemas
validate as Draft 2020-12 (run from /tmp to avoid the repo platform/
package shadowing stdlib platform which jsonschema's uuid import needs),
3 .py files py_compile, 3 .md files non-empty, all 11 decision IDs +
OpenTofu in PROJECT.md, architecture-v1.0.md status is v1.0, D-040..D-044
present, spike contract validates against contract schema, minimal IR
validates against IR schema. All checks pass: 'VERIFIED - Phase 07:
architecture v1.0 finalized; 6 files authored + 11 decisions resolved'.
Traceability: REQUIREMENTS REQ-16..22 -> complete (v1.1.2); ROADMAP
Phase 07 -> complete (v1.1.2).
2026-07-21 18:47:58 +00:00
Jon Chery
930c24be6d
docs(research): OIDC blocker found; adopt D-039..D-046; re-scope Phase 08
...
---ci---
project: acdl
phase: 0
milestone: v1.1
status: research
research_targets: 10
top_finding:
- TARGET 1 (conf 0.95): Gitea Actions does NOT support id-token: write / OIDC.
Real OIDC deferred to v1.2 (blocked on go-gitea/gitea#36988).
Spike adopts D-039: per-run-rotated long-lived key waiver.
decisions_adopted: [D-039, D-040, D-041, D-042, D-043, D-044, D-045, D-046]
risks:
- R-1 (highest): OIDC gap -> key-rotation waiver (mitigated by D-039)
- R-2: Checkov terraform_plan edge cases (mitigated by ACDL_TAG_NAMING skipped record)
- R-3: 6 confidence inputs are a recommendation (D-040 adopted in PROJECT.md)
---/ci---
RESEARCH.md (1330 lines) authored by ci-researcher. Key findings:
- TARGET 1: Gitea Actions does NOT support emitting an OIDC id-token
(Gitea docs list id-token as unsupported; go-gitea/gitea#33681 open;
draft PR #36988 unmerged; Gitea's own CI still uses long-lived keys
per #37980 ). Real-AWS OIDC is unachievable in this environment for v1.1.
- TARGETS 2-10: Terraform/Checkov install steps, IR prior art, Checkov
adapter, DynamoDB outbox, 6-input confidence signal, tiered ledger
(Object Lock deferred), HITL/SoD, contract schema, archive strategy
— all resolved with concrete sketches in RESEARCH.md.
Adopted D-039..D-046 in PROJECT.md. Re-scoped Phase 08 (ROADMAP) and
REQ-23 (REQUIREMENTS) to reflect the OIDC blocker: the spike uses a
per-run-rotated long-lived key (D-039) instead of OIDC; real OIDC is a
v1.2 deliverable. ARCHITECTURE.md Gitea API surface table updated with
the OIDC verdict.
2026-07-21 18:03:41 +00:00
Jon Chery
288607b3fa
docs(specify): ingest docs/vision+architecture; reframe .ciagent for v1.1
...
---ci---
project: acdl
phase: 0
milestone: v1.1
status: specify
decisions:
- D-034 temporary long-lived AWS key waiver (used once in Phase 08, rotated)
- D-035 milestone v1.1 (feature), ship tag v1.2.0
- D-036 spike picks l1-s3 + l2-static-asset
- D-037 demo archived to demo/
- D-038 open decisions resolved (accept recommendations + decide rest)
---/ci---
Ingest docs/vision.md (6 tenets, anti-goals, signals of success) and
docs/architecture.md v0.2 (4 layers + 6 cross-cutting concerns incl. the
substrate abstraction) as the source of truth for why/how. Reframe the
project from the v1.0 stub demo (tag v1.1.0, archived to demo/ in Phase 06)
to the real Agentic Cloud Delivery Platform.
- config.json: milestone v1.1, status specify
- PROJECT.md: vision + 4-layer/6-concern model + 11 open-decision
resolutions (W1.A/B, W2.A, BA.A accepted; W3.D/E, BA.B-F, OpenTofu
decided) + D-034..D-038
- ARCHITECTURE.md: target architecture (IR, confidence, ledger, HITL, SoD,
substrate abstraction) + v1.1 spike scope (l1-s3 + l2-static-asset)
- REQUIREMENTS.md: add REQ-16..REQ-28 + traceability
- ROADMAP.md: add v1.1 Phases 06-10 (archive, arch-finalize, OIDC, IR+L1,
L2+contract-e2e)
- PERSONAS.md: add platform-engineer + security-engineer (custom),
retire infra-stub-engineer, update territories + verification toolchain
(terraform validate + jsonschema)
- PLAN.md: v1.1 specify plan
2026-07-21 17:55:09 +00:00
Jon Chery
58adf9e231
docs(P05): post-ship traceability + roadmap update (v1.0.5)
...
---ci---
phase: 5
milestone: v1.0
status: shipped
requirements:
complete: [REQ-13, REQ-14, REQ-15]
release:
tag: v1.0.5
pr: 5
---/ci---
ROADMAP Phase 05 -> complete (v1.0.5). REQUIREMENTS REQ-13/14/15 -> complete.
All 5 phases of milestone v1.0 are now complete. Next: the COMPLETE gate
(review -> ship(milestone v1.1.0) -> audit).
2026-07-21 13:54:41 +00:00
grimacing
0672edfc3f
ship: phase-05 evidence-ui-and-demo-dry-run (v1.0.5)
...
Squash merge of phase/05-evidence-ui-and-demo-dry-run; evidence-ui/index.html + run_demo.sh 4-act simulation + verify_phase05.sh; demo live at acdl-evidence raw URL.
2026-07-21 13:53:54 +00:00
Jon Chery
1415c85d35
docs(P04): post-ship traceability + roadmap update (v1.0.4)
...
---ci---
phase: 4
milestone: v1.0
status: shipped
requirements:
complete: [REQ-10, REQ-12]
release:
tag: v1.0.4
pr: 4
---/ci---
ROADMAP Phase 04 -> complete (v1.0.4). REQUIREMENTS REQ-10/12 -> complete.
Phase 04 was the last 'skeleton-filling' phase; Phase 05 builds the
evidence UI and runs the 4 demo acts end-to-end.
2026-07-21 13:43:07 +00:00
grimacing
72b359c9a9
ship: phase-04 pipeline-and-approval-gates (v1.0.4)
...
Squash merge of phase/04-pipeline-and-approval-gates; pipeline.yml + issue-to-contract.yml + finalize_evidence.py; verify_phase04.sh green; 1 P0 fixed (shell injection).
2026-07-21 13:42:25 +00:00
Jon Chery
711b61d63e
docs(P03): post-ship traceability + roadmap update (v1.0.3)
...
---ci---
phase: 3
milestone: v1.0
status: shipped
requirements:
complete: [REQ-04, REQ-05, REQ-06, REQ-07, REQ-08, REQ-11]
partial: [REQ-12]
release:
tag: v1.0.3
pr: 3
---/ci---
ROADMAP Phase 03 -> complete (v1.0.3). REQUIREMENTS: REQ-04/05/06/07/08/11
-> complete; REQ-12 -> partial (full issue-trigger wiring in Phase 04).
2026-07-21 13:33:18 +00:00
grimacing
3ea36ef3ab
ship: phase-03 l2-modules-and-core-scripts (v1.0.3)
...
Squash merge of phase/03-l2-modules-and-core-scripts; 4 L2s + 5 core scripts; verify_phase03.sh green.
2026-07-21 13:32:21 +00:00
Jon Chery
6e27df7404
docs(P02): post-ship traceability + roadmap update (v1.0.2)
...
---ci---
phase: 2
milestone: v1.0
status: shipped
requirements:
complete: [REQ-02, REQ-03]
release:
tag: v1.0.2
pr: 2
---/ci---
ROADMAP Phase 02 -> complete (v1.0.2). REQUIREMENTS REQ-02/03 -> complete.
2026-07-21 13:18:51 +00:00
grimacing
00d0043866
ship: phase-02 l1-modules (v1.0.2)
...
Squash merge of phase/02-l1-modules into milestone/v1.0-initial; 8 L1 stub modules created; verify_phase02.sh green.
2026-07-21 13:18:12 +00:00
Jon Chery
fd423e2df1
docs(P01): post-ship traceability + roadmap update (v1.0.1)
...
---ci---
phase: 1
milestone: v1.0
status: shipped
requirements:
complete: [REQ-01, REQ-09]
partial: [REQ-10, REQ-12]
release:
tag: v1.0.1
url: https://git.cloudinit.dev/continuous-intelligence/acdl/releases/tag/v1.0.1
pr: 1
---/ci---
ROADMAP Phase 01 -> complete (v1.0.1). REQUIREMENTS REQ-01/09 -> complete;
REQ-10/12 -> partial (full impl in Phase 04).
2026-07-21 13:12:01 +00:00
Jon Chery
b953fd4a8e
docs(P01): complete repo-scaffolding phase
...
---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.
2026-07-21 13:10:50 +00:00
Jon Chery
e5f5604319
decision(P01): clarification — project mode, pages fallback, env gates
...
---ci---
phase: 1
milestone: v1.0
status: clarify
decisions:
- id: D-011
decision: Single-project mode explicitly enforced via config.json mode=single
rationale: run.md Step 0 reads projects[] length as multi-project trigger; explicit flag disambiguates from D-010
confidence: 0.95
alternatives: [move acdl into .ciagent/acdl/ subdirectory and adopt multi-project paths]
- id: D-012
decision: Gitea has no native Pages; serve acdl-evidence via raw file URLs + CORS note
rationale: Research confirms Gitea has no [pages] section; raw URLs work without server config
confidence: 0.85
alternatives: [sidecar static server, external Pages host]
- id: D-013
decision: QA/Prod gates modeled as workflow_dispatch approval inputs (D-004 fallback) instead of Gitea environments
rationale: Research confirms Gitea ignores environment: blocks and exposes no environments API
confidence: 0.90
alternatives: [external approval bot, drop approval gates entirely]
- id: D-014
decision: Cross-repo triggering uses workflow_dispatch API from inside a step (no repository_dispatch)
rationale: Gitea Actions does not support repository_dispatch
confidence: 0.85
alternatives: [push-based trigger with a sentinel file, polling]
- id: D-015
decision: New repos acdl-contracts and acdl-evidence use default_branch=main with auto_init=true
rationale: Matches Gitea DEFAULT_BRANCH=main; required for the default branch to exist before any push
confidence: 0.95
alternatives: [use milestone/v1.0-initial as default_branch]
- id: D-016
decision: Pages placeholder for Phase 01 is a minimal HTML stub; full timeline UI deferred to Phase 05
rationale: Phase 01 success criterion is the URL returns 200 with placeholder; full UI is Phase 05
confidence: 0.90
alternatives: [build a minimal timeline now]
---/ci---
Clarifications accepted at full autonomy per clarify.md Step 4. Three requirements
re-stated: REQ-09 (new repos default_branch=main), REQ-10 Pages (raw-URL 200
substitute), REQ-10 environments (workflow_dispatch inputs + qa/prod branches).
See .ciagent/REQUIREMENTS.md Clarifications table.
2026-07-21 12:57:50 +00:00
Jon Chery
e3416f8e77
docs(init): initialize Agentic Cloud Delivery Platform (5 phases)
...
---ci---
phase: 0
milestone: v1.0
status: specify
decisions:
- id: D-001
decision: Use Gitea org continuous-intelligence for all ACDL repos
rationale: User-specified target org; already exists at git.cloudinit.dev
confidence: 0.95
alternatives: [new dedicated demo org]
- id: D-002
decision: Map "GitHub Actions" to Gitea Actions (act_runner) using same workflow YAML
rationale: Environment is Gitea; syntax-compatible with act_runner
confidence: 0.85
alternatives: [migrate to GitHub.com, raw shell scripts]
- id: D-003
decision: Collapse acdl-platform into the existing empty acdl repo
rationale: acdl already exists at org root; avoids a 4th repo
confidence: 0.90
alternatives: [create separate acdl-platform repo]
- id: D-004
decision: Use Gitea environment blocks + required reviewers for QA/Prod; fallback to manual workflow_dispatch with approval input
rationale: Spec mandates approval gates; forge supports environment protection
confidence: 0.80
alternatives: [external approval bot, no approval gates]
- id: D-005
decision: Hash-chained ledger (prev_hash + own hash via SHA-256 of canonical JSON) for evidence; declared demonstrative not adversarially secure
rationale: Spec asks for simple JSON; chain gives visible tamper-evidence
confidence: 0.85
alternatives: [signed commits only, full Merkle tree]
- id: D-006
decision: Confidence gate threshold = 0.50 exactly (base 0.90, fail drops to 0.40)
rationale: Explicit in spec
confidence: 0.99
alternatives: []
- id: D-007
decision: Each mock_apply.sh echoes "[L1: <name>] applying..." + "OK", sleeps 1s, exits 0
rationale: Spec literal; uniformity aids timeline parsing
confidence: 0.95
alternatives: [randomized sleep durations]
- id: D-008
decision: L3B keyword->stack mapping: gas/price/ingest/data-lake->commodity-price-feed; invoice/billing->invoice-service; analytics/historical/query->energy-analytics-api; regulatory/compliance/reporting/trading->regulatory-reporting; fallback->invoice-service
rationale: Mirrors the 4 L2 modules + Act 3 example issue text
confidence: 0.85
alternatives: [single default stack, ML classifier (forbidden by no-AI constraint)]
- id: D-009
decision: Init milestone = v1.0, branch milestone/v1.0-initial
rationale: init.md Step 5 mandates milestone/v1.0-initial
confidence: 0.99
alternatives: []
- id: D-010
decision: Single-project mode for the acdl checkout; ---ci--- blocks omit project field
rationale: User chose standalone single-project; no other projects in this checkout
confidence: 0.90
alternatives: [register acdl in /root multi-project config]
---/ci---
Specification: 30-minute executive demo of the Agentic Cloud Delivery Platform proving automatic, safe, audited infra delivery via local stubs on Gitea Actions (no cloud, no AI APIs).
Requirements: [3 repos under continuous-intelligence org, 8 L1 stub modules, 4 L2 composed modules mirroring S&P Global Energy use cases, 5 core scripts (mock_executor.sh, policy_checker.py, confidence_signal.py, evidence_writer.py, l3b_agent_stub.py), reusable Dev->QA->Prod pipeline with approval gates, issue-triggered L3B agent, Pages evidence timeline UI, 4 scripted demo acts]
Constraints: [local Linux OS, Gitea Actions + Environments, no AWS/GCP/Azure, no external LLM APIs, state in flat JSON/artifacts, EKS Fargate + serverless primitives (no VPC module), L1 single-purpose substrate-agnostic max-depth-1, L2 max-depth-5]
Out of scope: [real cloud provisioning, real LLM inference, production-grade infrastructure, adversarial tamper-proofing of evidence]
2026-07-21 12:46:33 +00:00