Q token mark QUADPublic Accountability

Progress by evidence gate

Phases And Opening Gates

The public phase story is deliberately evidence-based: observe first, harden next, publish policy, then open narrow lanes only when the owning surface can carry the claim.

No phase on this page opens sale access, reward eligibility, production value movement, live liquidity, or a market module.

Phase Snapshot

A quick reading of where the stack sits without turning one chain's progress into another chain's authority.

CoreMainnet hardening and public observation
InfraProduct proof and BIGHT work paths
BridgePassage evidence with movement closed
LiquidMotion and settlement staging with markets closed
WebsiteIdentity, routing, source ranking, and release receipts
External referencesStaged or pending unless the outside source owns acceptance

Phase Order

The stack should advance through gates, not vibes.

1. Observe

Publish public state, chain metadata, status labels, and safe first-read paths.

2. Harden

Prove owner surfaces, endpoint freshness, failure behavior, and release artifacts under repeatable checks.

3. Explain

Publish purpose, model, category, risks, obligations, references, and product boundaries in plain language.

4. Freeze

Freeze intended indexed genesis, metadata, endpoint posture, and route contracts before outside submissions.

5. Open narrowly

Open one bounded lane at a time with owner-published status, fee, receipt, refusal, and recovery labels.

6. Expand on proof

Broader movement, liquidity, and markets require stronger public receipts and dated owner updates.

Chain Phase Map

Each chain has a different current job.

SurfaceCurrent public jobNext gate
CoreShow chain state, validator posture, token model, admission boundaries, and economic hardening.Genesis/endpoint freeze, registry readiness, validator review, and public policy closure.
InfraMake BIGHT work paths usable and provable: fund, upload, verify, retrieve, contract, balance, and receipt.More service receipts, failure-state closure, provider accounting, and product-path polish.
BridgeShow controlled passage, acquisition, inventory, vault lanes, gates, host evidence, proof, and closed movement labels.Route execution proof, refund/surplus posture, relayer/provider closure, and only then narrower movement gates.
LiquidShow motion, position, wrapper, risk, settlement-request, explicit-law, and market-closed labels.Settlement owner acknowledgement, market-risk controls, and public feed freshness before activation language.
Main websiteKeep the stack readable, link owner surfaces, and publish release receipts without claiming chain authority.Upload current artifacts, keep dated updates, and downgrade stale or blocked routes visibly.

What Opens Each Gate

Opening language needs public evidence, not just code progress.

State gate

Owner-published status, timestamp, chain/route id, evidence class, and stale-state behavior.

Economic gate

Minting, distribution, fee, payable, receivable, reserve, refund, and self-funding labels where relevant.

Security gate

Audit posture, disclosure path, report slot, high-sensitivity labels, and refusal of unsupported safety claims.

Operational gate

Provider, endpoint, relayer, gas float, hosting, monitoring, fallback, and recovery posture where public.

Integration gate

Packet, receipt, acknowledgement, timeout, replay, quarantine, and destination-boundary behavior.

Reference gate

Owner route first; outside reference only when accepted and scoped by the outside source.

What Readers Can Do Now

  • Observe Core: check current chain state through the Core public surface.
  • Use Infra where open: follow BIGHT-owned product paths on the Infra surface.
  • Read Bridge: inspect passage, inventory, gates, host evidence, and movement-closed labels.
  • Watch Liquid: inspect motion and settlement posture without treating motion as final balance truth.
  • Quote carefully: use source, reference, risk, and boundary pages before summarizing.

What Remains Closed

  • No public distribution, sale, airdrop, or reward campaign is open.
  • No public production Bridge movement lane is open from this page.
  • No live liquidity or market module is opened by phase wording.
  • No registry, explorer, wallet, repo, or crawler reference becomes authority by itself.
  • No observation, coordination, or testing action creates future economic entitlement.

Dated Update Rule

When a phase changes, the update should say what changed, what proof exists, what remains closed, and what someone can do next.

RoadmapPhase-based public readiness and economic gates. ActivationMinting, distribution, movement, liquidity, and market-opening conditions. UpdatesDated public changes and stale-entry rule. Readiness officeCurrent product, technical, operating, accounting, and market gaps. Evidence archiveProgress by owner, proof class, public route, boundary, and freshness. ReferencesOutside-reference boundaries and official source order.