QUADPublic Accountability
Each lens is allowed to inspect the whole stack. No lens is allowed to erase the boundary between Core, Infra, Bridge, Liquid, the website, or external support rails.
This page is a public map. It does not publish private procedure, signer details, provider internals, or sensitive mechanics.
Use these first when deciding what kind of readiness question you are really asking.
Can each chain keep its public promise when sibling chains, providers, relayers, or public pages are stale, delayed, refusing, or offline?
Can the stack be operated day to day without operations becoming protocol law?
Can each chain fund, meter, cap, reconcile, and prove its own obligations?
Can outsiders understand the stack without hype, category drift, reward framing, or unsupported production claims?
Can the stack run, recover, interoperate, expose state, refuse unsafe inputs, and prove readiness repeatably?
Can readers know what is true without private memory or stale artifacts?
Can receipts, exports, stats, endpoint contracts, and proof surfaces become reliable datasets without leaking payloads or creating false authority?
Can readers, testers, validators, builders, relayers, and reviewers complete a journey with clear fees, receipts, refusals, and next actions?
The main domain should not become a giant checklist, but each page should carry the lens that belongs there.
The website itself has to pass the lens test before it can explain the rest of the stack cleanly.
Every chain gets judged by the same public questions, but the answer stays chain-local.
Core must account, Infra must prove work, Bridge must prove passage, and Liquid must prove motion without borrowing another chain's authority.
Can it preserve admitted-value discipline, validator observation, invoice/payment labels, quarantine, and local export records when Infra, Bridge, Liquid, or external rails are unavailable?
Can it sell and prove storage, retrieval, receipt memory, contract work, repair, and challenge services in BIGHT without borrowing Core authority?
Can it prove passage, route labels, host evidence, inventory, refund/refusal, and destination handoff without claiming destination admission?
Can it expose motion, positions, risk, liquidation posture, and settlement requests without turning speed into final balance truth?
Review lenses, chain-local questions, proof standards, page mapping, and what stronger claims require.
Private procedure, credentials, signer paths, internal scoring, provider account detail, sensitive timing, and exploit-useful mechanics.
This page does not open mainnet, value movement, live liquidity, sale access, reward eligibility, allocation, market access, or production activation.