stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 16 Releases Wiki Activity
Files
18d87c64c5dafb8fa75276ad1ae3c092fbae2de3
git.stella-ops.org/docs/product-advisories/29-Nov-2025 - Acceptance Tests Pack and Guardrails.md
StellaOps Bot 18d87c64c5 feat: add PolicyPackSelectorComponent with tests and integration 
- Implemented PolicyPackSelectorComponent for selecting policy packs.
- Added unit tests for component behavior, including API success and error handling.
- Introduced monaco-workers type declarations for editor workers.
- Created acceptance tests for guardrails with stubs for AT1–AT10.
- Established SCA Failure Catalogue Fixtures for regression testing.
- Developed plugin determinism harness with stubs for PL1–PL10.
- Added scripts for evidence upload and verification processes.
2025-12-05 21:24:34 +02:00

1.1 KiB
Raw Blame History

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.