Architecture Decision Records
| ADR | Title | Status |
|---|---|---|
| ADR-001 | Module naming: kebab-case | Accepted |
| ADR-002 | Registry structure: oceansoft/terraform-aws/aws | Accepted |
| ADR-003 | Provider constraints: >= 6.28, < 7.0; terraform >= 1.11.0 | Accepted |
| ADR-004 | 3-tier testing: snapshot/localstack/integration | Accepted |
| ADR-005 | Example naming: {tier}-{descriptor} (mvp-/poc-/production-) | Accepted |
| ADR-006 | S3 native state locking (no DynamoDB) | Accepted |
| ADR-007 | Upstream dependency strategy: aws-ia fork + rebrand | Accepted |
| ADR-008 | Tag governance: Enterprise + FOCUS 1.2+ co-existence strategy | Proposed |
| ADR-009 | act .actrc platform mapping | Proposed |
| ADR-010 | ci:act task: full pipeline expansion + PATH injection | Proposed |
| ADR-011 | act advisory dry-run + artifact server for non-ci workflows | Proposed |
| ADR-012 | Local dev source override pattern for projects/ | Proposed |
| ADR-013 | build:validate + lock file scope expansion to projects/ | Proposed |
| ADR-014 | Priority examples for cross-validation | Proposed |
| ADR-015 | Root VERSION file update procedure (HITL gate) | Proposed |
| ADR-016 | CHANGELOG entries for version gap (HITL content) | Proposed |
| ADR-018 | Registry publish pre-flight checklist + HITL execution sequence | Proposed |
| ADR-019 | MCP cross-validation post-Registry-publish | Proposed |
| ADR-020 | Break-glass emergency access pattern | Accepted |
| ADR-021 | Documentation SSOT strategy (DevOps-TechDocs authoritative) | Accepted |
| ADR-022 | Release management automation (release-please + per-module tags) | Accepted |
| ADR-023 | Derived module pattern (clone + value-add) | Accepted |
| ADR-024 | Composition layer pattern (modules/web) | Accepted |
| ADR-025 | Per-component semver versioning | Accepted |
| ADR-026 | Registry & versioning strategy (GitHub source + unified version) | Accepted |
| ADR-027 | 3-phase cost model: LOCAL ($0) → Scenario 1 ($78-94/mo) → Scenario 2 ($150-180/mo) | Accepted |
Process
- Naming:
ADR-NNN-kebab-case-title.md - Lifecycle: Proposed → Accepted → Deprecated → Superseded
- Format: 5W1H (What, Why, Who, When, Where, How)