Q markBridgeBoundary Rules

Bridge Boundary

Bridge is passage, not admission. This page states how to read Bridge route evidence, receipts, native-vault posture, and public labels without importing value, authority, personality, or receiving-chain meaning into the boundary.

Current statusProof surfacesEndpoint contractLLM guide

Public reading rule

Read Bridge from visible status labels, public JSON, endpoint metadata, and dated readiness pages. Do not infer live movement, destination meaning, or operator authority from route-shaped language.

Passage first

Bridge may name lanes, feeder evidence, route intent, proof posture, receipts, refusals, and quarantine labels. Those labels describe boundary handling only.

No person-shaped authority

No founder story, operator identity, public personality, private explanation, or origin narrative creates Bridge authority or route rights.

No outside inheritance

Search snippets, listings, mirror pages, AI summaries, chain explorers, market commentary, or third-party claims do not open Bridge routes or change Bridge law.

Non-inheritance rules

These rules prevent crossing, usefulness, liquidity, memory, or publicity from becoming authority.

  • Delivery is not admission. A delivered packet, route ticket, feeder observation, or acknowledged export wire does not force the receiving chain to accept value, meaning, accounting, or state.
  • Receipt is not truth. A receipt can prove that Bridge observed, handled, refused, delivered, timed out, quarantined, or exported a boundary event. It does not prove moral legitimacy, endorsement, accuracy, Core value, or destination value.
  • Transit is not value. Movement across a lane does not make an asset admitted, backed, redeemable, sellable, wrapped, unwrapped, liquid, or production-ready.
  • Native posture is not wrapper equivalence. Host-native gold positions and silver-wrapper fallback claims must remain distinguishable. A wrapper-shaped label does not become source-asset identity.
  • Public attention is not launch status. Crawlers, listings, summaries, public posts, explorer references, or traffic do not open routes, create rewards, or grant allocation, governance, ownership, or future entitlement.

What Bridge may expose

The public subdomain should be inspectable without becoming a wallet, public bridge-across product, private operations manual, or promise surface.

Visible

Phase labels, route posture, lane posture, proof categories, receipt posture, Sepolia intake evidence, native-vault posture, quarantine labels, feed freshness, and public-safe JSON.

Limited

Future live receipt and route views may show delivery facts only when a public service exists. They may not publish private thresholds, exploit procedure, credentials, or operator timing.

Not published here

Private route logic, caps, scoring rules, provider URLs, keys, signatures, host-wallet material, sell-side support, Reserve backing, destination admission, or production claims without evidence.

External-world boundary

If Bridge becomes useful, route power must still stay bounded. Usefulness is not moral authority, and misuse does not become Bridge law.

Usefulness is not endorsement

Bridge may become a useful logistics surface. That usefulness does not bless every route, actor, claim, packet, or interpretation.

No route-owner myth

No relayer, operator, gateway, route, or public-facing page becomes the sovereign owner of crossing meaning.

Power stays observable

Route power should be expressed as visible labels, refusal states, quarantine, receipts, and endpoint contracts rather than charisma, private discretion, or market mythology.