Site Map

HomeMain public entry point and surface routing. StartFirst-reading order, surface ownership, evidence classes, and safe visitor paths. Why use QUADPlain utility map for Core, Infra, Bridge, and Liquid, with proof ownership and closed-claim boundaries. Stack overviewOne sitting narrative map for Core, Infra, Bridge, Liquid, proof-first paths, phases, and boundaries. Category guideWhat QUAD is, common category misreads, proof routes, and what is not claimed. Product comparisonCompare QUAD by job and proof owner without competitor attacks, reward framing, or unsupported superiority claims. Data provenanceHow to read public data by owner, route, proof class, freshness, and boundary. Data catalog JSONMachine-readable map of public JSON owners, evidence classes, freshness rules, stale behavior, and boundaries. Reconciliation JSONMachine-readable downgrade rules for stale, conflicting, incomplete, local-only, external, and owner-mismatched data. Lineage JSONMachine-readable map of public JSON source class, source owner, transformation, display routes, freshness, and broken-lineage behavior. Freshness JSONMachine-readable policy for current, fallback, cached, stale, unavailable, conflicted, local-package-only, and superseded data labels. Redaction JSONMachine-readable public/private boundary for payloads, receipts, provider labels, vault labels, route proof, financial posture, and sensitive material. Retention JSONMachine-readable retention, prune, tombstone, restore, and reissue policy for public records and ended access. Consumer JSONMachine-readable allowed-use and downgrade rules for public data consumers, product surfaces, reviewers, and refusal gates. Readiness JSONMachine-readable readiness gate for deciding when a public dataset is ready within boundary, partial, not ready, or historical only. Review Questions JSONMachine-readable standing questions for deciding whether a dataset has meaning, owner, evidence, freshness, safe inference, and trust-from-action. Information Governance JSONMachine-readable contract for source, artifact, deployed route, stale copy, internal-only material, change records, access boundaries, and recovery paths. Public referencesOfficial surfaces, repositories, registry packets, explorers, audit slots, and external-reference boundaries. External referencesHow to share, list, post, submit, or route QUAD without spam, phishing, false-validation, or token-promo framing. Credibility inventoryProof handles, owner surfaces, evidence classes, pending assets, and what each handle cannot prove. Core pathAdmitted-value, monetary-accounting, validator, supply, activation, and mainnet-hardening path for QUAD Core. Bridge pathControlled passage, acquisition, inventory truth, owner vaults, host evidence, provider risk, receipts, and destination-admission boundaries. Liquid pathFast movement with settlement discipline, position lifecycle, wrapper posture, risk, liquidation, venue quality, and closed market claims. PhasesCurrent phase, opening gates, lane order, what opens each gate, and what remains closed. Public journeysAllowed actions, refusal reasons, fees, finality, receipts, operators, governance, stale data, and boundaries. Surface first readsDirect first-read paths for Core, Infra, Bridge, Liquid, and the whole stack. AboutWhat QUAD is and how to approach the public surface. PurposeWhy the system exists and what it tries to prove. ModelEconomics, validator incentives, governance, security assumptions, token utility, rollout, and chain interaction. BoundaryNon-inheritance, personality-free authority, and plain interpretation rules. StatusPublic status labels and surface destinations. Observability JSONMachine-readable public telemetry contract for metric owners, stale behavior, alert labels, next checks, and non-inference boundaries. Public surfacesDirectory of proof routes for Core, Infra, Bridge, and Liquid. VerifyEvidence labels and source-backed review guide. Proof archiveEvidence timeline, proof classes, freshness rules, and source-owned boundaries. Dependency mapWhat Core, Infra, Bridge, Liquid, public sites, RPC, wallets, indexers, and support rails depend on. Dependency JSONMachine-readable public dependency map for owner, class, stale behavior, fallback behavior, and claim boundary. Acceptance pathsComplete-enough journey standards for Core, Infra, Bridge, Liquid, providers, and support. Acceptance JSONMachine-readable public journey register for owner, entry condition, quote/cost label, receipt requirement, failure path, support path, and boundary. Custody mapWho owns, owes, holds, records, refuses, pays, or cannot touch value and state. ContinuityHow surfaces degrade, recover, hand off, and preserve meaning when dependencies are stale. Release provenance JSONMachine-readable public release contract for artifact classes, checks, handoff labels, rollback shape, and local-package boundaries. Receipt guideWhat receipts prove, what they do not prove, and which surface owns verification. Financial inference checkHow to read custody, reserve, liquidity, redemption, yield, admission, and launch labels. Wallet labelsChain metadata, denom labels, balance classes, fee classes, and finality states. Integrator guideQuery contracts, schema examples, receipt lookup, stale responses, endpoints, and must-not-build warnings. Public contractsContract shapes, schema families, versioning, stale behavior, consumer rules, and endpoint boundaries. Interface contract JSONMachine-readable public contract register for packets, receipts, acknowledgements, refusals, quarantine, exports, and must-not-infer boundaries. Source-of-truth mapTruth ladder, owner surfaces, conflict rules, quote rules, and stale/cache/local/external downgrade behavior. Fees and finalityQuotes, gas, service fees, host costs, refunds, receipts, delays, and finality boundaries. Action lifecycleRequest, quote, payment/signature, execution, waiting, receipt, refusal, refund, quarantine, and closure states. ObligationsOperating costs, payer labels, payable and receivable states, floats, receipt closure, and self-funding boundaries. Risks and assumptionsRisk labels, open assumptions, closing evidence, downgrade behavior, and owner boundaries. Operator guideValidator, relayer, provider, endpoint, degraded-state, and emergency posture labels. Governance guideProposal types, voting labels, failure states, emergency caution, and hard-law boundaries. Receipts and supportReceipt lookup, refusal records, reissue paths, evidence packets, and support triage. Discord onboardingFirst actions, role paths, bug reports, docs feedback, update-channel shape, and public chat boundaries. Support playbooksCommon response paths for stuck transactions, wrong denoms, unpaid quotes, stale routes, failed uploads, delayed receipts, and provider issues. Status and error labelsRefused, pending, stale, unavailable, unpaid, expired, duplicate, invalid, unauthorized, and degraded states. Failure JSONMachine-readable public failure matrix for failure class, expected state, evidence to bring, next check, recovery shape, and boundaries. Recovery drill JSONMachine-readable public drill contract for triggers, expected states, recovery actions, terminal receipts, summaries, and boundaries.

CoreAdmitted value, custody labels, chain metadata, and public review. InfraStorage, receipts, proof, BIGHT work payments, contract-work lanes, whole-product evidence gates, and retained evidence. Infra pathProduct route for BIGHT purchase, upload, receipt verification, retrieval, contracts, providers, proof memory, and payload boundaries. Infra pricingPublic work-pricing guide for pricing posture, BIGHT conversion, tiers, and upload/account boundaries. BridgePassage, acquisition, reserve ledger, inventory truth, vault lanes, gates, counterparties, host evidence, proof labels, receipts, and staged movement boundaries. Bridge pathProduct route for native acquisition, inventory truth, route-output classification, owner vaults, host evidence, provider risk, and proof receipts. LiquidFast movement, signed lifecycle smoke, motion proposals, wrappers, settlement labels, and market posture where publishable. Liquid pathMarket path for quotes, orders, positions, wrappers, risk, liquidation, venue quality, settlement truth, and public boundaries. Stack overviewFour-chain role map, architecture in plain terms, use cases, roadmap gates, and safety boundaries. ArchitectureHow Core, Infra, Bridge, Liquid, and service surfaces fit without merging authority.

ActivationMinting policy, distribution, value movement, liquidity, and market-opening path. Core pathHow Core should be read before any economic or validator claim is trusted. RoadmapPhase-based opening path and evidence gates. PhasesNow, next, later, and what evidence changes phase labels. ReadinessObserved, staged, production, and public opening labels. Readiness officeCurrent product, technical, operating, financial, and market gaps without private procedure. Readiness lensesThe public checkpoint frame for judging those gaps without flattening chain boundaries. Network useUsable public paths, usage evidence standards, partner disclosure boundaries, and what does not count as traction. UpdatesDated public release notes. CommunityPublic coordination without seed phrases, payments, or private support promises. Discord onboardingPublic coordination guide for roles, reports, docs feedback, updates, and support boundaries.

DocsTester, validator, reviewer, and provider paths. CategoryHow to explain QUAD without turning it into a generic bridge, DePIN, mining chain, or claim page. Product comparisonWhat QUAD may be mistaken for, what it actually does, what proof to check, and what is not claimed. Data provenanceHow owner, route, proof class, freshness, and boundary travel with public data. Data catalog JSONMachine-readable public dataset catalog for owner, freshness, stale behavior, redaction, and non-inference rules. Reconciliation JSONHow public claims downgrade when sources conflict, schemas are incomplete, lineage breaks, or live routes disagree with local packages. Lineage JSONHow public JSON moves from source route to release package and display route, and how claims degrade when that path breaks. Freshness JSONHow stale-state labels, machine labels, consumer behavior, and downgrade behavior should be applied to public data. Redaction JSONHow public fields, private fields, redaction behavior, and consumer behavior should be applied before publishing data. Retention JSONHow retained fields, pruned fields, tombstones, restore/reissue states, and terminal receipts should be read. Consumer JSONHow readers, wallets, explorers, websites, keepers, importers, proof/reissue services, dashboards, reviewers, pricing engines, and refusal gates may use public data. Readiness JSONHow catalog, schema, lineage, freshness, redaction, retention, reconciliation, consumer, wording, evidence, and owner-review checks decide dataset readiness. Review Questions JSONHow purpose, owner, producer, evidence class, freshness, failure behavior, inference, public need, and trust-from-action questions decide whether data should publish, downgrade, hold, or refuse. Information Governance JSONHow facts distinguish active source, generated artifact, deployed route, external reference, stale copy, internal-only material, and non-authoritative copies. ReferencesHow to read official references, outside links, repo material, listings, and audit slots without inventing validation. External referencesHow to make outside references useful without pretending they are endorsement, launch, rewards, or market access. CredibilityHow to read proof handles, owner routes, pending assets, and boundaries before trusting a claim. JourneysHow to choose the right owner, action, receipt, and next public check. GlossaryTerms for QUAD, Core, Bridge, Infra, Liquid, Vault, and service surfaces. WalletsHow to read metadata, denom labels, balances, fees, finality, wrappers, and vouchers. IntegratorsHow to build against public contracts without overclaiming state. ContractsHow public data shapes should name owner, version, freshness, evidence class, and non-inference boundary. Infra pathHow to use Infra as a product surface without inferring rewards, reserve backing, or payload truth. Bridge pathHow to read Bridge passage without inferring live bridging, wrapper minting, redemption, swaps, or destination admission. Liquid pathHow to read Liquid market posture without inferring live trading, yield, guaranteed execution, or Core worth. SourcesHow to choose the authoritative public source before quoting or building against a claim. FeesHow to read expected cost, actual charge, refund, finality, and receipt closure before acting. LifecycleHow an action should move from request to closure without hiding stop states. ObligationsHow operating costs and payable states should shrink or close public claims. RisksHow assumptions, unknowns, stale routes, and dependencies should reduce or close public claims. OperatorsHow to read operational roles without exposing private procedures. GovernanceHow to read proposals without treating votes as private override. SupportHow to bring public evidence without exposing private material. PlaybooksHow to narrow visible failures with public ids, safe escalation boundaries, and next checks. Proof archiveHow to quote progress by owner, proof class, public route, boundary, and freshness. Dependency mapHow stale, blocked, external, or local-only dependencies shrink public claims. Acceptance pathsHow to tell whether a journey has enough owner, cost, receipt, failure, and boundary evidence. Custody mapHow to separate account class, spendability, payables, receivables, reserve, and quarantine. ContinuityHow release labels, downgrade behavior, fallback states, and handoff boundaries should be read. Error labelsHow to make refused, stale, unpaid, invalid, and unavailable states readable. SecurityAudit posture, publication boundaries, and withheld mechanics. summary.txtPlain-language canonical summary. llms.txtAssistant quoting guide and misclassification guardrails. robots.txtCrawler allowance file that points search and assistant crawlers toward the static public entry paths. sitemap.xmlMachine-readable sitemap for search discovery.

core.uquad.orgCore chain observatory, chain state, chain metadata, official purchase path, and endpoint boundaries. infra.uquad.orgInfra storage, receipts, proof, BIGHT wallet paths, public data, and contract surfaces. bridge.uquad.orgBridge product surface for source pools, owner vaults, acquisition, ledger, inventory, gates, counterparties, host evidence, proof, status, receipts, and public data. liquid.uquad.orgLiquid endpoint contracts, motion, position, state durability, state promotion, migration rehearsal, explicit-law labels, and publishable market state. rpc.uquad.orgPrivate endpoint service, quote-first CU purchase, fleet status, key status, payment rails, and access boundary.