Q token mark QUADPublic Accountability

Who can touch what

Custody And Account Map

This page separates what each surface can own, owe, hold, refuse, pay, record, observe, or leave untouched. A visible balance is not spendable until its account class says it is spendable.

Custody words stay narrow. A wallet label, receipt, route, or public page does not create spend authority.

Reading Rule

Start with account class before amount. Same number, different law.

OwnsThe surface has local authority over the state class.
OwesA payable, refund, provider, relayer, host, or service obligation exists.
HoldsThe surface can hold value or state under a named restriction.
RecordsThe surface can record a fact without controlling the underlying value.
RefusesThe surface can block, quarantine, expire, or close unsafe state.
Cannot touchThe state belongs to another surface, host chain, or user-controlled context.

Surface Authority Map

These are public account boundaries. They are not private signer maps and not live custody proofs.

SurfaceCan own or account forCannot imply
CoreCore-native accounting, admitted-value posture, Treasury/accounting classes, quarantine, terminal state, supply posture, fees, staking, and Core-owned receipts.Sale access, redemption, external legal custody, unlocked Treasury spend, or sibling-chain authority.
InfraBIGHT-priced work, uploads, retrievals, receipt memory, proof work, contract work, provider/service ledgers, capacity labels, and reserve-rail labels where published.Core admission, payload truth, Bridge finality, Liquid settlement, raw compute rewards, or reserve backing by itself.
BridgePassage posture, source pools, owner-vault labels, route funds, host evidence, inventory labels, gate results, refunds, surplus, refusal, and quarantine.Destination admission, native-host ownership, wrapper minting, redemption, swap access, or clean user spendability.
LiquidMotion records, quote/order posture, position state, risk labels, wrapper labels, clearing posture, liquidation/refusal state, and settlement requests.Final balance truth unless settlement owns it, Core worth, reserve backing, or live public market activity.
Main websitePublic orientation, summaries, claim boundaries, release receipts, page maps, and links to owning surfaces.Live balances, custody, settlement, admission, payment authority, or production activation.

Account Classes

Use these classes before treating a value as available, owed, blocked, or terminal.

ClassPublic meaningNot spendable as
Native tokenThe chain's local unit for gas, staking, accounting, or product use where the chain publishes it.Reserve value, sale allocation, price support, or sibling-chain money.
Admitted external assetAn outside asset accepted under the owning surface's rule and evidence path.Automatic redemption, universal backing, or unrestricted liquidity.
Treasury or custody stateValue or posture tracked by a Core-like custody/accounting surface.Available spend, operator discretion, or personal wallet control.
Escrow / bondedValue tied to a quote, route, order, validator, provider, work item, or pending condition.Completed work, approved refund, or liquid spend authority.
Reserve / bufferBallast, host-fee, finality, service, safety, repair, or continuity margin.Solvency guarantee, yield, market depth, or redemption pool.
Payable / receivableObligation, invoice, refund, provider payment, relayer gas float, host gas float, or pending settlement record.Cash on hand before payment and receipt closure.
Restricted / stagedVisible but constrained by test state, disabled lane, policy, route, proof, or not-yet-public status.Live access, allocation, or permission to act.
QuarantineUnsupported, unsafe, unresolved, replayed, stale, or not-yet-admitted state.Clean balance, admitted value, or eligible user funds.
Sink / terminalBurn, closure, expiry, refusal, deletion, tombstone, or final disposition where published.Marketing scarcity, reward event, or broader economic activation.

Payable And Receivable States

Owed is not paid. Receivable is not spendable until paid and receipted.

Current

Known obligation inside its expected service window.

Due soon

Approaching payment, refund, service, proof, or settlement window.

Due now

Requires action or explicit refusal before stronger claims continue.

Late

Downgrade public claims until payment, receipt, refund, or refusal is visible.

Disputed

Challenge, evidence, appeal, or support path must own the next state.

Closed

Paid, refunded, refused, written off, expired, or terminal with a receipt or status.

Must Not Confuse

These mistakes create the wrong public behavior.

Operational wallet is not reserve

A service wallet can pay bills or gas without becoming reserve proof, Treasury custody, or market depth.

Faucet is not custody

Test funds, staged credits, or faucet-style coordination do not prove user custody, sale access, or future entitlement.

Relayer is not buyer or custodian

A relayer may move packets or gas, but it does not become market-maker, pricing authority, or admitted-value owner.

Provider is not protocol authority

A provider can perform accepted work or hold service obligations without controlling chain law.

Receipt is not spend authority

A receipt proves its bounded event. It does not unlock funds unless the owning surface says so.

Website is not the ledger

The main domain can explain and route. It cannot make a balance live, admitted, settled, or spendable.