Q token mark QUADPublic Accountability

Surface directory

Open The Surface That Owns The Evidence

The main domain explains the stack. The subdomains carry the public state, product labels, receipts, and current boundaries for their own chain.

How To Use This Directory

Start with the surface that owns the claim. The main site explains the stack; the subdomains carry the current chain, product, receipt, and route evidence.

Core

Use Core for chain observation, supply policy, admission posture, validators, blocks, and public monetary condition.

Infra

Use Infra for BIGHT work, storage, upload, verification, retrieval, balances, receipts, and proof labels.

Bridge

Use Bridge for passage, source pools, owner vaults, host evidence, receipts, refusal, and movement-closed status.

Liquid

Use Liquid for motion, wrappers, risk labels, settlement posture, migration rehearsal, and market-closed status.

Main domain

Use uquad.org for identity, purpose, status, readiness, verification, boundary, summaries, and discovery.

Public boundary

Live observation, receipt files, static exports, and product pages do not open sale access, production value movement, reward eligibility, allocation, or mainnet activation.

Surface Directory

Use these links when reviewing or quoting the stack.

CoreCore chain observatory, economic law pages, chain metadata, blocks, validators, and static indexer. InfraVerifiable storage, BIGHT work, quote-first funding, receipt verification, retrieval, proof labels, balances, reserve posture, and failure states. BridgeProduct journey, held-asset labels, source-pool mapping, owner vaults, host evidence, public status, and movement-closed boundaries. LiquidMotion, position, wrapper, risk, settlement, state promotion, migration rehearsal, endpoint, explicit-law, and public market-closed labels. StatusMain-domain status, stale-state behavior, and where public data belongs. VerifyHow to read source-backed status without turning receipts or public attention into authority. ReadinessProduct, technical, operating, financial, and market gap map. Site mapAll main-domain pages, reference files, and subdomain entry points.

Detailed Routes

The direct links remain here for reviewers and assistants. First-time readers should usually start with the four surface links above.

Core routes
StatusCore public state, chain posture, and endpoint labels. BlocksRunning chain observation when the public indexer is available. Supply policyBounded supply law, expansion limits, sink boundary, and refused claims. Treasury admissionAdmission and custody labels without redemption or spend claims. ReceiptsCore receiver receipts and quarantine-first Bridgechain delivery posture. Delivery indexRead-only Bridgechain delivery index; receipts do not admit value into Treasury, Alloc, Mint, Foundation, or CoreImport. ActivationPermission-to-attempt model for economic lanes that remain closed until evidenced. chain.jsonWallet metadata for Core chain review. Wallet labelsHow to read chain metadata, denoms, balances, wrappers, vouchers, fees, and finality states. Endpoint contractPublic route contract and claim boundaries. Static indexPlain classification page for wallets, explorers, assistants, and reviewers.
Infra routes
WalletAddress path and BIGHT public labels. Fund BIGHTQuote-first funding path with payment proof and BIGHT credit receipt boundary. UploadQuote and accepted-record path for bounded service work. VerifyReceipt verification route. RetrieveQuery and restore path by receipt or handle. ProofEvidence labels and proof boundaries. FailuresFailure-first matrix for stale, replayed, refused, queued, quarantined, and terminal states. Continuity gateGenesis continuity proof requirements and first-proof posture.
Bridge routes
Product journeyBuyer intent, source-pool mapping, stable owner vaults, terminal receipts, and public movement limits. AcquisitionIntent, quote, route, assignment, funding evidence, receipt, and refusal posture. LedgerHost-fee, buffer, route-output, receipt, and refusal categories. InventoryProtocol inventory, request-linked value, host-vault assignment, and public accounting labels. VaultsNative-vault posture and product-class boundaries. GatesProduction verifier, signer, finality, DA receipt, quarantine, fee, and authority gates. Live status JSONRead-only node-status receipt with public value movement closed. Relayer healthTransport observation, provider posture, backlog/gas labels, and activation boundaries.
Liquid routes
Liquid homeFast movement overview and public status labels. Status JSONPre-SDK runtime smoke, signed lifecycle smoke, and market-closed labels. Motion JSONStatic motion-summary contract and local-meaning labels. Endpoint contractStatic route contract and claim guards. BoundaryMotion is not worth; liquidity is not backing or authority. Site mapLiquid-owned route map. Main overviewMain-domain explanation of Liquid's role in the stack. System modelHow Liquid interacts with Core, Infra, and Bridge without merging authority.

Reading Rule

Proof ownership keeps the project legible without giving every public file the power to make economic claims.

Core admits locally

Bridge arrival, Infra receipt, Liquid motion, or website copy cannot force Core admission.

Infra proves bounded work

An Infra receipt can prove a bounded service event. It does not become Core value, Bridge finality, or Liquid settlement.

Bridge preserves passage

Transport, inventory, host evidence, and fallback readiness do not open destination admission or production value movement by themselves.

Liquid settles locally

Motion, wrappers, speed, or public attention cannot create settlement truth, backing, or launch status.

Main site maps

The main domain routes readers, maintains static summaries, and labels boundaries. It does not own live balances or activate markets.

Unavailable means unavailable

If a live endpoint cannot be read, say the current state cannot be verified instead of inventing height, rewards, volume, launch state, or history.