Acceptance Tests Pack & Guardrails Checklist

Audience: engineers and reviewers assembling or signing off an acceptance-test (AT) pack for a Stella Ops release gate. Purpose: a single pre-merge checklist that confirms an AT pack is deterministic, offline-reproducible, cryptographically provenanced, and enforced in CI before it can gate a release.

Use this checklist alongside the documentation-process sprint (SPRINT_0300_0001_0001_documentation_process.md, task 4 — AT1–AT10). Tick every item; an unchecked box blocks sign-off.

Pack integrity

• [ ] AT schema version is pinned; the schema file is DSSE-signed and stored with the pack.
• [ ] Inputs are locked (inputs.lock) with scanner and database versions plus all seeds.
• [ ] DSSE provenance is attached for both packs and results, and signatures are verified in CI (see pack.dsse.json).

Determinism & offline posture

• [ ] Fixtures are reproducible offline — no external network calls during the run.
• [ ] Replay parity check is documented (a second run reproduces identical results from the locked inputs).

Coverage & gating

• [ ] Admission, VEX, and auth coverage are present.
• [ ] Gating thresholds are defined and enforced in CI.
• [ ] Reporting SLOs are captured and the failure-triage path is documented.

Cross-references

• [ ] README links are added to the relevant sprint docs and module AGENTS.md files.