Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
ACES Scenario Packs 2.0.2
ACES Scenario Packs 2.0.2

Definition

  • Scenario Packs
  • Golden Readiness
  • Migration Scrub Policy

Tools

  • New Pack Script
  • Pack Issue Skeleton Script

Decisions

  • Architecture Decision Records
    • ADR 0001 — Repository purpose and boundary
    • ADR 0002 — Distribute as an installable Python package bundling schemas and template
    • ADR 0003 — Build and release model
    • ADR 0004 — SBOM and supply-chain provenance
    • ADR 0005 — Automatic release on merge to main
    • ADR 0006 — Conventional-commit-driven automatic releases
    • ADR 0007 — Changelog-driven versioning (committed literal)
    • ADR 0008 — Adopt release-please
    • ADR 0009 — Scenario packs are strictly subordinate to ACES (zero extensions)
    • ADR 0010 — Consume ACES reusable-asset trust policy for pack provenance
    • ADR 0011 — Require pinned ACES SDL validation for scenario packs
    • ADR 0012 — Pack content identity consumes ACES associated-artifact manifests
    • ADR 0013 — Separate consumer static validation from author CI
    • ADR 0014 — Keep governed concept references in ACES concept-authority
    • ADR 0015 — Attest Python distribution build provenance
    • ADR 0016 — Automate dependency updates and ship ACES bumps as releases
    • ADR 0017 — Sign release tags with keyless Sigstore
    • 0018. OpenSSF Scorecard posture
    • ADR 0019 — Preserve history in dev-to-main promotions
Back to top
Copyright © Brad Edwards, MIT licensed
Made with Sphinx and @pradyunsg's Furo