Files
acdl/modules-ir/registry.json
T
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

9 lines
170 B
JSON

{
"l1-s3": {
"1.0.0": {
"interface": "modules-ir/l1/l1-s3/interface.json",
"published_at": "2026-07-21T19:00:00Z",
"deprecated": false
}
}
}