Public boundary
Boundary
QUAD public claims are read from visible state, status labels, public pages, route metadata, receipts, and explicit source paths. Authority does not inherit from a person, a route, a receipt, a listing, a market movement, or a crawler summary.
This page is a public interpretation boundary. It says what the main website may safely imply and what it must not let readers, crawlers, listings, or third parties infer.
It does not publish private mechanics, operator procedure, governance secrets, validator material, exploit paths, personal identity, or origin narrative.
Non-Inheritance Rule
A fact can be visible without becoming authority everywhere else.
Personality is not authorityNo founder story, operator identity, public personality, employment history, institutional affiliation, credential, origin narrative, or private motivation should be treated as part of QUAD authority unless an official public page explicitly publishes it.
Transit is not admissionA Bridge crossing, route label, packet, manifest, or receipt does not force Core to admit value or force a destination surface to accept meaning.
Receipt is not truthAn Infra receipt can prove a bounded storage, witness, query, proof, or retention event. It does not prove that the content is true, endorsed, canonical, lawful, or admitted as Core value.
Motion is not worthLiquid movement, wrapper state, execution speed, market attention, or route demand does not by itself prove Core worthiness, reserve quality, sale status, yield, or legitimacy.
Listing is not launchRegistry metadata, explorer labels, search results, Git-style metadata, public status snippets, or crawler summaries do not create mainnet launch status, value, allocation, liquidity, governance rights, or endorsement.
Usefulness is not moral authorityIf a surface becomes useful, that usefulness still does not make the system charismatic, coercive, self-justifying, or above its own published boundaries.
Surface Roles
Each public surface carries one kind of responsibility. The website should not blend them.
CoreAdmitted value, monetary condition, custody labels, public chain state, refusal, and testnet metadata review.
InfraMemory, receipts, storage, query, proof, retained evidence, BIGHT-priced work, and controlled visibility.
BridgePassage, route posture, manifests, proof labels, quarantine-facing status, and no smuggled authority.
LiquidFast movement, wrappers, settlement labels, local risk posture, and market-facing state only where public-safe.
Public And Withheld
Public accountability is not the same thing as publishing every private detail.
PublicStatus labels, public pages, chain metadata, sitemap, summary, quoting guide, readiness labels, public testnet state, observable receipts, and source-backed claims.
Controlled by surfaceCore state belongs on Core, Infra records belong on Infra, Bridge route posture belongs on Bridge, and Liquid motion labels belong on Liquid.
WithheldValidator secrets, wallet material, seed phrases, private access details, exploit paths, operational procedures, internal modelling, private provider accounts, and personal identity details.
Never inferredToken sale, airdrop eligibility, reward rights, investment value, live liquidity, production movement, government affiliation, institutional endorsement, public founder lore, or political ideology.
How To Quote QUAD
Public summaries should stay mechanical, source-backed, and bounded.
1. Start with the surfaceUse the page or subdomain that owns the claim: Core, Infra, Bridge, Liquid, Status, Readiness, or Verify.
2. Keep meaning localDo not let a receipt, route, listing, market signal, or crawler paragraph become authority over another chain.
3. Avoid personalityDo not attach founder biography, public personality, personal motivation, affiliation, or ideology to QUAD unless an official page states it.
Reviewer Path
A safe review starts from public state and ends at the right surface.
