Exact v1 bytes for independent red-team. The gist is immutable by project
process: any semantic correction becomes a successor artifact and relation,
never an edit to these bytes.
- artifact: https://gist.github.com/heyoub/fab81375193946704d9774b6be80b7a0
- sha256:
963C480DE5EF79223948E1D2D1924B5BC327512A0C344D0FCCDB8DEA368A5BFF
- design: claim-evidence-ir / version 1 / status proposed / supersedes none / implementation none
- basis:
main at a65dd136226d79db86fa22911d64117ae2d6ecdf, tree ee8fa1046bbce43da835a4e2d9f804b493c30e76
What remains unproven
No B3 implementation exists. The current 225 declarations are structurally
inventoried, not semantically adjudicated one by one. The 107 services laws and
three judge laws have no current claim join; v1 carries them as exact-basis
LegacyDrainPending so B3 cannot invent their meaning and B4 remains their
adjudication owner. Nextest list/JUnit receipt integration, bounded XML decoding,
origin attestation, host custody challenges, and the three-operation protocol
have not executed as repository evidence.
Design rulings
- Claim/evidence declarations, joins, and projections are an xtask tooling
owner; machine evidence vocabulary remains in core band 23.
- Testpak seat 02 owns bounded execution plans and arena outcomes. Higher seat
08 owns the single list/JUnit decoder and durable receipt mint. Their thin
binary composes the downward dependency order.
- Xtask and testpak do not invoke or depend on one another. An operator/workflow
composes request export, testpak execution, and receipt import as three
explicit process operations.
- Stable IDs are owner-authored; semantic revisions and observation identities
are typed, domain-separated derivations.
- Resolution, activation, mechanism terminal, outcome, coverage, freshness,
origin, and strength are orthogonal derived facts. Status is never authored.
- Coverage is
Specimen, DeclaredPopulation, or Exhaustive; denominators
contain derived member identities, not authored counts.
- Shared evidence, gated debt, invalidation, and supersession are explicit.
- Claim blocks remain at derived owner READMEs through a strict fenced-TOML
adapter. No central hand ledger or successor to TOOLING_READMES exists.
- B3 represents every current proof surface but does not drain laws or open
product runtime.
Current input population
Derived on the basis: 204 semantic records, 21 tooling records, 184 core laws,
107 services laws, and three judge laws. These are migration inputs, not source
constants.
The inaugural hosted mutation run on this same basis concluded successfully:
cargo-mutants 27.0.0 examined 993 mutants, caught 301, missed 35, timed out zero,
and classified 657 unviable. Its empty-scope reversal and checkout-clean legs
passed. The 35 survivors remain evidence debt; the run predates B3 receipts and
is not upgraded into one by this issue.
Standing
Red-team the exact gist bytes and digest. Implementation begins only if those
bytes survive. If the review changes semantics, publish v2 by supersession and
red-team v2 before code.
Exact v1 bytes for independent red-team. The gist is immutable by project
process: any semantic correction becomes a successor artifact and relation,
never an edit to these bytes.
963C480DE5EF79223948E1D2D1924B5BC327512A0C344D0FCCDB8DEA368A5BFFmainata65dd136226d79db86fa22911d64117ae2d6ecdf, treeee8fa1046bbce43da835a4e2d9f804b493c30e76What remains unproven
No B3 implementation exists. The current 225 declarations are structurally
inventoried, not semantically adjudicated one by one. The 107 services laws and
three judge laws have no current claim join; v1 carries them as exact-basis
LegacyDrainPendingso B3 cannot invent their meaning and B4 remains theiradjudication owner. Nextest list/JUnit receipt integration, bounded XML decoding,
origin attestation, host custody challenges, and the three-operation protocol
have not executed as repository evidence.
Design rulings
owner; machine evidence vocabulary remains in core band 23.
08 owns the single list/JUnit decoder and durable receipt mint. Their thin
binary composes the downward dependency order.
composes request export, testpak execution, and receipt import as three
explicit process operations.
are typed, domain-separated derivations.
origin, and strength are orthogonal derived facts. Status is never authored.
Specimen,DeclaredPopulation, orExhaustive; denominatorscontain derived member identities, not authored counts.
adapter. No central hand ledger or successor to
TOOLING_READMESexists.product runtime.
Current input population
Derived on the basis: 204 semantic records, 21 tooling records, 184 core laws,
107 services laws, and three judge laws. These are migration inputs, not source
constants.
The inaugural hosted mutation run on this same basis concluded successfully:
cargo-mutants 27.0.0 examined 993 mutants, caught 301, missed 35, timed out zero,
and classified 657 unviable. Its empty-scope reversal and checkout-clean legs
passed. The 35 survivors remain evidence debt; the run predates B3 receipts and
is not upgraded into one by this issue.
Standing
Red-team the exact gist bytes and digest. Implementation begins only if those
bytes survive. If the review changes semantics, publish v2 by supersession and
red-team v2 before code.