Q token mark QUADPublic Accountability

Dependency discipline

Dependency Map

This page names the public dependencies that shape QUAD, Core, Infra, Bridge, and Liquid. If a dependency is stale, missing, blocked, or local-only, the public claim must downgrade with it.

A link between surfaces is not inherited authority. It is a thing to verify.

Machine-Readable Map Information Governance JSON Operating Control Plane Source Map Continuity

How To Read Dependencies

Dependencies are not marketing decoration. They decide what can continue, sleep, refuse, retry, quarantine, or downgrade.

RequiredThe route cannot honestly open without it.
ExternalThe surface relies on a host chain, provider, wallet, indexer, or public site outside its own runtime.
StaleThe public page may remain useful, but current state cannot be inferred.
DegradedThe route is still readable or partially usable with weaker claims.
BlockedThe dependency is missing or not yet proved for the requested action.
Local-onlySource-folder evidence exists, but the matching public route has not caught up.

Surface Dependency Matrix

Each surface owns its own state. Shared routes help readers, but they do not merge authority.

SurfacePublic dependenciesIf dependency is stale or blocked
CoreValidators, Core RPC/status, Core index pages, chain metadata, wallet metadata, registry packets, public receipts, and bounded website explanation.Core observation can continue if the chain is reachable, but admission, custody, supply, and launch claims must stay with Core-owned proof.
InfraBIGHT wallet labels, quote-first funding path, upload/verify/retrieve routes, storage providers, receipt memory, proof routes, balances, contracts, and public data exports.Service routes should refuse, wait, or publish a weaker status. Infra receipts do not become Core admission, Bridge finality, or Liquid settlement.
BridgeSource pools, owner vaults, host-chain status, route providers, relayer/IBC posture, fee evidence, gate labels, host evidence, inventory, ledger, and proof pages.Bridge should keep passage closed, record-only, quarantined, refunded, or pending until the owning route proves more.
LiquidMotion engine state, position views, risk labels, wrapper labels, settlement owner, Bridge/Infra export routes, endpoint contracts, and market-closed posture.Motion can be visible while settlement, market access, balance truth, and Core worth remain unclaimed.
Main websiteStatic HTML, sitemap, summary, assistant guide, release package, public summaries, claim boundaries, and subdomain links.The main site can orient and route readers, but it does not prove current chain height, balances, custody, settlement, or production activation.

Machine-Readable Map

The public JSON map carries the same boundary in a shape that crawlers, reviewers, and future tooling can read without scraping prose.

Scope

Surface owner, public role, dependency class, stale behavior, fallback behavior, and claim boundary.

Limit

The JSON is a static public dependency map. It does not prove current chain state, custody, admission, settlement, liquidity, launch, rewards, allocation, or economic activation.

Information Governance Layer

Dependencies are only useful when their source state is named. The information-governance contract separates source, artifact, deployed route, external reference, stale copy, and internal-only material.

Use

Use it before treating a dependency, route, zip, export, recovered folder, or outside reference as current authority.

Limit

The contract does not expose private procedure, credentials, provider detail, current chain state, or economic activation.

Shared Support Rails

These rails help the public inspect the stack. They are support infrastructure, not chain authority.

RPC and status

Used for liveness and current state. If unreachable, say current state cannot be verified.

Indexers and explorers

Used for discoverability and inspection. Listing does not create launch, value, liquidity, or endorsement.

Wallet metadata

Used for chain labels, denoms, prefixes, and fee display. Metadata is not a sale, claim page, or price feed.

Relayers and host chains

Used for movement or host evidence where explicitly active. Transport is not destination admission.

Public sites

Used for summaries, status, receipt lookup, and proof routing. Static pages are not live telemetry unless the owning route says so.

Community coordination

Used for questions, tester coordination, and support. Joining a channel creates no allocation, reward, entitlement, or privilege.

Downgrade Rules

When a dependency fails, the public story gets smaller. That is a feature, not a failure.

Continue

Read-only pages, older receipts, and static boundaries may remain useful when clearly labeled.

Sleep

Routes that need current sibling state can wait without pretending progress happened.

Refuse

Invalid, unpaid, stale, unauthorized, duplicate, or unsupported actions should return named refusal labels.

Retry

Transient host, RPC, indexer, or relayer issues can retry without creating a stronger claim.

Quarantine

Boundary-crossing material can be held for review instead of entering an owning economy.

Downgrade

If current state cannot be read, say so. Do not infer from old proof, cached pages, or adjacent surfaces.

What This Page Withholds

Public dependency mapping should help readers reason correctly without publishing sensitive operations detail.

No private configuration

Private keys, credentials, provider internals, and private endpoint configuration stay out of public pages.

No private procedure

The public map names dependencies and claim effects, not behind-the-scenes operating steps.

No automatic authority

Dependency visibility never turns one chain into the authority for another chain's admission, custody, settlement, or balances.