Q token mark QUADPublic Accountability

Proof handles

Credibility Inventory

A public inventory of the proof handles QUAD can point to today, who owns them, and what each handle cannot prove.

How To Read Credibility

Credibility comes from owner-published evidence, not volume, social pressure, or a familiar-looking page.

Owner first

Use the chain or product surface that owns the claim before quoting it.

Proof class second

Name observation, receipt, proof, refusal, endpoint contract, release check, registry packet, or report slot.

Boundary always

Every proof handle should say what it does not prove.

Freshness matters

Old proof remains history. It should not be quoted as current state.

Public Proof Handles

These are useful because they are narrow. None of them becomes universal validation.

AssetWhat it can proveWhat it cannot prove
Core observatorycore.uquad.org can publish Core chain observation, validators, metadata, receipts, endpoint contracts, and status labels.Sale access, redemption, liquidity, price, production value movement, or Core economic opening.
Infra product surfaceinfra.uquad.org can publish BIGHT funding, upload, verify, retrieve, balances, proof, ledger, and receipt paths.Core admission, payload truth, Bridge finality, Liquid settlement, node earning, or raw compute rewards.
Bridge product surfaceBridge product can publish acquisition, pools, vaults, route gates, host evidence, receipts, proof, and refusal posture.Destination admission, redemption, live swapping, wrapper minting, reserve backing, or open movement.
Liquid surfaceliquid.uquad.org can publish motion, position, risk, readiness, endpoint contracts, and market-closed labels.Final balance truth, Core worth, reserve quality, live market access, or settlement by speed alone.
Proof archiveEvidence timeline can show dated entries, current routes, source/package/deployed distinctions, and superseded proof.Current state unless the owner route is fresh and reachable.
Data provenanceData Provenance can show how owner, route, proof class, freshness, and boundary travel with public data.It does not make stale, local, static, or bounded data current chain state.
Product comparisonProduct Comparison can explain common misreads and route readers to the owner surface that carries proof.It does not prove superiority, audit completion, live liquidity, sale access, rewards, or external endorsement.
Source mapSource-of-truth map ranks owner routes, JSON, receipts, main-domain orientation, static fallback, external sources, and assistant summaries.A weaker source cannot upgrade a missing owner claim.
Reference ladderReferences separate official pages, repos, registry packets, explorers, audit slots, forum posts, and assistant summaries.Discovery, indexing, or discussion as endorsement.
Public repository materialExternal References defines how intentionally published repository material should name scope, owner, phase, proof, and boundary.A repo is not launch, audit, listing, liquidity, reward access, market access, or production activation.
Release receiptsMain-domain receipts can prove local package checks, smoke checks, zip freshness, and manifest hashes.Hostinger upload, live propagation, chain state, accepted listings, or economic activation.

Credibility Assets By Audience

Different readers need different proof handles.

New visitorReader paths, stack overview, category guide, and boundary page. ValidatorCore chain observation, validators, chain metadata, endpoint contract, and operator labels. BuilderIntegrator guide, public contracts, source map, wallets, fees, lifecycle, and stale-state rules. Security reviewerSecurity posture, audit slots, disclosure boundaries, and proof archive. Financial reviewerObligations, fees/finality, custody/account map, risks, and readiness office. Outside reference readerReference ladder, registry posture, repo boundaries, explorer/listing status, and report slots. Data readerOwner, route, proof class, freshness, and downgrade rules for public data.

Missing Or Pending Handles

Pending items stay pending until a public owner route or accepted third-party source exists.

Audit reportNo completed public external audit report is claimed here.
Accepted listingRegistry and explorer packets are review artifacts until accepted by the outside owner.
Partner proofNo public partner or pilot claim is made without approved public disclosure.
Economic openingSale, reward, liquidity, market, redemption, and production movement lanes remain closed unless owner evidence says otherwise.

What To Quote

Use a narrow sentence. That is what keeps proof from turning into sales language.

1. Name the owner

Core, Infra, Bridge, Liquid, main website, or an outside owner.

2. Name the route

Link the public page, JSON, receipt, report, or index.

3. Name the proof

Observation, receipt, proof, refusal, endpoint contract, release check, or accepted external source.

4. Name the limit

Say what the proof does not prove.

5. Name freshness

If current state cannot be read, say it cannot be verified.