Choose A Path
Pick the path that matches the question. The owning surface still carries the current proof.
StartFirst-reading order, surface ownership, and the safe review path.Best first click for a cold reader.
Why use QUADPlain utility map for Core, Infra, Bridge, and Liquid, with proof ownership and claim limits.Best before deciding whether to keep reading.
Stack overviewOne sitting map of the four jobs: Core accounts, Infra proves, Bridge carries, and Liquid moves.Best before deeper pages.
CategoryWhat QUAD is, common misreads, proof routes, and what is not claimed.Best before comparing labels.
Product comparisonCompare QUAD by job: Core accounts, Infra proves, Bridge carries, and Liquid moves.Best before comparing products.
Data provenanceOwner, route, proof class, freshness, and boundary rules for public data.Best before quoting data.
Data catalog JSONMachine-readable catalog for public JSON owner, evidence class, freshness, stale behavior, redaction, and boundaries.Best before tooling quotes public data.
Reconciliation JSONMachine-readable rules for stale, conflicting, incomplete, local-only, external, and owner-mismatched public data.Best before resolving a mismatch.
Lineage JSONMachine-readable map for public JSON source class, source route, transformation, display route, freshness, redaction, and lineage-break behavior.Best before tracing data origin.
Freshness JSONMachine-readable stale-state policy for current, fallback, cached, stale, unavailable, conflicted, local-package-only, and superseded public data.Best before quoting current state.
Redaction JSONMachine-readable public/private boundary for receipts, payloads, providers, host-chain labels, financial posture, route proof, and doctrine-sensitive material.Best before publishing fields.
Retention JSONMachine-readable retention, prune, tombstone, restore, and reissue policy for receipts, payload access, datasets, and support evidence.Best before deleting or reissuing records.
Consumer JSONMachine-readable allowed-use contract for public readers, wallets, explorers, websites, chain keepers, importers, proof/reissue services, dashboards, reviewers, pricing engines, and refusal gates.Best before using data in a product or decision path.
Readiness JSONMachine-readable data-product readiness gate for catalog, schema, lineage, freshness, redaction, retention, reconciliation, consumer contract, wording, evidence, and owner review.Best before trusting a dataset.
Review Questions JSONMachine-readable standing questions for dataset purpose, owner, producer, evidence, freshness, failure behavior, inference, public need, and trust-from-action.Best before publishing or integrating data.
Information Governance JSONMachine-readable source, artifact, deployed-route, stale-copy, access-boundary, change-record, and recovery-path contract.Best before trusting a fact or artifact.
ReferencesOfficial surfaces, public repos, registry packets, explorers, audit slots, and outside-reference boundaries.Best before sharing elsewhere.
External referencesHow to share, list, post, submit, or route QUAD without spam, phishing, false-validation, or token-promo framing.Best before posting outside uquad.org.
Network useUsable public paths, usage evidence standards, partner disclosure boundaries, and what does not count as traction.Best before claiming adoption.
CredibilityInventory of proof handles, owner surfaces, pending assets, and what each handle cannot prove.Best before trusting a claim.
Core pathAdmitted-value and monetary-accounting path for QUAD, validators, supply policy, activation gates, and closed claims.Best before reading Core economics.
PhasesCurrent phase, next gates, what opens each lane, and what remains closed.Best before reading launch timing.
JourneysAllowed actions, refusal reasons, fees, finality, receipts, operators, governance, stale data, and boundaries.Best before acting.
Surface first readsChoose Core, Infra, Bridge, Liquid, or the whole-stack path without guessing ownership.Best chain-specific entry.
Reader pathsChoose visitor, tester, validator, provider, builder, reviewer, security, route, liquidity, community, or crawler path.Best before searching blindly.
SurfacesCurrent routes for Core, Infra, Bridge, Liquid, status files, and proof labels.Best map for fresh stack state.
State labelsLive, testnet/rehearsal, planned, disabled, stale, and not-yet-public definitions.Best before using a route.
Observability JSONMachine-readable public telemetry contract for metric owners, stale behavior, alert labels, next checks, and non-inference boundaries.Best before quoting telemetry.
Financial inferenceCustody, reserve, liquidity, redemption, yield, admission, and launch words stay evidence-owned.Best before quoting money claims.
Wallet labelsChain metadata, denom labels, balance classes, fee classes, and finality states.Best before adding metadata.
IntegratorsQuery contracts, schema examples, receipt lookup, stale responses, endpoints, wallet metadata, and must-not-build warnings.Best before building a UI.
ContractsPublic contract shape, schema families, versioning, stale behavior, consumer rules, and endpoint boundaries.Best before consuming data.
Interface contract JSONMachine-readable public contract register for schema families, evidence classes, replay domains, timeout policy, and must-not-infer boundaries.Best before tooling reads contract shape.
Infra pathStore, prove, retrieve, remember: BIGHT work payments, upload, verification, retrieval, contracts, providers, and payload boundaries.Best before using Infra.
Bridge pathControlled passage, native acquisition, inventory truth, owner vaults, host evidence, provider risk, and receipt boundaries.Best before trusting movement labels.
Liquid pathFast movement with settlement discipline: motion posture, positions, wrappers, risk, liquidation, venue quality, and settlement truth.Best before reading market labels.
SourcesSource-of-truth ladder, owner surfaces, conflict rules, quote rules, and downgrade behavior.Best before quoting current state.
FeesQuotes, gas, service fees, host costs, refunds, receipts, delays, and finality boundaries.Best before paying or signing.
LifecycleRequest, quote, payment/signature, execution, waiting, receipt, refusal, refund, quarantine, and closure states.Best after choosing an action.
ObligationsOperating costs, payer labels, payables, receivables, floats, receipt closure, and self-funding boundaries.Best before claiming sustainability.
RisksOpen assumptions, risk labels, closing evidence, downgrade behavior, and chain-owned boundaries.Best before relying on a claim.
OperatorsValidator, relayer, provider, endpoint, degraded-state, and emergency posture labels.Best before running infrastructure.
GovernanceProposal types, voting labels, failure states, emergency caution, and hard-law boundaries.Best before reading proposals.
SupportReceipt lookup, refusal records, reissue paths, evidence packets, and support triage.Best when something needs checking.
Discord onboardingFirst actions, role paths, issue reports, docs feedback, update-channel shape, and public chat boundaries.Best before posting.
PlaybooksStuck transactions, wrong denoms, unpaid quotes, stale routes, failed uploads, delayed receipts, and safe escalation boundaries.Best when a visible path goes wrong.
Error labelsRefused, pending, stale, unavailable, unpaid, expired, duplicate, invalid, unauthorized, and degraded states.Best before writing status text.
Failure JSONMachine-readable public failure matrix for failure class, expected state, evidence to bring, next check, recovery shape, and boundaries.Best before tooling reads failures.
Recovery drill JSONMachine-readable public drill contract for triggers, expected states, recovery actions, terminal receipts, summaries, and boundaries.Best before claiming resilience.
Observe CoreCore chain state, validators, blocks, metadata, and public status.No seed phrase or payment.
Use BIGHTWallet, quote-first purchase, upload, verify, retrieve, contract, proof, and public data lanes.Product utility path.
Read BridgeProduct journey, acquisition, inventory, source pool, owner vault, gates, host evidence, and proof.Movement remains bounded.
Observe LiquidMotion, position, risk, settlement, state promotion, migration rehearsal, and readiness surfaces.Public exports are not settlement truth.
Use Private RPCQuote-first API-key access to the customer endpoint surface, CU allowances, payment rails, key status, fleet status, and service boundary.External rail, not chain truth.
Read receiptsWhat a receipt proves, what it does not prove, and which surface owns verification.Best before acting on proof claims.
Proof archiveEvidence timeline, proof classes, owner routes, freshness rules, and boundary checks.Best before quoting progress.
Dependency mapSurface dependencies, stale-state downgrade rules, shared support rails, and claim effects.Best before relying on another surface.
Dependency JSONMachine-readable public dependency map for owner, class, stale behavior, fallback behavior, and claim boundary.Best before tooling reads dependencies.
Acceptance pathsComplete-enough journey standards for success, refusal, delay, recovery, and support.Best before claiming readiness.
Acceptance JSONMachine-readable public journey register for owner, entry condition, quote/cost label, receipt requirement, failure path, support path, and boundary.Best before tooling reads journey readiness.
Custody mapWho owns, owes, holds, records, refuses, pays, or cannot touch value and state.Best before reading balances.
ContinuityDegraded surfaces, release labels, handoffs, public downgrade behavior, and recovery boundaries.Best when something goes stale.
Release provenance JSONMachine-readable public release contract for artifact classes, checks, handoff labels, rollback shape, and local-package boundaries.Best before quoting a release artifact.
ReviewProduct gaps, technical closure, operating readiness, accounting gaps, and market readiness.Gap map.
Executive lensesContinuity, operations, finance, market, technical, information, data, and experience checkpoints.How the gap map is judged.