Q token mark QUADPublic Accountability

Public data, owned meaning

Data Provenance

Public data is useful only when the owner, route, proof class, freshness, and boundary are visible together. This page explains how to read QUAD public data without turning stale, local, or bounded evidence into a stronger claim.

Source Map Data Catalog JSON Reconciliation JSON Lineage JSON Freshness JSON Redaction JSON Retention JSON Consumer JSON Readiness JSON Review Questions JSON Information Governance JSON Public Contracts Proof Archive Verify Claims

The Provenance Rule

A public value should be read with the surface that produced it and the limits that travel with it.

1. Owner

Core, Infra, Bridge, Liquid, main website, or an accepted outside source.

2. Route

The page, JSON, receipt, endpoint contract, artifact, or report that carries the data.

3. Proof class

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

4. Freshness

Current timestamp, update cadence, stale label, superseded label, or cannot-verify state.

5. Boundary

What the data does not prove for value, custody, admission, settlement, launch, market access, or entitlement.

Owner Surfaces

Use the owner route before quoting the value.

OwnerData it can publishWhat not to infer
CoreChain observation, validators, blocks, metadata, endpoint contracts, receipts, supply/economic labels, admission posture, and status.Sale access, redemption, price support, live liquidity, or sibling-chain authority.
InfraBIGHT funding paths, upload, verify, retrieve, contracts, balances, ledger, receipts, proof, retained evidence, reserve labels, and product data.Core admission, payload truth, raw compute rewards, node earning, Bridge finality, or Liquid settlement.
BridgeAcquisition, inventory, source pools, owner vault labels, gates, host evidence, counterparties, ledger records, receipts, proof, and movement-closed labels.Destination admission, wrapper minting, live swapping, redemption, reserve backing, or open movement.
LiquidMotion, positions, risk posture, settlement requests, endpoint contracts, readiness labels, explicit-law data, and market-closed state.Final balance truth, Core worth, live market access, settlement by speed, or reserve quality.
Main websiteOrientation, summaries, crawler files, source maps, proof archive, release receipts, docs, and boundary rules.Live chain state, Hostinger propagation, subdomain deployment, external acceptance, or economic activation.
Outside ownerRegistry, explorer, wallet, audit, repo host, article, or indexer status only within the scope it publishes.Endorsement, launch, custody, audit completion, or market access beyond the outside source's explicit scope.

Data Classes

Different data classes have different failure modes.

Live or current

Served by an owner route with current freshness. If it cannot be read, quote it as unverifiable.

Static fallback

Useful for meaning, route shape, and crawler reading. It should not be quoted as live height, balance, volume, or market state.

Receipt data

Proves a bounded event under the owner surface. It does not force another surface to accept the same meaning.

Release artifact

Proves local package condition, smoke checks, manifest hash, or export state. It does not prove live upload or chain state.

Staged or local

Useful for readiness and review. It is not a public owner route until published by the owner surface.

Superseded

Useful for history. It should not be treated as current state, current proof, or current risk posture.

Public Data Catalog

The catalog is the machine-readable companion to this page. It names each main-domain JSON file, owner surface, evidence class, freshness rule, stale behavior, allowed use, redaction rule, consumer contract, and what must not be inferred.

RouteUseBoundary
data/public-data-catalog.jsonUse when tooling needs to discover which public JSON files exist and how each one should be read.Catalog presence does not make a dataset live, current, complete, accepted by another surface, or externally validated.

Reconciliation Rules

When public sources disagree, the reconciliation rules explain how to make the claim weaker until the owner route publishes a clear state.

RouteUseBoundary
data/reconciliation-rules.jsonUse when tooling or readers need to handle stale fallbacks, live-route mismatches, release-package mismatches, incomplete schemas, conflicting receipts, metadata mismatches, outside-reference scope, or broken lineage.Reconciliation guidance downgrades claims. It does not prove a route is live, repaired, complete, accepted by another surface, or externally validated.

Lineage Map

The lineage map explains how each public JSON file moves from source route to public display, and what must happen when source, transformation, freshness, or boundary cannot be named.

RouteUseBoundary
data/lineage-map.jsonUse when tooling or readers need source class, source owner, source route, transformation, display routes, freshness signal, redaction rule, aggregation rule, and lineage-break behavior for main-domain JSON files.Lineage guidance explains where data came from and how claims degrade. It does not prove current state, route repair, dataset completeness, owner acceptance, or external validation.

Freshness Policy

The freshness policy names how public values should be labelled when they are current, fallback, cached, stale, unavailable, conflicted, local-package-only, or superseded.

RouteUseBoundary
data/freshness-policy.jsonUse when tooling or readers need public labels, machine labels, consumer behavior, downgrade behavior, and must-not-infer boundaries for stale-state handling.Freshness guidance shrinks or qualifies public claims. It does not prove owner authority, current state, route repair, dataset completeness, owner acceptance, or external validation.

Redaction Boundary

The redaction boundary names what public datasets may show and what must remain private across payloads, receipts, providers, host-chain labels, financial posture, route proof, and doctrine-sensitive material.

RouteUseBoundary
data/redaction-boundary.jsonUse when tooling or readers need public/private data classes, allowed public fields, private field classes, redaction behavior, consumer behavior, and must-not-infer boundaries.Redaction guidance protects payloads, secrets, credentials, private procedure, payment mechanics, sensitive provider detail, and protected implementation detail. It does not prove payload truth, provider identity, custody, settlement, admission, or current state.

Retention Policy

The retention policy names what public metadata survives after payload access ends, what can be pruned, how tombstones should read, and what restore or reissue is allowed to prove.

RouteUseBoundary
data/retention-policy.jsonUse when tooling or readers need retained public fields, prunable private fields, tombstone behavior, restore/reissue behavior, consumer behavior, and must-not-infer boundaries.Retention guidance explains surviving evidence and ended access. It does not prove payload access, payload truth, current state, custody, settlement, admission, or external validation.

Consumer Contracts

The consumer contract names who may read a dataset, what they may use it for, what they must check first, and when the path must downgrade or refuse.

RouteUseBoundary
data/consumer-contracts.jsonUse when tooling or readers need allowed-use rules for public readers, wallets, explorers, website display, chain keepers, cross-chain importers, Infra proof/reissue, operator dashboards, governance, external review, product pricing, and refusal gates.Consumer guidance does not grant authority, make stale data current, open product routes, prove chain state, or create economic rights.

Data Product Readiness

The readiness gate names the checks a dataset needs before it can be trusted inside its own boundary.

RouteUseBoundary
data/data-product-readiness.jsonUse when tooling or readers need readiness states and checks for catalog, schema, lineage, freshness, stale/refusal behavior, redaction, retention, reconciliation, consumer contract, wording, current evidence, and owner review.Readiness guidance does not make a dataset authoritative, current, accepted by another surface, externally validated, or economically active.

Standing Review Questions

The question set is the public review rubric for deciding whether data is useful, publishable, action-ready, orientation-only, or should be held.

RouteUseBoundary
data/data-stewardship-questions.jsonUse when tooling or readers need standing questions for purpose, owner, producer, evidence class, freshness, failure behavior, safe inference, forbidden inference, public need, and trust-from-action.Questions review meaning before use. They do not make a dataset authoritative, current, accepted by another surface, externally validated, or economically active.

Information Governance

The governance contract separates active source, generated artifact, deployed route, external reference, stale copy, internal-only material, and non-authoritative copies.

RouteUseBoundary
data/information-governance.jsonUse when tooling or readers need source state, artifact state, route state, control domains, change-record behavior, access boundaries, recovery packet classes, and closure questions.Information governance makes facts recoverable and quotable inside boundary. It does not expose private procedure, credentials, current chain state, owner acceptance, or economic activation.

Freshness And Downgrade

If freshness is unclear, the public claim should get weaker.

If the data is...Say thisDo not say this
Current and owner-publishedThe owner surface currently publishes this value or state.It proves more than the route's stated scope.
Static fallback onlyThe site publishes a static label, explanation, or route contract.The value is live, current, moving, or economically active.
Local package evidenceThe local release artifact or working source supports review.The public domain is updated or an external owner accepted it.
Stale, blocked, or unreachableCurrent state cannot be verified from the public route.Invented height, balance, volume, status, rewards, or launch state.
External referenceThe outside owner published this reference within its own scope.The outside source endorsed everything QUAD claims.

Safe To Publish

  • Public route names, public timestamps, public ids, public receipts, public endpoint contracts, and public status labels.
  • Owner, proof class, freshness, and boundary for a public route.
  • Dated release receipts and package hashes for the main website.
  • Accepted outside reference status where the outside owner publishes it.

Keep Out

  • Seed phrases, private keys, recovery phrases, credentials, private endpoints, and private payment details.
  • Private payloads, protected operator procedure, sensitive recovery mechanics, and exploit detail.
  • Claims that turn local work, crawler guesses, community comments, or public attention into authority.
  • Unsupported sale, reward, liquidity, market, launch, audit, listing, or endorsement claims.