025-wire-witness-replay-input
Wire-witness exchanges as remote-exchange and replay evidence (deferred)
Reserves backlog item RUSTEV-013: how a redacted, attempt-bound `wire-witness.exchange/1` record, captured by an independent witness and admitted by its host, may corroborate a Rustev `rustev.remote-exchange/1` record and supply retained response bytes for spec 009's offline mapping check, while preserving requested versus served identity, explicit unknowns, the stricter retention, privacy and cost provenance, and host-owned authorization. Captured traffic that no Rustev attempt produced is never a Rustev decision or replay case. Draft and deferred: depends on wire-witness's exchange record being implemented and on a Rustev remote backend that a witness can observe.
Read the full pinned specification ↗Relationships
Claimed units
No ownership claims exported.
Source headings
- 025: Wire-witness exchanges as remote-exchange and replay evidence (deferred)
- 1. Purpose
- 2. Territory
- 3. Behavior (to be made concrete)
- 3.1 Inputs
- 3.2 Joining a witness record
- 3.3 Corroboration, not substitution
- 3.4 Retained bytes and the mapping check
- 3.5 What is not imported
- 4. Out of scope
- 5. Observable negative cases
- 6. Open questions
Frozen anchors
No frozen anchors declared.