continuous-intelligence/acdl

Fork 0

Commit Graph

Author	SHA1	Message	Date
Jon Chery	3508671377	refactor(modules): remove thin-composition layer; rewrite all module READMEs The L2 thin-composition layer (composition.json + contract_resolver.py + contract schema + sample contracts) has been removed completely. The implementation was unsatisfactory and is deferred for a later redesign. - Delete: composition.json x2, contract_resolver.py, contracts/ x2, contract.schema.json - Patch: run_platform.sh now loads a pre-existing IR instance instead of resolving a contract (the downstream adapter/checkov/confidence/outbox pipeline is unchanged) - Prune: L2 entries removed from registry.json (L1 entries unchanged) - Rewrite: all 7 L1 module READMEs in plain language (no jargon), each with Resources/Inputs/Outputs/Usage/Compliance-extension-points/Versioning sections derived from interface.json - Add: 2 L2 placeholder READMEs noting the composition is under redesign - Add: modules-ir/README.md catalog index + README-TEMPLATE.md ---ci--- project: acdl phase: 17 milestone: v1.3 status: execute ---/ci---	2026-07-22 13:54:40 +00:00
Jon Chery	e054a95fd5	phase: 9, status: plan-as-execute, persona: platform-engineer, task: T-9.1..T-9.4 ---ci--- project: acdl phase: 9 milestone: v1.1 status: plan-as-execute persona: platform-engineer task: [T-9.1, T-9.2, T-9.3, T-9.4] requirements.covered: [REQ-24] ---/ci--- Wave 1: the IR-typed L1 module l1-s3. - T-9.1: modules-ir/l1/l1-s3/interface.json - the L1 interface contract (typed inputs bucket_name/region, outputs bucket_arn/bucket_name, NFR versioning; type aws:s3:bucket). Per D-P09-2 this is a contract (typed declarations), NOT an IR-schema instance. - T-9.2: modules-ir/l1/l1-s3/spike_instance.json - a concrete stack instance with values (bucket_name=acdl-spike-bucket, region=us-east-1) that validates against schemas/ir.schema.json (verified). - T-9.3: modules-ir/registry.json - the L1 registry, one entry l1-s3@1.0.0 -> interface.json (D-P09-3, co-located with modules-ir/). - T-9.4: modules-ir/l1/l1-s3/README.md - the L1 doc + the IR->Terraform mapping table the adapter performs. Spike instance validates against ir.schema.json; interface + registry valid JSON.	2026-07-21 19:13:31 +00:00

Author

SHA1

Message

Date

Jon Chery

3508671377

refactor(modules): remove thin-composition layer; rewrite all module READMEs

The L2 thin-composition layer (composition.json + contract_resolver.py +
contract schema + sample contracts) has been removed completely. The
implementation was unsatisfactory and is deferred for a later redesign.

- Delete: composition.json x2, contract_resolver.py, contracts/ x2,
  contract.schema.json
- Patch: run_platform.sh now loads a pre-existing IR instance instead of
  resolving a contract (the downstream adapter/checkov/confidence/outbox
  pipeline is unchanged)
- Prune: L2 entries removed from registry.json (L1 entries unchanged)
- Rewrite: all 7 L1 module READMEs in plain language (no jargon), each
  with Resources/Inputs/Outputs/Usage/Compliance-extension-points/Versioning
  sections derived from interface.json
- Add: 2 L2 placeholder READMEs noting the composition is under redesign
- Add: modules-ir/README.md catalog index + README-TEMPLATE.md

---ci---
project: acdl
phase: 17
milestone: v1.3
status: execute
---/ci---

2026-07-22 13:54:40 +00:00

Jon Chery

e054a95fd5

phase: 9, status: plan-as-execute, persona: platform-engineer, task: T-9.1..T-9.4

---ci---
project: acdl
phase: 9
milestone: v1.1
status: plan-as-execute
persona: platform-engineer
task: [T-9.1, T-9.2, T-9.3, T-9.4]
requirements.covered: [REQ-24]
---/ci---

Wave 1: the IR-typed L1 module l1-s3.

- T-9.1: modules-ir/l1/l1-s3/interface.json - the L1 interface contract
  (typed inputs bucket_name/region, outputs bucket_arn/bucket_name, NFR
  versioning; type aws:s3:bucket). Per D-P09-2 this is a contract (typed
  declarations), NOT an IR-schema instance.
- T-9.2: modules-ir/l1/l1-s3/spike_instance.json - a concrete stack
  instance with values (bucket_name=acdl-spike-bucket, region=us-east-1)
  that validates against schemas/ir.schema.json (verified).
- T-9.3: modules-ir/registry.json - the L1 registry, one entry
  l1-s3@1.0.0 -> interface.json (D-P09-3, co-located with modules-ir/).
- T-9.4: modules-ir/l1/l1-s3/README.md - the L1 doc + the IR->Terraform
  mapping table the adapter performs.

Spike instance validates against ir.schema.json; interface + registry
valid JSON.

2026-07-21 19:13:31 +00:00

2 Commits