QUAD Architecture

Proof Of Utility

Two linked jobs: Core accounts for value while Infra proves useful work.

Core Paymaster

Stable public accounting for admitted value, supply condition, and monetary status.

Evidence: Core observed Public access: public observatory

Commercial link BIGHT makes Infra work payable, while hard collateral belongs to reserve rails; accepted work can then be accounted for without blending product payments into backing.

Infra Worker

Utility work for storage, retrieval, retained state, BIGHT-priced service lanes, receipts, and infrastructure evidence under active development.

Evidence: public product surface active Public access: public observatory

Economic Layers And Product Surfaces

The top layer moves and accounts for value. The product layer turns bounded work into receipts, proofs, and payable service state.

Core custody Bridge Liquidity surface

Work Evidence Storage

Plain Flow Examples

The chains are easiest to read as separate jobs that pass evidence across boundaries.

Pay for work

A user follows an Infra quote path, pays in the Infra-owned work context, and receives a receipt when accepted work completes.

Hold value apart

Core keeps admitted-value accounting separate from product payments, sibling tokens, and ordinary service receipts.

Move with proof

Bridge records route, source-pool, host evidence, and refusal labels so passage can be reviewed instead of assumed.

Move fast locally

Liquid can handle motion and market-state labels while still deferring final meaning to the surface that owns settlement.

How The Economics Fit

Utility needs payment, and payment needs evidence that useful work happened.

Core custody

Gives admitted value a custody and accounting base.

Payment routing

Shows payment and provider-settlement state where public summaries are ready.

Infra work

Turns accepted storage, retrieval, proof, receipt, and memory work into BIGHT-priced product lanes.

Reserve rail

Keeps admitted outside assets separate from ordinary product payments.

Coordination Law

The chains can interact, but they do not inherit each other's authority. See the main boundary page for the public non-inheritance rules.

Coordinated, not merged

QUAD, Infra, Bridge, and Liquid keep separate economies and separate public surfaces.

Evidence crosses borders

Exports, receipts, proofs, invoices, packets, and endpoint contracts can move between surfaces.

Meaning is local

The receiving chain decides what an imported fact means under its own rules. Receipt, transit, or motion does not force admission.

Service needs payment

If one chain consumes another chain's work, the dependency needs an invoice, receipt, contract, prefund, retained balance, or approved liability path.

Boundary is public

The main domain publishes authority, visibility, and public meaning rules at boundary.html.

Dependency is named

The public dependency map at dependencies.html shows when a route should continue, sleep, refuse, retry, quarantine, or downgrade.

Token Role Separation

Names are not interchangeable payment rails. Each token belongs to the economy that gives it meaning.

QUAD, BIGHT, OBOL, and MALI are not four names for the same thing. They describe separate jobs across accounting, work payment, passage, and motion.

Open token role table

TokenPublic roleBoundary

QUADCore value gravity and Core-aligned monetary pressure.Not a generic wrapper, sale unit, or shortcut around admission law.

BIGHTInfra work metering, service settlement, and memory-economy pressure.Not admitted reserve value merely because Infra prices work in it.

OBOLBridge passage, lane security, proof carriage, receipt work, finality risk, relayer work, and border friction.Not Core Treasury, Infra truth, or Liquid settlement.

MALILiquid motion, wrapper utility, market execution, and fast-lane liquidity pressure.Not the vault and not final balance truth by speed alone.

Hot-Path Support

Fast tooling can help a chain move, but it cannot become the chain's truth.

Engine-style support can help Bridge or Liquid prepare movement, but the owning chain still validates, records, refuses, and explains the result.

Open hot-path boundary

Engine

Engine is Liquid/Bridge-adjacent hot-path tooling for bounded motion intake and advisory batch proposals.

Liquid authority

Liquid's authority rail still validates proposals, applies local law, mutates settlement only through settlement, and emits audit/export records.

Bridge authority

Bridge can use hot-path assistance for feeder or relay-adjacent work while still owning provenance, lane policy, receipts, and refusal reasons.

Public boundary

Engine roots and counters are observability until a chain imports and records them through its own audit/export path.

Infra Public Boundaries

Public Infra material separates normal product receipts from opt-in hook packets without exposing private repository, operator, or verifier details.

Infra can return normal product receipts or opt-in hook packets. The receiving chain still checks binding and applies local policy.

Infra overview Infra pricing Verification guide

Open Infra boundary flow

Normal contract

Infra records bounded product receipts for anchor, retention, query, and proof surfaces.

Hook packet

Infra can return a compact packet for opt-in contract work.

Review locally

The receiving chain checks receipt or packet binding before using it.

Apply local policy

The receiving chain decides what the receipt or packet means under its own published rules.

Audience Lens

Different readers need different levels of explanation.

UsersWhat can I do, what is open, and which surface owns the next proof?Plain outcomes, status labels, and next steps. ProvidersHow does capacity connect to accepted work and public settlement labels?Public work path without private evaluation logic. PartnersHow do retained memory, service evidence, and chain boundaries scale safely?Reliability, growth story, risk boundaries, and audit state. ReviewersHow do economics, governance, validators, rollout, and chain interaction hold together?Public model without private controls.

Project Map

The public architecture follows project boundaries instead of blending every area into one story.

WebsiteExplains public state, status, terms, and plain summaries.

QUADEconomic-chain workstream and Core chain observatory.

InfraEvidence, storage, witness, memory, BIGHT work payments, reserve rail labels, and utility-work infrastructure.

BridgeBoundary movement, source-pool mapping, owner-vault evidence, and quarantine-facing receipt design.

LiquidParallel execution, state-promotion rehearsal, migration planning, and market-facing public labels.

Public Surface Maturity

The main site is now an entry point into four bounded public surfaces.

CoreLive chain observatory, metadata, blocks, transactions, validators, and public economic labels. InfraProduct surface for BIGHT purchase, upload, retrieve, balances, ledger, receipt, and proof paths. BridgeProduct surface for passage, source pools, owner vaults, host evidence, proof, and lane-gated labels. LiquidMotion surface for wrappers, settlement posture, risk labels, migration rehearsal, and market-closed state.

External Support

External services are support rails, not system identity.

Website hosting, chain nodes, and providers support public availability. They do not become chain identity, token utility, or economic authority.

Open support boundaries

Shared website

Core may carry the shared website hosting rail because the public site is the common information, status, and coordination surface.

Chain nodes

Each chain is responsible for its own operated node support through its own chain-local rail.

Provider boundary

Providers do not receive validator keys, wallet material, seed phrases, open-ended authority, or chain identity.

Public meaning

Operated nodes prove liveness and support observation; they are not mining, rewards, DePIN identity, or the purpose of the chains.