Files

T

Jon Chery c80060878a feat(P56b): author 11 L1 module terraform subdirs + fix adapter output format

EXECUTE stage. Authors the remaining 11 L1 module terraform subdirs with
the full versions/variables/locals/main/outputs split. Defaults previously
hardcoded in the adapter move into locals.tf.

Simple single-resource modules (7):
- kms-key: aws_kms_key + alias (enable_key_rotation, deletion_window defaults)
- ecr: aws_ecr_repository (encryption_configuration from kms_key_arn, image_scanning)
- ecs-cluster: aws_ecs_cluster (name default)
- iam-role: aws_iam_role + inline_policy (assume_role_policy fallback, ECR/logs policy in locals.tf)
- rds: aws_db_instance (storage_encrypted, multi_az, kms_key_arn defaults)
- waf: aws_wafv2_web_acl (default_action, visibility_config, dynamic rules)
- uptime: aws_ecs_task_definition + aws_ecs_service (Fargate compat, container_definitions in locals.tf)

Multi-resource modules with intra-refs (4):
- vpc: aws_vpc + aws_subnet + aws_internet_gateway + aws_route_table (CIDR derivation in locals.tf)
- ecs-service: aws_ecs_task_definition + aws_ecs_service (Fargate compat, container_definitions, network_config in locals.tf)
- alb: aws_lb + aws_lb_target_group + aws_lb_listener (subnet/security_group list derivation in locals.tf)
- cloudfront: aws_cloudfront_distribution + aws_cloudfront_origin_access_control (OAC defaults in locals.tf)

Registry: terraform_dir added to all 11 remaining entries.

Adapter fix: stack output format uses separate 'from' + 'output' fields
(not 'from': 'rid.output'). Fixed _emit_root_output to read both fields.

6 previously-skipped tests unblocked (run_platform.sh --check-only now
resolves static-assets.yml through the new module-assembled adapter).
Removed skip markers. Fixed test assertion (aws_s3_bucket → module).

Regression: 461 passed, 0 skipped, 5 deselected (slow). All 12 modules
pass run_primitive_plan.sh --check-only. All 12 terraform/ subdirs pass
terraform init + validate standalone.

---ci---
project: acdl
phase: P56b
milestone: v1.11
status: execute
---/ci---

2026-07-28 16:07:57 +00:00

feat(P56b): author 11 L1 module terraform subdirs + fix adapter output format

2026-07-28 16:07:57 +00:00

refactor(P57): contract surface redesign + rename + .yml repo-wide

2026-07-27 21:37:40 +00:00

.gitkeep

docs(P20): specify phase 20 — consumer happy path + reusable deploy workflow (v1.5)

2026-07-22 17:09:23 +00:00

README-TEMPLATE.md

docs(P47): presentation slide updates + HIPAA removal from all docs

2026-07-23 14:08:40 +00:00

README.md

docs(P48): vision gaps + badge system + substrate→engine + CR format + agentic tags

2026-07-23 14:58:29 +00:00

registry.json

feat(P56b): author 11 L1 module terraform subdirs + fix adapter output format

2026-07-28 16:07:57 +00:00

STANDARDS.md

feat(P56a): stateless adapter rewrite + s3 reference terraform module

2026-07-28 16:07:57 +00:00

README.md

ACDL Modules

Reusable building blocks for cloud infrastructure. Each module is self-documented with a README.md following the template.

How the modules work

There are two kinds of module:

Primitives — a single cloud resource or a small group of related resources (e.g. a VPC with subnets and routing). Each primitive has an interface.json declaring its inputs and outputs, and a README.md in plain language.
Modules — a pattern that references multiple primitives to deploy a complete stack (e.g. an ECS Fargate microservice). Each module has a composition.json declaring its children and wires.

The engine adapter (adapters/terraform/adapter.py) compiles a module instance to infrastructure. Each module's README documents which resources it creates.

Primitives

Module	What it creates	README
`s3`	`aws_s3_bucket` — a single S3 bucket	README
`vpc`	`aws_vpc` + `aws_subnet` + `aws_route_table` + `aws_internet_gateway` — VPC with subnets and routing	README
`ecs-cluster`	`aws_ecs_cluster` — ECS Fargate cluster	README
`ecs-service`	`aws_ecs_task_definition` + `aws_ecs_service` — Fargate service with task definition	README
`iam-role`	`aws_iam_role` — IAM role with assume-role policy	README
`alb`	`aws_lb` + `aws_lb_target_group` + `aws_lb_listener` — Application Load Balancer	README
`ecr`	`aws_ecr_repository` — ECR container image repository	README
`cloudfront`	`aws_cloudfront_distribution` + `aws_cloudfront_origin_access_control` — CloudFront distribution with S3 origin via OAC	README
`waf`	`aws_wafv2_web_acl` — WAFv2 Web ACL (CloudFront-scoped)	README
`rds`	`aws_db_instance` — Relational database (PostgreSQL, MySQL, etc.) with multi-engine support	README
`kms-key`	`aws_kms_key` — Customer-managed KMS key with rotation enabled (per-stack CMK)	README
`uptime`	`aws_ecs_service` — Uptime-kuma monitoring on ECS Fargate with alert channels	README

Modules

Module	What it references	README
`microservice`	6 primitives (vpc, cluster, ecr, iam-role, alb, ecs-service)	README
`static-assets`	3 primitives (s3, cloudfront, waf)	README

Registry

Module versions are tracked in registry.json. Both primitives and modules are registered.

Template

New modules should use README-TEMPLATE.md as their starting point.

Module patterns (roadmap)

The current composition.json mechanism is a thin pattern layer. A future redesign will let a consumer dynamically create a module directly from the contract file (an agentic "composition" flow). That is on the roadmap, not implemented today.