Jon Chery
7585c828f0
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---
ecs-cluster — ECS Fargate cluster
Module kind: primitive | Version: 1.0.0
An ECS Fargate cluster. The simplest ECS module — one resource, two
inputs, two outputs. The cluster is the container orchestration
boundary that ecs-service references for task placement.
Resources
| Resource | Type | Purpose |
|---|---|---|
| cluster | aws_ecs_cluster |
The ECS Fargate cluster |
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name |
string | yes | — | The ECS cluster name |
region |
string | yes | — | AWS region the cluster is created in |
Outputs
| Name | Type | Description |
|---|---|---|
cluster_arn |
arn | The ECS cluster ARN |
cluster_id |
string | The ECS cluster id (name) |
Usage
{
"id": "cluster",
"type": "aws:ecs:cluster",
"module": "ecs-cluster@1.0.0",
"inputs": {
"name": "acdl-microservice",
"region": "us-east-1"
}
}
The cluster_arn output is referenced by ecs-service as its
cluster_arn input.
Compliance extension points
- Container Insights — add
configuration { container_insights = "enabled" }for observability (SOC2 CC7.3, DORA ICT risk monitoring). - CloudWatch Logs — add a log group with retention policy for cluster-level audit logs (SOX, SOC2 CC7.2.
- Encryption — add
settings { name = "containerInsights", value = "enabled" }and KMS-based encryption for container data (GDPR Art.32).
Examples
Validated example contracts are in examples/. The platform-test
pipeline validates them against schemas/contract.schema.json.
Simple
A minimal deployment:
uses: acdl/pipelines/deploy.yaml@v1.6
module: ecs-cluster
environment: dev
inputs:
name: my-cluster
region: us-east-1
Complex
A production deployment with optional inputs:
# Complex ECS cluster with container insights
uses: acdl/pipelines/deploy.yaml@v1.6
module: ecs-cluster
environment: dev
inputs:
name: my-production-cluster
region: us-east-1
Versioning
1.0.0 — interface MAJOR, behavior MINOR, lifecycle PATCH. MAJOR bumps
require a new registry entry (immutable publication); old entries enter
a 12-month deprecation window.