baselines

Release-line baselines

This directory holds invariant baseline artifacts for the v0.13.0 release line. The artifacts are descriptive snapshots of what v0.13.0 ships, not aspirational roadmap documents. Each artifact is file-suffixed by version (<NAME>-v0.13.0.md) so future release lines can land their own baselines alongside without renaming or overwriting the v0.13.0 set.

Contents

Artifact	Purpose
BASELINE-v0.13.0.md	Released-package surface, wire-format invariants, and resource-limit invariants pinned at v0.13.0.
ERROR-EMISSION-AUDIT-v0.13.0.md	Per-code classification of specs/kernel/errors.json: emitted in production, tests-only, unreferenced. Advisory.
ERROR-EMISSION-AUDIT-v0.13.0.json	Machine-readable counterpart to the above. Regenerated by pnpm audit:errors:write.
MUTATION-BASELINE-v0.13.0.md	Mutation-testing posture for v0.13.0. Advisory; not CI-wired.

Adjacent normative documents that these artifacts reference but live outside this directory:

• docs/specs/RESOURCE-LIMITS.md - normative invariant table for every size, time, and cache ceiling.
• docs/STANDARDS_LEDGER.md - status table for every external standard PEAC cites.
• docs/STABILITY-CONTRACT.md - classification of every public surface PEAC publishes.
• docs/THREAT_MODEL.md - per-threat mitigation table with test coverage.

Regeneration

The error-emission audit is generated:

pnpm audit:errors:write

The mutation baseline is run locally (not in CI):

pnpm mutation:baseline

The baseline doc itself, the resource-limits doc, and the standards ledger are hand-maintained. CI enforces several invariants on these files:

• scripts/verify-trust-artifacts.mjs checks that every linked test path under docs/THREAT_MODEL.md resolves to a tracked file and that public docs do not link to the gitignored reference/ tree.
• scripts/release/api-surface-lock.sh checks that every export named in the baseline's "Public API" table stays byte-stable in the per-package snapshot under docs/releases/api-surface/.