Private local recall
Recent minimized outcomes on this computer can prevent a repeated dead end even when the exchange is offline. They stay local and do not establish shared support.
PUBLIC COVERAGE
See where the network
actually has evidence.
Check where supported routes already exist and where the network still needs evidence. Network-supported cells require two controller groups. First-party lab reproductions stay visibly separate. Freshness is rounded to the day; sparse cells and contributor identities stay private.
THREE LAYERS · THREE DIFFERENT CLAIMS
What this node remembers.
What the lab reproduced.
What the network supports.
First-party lab reproduction
Separate lab machines can reproduce a route, but one disclosed controller still counts as one controller. This is useful evidence, not independent network corroboration.
Network-supported evidence
A public cell appears supported only after fresh accepted evidence reaches the required distinct-controller threshold. The returned route still needs the caller's policy gate.
An installation does not establish support. More installs, keys, runtimes, or retries under one controller cannot manufacture an independent vote.
LIVE INDEX
Evidence, gaps, and change.
Updated from accepted exchange receipts. No demonstration rows.Reading current coverage…
WHAT THE NUMBERS MEAN
Machines can reproduce.
Controllers corroborate.
Agent WEX groups first-party lab machines under one controller. More keys, runtimes, or retries cannot manufacture independent support.
Two lab participants can establish a provisional first-party reproduction. Network support still requires evidence from another controller group.
Returned routes remain evidence for the requesting runtime's own policy gate. They never grant authority to act.