EngineeringSpec v0.1.0-rc.12 — Routing-derived evidence
Pre-release
Pre-release
EngineeringSpec v0.1.0-rc.12
RC12 makes EngineeringSpec’s evidence layer use the same immutable, repository-wide routing decision as enforcement.
What’s new
- Added deterministic
concrete-paths-v2measurement receipts - Added canonical candidate-set, routing-decision and path-set digests
- Measurement now loads every approved contract from the immutable base
- Requested contracts are projections over repository routing, not separate authority
- Corrected finite authority calculations, including unexercised exact create paths
- Retains paths selected for other contracts, denied, ambiguous or uncovered
- Added stronger paired-run provenance for prompts, revisions, agents, harnesses, timestamps and review blinding
- Added scope-measurement schema 0.2
- Preserved schema 0.1, v1 receipts and sparse historical benchmark records
Evidence integrity
Complete negative routing outcomes remain publishable observations when otherwise valid. They are not removed from the sample.
When a run has open authority or negative routing outcomes, single-contract scope precision is reported as unavailable instead of producing a misleading number.
Manual and v1 scope evidence remains readable and summarizable, but does not qualify as RC12 publishable quantitative scope evidence.
Trust boundaries
- Authority is loaded only from immutable base Git state
- Candidate loading is bounded at 10,000 documents
- Strict validation warnings and duplicate approved IDs fail closed
- Dirty workspace state is excluded from measurement
- Specification runners remain inert
- Receipt paths remain private unless explicitly requested
- Receipts grant no authority and prove neither correctness nor trusted-check execution
- EngineeringSpec format 0.1 and existing enforcement semantics are unchanged
Verification
- 216 tests passed
- 59 conformance tests passed
- 94.82% coverage
- Clean package installation passed
- Installed-package v2 measurement passed
- Deterministic site regeneration passed
- Strict EngineeringSpec release check passed with zero violations
Upgrade
npx --yes @engineeringspec/cli@0.1.0-rc.12 doctor . \
--spec-dir docs/engineering-specs \
--base origin/main \
--strict