Runtime feed target: chain status / environment.
Plain public health label, not operator internals.
Plain-language chain posture from audit human data.
Whether the public audit feed is ready, waiting, or offline.
Current machine-reported value estimate.
Audit-confirmed public supply state.
Cumulative public burn count.
Public freshness marker from the feed exporter.
Public feed source; not an operations manual.
Summary only. Top-level data can be inspected elsewhere.
Chain surfaces
Each economy keeps its own page. The landing page only links to the public surface it can defend.
Latest public events
Public events are short human-readable summaries from audit data. The website explains condition without exposing the playbook.
[000000] surface.init status=public_v5
[000001] stats.source status=fallback_json
[000002] audit.export status=awaiting_live_quad
[000003] public.events status=summary_only
[000004] private.logic status=omitted
Public data boundary
The live feed is intentionally narrow. It shows condition and freshness, while leaving deeper inspection to the proper chain surfaces.
Shown
NAV, token count, total burned, health, posture, audit export state, source, freshness, and latest summary.
Not shown
Private thresholds, route pressure, defensive timings, provider credentials, and operational playbooks.
Until launch
Fallback values remain visible until QUAD itself is live and the trusted audit exporter is connected.
Quarantine-facing chain boundary.
Witness, storage, and memory layer.
Parallel execution and market surface.