Q token mark QUADPublic Accountability

Trust the owner, label the rest

Source Of Truth Map

A source-of-truth map tells a reader where a claim is owned, when it is only a summary, and how to downgrade stale, cached, local-only, or external references.

The main website explains meaning. The owning surface proves current state.

Truth Ladder

Use the strongest available public source. If a stronger source is missing or stale, say that plainly.

RankSource classHow to quote it
1Owning chain or product surfaceQuote as current only when the owner publishes current state, freshness, and boundary.
2Owner-published JSON, endpoint contract, receipt, or status pageQuote the exact label, timestamp, owner, and non-inference boundary.
3Main-domain orientation pageUse for purpose, naming, route discovery, definitions, and claim boundaries.
4Static fallback or cached exportQuote as fallback or cached only. Do not call it current chain state.
5External indexer, wallet registry, search result, or third-party summaryUse as a reference only when it matches the owner or clearly labels its own limits.
6Assistant, crawler, forum, chat, or repostNever use as authority. It may quote the site; it does not replace the site.

Surface Ownership

Each public surface owns a different class of truth. Coordination does not merge authority.

Core owns Core stateChain observation, public law labels, Core metadata, validator posture, admission labels, receiver evidence, and Core economic boundaries. Infra owns BIGHT workFunding quotes, upload, retrieval, receipts, proof, contract-work lanes, retained evidence, balance labels, and Infra data contracts. Bridge owns passage evidenceRoute posture, source pools, owner vaults, acquisition records, inventory labels, gates, host evidence, proof, and movement boundaries. Liquid owns motion postureMotion, position, wrapper, risk, settlement-request, explicit-law, readiness, and market-closed labels where published. Main website owns orientationIdentity, purpose, route discovery, public docs, static fallback, claim boundaries, and crawler-readable summaries. Contracts own reading rulesSchema shape, owner fields, freshness rules, stale states, consumer behavior, and must-not-build warnings.

Current, Cached, Local, External

  • Current: the owning public surface publishes a fresh value and a readable boundary.
  • Cached: the value was copied from another source and must carry age or snapshot context.
  • Static fallback: a baseline display that keeps the page understandable when a live feed is unavailable.
  • Local-only: source-folder or working evidence that is not yet a public deployed claim.
  • External: registry, indexer, wallet, or third-party reference that should match the owner before being repeated.

Conflict Rules

  • Owner beats mirror: the owning surface outranks copied summaries and old exports.
  • Fresh beats stale: stale values may be historical evidence, not current state.
  • Specific beats general: a chain-owned receipt beats a broad main-domain summary for that event.
  • Label beats inference: if the owner says refused, staged, closed, stale, or not yet public, keep that label.
  • Unknown stays unknown: missing live data should become cannot verify, not an invented number.

Quote Rules

A good public quote says what was read, who owns it, how fresh it is, and what it does not prove.

Quote owner

Name Core, Infra, Bridge, Liquid, main website, wallet registry, indexer, or external rail when quoting a record.

Quote state

Include live, staged, closed, stale, degraded, refused, quarantined, retired, or cannot verify where the source provides it.

Quote freshness

Use the timestamp, block height, version, release hash, or snapshot label where available.

Quote boundary

State whether the record proves observation, receipt, metadata, route posture, proof, refusal, finality, or orientation.

Do not upgrade

Do not turn metadata, routes, receipts, visible balances, fallback JSON, or search snippets into launch, custody, admission, liquidity, redemption, or reward claims.

Do not invent

If height, balance, receipt status, route state, or finality cannot be read from the owner, say it cannot be verified.

Claim-To-Source Map

Start from the kind of claim. Then open the surface that owns it.

ClaimFirst sourceDowngrade if missing
What is QUAD?summary.txt, About, PurposeDo not infer identity from search snippets or name similarity.
Which surface owns this action?Public surfaces, Journeys, Custody mapDo not merge Core, Infra, Bridge, and Liquid roles.
Is a product route open?Owning subdomain, state labels, error labelsUse closed, staged, stale, or cannot verify.
What fee or finality applies?Fees and finality, owning quote/status route, wallet fee labelsDo not infer custody, yield, admission, destination acceptance, or settlement from a fee label.
What lifecycle state applies?Action lifecycle, owning status or receipt routeDo not treat a lifecycle label as proof a closed, stale, or missing route is open.
What does a receipt prove?Receipt guide, owning receipt endpoint, ContractsLimit the claim to the event and proof class.
Can a wallet show this chain?Wallet labels, owner chain metadataMetadata does not prove spend authority or launch.
Is there custody, reserve, liquidity, or admission?Financial inference check, owning chain evidenceDo not infer from balances, wrappers, route labels, or registry files.
Is an endpoint schema stable?Public contracts, owner endpoint contractUse stale, missing, unsupported, or cannot verify.
Which public JSON files exist?Public data catalog, Data provenance, ContractsCatalog presence does not prove live state, dataset completeness, external validation, or owner acceptance by another surface.
What if sources disagree?Reconciliation rules, Data provenance, owner routeUse the strongest readable owner state. If that cannot be read, downgrade to stale, conflicted, or cannot verify.
Where did a public data point come from?Lineage map, Data provenance, release receiptIf source, transformation, freshness, or boundary cannot be named, do not use the value for current-state or action claims.
How fresh is a public value?Freshness policy, Data provenance, owner routeIf freshness cannot be named, quote fallback, cached, stale, conflicted, local-package-only, or cannot verify instead of current state.
Can this field be public?Redaction boundary, Boundary, owner routeIf public/private class cannot be named, keep payloads, secrets, private procedure, payment mechanics, and sensitive provider detail out of the public claim.
Does this record still exist?Retention policy, Lifecycle, Support, owner routeIf retention state cannot be named, say cannot verify instead of inventing payload access, deletion, restore, or terminal status.
Who may use this data?Consumer contracts, Public contracts, Data provenance, owner routeIf the consumer, allowed use, required checks, and refusal behavior cannot be named, keep the path at orientation-only or refuse stronger action.
Is this dataset ready?Data product readiness, Data catalog, Consumer contracts, release receipt, owner routeIf catalog, schema, lineage, freshness, redaction, retention, reconciliation, consumer, wording, evidence, or owner review is missing, keep the dataset partial, not ready, or historical only.
Has this dataset answered the standing questions?Review questions, Data product readiness, owner routeIf purpose, owner, producer, evidence, freshness, failure behavior, inference, public need, or trust-from-action is unanswered, publish only as orientation, hold/redact, or refuse stronger action.
What state is this fact in?Information governance, release receipt, owner route, source mapSeparate active source, generated artifact, deployed route, external reference, stale/superseded material, internal-only material, and non-authoritative copies before quoting.
What changed recently?Updates, Proof archive, owner surface receiptsLocal source evidence is not deployed evidence until published.

Public Enough To Quote

  • Public chain id, denom, address prefix, and owner-published metadata.
  • Public route labels, status labels, receipt ids, proof classes, and timestamps.
  • Public release hashes, sitemap entries, static summaries, and assistant quoting guides.
  • Public evidence that an owning surface chooses to publish with a boundary.

Not Public Authority

  • Private keys, private accounts, private payment details, and private payloads.
  • Provider account setup, unpublished configuration, and sensitive recovery material.
  • Old zips, old screenshots, old registry drafts, stale cache, and copied summaries.
  • Assistant answers, crawler guesses, chat comments, search snippets, or forum reposts.