014-report-integrity
Task adapter rules bound into evaluation identity (amends 004)
Lifecycle approvedImplementation completeVerification unknownQualification unknown
An amendment of approved spec 004 (R-16). The evaluator configuration names its task adapter only by name and version, so the configuration identity a report carries does not change when the adapter's correctness rules change under the same version, and a gate can compare two reports that judged correctness differently. Spec 006 closes this for the CLI alone, by writing the adapter document beside each report and comparing bytes. This amendment binds a digest of the adapter's rules into a new evaluator configuration version, so the report identity itself covers correctness, and makes a gate unknown whenever either side's rules are unbound. Approved (A-10, 2026-09-25) and implemented.
Read the full pinned specification ↗Relationships
depends on
depended on by
Claimed units
- extends
{ "nature": "amending", "spec": "004-evaluation-and-replay", "unit": { "kind": "directory", "path": "crates/rustev-eval/" } } - extends
{ "nature": "amending", "spec": "006-cli-surface", "unit": { "kind": "directory", "path": "crates/rustev-cli/" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Makefile" } }
Source headings
- 014: Task adapter rules bound into evaluation identity (amends 004)
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 The adapter's rules identity
- 3.2 Evaluator configuration, version 2
- 3.3 Gates
- 3.4 Compatibility
- 4. Out of scope
- 5. Observable negative cases
- Acceptance
- Open questions
- Implementation record
- Verification
Frozen anchors
No frozen anchors declared.