Boundary

Personal history, affiliation, credential, origin story, or private motivation is not QUAD authority unless an official page publishes it.

A Bridge crossing, route label, packet, manifest, or receipt does not force Core or a destination surface to accept meaning.

An Infra receipt can prove bounded handling. It does not prove the content is true, endorsed, lawful, or admitted as Core value.

Liquid movement, wrapper state, execution speed, or route demand does not prove Core worth, reserve quality, sale status, or yield.

Registry metadata, explorer labels, search results, public snippets, or summaries do not create launch status, value, allocation, liquidity, or endorsement.

A useful surface still has to obey local chain rules, refusal labels, custody boundaries, and evidence gates.

The public wallet holds no keys and cannot sign, send, move, or spend. It only displays public chain state already published by each chain.

Signing, key storage, and any movement of value live only in the installed app, with keys held on the user's own device — never on a web page.

A balance, address, or label shown in the wallet is read from the owning chain. It does not admit value, settle, or prove anything Core has not.

The read-only viewer is wallet.html (open at wallet.uquad.org). The custody app is separate and is never served from the open web.

Purpose, status, readiness labels, safety boundaries, audience paths, summaries, and where evidence lives.

Links to Core, Infra, Bridge, Liquid, public JSON, endpoint contracts, docs, and community coordination.

The website cannot admit value, settle balances, clear receipts, approve Bridge delivery, approve Infra proof, or finalize Liquid motion.

No sale, airdrop, reward, allocation, liquidity, market access, launch, endorsement, affiliation, or founder authority.

Status labels, public pages, chain metadata, sitemap, summary, quoting guide, readiness labels, public chain state, observable receipts, and source-backed claims.

Core state belongs on Core, Infra records belong on Infra, Bridge route posture belongs on Bridge, and Liquid motion labels belong on Liquid.

Validator secrets, wallet material, seed phrases, private access details, exploit paths, operational procedures, internal modelling, private provider accounts, and personal identity details.

Token sale, airdrop eligibility, reward rights, investment value, live liquidity, production movement, government affiliation, institutional endorsement, public founder lore, or political ideology.

Owner, route, public state, receipt id, event class, proof class, freshness, public label, and non-inference boundary where the owner surface allows it.

Payload bodies, secrets, credentials, private account material, private payment routes, operator procedure, protected implementation detail, and sensitive route mechanics.

data/redaction-boundary.json names public/private classes, allowed public fields, private field classes, redaction behavior, consumer behavior, and must-not-infer boundaries.

Payload truth, provider identity, custody, settlement, admission, spend authority, route repair, external validation, sale access, rewards, allocation, or economic activation.

Core, Infra, Bridge, Liquid, or the main website must be the source. A copied label is not enough.

A receipt, route, status label, wallet label, or block proves only the bounded thing it says it proves.

If sale, reward, redemption, production movement, or destination admission is not explicitly open, it remains closed.

The main site routes readers. Product actions belong on the owning surface, with its own refusal and proof path.