Q markQUADArchitecture

Architecture

A public map for the stack terms used around QUAD. It explains how economic layers make service layers commercially usable while keeping each chain's authority local.

ReadinessUsage EvidenceSecurityBoundaryMain architecture

Stack Diagram

The economic layer makes service work payable and auditable. The service layer produces useful work and records what happened.

VaultCore custody and accounting context for admitted value. BridgeBoundary movement, route evidence, source pools, and receipt labels. LiquidityMarket motion and provider-reward routing surface, bounded by local settlement rules. ComputeAccepted work, provider capacity, task receipts, and service proof. StorageProvider-held data availability, retention, retrieval, and proof records. Data ChainRecords, indexes, and finds the information the network needs to recover or prove later.

Narrative Bridge

The public model is one commercial loop, not one merged chain.

Vault

Vault provides custody and accounting context for admitted value. It is the place where backing and reserve posture are read, not the place where every service action is commanded.

Liquidity

Liquidity routes payment and provider rewards. It can make useful work economically reachable without becoming final truth for every other surface.

Compute and Storage

Compute and Storage provide useful work and capacity. They are commercially viable when payment, receipt, and proof surfaces can explain what was done.

Data Chain

Data Chain records and indexes what the network needs to find again: receipts, retrieval state, public proof references, and retained memory boundaries.

Rosetta Stone

Use these terms consistently in first-read public pages.

VaultCore custody and accounting
BridgeBoundary movement and receipts
Liquidity ChainMarketplace and reward routing surface
Data ChainIndexing and storage coordination surface
Compute ChainProvider work and task execution surface
StorageProvider-held data availability surface

Audience Split

The same system should not be explained with the same depth to every reader.

UsersWhat can be done now, current limits, and which testnet actions are visible without implying rewards or value. ProvidersHow capacity connects to accepted work and reward labels without exposing private scoring, thresholds, or operator procedure. PartnersHow Data Chain, Compute, Storage, Bridge, Liquidity, and Vault scale together, with evidence labels on public claims. ObserversHow Vault, Liquidity, Bridge, Compute, and Storage connect commercially, and which gates remain pending.

Boundary Rules

Architecture explains relationship, not inherited authority.

  • Separate economies. QUAD/Core, Infra, Bridge, Liquid, and the website keep separate surfaces and separate authority.
  • Evidence can cross borders. Receipts, exports, invoices, packets, and route records can move between chains, but the receiving chain decides what they mean.
  • Code names stay secondary. First-read public pages should use product terms. Module names appear only when they help verification.
  • No silent upgrade. Transit, receipt, liquidity, storage, indexing, or public attention does not create Core admission, value, mainnet launch, audit completion, or safety.