Q token mark QUADPublic Accountability

Public Rosetta Stone

Glossary

A plain-language map for the terms readers will meet across Core, Infra, Bridge, Liquid, receipts, status labels, and product pages.

Term Map

Start with these core meanings. Expand the archive only when a specific term needs translation.

The projectThe public map for separate QUAD-related workstreams and public-site assets. It is not a claim page or operator manual.
CoreThe stable public accounting surface for admitted value, supply condition, and monetary status.
InfraThe utility-work surface for storage, retrieval, receipts, proofs, BIGHT-paid services, balances, ledgers, and accepted product work.
BridgeThe boundary layer for movement, route posture, host evidence, refusal, and receipts between systems.
LiquidThe motion and settlement-adjacent surface for fast state, positions, risk labels, clearing posture, and market-state labels.
BIGHTInfra work metering and product payment token. It is not reserve collateral or its own backing.
EvidenceA receipt, proof, quote, route, upload, retrieval, refusal, or status record from the owning surface.
MainnetProduction network state, used only when the public production surface exists.
More term translations
Core custodyThe custody and accounting surface that gives admitted value a public rule base.
Legacy service labelsOlder or internal wording such as Data Chain or Compute should be read as service-area labels, not QUAD's public identity.
WorkAccepted service requests and returned results. Public pages should say which surface owns the work and receipt.
StorageRetained memory and retrieval paths for records Infra agrees to hold.
ProviderA participant offering service capacity when the public path is open and the relevant chain publishes that role.
Provider settlementA payment outcome for accepted work, shown publicly only as bounded summaries when the public path is ready.
Hard collateralOutside admitted assets that support reserve buffers separately from BIGHT product payments.
PAX/UPAXLow-liquidity hard reserve ballast. It may sit in reserve backing, but it is not ordinary spend liquidity.
TestnetA temporary public testing surface that must not be confused with mainnet value custody.
Public AuditA public summary of status, freshness, and evidence without private operating mechanics.
Proof of UtilityThe public idea that Infra does useful work and returns evidence while Core keeps admitted-value accounting separate.

Rosetta Stone

Use this mapping when the same surface appears under different labels in public pages, docs, or app copy.

Public termAlso appears asPlain meaning
The projectworkstreams, public surfacesSeparate areas for website, QUAD, Infra, Bridge, and Liquid; not a user action or access path.
CoreVault, paymaster, accounting surfaceStable accounting and public monetary condition.
InfraWorker surface, storage surface, retained-memory surfaceUtility work, storage, retrieval, receipts, proofs, BIGHT service lanes, and retained evidence.
LiquidMarket surface, settlement-routing surface, fast laneMotion, risk, position, wrapper, clearing, settlement-request, and market labels without becoming Core value truth.
BridgeBoundary movement, receipt surfaceExternal movement and public receipt summaries.
Data Chain / ComputeLegacy or internal service-area labelsRead as bounded work/evidence/storage vocabulary, not as the public category for QUAD.

How To Use This Page

The glossary translates terms; it does not create product access or authority by itself.

1. Translate

Find the plain meaning of a term before treating it as a feature, claim, or status.

2. Follow the owner

Move from the term to the surface that owns it: Core, Infra, Bridge, Liquid, or the main site.

3. Check status

Use readiness and verification labels to separate described, implemented, observed, staged, closed, and live claims.

4. Keep boundaries

Do not turn old service labels, wallet labels, route labels, or receipts into broader authority.

Use

Plain public terms, readiness labels, and outcome-level explanations.

Avoid

Private access details, evaluation rules, keys, and operator procedure.

Rule

Every major public claim should map to described, implemented, observed, staged, closed, or live.