Q token mark QUADPublic Accountability

Proof-first archive

Proof Archive

This page gathers the public proof classes and evidence routes without upgrading them into custody, admission, settlement, redemption, reward, or launch claims.

Evidence is useful because it is bounded. Every proof class keeps its owner and its limit.

What the stack has actually done — check it yourself

Not milestones about publishing pages: real capability, recorded on the chains' own surfaces. Each link proves the named capability only — not custody, settlement, redemption, reward, or value.

Assets have really crossed

Real cross-chain crossings, each with host-side evidence and a reconstructable receipt — recorded events, not a promise.

Bridge proof
The vaults sit on real pools

Per-user vaults are backed by actual asset pools on Ethereum and across Cosmos, with owner-vault allocation proof — not a wrapper label.

Host evidence
Core records what it refused

Admitted, quarantined, and refused actions all leave a receipt you can read — including the refusals, not just what got in.

Core receipts
Infra's loop is receipted

Buy BIGHT, upload, verify, retrieve — each step leaves a proof you can check later.

Use Infra

Dated Evidence Register

Public milestones are listed by owner, route, and limit. A stronger claim needs owner-published evidence, not momentum.

Date and ownerEvidence and routeBoundary
2026-06-02 / Main websiteWhy Use QUAD publishes the practical use case: separate accounting, work proof, passage, and motion so one surface cannot silently borrow another surface's authority.Purpose language is not a sale, allocation, reward, market, or value-claim route.
2026-06-02 / Main websiteProduct Comparison compares QUAD by job and proof owner across common misreads: bridge, DePIN, AI chain, storage network, wrapped-asset system, mining chain, explorer, and claim page.Comparison is orientation. It does not claim superiority, guaranteed security, live liquidity, sale access, rewards, or endorsement.
2026-06-02 / Main websiteData Provenance explains owner, route, proof class, freshness, source/package/deployed distinctions, and downgrade rules for public data.Provenance explains how to read data. It does not make stale, local, static, or bounded data current chain state.
2026-06-02 / Main websiteNetwork Use explains usable public product paths and the evidence standard for usage, receipt, partner, provider, and traction claims.Usage framing is evidence-gated. It does not treat community activity, screenshots, private messages, copied claims, public attention, or product-route visibility as adoption, liquidity, rewards, allocation, or investment demand.
2026-06-02 / Main websiteOperating Control Plane gives a public triage view for Core, Infra, Bridge, Liquid, the main website, and external rails.Operating status coordinates and downgrades claims. It does not grant protocol authority, governance authority, launch status, financial reconciliation, custody authority, or economic activation.
2026-06-02 / Main websiteDependency JSON publishes a machine-readable static map of surface owners, dependency classes, stale behavior, fallback behavior, and claim boundaries.The JSON is dependency data, not live telemetry. It does not prove current chain state, custody, settlement, liquidity, launch, rewards, allocation, or economic activation.
2026-06-02 / Main websiteInterface Contract JSON publishes a static public register for schema families, packets, receipts, acknowledgements, refusals, quarantine, exports, replay domains, timeout policies, and must-not-infer boundaries.The JSON is contract guidance, not live interop proof. It does not prove current chain state, custody, admission, settlement, liquidity, launch, rewards, allocation, or economic activation.
2026-06-02 / Main websiteAcceptance Journey JSON publishes a static public register for owner, entry condition, quote/cost label, receipt requirement, failure path, support path, acceptance requirement, and must-not-infer boundaries.The JSON is journey guidance, not route-open proof. It does not prove current route state, funding, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteFailure Matrix JSON publishes a static public register for failure class, expected public state, evidence to bring, next public check, recovery shape, and must-not-infer boundaries.The JSON is failure guidance, not live drill proof. It does not prove recovery has been tested live, route availability, funding, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteRecovery Drill JSON publishes a static public drill contract for triggers, expected states, recovery action classes, terminal receipt requirements, public summaries, and must-not-infer boundaries.The JSON is drill guidance, not completed drill proof. It does not prove live recovery, chain restart closure, route repair, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteRelease Provenance JSON publishes a static public release contract for artifact classes, expected checks, release path, handoff labels, rollback shape, and local-package boundaries.The JSON is release guidance, not live-upload proof. It does not prove DNS propagation, current chain state, current subdomain state, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteObservability Contract JSON publishes a static public telemetry contract for metric families, owners, stale behavior, alert labels, next checks, and must-not-infer boundaries.The JSON is telemetry guidance, not live telemetry. It does not prove current height, route state, recovery, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websitePublic Data Catalog JSON publishes a static catalog for public JSON owner surface, schema family, evidence class, freshness rule, stale behavior, redaction rule, consumer contract, and must-not-infer boundaries.The catalog is discovery and reading guidance. It does not prove live chain state, dataset completeness, owner acceptance by another surface, external validation, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteReconciliation Rules JSON publishes static downgrade rules for owner-route mismatches, fallback/live conflicts, release-package/live-domain mismatches, incomplete schemas, conflicting receipts, metadata mismatches, outside-reference scope, and broken lineage.The rules downgrade claims when evidence disagrees. They do not prove route repair, dataset completeness, owner acceptance, external validation, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteLineage Map JSON publishes static lineage rows for public JSON source class, source owner, source route, transformation, display routes, freshness signal, redaction rule, aggregation rule, and broken-lineage behavior.The lineage map explains origin and downgrade behavior. It does not prove current state, route repair, dataset completeness, owner acceptance, external validation, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteFreshness Policy JSON publishes static stale-state labels for current, fallback, cached, stale, unavailable, conflicted, local-package-only, and superseded public data.The freshness policy tells readers and tooling when claims should shrink. It does not prove owner authority, current state, route repair, dataset completeness, owner acceptance, external validation, custody, settlement, admission, liquidity, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteRedaction Boundary JSON publishes public/private field classes for public route metadata, receipt metadata, payloads, public-rented visibility, provider labels, host-chain vault labels, financial posture, route proof, doctrine-sensitive material, and support evidence packets.The redaction boundary describes what may be shown and what stays private. It does not prove current state, payload truth, provider identity, custody, settlement, admission, external validation, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteRetention Policy JSON publishes retention, prune, tombstone, restore, and reissue classes for receipt metadata, payload access, pruned datasets, owner-touch refresh, cold retention, terminal receipts, and refusal notes.The retention policy explains surviving evidence and ended access. It does not prove payload access, payload truth, current state, custody, settlement, admission, external validation, sale access, rewards, allocation, or economic activation.
2026-06-02 / Main websiteConsumer Contracts JSON publishes allowed-use and downgrade rules for public readers, wallets, explorers, website displays, chain keepers, cross-chain importers, Infra proof/reissue services, operator dashboards, governance reviewers, external reviewers, product pricing engines, and refusal gates.The consumer contract tells each reader what it may use data for. It does not grant authority, make stale data current, open product routes, prove chain state, or create economic rights.
2026-06-02 / Main websiteData Product Readiness JSON publishes readiness states and checks for catalog rows, schema versioning, lineage, freshness, stale/refusal states, redaction, retention, reconciliation, consumer contracts, public wording, evidence artifacts, and owner review.The readiness gate says when a dataset may be trusted within boundary. It does not make data authoritative, current, externally validated, accepted by another surface, or economically active.
2026-06-02 / Main websiteData Stewardship Questions JSON publishes the standing review questions for dataset purpose, owner, producer route, evidence class, freshness, failure behavior, safe inference, forbidden inference, public need, and trust-from-action.The question set reviews meaning before use. It does not make data authoritative, current, externally validated, accepted by another surface, or economically active.
2026-06-02 / Main websiteInformation Governance JSON publishes source, artifact, deployed-route, external-reference, stale/superseded, internal-only, non-authoritative-copy, access, change, observability, runbook, and recovery packet rules.The governance contract makes facts easier to recover and quote inside boundary. It does not expose private procedure, credentials, current chain state, owner acceptance, or economic activation.
2026-06-02 / Main websiteUpdates publishes update types, cadence rules, and the required dated-update shape for future public notes.Updates point to owner proof. They do not replace proof, open economic lanes, or upgrade old evidence into current state.
2026-06-02 / Main websiteStack Overview publishes the one-sitting role map: Core accounts, Infra proves, Bridge carries, and Liquid moves.Stack narrative is orientation. It does not prove chain state, production value movement, liquidity, allocation, or economic opening.
2026-06-02 / Main websiteStack Overview now separates observable state, product-active paths, published boundaries, staged/local evidence, and external references.This makes evidence easier to quote narrowly. It does not turn staged or local evidence into live deployed proof.
2026-06-02 / Main websiteCommunity Onboarding gives first actions for Discord, tester questions, validator interest, bug reports, docs feedback, update channels, and public chat routing.Community participation is coordination. It is not allocation, reward eligibility, validator advantage, governance rights, private support, or authority over chain state.
2026-06-02 / Main websiteExternal References names the outside-reference path for registries, explorers, wallets, repos, articles, community posts, and search/crawler summaries.Outside references help discovery only inside their published scope. They do not prove endorsement, custody, audit completion, launch, market access, or economic activation.
2026-06-02 / Main websitePhases publishes observe, harden, explain, freeze, open narrowly, and expand-on-proof gates.Phase language is evidence-gated. It does not open sale access, rewards, live liquidity, market activation, or production value movement.
2026-06-02 / Main websitePublic References publishes the reference ladder for official surfaces, repos, registries, explorers, audit slots, and outside summaries.References help discovery inside their own scope. They do not prove endorsement, audit completion, custody, launch, or market access.
2026-06-02 / Main websiteCategory Guide gives the public category handle for admitted value, verifiable work, controlled passage, and fast settlement.Category wording prevents misclassification. It is not a product-availability, wallet, claim, investment, or liquidity signal.
2026-06-01 / CoreCore receipts can expose Bridge-origin quarantine-only receiver evidence where published.Receiver evidence is delivery-not-admission. It is not Treasury admission, spend authority, sale access, or production value movement.
2026-06-01 / Main websiteReceipts and Support, Support Playbooks, and Continuity define what to provide, what to withhold, and how stale or degraded routes should be read.Support paths route public evidence. They do not expand proof meaning, expose private procedure, or create economic rights.

Current Evidence Routes

Use these routes for the latest owner-published proof. If a route is stale or unavailable, say that directly.

EvidenceCurrent public routeBoundary
Core chain observationcore.uquad.org publishes Core observation routes, blocks, validators, chain metadata, endpoint contract, receipts, and status labels where available.Observation is not sale access, market value, custody upgrade, redemption, or economic activation.
Core receiver rehearsalCore receipts and delivery-index surfaces can show Bridge-origin quarantine-only receiver receipts where published.Receiver evidence is delivery-not-admission. It is not Treasury admission or production value movement.
Infra product evidenceinfra.uquad.org publishes BIGHT wallet support, quote-first purchase, upload, verify, retrieve, contracts, balances, receipts, proof, and public data lanes.Infra receipts prove bounded service events, not payload truth, Core value, Bridge finality, or Liquid settlement.
Bridge product evidenceBridge product, proof, host evidence, ledger, inventory, vault, and gate pages publish passage posture where available.Bridge evidence does not force destination admission, redemption, native ownership, or public movement.
Liquid motion evidenceliquid.uquad.org publishes status, proof, roles, readiness, endpoint contracts, motion/position JSON, state labels, and pre-SDK motion evidence where available.Motion evidence is not final settlement, live market activity, Core worth, or balance truth by itself.
Main-site release evidenceMain-domain release checks are recorded in local release receipts and packaged through `launch.zip` with a manifest hash before Hostinger upload.Local release evidence is not live propagation, Hostinger upload, or chain activation.

Source, Package, Deployed

These states are deliberately separate. Mixing them is how old proof turns into bad summaries.

Source evidence

A page, checklist row, JSON file, or code change exists in a working folder. It can guide review, but it is not deployed evidence by itself.

Package evidence

A release artifact passed local checks, rendered smoke, zip validation, and manifest hashing. It proves package condition, not live propagation.

Deployed evidence

The owning public domain or subdomain serves the route. It still proves only the named route, status, receipt, or proof class.

Superseded evidence

Older receipts remain history. They should not be quoted as current height, current balance, current volume, current route state, or current readiness.

Proof Class Map

Use the proof class first, then read the owning surface.

Observation

Blocks, validators, status, metadata, endpoint contracts, and public labels. Good for liveness and route ownership, not economic claims.

Receipt

A bounded event record: upload, retrieval, passage, refusal, quarantine, quote, status, or settlement request.

Proof

A source-backed proof path from the owning surface. It proves the named event class, not every downstream interpretation.

Refusal

A published no, expiry, duplicate, invalid, unavailable, unpaid, unauthorized, or quarantine state. Refusal is evidence too.

Endpoint contract

A public promise about route shape and status. Endpoint visibility is not admission, custody, or launch.

Release check

A website/package validation receipt. It proves local package condition, not live domain state.

What To Quote

Quote narrow evidence. Do not inflate it.

1. Owner

Name Core, Infra, Bridge, Liquid, or the main website.

2. Proof class

Name observation, receipt, proof, refusal, endpoint contract, or release check.

3. Public route

Link the public page, JSON, proof route, receipt page, or status page.

4. Boundary

Say what the proof does not prove.

5. Freshness

If current state cannot be verified, say so directly.

Archive Boundaries

The archive should make stronger claims harder, not easier.

No private proof upgrade

Private work is not a public claim until an owning public surface publishes it.

No stale upgrade

Old proof does not become current height, current balance, current volume, or current route status.

No cross-surface inflation

Infra proof does not become Core admission; Bridge receipt does not become destination acceptance; Liquid motion does not become settlement truth.

No market inference

Proof of liveness, product work, route posture, or receipts does not imply price, liquidity, allocation, reward, or investment status.