# 29-Nov-2025 · Acceptance Tests Pack and Guardrails

**Why now:** Guardrail coverage (AT1–AT10) is required before Md.I ladder can proceed; acceptance packs must be deterministic, signed, and offline-ready.

## Scope
- Publish acceptance test pack schema + checklist for CI/DB/rew definitions.
- Bundle deterministic fixtures (pinned seeds, UTC timestamps) with DSSE provenance.
- Define gating thresholds and replay parity checks for admission/VEX/auth flows.

## Required artefacts (MVP for DONE)
- Advisory summary (this file) plus checklist stub under `docs/process/` referencing AT1–AT10.
- Links into sprint tracker row 4 (`SPRINT_0300_0001_0001_documentation_process.md`).
- Placeholder fixture pack path reserved under `tests/acceptance/packs/guardrails/` (no network).

## Determinism & Offline
- Freeze scanner/db versions; record in a `inputs.lock` for the pack.
- All fixtures must be reproducible from seeds; include DSSE envelopes for pack manifests.

## Next actions
- Add checklist stub and register the pack path; log evidence in sprint Execution Log before 2025-12-08.