What can your stack prove about itself?
Six sub-scores, every one computed from measured telemetry our own operating layer emits — heartbeats, signed receipts, routing logs, session economics. No benchmarks invented, no industry averages, no dollar estimates. Where a number is not measured, the card says “not measured” and tells you why. Every card links the artifact that proves it.
- Sub-scores
- 6
- Data
- Measured only
- Source
- Our own node
- Verify
- Every card
- Refresh
- Live artifact
One verdict word for the whole runtime — composited from the measured sub-scores only. A yellow ring shown honestly beats a green ring assembled from hope.
method: worst verdict among measured sub-scores only; the denominator is shown ('N of 6 measured') — the ring never silently fills in for missing data · artifact generated 2026-07-09
heartbeat fail / warn / ok
how this is measured
verdict = the heartbeat run's own GREEN/YELLOW/RED, emitted verbatim; activation and the hermetic-CI launch gate shown with denominators; CI test COUNTS are not publicly instrumented and stay null
Apex Max · One mesh, every node heartbeating.
verify: the live status page renders the same heartbeat tile — counts match this card
signed receipts · chain intact
how this is measured
chain_intact = the publisher's fail-closed Ed25519+ML-DSA-65 chain replay passed (a bundle that fails is never published); verdict GREEN when ≥1 receipt is on the verified chain, YELLOW at 0
verify: re-verify the chain yourself: the published bundle at /proof/receipts-bundle.json, in-browser or offline
session-economics checker not available on build machine
work on rung-1 scripts · flagship-on-deterministic 0
cost-discipline proxy (routing) — $ not measured
how this is measured
verdict GREEN when zero deterministic units reached a flagship model, YELLOW otherwise; billing instrumentation is gated so no dollar figure exists anywhere in this artifact
verify: the live status page's routing tile — histogram recomputable from the counts shown
evidence bundle verifies offline, no vendor in the loop
how this is measured
verdict GREEN when a verified chain with ≥1 receipt is published as a portable bundle a third party can verify offline, YELLOW otherwise
verify: download the bundle and run the offline verifier — the verification layer needs no vendor in the loop
substrate components PRODUCTION
how this is measured
verdict GREEN when every component is PRODUCTION and the hermetic-CI gate is done; YELLOW when CI is done and more than half are PRODUCTION; RED otherwise — non-PRODUCTION components are counted, never hidden
verify: the live status page's activation matrix lists every component with its honest state
Not measured — and saying so
- dollar cost — billing instrumentation gated — ESTIMATED figures exist internally and are never published
- fixed-context slimming — single-run ESTIMATED — replication needed before it can render as measured
- CI test counts — test totals are not publicly instrumented; only the hermetic-CI gate's done state is published
- nodes-online fleet counts — single-node today
- workflow completion counts — not publicly instrumented
Why this page exists
This is our node scoring itself, in public, with its warns showing. When you install StratosAgent, your node gets the same six cards about itself — they start grey, and your first verified receipt lights the first one up. The point is not our score; it is that a score like this can exist at all: measured, portable, and verifiable without trusting the vendor — the full status page carries the raw tiles.