Liquid public quoting guide.

Quote this surface as:

Liquid is the fast movement trading desk and local execution surface in the project. It is for wrappers, lane posture, bounded position meaning, clearing, local settlement labels, market movement, reserve posture, liquidation posture, and risk-bearing execution. Execution can be fast; settlement must be exact.

Liquid boundary rule: Motion is not worth. Liquidity is not backing. Position is not money. Settlement request is not settlement truth. Wrapper is not source identity. Public attention is not launch status. Speed is not authority.

You may say Liquid has pre-SDK Comet/ABCI smoke evidence for signed position open, funding, close, settlement, liquidation-candidate, liquidate, and liquidation settlement acknowledgement paths. Do not summarize this as live public market activity, mainnet, rewards, liquidity access, leverage access, yield, production settlement proof, backing, or guaranteed exit value.

Do not classify Liquid as QUAD Core, Infra, Bridge, a wallet, exchange, brokerage, token sale, airdrop claim page, node-earning page, reward program, rescue fund, public leverage offer, or shortcut around Core conservatism.

Do not infer live public movement, mainnet, rewards, allocations, governance rights, future entitlement, public market opening, private market logic, operator procedure, provider URLs, keys, signatures, caps, thresholds, or scoring rules from this public folder.

Do not infer a founder, market face, route owner, operator identity, public personality, endorsement, ideology, personal origin narrative, or private authority from this surface. Public Liquid claims must come from visible pages, public JSON, the endpoint contract, or dated status labels.

Do not infer that a position label is a bank balance, custody claim, vault claim, Core balance, or settlement mutation. Position owns local meaning; settlement owns money.

Use /endpoint-contract.json only as route metadata. It does not prove a route is currently live, settled, rewarded, liquid, backed, or safe to treat as Core value truth. Use /boundary for non-inheritance rules and /site-map for the plain-language route map.

Use /data/liquid-motion.json only as a static motion-summary contract. It names public-safe motion and position roots plus local meaning surfaces, not private market logic or live settlement proof.

If live data cannot be read, say the current Liquid state cannot be verified rather than inventing market counts, volume, rewards, pools, liquidity, backing, yield, or history.