Q token mark QUADPublic Accountability

Liquid market path

Fast Movement With Settlement Discipline

Liquid is the fast-movement surface. It can describe quotes, orders, positions, wrappers, risk, liquidation, and settlement requests, but final balance truth stays with settlement.

The Fast Answer

Liquid lets motion be fast without letting motion become authority.

It is built to separate market intent, position meaning, wrapper posture, risk checks, clearing, liquidation, and settlement requests. A fast path can propose, queue, refuse, or hand off state. It does not become final money by being fast.

Current Liquid Path

Use Liquid-owned routes for current state. Use the main domain to understand what each label can and cannot mean.

1. Open LiquidStart at the Liquid surface for status, proof, roles, readiness, boundary, public data, and endpoint contract routes. 2. Check readinessRead movement-closed labels, position lifecycle posture, engine smoke, claim guards, and production blockers. 3. Check proofRead wrapper, position, settlement, risk, liquidation, execution, and boundary evidence categories. 4. Check motion contractUse motion and position-meaning contract fields without treating them as live settlement proof. 5. Check endpointsRead static and future-live route shapes without inferring market access or current state. 6. Read Liquid overviewUse the overview for surface purpose, current posture, evidence, and stale-state behavior.

What Liquid Owns

Liquid is a market-facing surface, but each job stays in its lane.

Desk posture

Desk state can record intent, quote posture, motion claims, inventory posture, and execution pressure without becoming settlement truth.

Positions

Position owns lifecycle meaning: opening, open, reducing, closing, liquidation pending, liquidating, closed, quarantined, bankrupt, or refused.

Risk

Risk owns exposure caps, lane cadence, local exposure evaluation, and refusal posture. It does not become price-oracle truth.

Clearing

Clearing owns fill and fee result roots before settlement. It can build a result; it cannot mutate final balances directly.

Settlement

Settlement is the final balance-truth owner. Other Liquid components hand settlement-only requests to it.

Exports

Infra export and Bridge intake can carry evidence, but Liquid decides local meaning under Liquid rules.

Position Lifecycle

A position is a bounded local state, not money.

StagePublic meaningNot implied
QuoteIndicative, accepted, expired, or refused cost and route posture with expiry, fees, slippage limit, and settlement owner.Trade execution, custody, redemption, guaranteed fill, or Core admission.
OpenA position snapshot can show owner, market, collateral label, debt label, entry root, mark root, health, leverage, and risk check.Wallet balance, vault claim, settlement truth, or spend authority.
Reduce / closeA close intent or reduction can move toward clearing and settlement through bounded receipts.Instant settlement, guaranteed exit value, or hidden desk discretion.
FundingFunding accrual can be represented as settlement-bound context.Yield, reward, entitlement, or a future payout promise.
Quarantine / refusalBad source, bad risk, bad wrapper, missing settlement, stale proof, or authority mismatch can stop the position.Soft approval, hidden access, or a reason to retry blindly.
SettlementFinal balance mutation belongs only after settlement accepts a settlement-only request.Position, clearing, wrapper, reserve, or engine output mutating balances directly.

Risk And Liquidation Boundary

Liquidation should read like a machine state, not a story about winners and losers.

Exposure check

Risk evaluates local exposure and cadence before a market path can continue.

Threshold breach

A liquidation condition may be identified from position state and risk posture.

Candidate

A candidate is not liquidation execution. It is a bounded claim that still needs the allowed path.

Execution plan

Liquidation proof can name condition, position snapshot, execution plan, and refusal gates.

Settlement request

Liquidation output must hand off to settlement. It does not mutate balances directly.

Surplus or deficit

Surplus, deficit, backstop, reserve, or release labels must stay receipt-bound and purpose-bound.

Wrapper And Redemption Boundary

Wrappers are local meaning records. They are not source identity by convenience.

Gold reference

Bridge-side native-host-vault or host-chain evidence can be referenced as provenance.

Silver meaning

Liquid settles, quarantines, refuses, and admits only the local wrapper meaning it owns.

Backing class

Backing should name representation class, source proof, local risk, settlement state, and any degraded posture.

Redemption failure

Disabled, degraded, refused, missing-proof, stale-proof, or unsupported redemption states must remain visible if applicable.

No source equivalence

A wrapper must not claim native-vault control, source-asset identity, Core truth, Bridge authority, or balance mutation.

No rescue shortcut

Reserve or backstop labels are purpose-bound. They are not discretionary rescue, yield, or guaranteed exit.

Venue And Execution Quality

Execution quality can be described only where the evidence is owned and current.

SignalMay showMust not imply
Endpoint contractRoute names, static/future-live shape, public JSON contract, and stale behavior.Current market access, settlement truth, or route availability.
Motion engineDefault-safe build, queue, affinity, parser, runtime-config, host-test mode, and advisory proposal evidence.Settlement, admission, routing, governance, payment approval, production stress, or market opening.
Stress outputSubmitted, accepted, refused, conflict, blocker, and refusal-rate labels where published.Production throughput while production profile blockers remain.
ClearingFill input, fee input, clearing result, build result, and boundary refusal labels.Direct balance mutation, payout authority, risk bypass, or settlement bypass.
InventoryHolding lots, orders, summaries, PnL statements, reservations, earning receipts, and PnL events as review state.User collateral, reserve backing, payout authority, private strategy, or direct Core route.
ReadinessState owners, blockers, keeper-store rehearsals, and live-application refusal.Mainnet, live market, leverage access, or economic activation.

Current Evidence Readers Can Ask For

Liquid has useful proof posture. Each proof opens only the named claim.

EvidenceWhat it can showBoundary
Position lifecycle proofLifecycle statuses, position root, risk handoff, clearing handoff, settlement request, and refusal labels.Not money, custody, final balance truth, or Core worth.
Authority separation proofSettlement-only balance mutation, non-settlement refusal, no direct Core routing, and local-state ownership.Not live market operation or private override.
Wrapper boundary proofGold provenance versus silver local meaning, replay-domain checks, wrapper quarantine, and redemption posture.Not source equivalence, native-vault control, or redemption access.
Engine smoke proofOne-second engine default-safe build and lightweight runtime checks passed on 2026-06-01.Not settlement, production stress, validator-default kernel bypass, or public market opening.
Migration apply candidateKeeper prefixes, state roots, proof flags, query/message contracts, and genesis export rehearsal.Not live consensus-store application until migration is actually applied.
Public endpoint contractStatic and future-live route shape plus public data contract boundaries.Not current live state if the endpoint cannot be read.

Liquid Is Not

These refusals keep fast movement from becoming the wrong public identity.

Not a live exchangePublic pages do not open brokerage, leverage, market access, or live trading.
Not yieldFunding, surplus, earning receipts, or PnL labels are not rewards, yield, or future entitlement.
Not guaranteed executionQuotes, orders, motion, and route labels can expire, refuse, quarantine, or remain pending.
Not hidden desk profitInventory, PnL, reservation, fee, and surplus labels should stay receipt-bound and owner-labelled.
Not investment strategyRisk labels and position posture are state explanations, not advice or strategy.
Not Core worthLiquid motion, liquidity, wrappers, speed, and attention do not create QUAD/Core value or admission.