continuous-intelligence/acdl
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 128 Wiki Activity
Files
v1.10.2
acdl/modules/README.md
T
Jon Chery 7585c828f0
acdl-ci / Lint (push) Successful in 7s
Details
acdl-ci / Test (push) Successful in 23s
Details
acdl-ci / Platform check-only (offline) (push) Successful in 8s
Details
docs(P48): vision gaps + badge system + substrate→engine + CR format + agentic tags 
9 requirements implemented across presentation decks and project docs:

1. DX closing slide: added 'Infrastructure as a utility, not a craft' bullet
   to convey the full vision (infrastructure consumed, not maintained;
   platform compounds value over time).
2. PW Problem slide: 'moving a merged change' → 'promoting a change'.
3. PW Problem slide: added 'Red tape' and 'Scalability without increasing
   headcount' bullets (4 frictions, not 2).
4. PW Roadmap slide: redesigned with side-by-side HTML table layout
   (Testing | Planned), 16px font, no overflow.
5. PW deck: added new slide 'What This Platform Is — and Isn't' after North
   Star (sovereign boundary, infrastructure as utility, 4 anti-goals).
   PW deck now 16 slides (was 15).
6. Maturity nomenclature: 'Available today'/'shipped' → 'Testing' across
   both decks + source markdown. New .testing badge (blue/teal #DBEAFE).
   Roadmap title: 'Testing vs. Planned'. The platform has 0 consumer
   adoption — 'shipped' was inaccurate.
7. Global: 'substrate' → 'engine' across entire project (88 matches, 30+
   files including .ciagent/, docs/, modules/, adapters/, schemas/, code).
8. Presentation files only: 'forge' → 'VCS' / 'version control system'
   (6 occurrences in 4 files). 'forge' retained in all technical docs and
   code as the industry-standard term.
9. New .agentic badge (purple/violet #EDE9FE) appended to agentic features
   in both decks: confidence signal, autonomous dev, pattern recognition,
   dynamic module creation, citizen developer surface, auto-promotion.

Also: Change Request ID format changed from 'CR-2026-001' to 'CHG0678912'
across presentation files, consumer guide, and test fixtures.

HTML re-rendered. PPTX rendered for release upload.

---ci---
phase: 48
milestone: v1.9
status: complete
requirements:
  covered: []
  partial: []
---/ci---
2026-07-23 14:58:29 +00:00

3.1 KiB
Raw Permalink Blame History

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.

Reference in New Issue View Git Blame Copy Permalink