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---
ecr — ECR repository
Module kind: primitive | Version: 1.0.0
A single ECR repository that hosts the container image for the ECS task. The simplest container-registry module — one resource, two inputs, two outputs.
Resources
| Resource | Type | Purpose |
|---|---|---|
| repository | aws_ecr_repository |
The ECR repository |
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name |
string | yes | — | The ECR repository name |
region |
string | yes | — | AWS region the repository is created in |
Outputs
| Name | Type | Description |
|---|---|---|
repository_url |
string | The ECR repository URL |
repository_arn |
arn | The ECR repository ARN |
Usage
{
"id": "ecr",
"type": "aws:ecr:repository",
"module": "ecr@1.0.0",
"inputs": {
"name": "acdl-microservice",
"region": "us-east-1"
}
}
The repository_url output is used to build the image input for
ecs-service (e.g. <repository_url>:latest).
Compliance extension points
- Image scanning — add
image_scanning_configuration { scan_on_push = true }for vulnerability scanning (SOC2 CC7.6, DORA ICT risk testing, security monitoring). - Encryption — add
encryption_configuration { encryption_type = "KMS", kms_key = ... }with a customer-managed key (SOC2 CC6.1, GDPR Art.32). - Image tag immutability — add
image_tag_mutability = "IMMUTABLE"to prevent tag overwriting (SOX §802, SOC2 CC6.1 integrity, DORA audit integrity). - Lifecycle policy — add
aws_ecr_lifecycle_policyto enforce image retention / cleanup (GDPR Art.5(2) data minimization, SOC2 CC5.2). - Access policy — add a repository policy restricting pull/push to known roles (SOC2 CC6.1.
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: ecr
environment: dev
inputs:
name: my-repo
region: us-east-1
Complex
A production deployment with optional inputs:
# Complex ECR with lifecycle policy + image scanning
uses: acdl/pipelines/deploy.yaml@v1.6
module: ecr
environment: dev
inputs:
name: my-production-repo
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.