statecraft.
Catalog/rustev

015-per-case-bundle-failures

Per-case reporting of unusable replay bundles (amends 004)

Lifecycle approvedImplementation completeVerification unknownQualification unknown

An amendment of approved spec 004 (R-16). Evaluation takes parsed replay bundles only, so a retained bundle whose bytes cannot be read, exceed their limit or do not parse cannot be reported as one incomparable case: a host must either stop the whole evaluation (the CLI's choice, spec 006 E-31) or leave the case out, which the library then reports as `bundle-missing`, misstating corruption as absence. This amendment lets the caller supply a typed bundle-load failure per case, reported as incomparable with its own reason, counted in coverage and excluded from quality. Approved (A-11, 2026-09-25) and implemented.

Read the full pinned specification ↗

Relationships

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

  1. 015: Per-case reporting of unusable replay bundles (amends 004)
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 Bundle inputs
  6. 3.2 Reporting
  7. 3.3 The CLI
  8. 3.4 Compatibility
  9. 4. Out of scope
  10. 5. Observable negative cases
  11. Acceptance
  12. Open questions
  13. Implementation record
  14. Verification

Frozen anchors

No frozen anchors declared.