Q token mark QUADPublic Accountability

Transition labels

Readiness

A public readiness page for phase labels, thresholds, and evidence links. It does not publish a launch date before one is ready.

Current Phase

The short version. Expand the detailed inventory only when you need the longer state map.

CoreLive chain, public metadata, and quote-first paid mint; current state belongs to Core.
InfraQuote-first BIGHT product routes for upload, verify, retrieve, contracts, ledger, and proof.
BridgeLive chain and route-gated movement; specific pairs require the live manifest and quote.
LiquidLive chain with readiness evidence; public market closed.
RPCPublic and paid endpoint access; fleet and payment totals remain owner-live.
WalletWatch-only web surface plus separately verifiable installed-wallet releases.
Target dateNo single stack-wide launch date; each owner lane carries its own state.
Detailed phase inventory
RegistryMetadata staged; submission held
Core law mapTruth order, audit, custody, refusal, quarantine, sink, and bounded supply posture visible
Core receiverBridge-origin delivery and quarantine evidence belongs to Core receipts; delivery never implies Treasury admission
Infra receipt memoryOriginal receipt included; later memory services are BIGHT-paid and surface-labeled
Bridge evidenceProduct journey, source-pool mapping, owner-vault evidence, Ethereum-mainnet host evidence, host-gas accounting, and receiver acknowledgements visible
Liquid evidencePre-SDK durability, state promotion, migration rehearsal, local meaning labels, and endpoint contract visible
EngineHot-path proposal tooling evidence; not a chain and not settlement truth
Local evidenceSource folders may have hardening proof before every item is exported on subdomains

Before Any Stronger Claim

These are evidence thresholds for expanding an owner lane, not a claim that the whole stack is pre-launch. The roadmap shows the proof order.

Core chain

Keep paid-mint health, enabled sources, quotes, custody, receipts, supply posture, and public law inspectable.

Economic expansion

Distribution, broader liquidity, redemption, and markets need separate owner law and evidence; no adjacent live route opens them.

Infra product

Keep BIGHT purchase, upload, verify, retrieve, balances, ledger, proof, failure, and retention state owner-readable.

Bridge passage

Keep each source/target pair bound to a live manifest, quote, capacity, finality, receipt, and refund or refusal path.

Liquid motion

Keep motion, risk, settlement-request, and production-profile evidence separate from public market access.

Security and docs

High-sensitivity surfaces keep report slots and withheld-detail boundaries instead of unsupported audit claims.

Detailed blockers
  • Bridge: IBC execution waits for keeper-owned sequence consumption, packet planning, acknowledgements, timeouts, relayer service, and handshakes.
  • Liquid: chain readiness still depends on consensus-backed stores, state roots, keeper authority, migration application, runtime compatibility, relayer gas floats, and live endpoint checks.
  • Shared: local source-folder evidence can advance before export, but public copy must name the owning surface and avoid implying feeds that are not deployed.

If Timing Changes

The public site should publish a dated update and keep the production date unset until the date is credible and approved.

Updates Roadmap Activation gates

What To Watch

Use the owning surface for the evidence you need: Core for liveness, Infra for BIGHT work paths, Bridge for passage evidence, Liquid for motion posture, Security for report slots, and Docs for practical paths.

Core state Infra product Bridge product Liquid motion

Readiness Office

The main readiness page shows phase labels. The Readiness Office summarizes the wider product, technical, operating, financial-accounting, and market gaps without exposing private procedure.

Product gapsWhat still has to be offerable, testable, payable, provable, and operable. Technical closureInterfaces, integration harnesses, observability, provenance, and failure behavior. Operating readinessControl plane, dependency graph, support playbooks, provider obligations, and handoff. Accounting readinessPer-chain books, payables, receivables, inventory, custody, and reconciliation. Market readinessPublic positioning, audience paths, proof archive, updates, and external references. Readiness lensesContinuity, operations, finance, market, technical, information, data, and experience checkpoints.

Hosting Readiness

Hosting labels are public posture only. They do not publish provider procedure, private account details, or production availability.

Hosting keeps public surfaces reachable. It does not create chain authority, token utility, rewards, allocation, or production value movement.

Open hosting boundary
Shared website

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

Chain-local nodes

QUAD/Core, Infra, Bridge, and Liquid keep operated-node support on their own chain-local funding paths.

Provider boundary

External services are replaceable support. They do not hold validator keys, wallet material, seed phrases, or open-ended authority.

Status boundary

Node and hosting readiness proves operational support only; it does not create node rewards, allocation, or production value movement.

Shown

Phase, thresholds, links to evidence pages, and dated public updates.

Not shown

Private controls, private launch procedure, sensitive timing, or unsupported production claims.

Rule

If public data cannot be read, say the current state cannot be verified instead of inventing state.