Market integrityShadow
Provider bonds & quarantine
Declared bond metadata and recorded quarantine state. Neither collateral nor routing enforcement is active in Shadow.
The router can attach a model claim to a provider and record a declared bond_amount. In the current Shadow integrity mode, that field is metadata: the default minimum is zero, no USDC is escrowed, and no withdrawal or loss-allocation terms exist.
declared is not depositedA claim's
bond_amount must not be described as customer-protected collateral. Any provider-bond program remains Proposed until its amount, custody, withdrawal delay, slash authority, customer remedy, and jurisdictional terms are published.What exists now
- A provider identity can be tied to a specific model claim.
- Claims and linked receipts can be read by the integrity and operator surfaces.
- Approved reviewer wallets can file a points-backed challenge in the Shadow lane.
- An operator-recorded upheld verdict records the affected claim state as quarantined. In Shadow mode, that state does not filter quotes.
What does not exist
- No on-chain provider vault or USDC bond escrow.
- No approved minimum collateral or capacity-based bond schedule.
- No automatic customer refund or insurance-pool split.
- No permissionless slash or appeal process.
Quarantine and recovery
The quarantine state is claim-scoped rather than provider-wide. Recovery is operator-mediated and requires fresh evidence that the deployment now serves what it claims. Changing claim state does not reverse an existing Shadow points outcome. If routing enforcement is later activated, its trigger, review SLA, appeal path, and restoration effect must be published first.
As a providerTreat a declared bond as public claim metadata, not funds on deposit. Beta routing uses measured service. Canary evidence, approved-reviewer challenges, and quarantine transitions are Shadow records; they are not presented as active routing enforcement.
As a challengerA declared number is not your bounty pool. The only implemented Shadow payoff is the versioned points arithmetic in
s0-2026.07.1.where this lives in code
- mechanisms.json current status and explicit non-claims
- router/src/trust/integrity.ts claims, declared bond fields, and quarantine transitions
- router/src/shared/config.ts Shadow mode and zero default minimum