Public evidence categories
Bridge proof pages should make the category visible before any live route opens.
Source, destination, enabled or paused posture, and route class can become public labels when safe.
Public labels can describe finality posture without exposing safety limits or private timing.
Public proof status can say staged, pending, verified, refused, expired, or unavailable when backed by a safe source.
Receipts show what happened at the boundary: accepted, delivered, refused, timed out, or quarantined.
Unsupported or unclear inbound material stops at the border until the receiving chain decides meaning.
Replay posture belongs in public labels only when it can be described without exposing exploit procedure.
Older Sepolia intake events can be retained as host-contract smoke evidence. They do not admit destination value or open a public bridge-across product.
Gold native-vault posture and silver-wrapper fallback must stay distinguishable so wrapper claims do not become source-asset equivalence.
Production native-vault activation requires verifier, signer, finality, DA binding, quarantine/refusal, fee/dust, and authority-boundary gates to be satisfied together.
Bridge exports become reader-consumable evidence only after accepted Infra DA receipt binding; missing, stale, challenged, or mismatched receipts should block, sleep, quarantine, or refuse consumption.
Native purchase quotes must keep asset cost, host execution cost, proof and memory cost, Bridge service margin, and risk buffer visibly separate.
VPS proof evidence can show Bridge epoch export wires staged and acknowledged for Infra. That ack is transport evidence, not Infra admission or Core truth.
The live resident node runs from a clean Comet home. CLI proof-soak homes stay preserved as evidence, not reused as resident block history.
A route ticket can name a receiving boundary for native host exposure or yield ownership while refusing admission, accounting, sell, or public-exit claims.