Jon Chery
895a2f3806
---ci--- project: acdl phase: 20 milestone: v1.5 status: specify ---/ci--- Add v1.5 milestone to ROADMAP.md + REQUIREMENTS.md. Phase 20 covers REQ-46 (README consumer model + mermaid + L3B/spike scrub), REQ-47 (generic CONSUMER_GUIDE.md + versioned uses: + consumer-scoped prereqs + run-time platform fetch), REQ-48 (zero-trust OIDC/ABAC credentials + static-key override + daily rotation), REQ-49 (reusable byte-identical deploy.yml Gitea+GitHub implementing pipelines/deploy.yaml), REQ-50 (contracts/static-asset.yaml @v1.4), REQ-51 (deploy-workflow conformance tests). Update config.json milestone to v1.5.
l2-static-asset — S3 static asset (composition being redesigned)
Module kind: L2 composition | Version: TBD | Status: Under redesign
A composition that references the l1-s3 primitive to deploy a single
S3 bucket for static asset hosting.
The composition layer is being redesigned. The previous
thin-composition implementation (a composition.json with children +
wires) has been removed. A new composition mechanism will be designed
in a later phase.
Resources
TBD — the composition will reference this L1 primitive:
| L1 module | Purpose | README |
|---|---|---|
l1-s3 |
S3 bucket | README |
Inputs
TBD — will be defined when the composition mechanism is redesigned.
Outputs
TBD — will be defined when the composition mechanism is redesigned.
Usage
TBD — the composition mechanism is being redesigned. Until then, use
l1-s3 directly. See the l1-s3 README for a
usage example.
Compliance extension points
The composition will need to wire compliance resources when the compliance milestone (GDPR, SOX, SOC2, HIPAA, DORA) lands:
- KMS key — shared encryption key for S3 SSE.
- S3 access logs — access logging to a separate audit bucket.
- Object Lock — 7-year immutable retention for evidence.
- Public access block — prevent data exfiltration.
See the l1-s3 README for per-module compliance extension points.
Versioning
Versioning will be defined when the composition mechanism is redesigned.