Barycenters / Status
Substrate · live status board

Is the boundary up — and honest about what it is?

Every value on this page is fetched from the running admission runtime and derived from the response — nothing here is typed in. It adjudicates signed decisions; it binds nothing itself. A healthy board means can adjudicate, never is enforcing. authority_effect = 0.

connecting to the runtime… base api.barycenters.ai —
Status
…
reading /readyz
Adjudicates
…
issues signed decisions
Binds
…
enforcement is the caller's posture
Issuer key
…
durable signer
Readiness

What the runtime checks before it says it is ready.

Each of these must be true for /readyz to report ready. They are re-run on every request — a green here is a live re-verification, not a cached flag.

Readiness checksGET /readyz
·awaiting the runtime…
Connecting…
The decision tape

Every admission the runtime has reached — accepted or refused.

Aggregate counters from /metrics. This is the shadow-mode record: real decisions, on real traffic, binding nothing. The refusals are the interesting half — read the shadow tape → for the reproducible cases behind them.

DecisionsGET /metrics
Decisions
—
Accepted
—
Refused
—
Tokens issued
—
awaiting the runtime…
Connecting…
Integrity

The tape is hash-chained, signed, and the constitution is intact.

The decision log is a signed, append-only chain; the No-Kill Constitution is probed on every readiness check. Both are verifiable with the public key alone — no trust in us required.

Ledger integrityGET /v1/audit/checkpoint
Chain length
—
Head signature
—
Signed head hash
Signed by
—
Connecting…
No-Kill ConstitutionGET /v1/constitution/no-kill
·awaiting the runtime…
Connecting…
The law it runs

The signed policy bundle it decides against.

The admission policy is versioned and signed; /readyz refuses to be ready unless the running bundle matches the version it verifies. This is the exact bundle currently in force.

Policy bundleGET /v1/policy
Policy id
—
Canon
—
Deploy domain
—
Environments
—
Version
—
Checks
—
Connecting…
What a green board is, and isn't. Every panel above is can adjudicate — the runtime can reach and sign a decision. Whether a REFUSE actually stops an action is the caller's posture (e.g. ADMIT_ENFORCE in the consuming job), and it is deliberately not observable from here. That honesty is the point: a status page that claimed to be "enforcing" would be lying about a thing it cannot see. Re-verify the chain yourself at the public ledger, or verify a single receipt with the public key. authority_effect = 0.