Each case fixes its object and its conditions before anything is run, states what the outcome should be, and carries a negative control that must fail in the expected way. The protocol has been executed against the published estate harness, and the resulting carrier is shown below each case. BW-WX-004 is not executed: a reproduction has to come from an examiner who took no part in producing the object.
This run executes the witness protocol against the named artefact below, which this app publishes in full. It is real execution with real carriers. It is not evidence about BW, and it does not promote any BW claim: no BW artefact is held or executed by this app.
90b29ef3b758c15fa010878d69a29fb9b47fe47f64f33ccd72c3c9afbcdb1f67The stored canonical carrier hashes to the recorded carrier hash, so the record is byte-for-byte what was written.
Nothing external holds this carrier yet. The hash above is this app's own statement about its own record, and this app cannot make it independent of itself.
The carrier text above is the input to a signed, chained ledger entry, so the run is checkable in the same terms as every other record. Verify the entry with the record identifier below.
One fixed input document, frozen by fingerprint before any run, stored with the packet. The object is not edited between repetitions.
Every repetition produces the same output artefact, or the divergence is reported as a finding rather than discarded.
A single altered input, differing only in one byte, must produce a different output or a detectable refusal. An unchanged output under an altered input falsifies the binding.
The packet carries the specification and empty examiner fields. Any observed result for this case is published separately from the run carrier, not baked into the specification.
BW Proof is an evidence estate, not a live BW runtime, not a certification, and not an independent audit. Nothing here substitutes for an examiner inspecting real artefacts.