Architecture Decision Records¶
Records of the significant, hard-to-reverse decisions for this repository. Each ADR states the context, the decision, and its consequences. ADRs are immutable once accepted; a later ADR supersedes an earlier one rather than editing it.
ADR |
Title |
Status |
|---|---|---|
Repository purpose and boundary |
Purpose/boundary superseded by 0009 |
|
Distribute as an installable Python package bundling schemas and template |
Accepted |
|
Build and release model |
Accepted |
|
SBOM and supply-chain provenance |
Accepted |
|
Automatic release on merge to main (amends 0003) |
Superseded by 0006 |
|
Conventional-commit-driven automatic releases (reusable blueprint) |
Versioning superseded by 0007 |
|
Changelog-driven versioning (reusable blueprint) |
Superseded by 0008 |
|
Adopt release-please (reusable blueprint) |
Accepted |
|
Scenario packs are strictly subordinate to ACES (zero extensions) |
Accepted |
|
Consume ACES reusable-asset trust policy for pack provenance |
Accepted |
|
Require pinned ACES SDL validation for scenario packs |
Accepted |
|
Pack content identity consumes ACES associated-artifact manifests |
Accepted |
|
Separate consumer static validation from author CI |
Accepted |
|
Keep governed concept references in ACES concept-authority |
Accepted |
|
Attest Python distribution build provenance |
Accepted |
|
Automate dependency updates and ship ACES bumps as releases |
Accepted |
|
Sign release tags with keyless Sigstore |
Accepted |
|
OpenSSF Scorecard posture |
Accepted |
|
Preserve history in dev-to-main promotions |
Accepted |