Service Status
Every finding below is a typed, hashed statement about one component of this service. The English under each one is generated from it, so it cannot say something the underlying statement does not.
Summary
Reduced from the packets below. Only packets whose hash and symbol both verify are counted, so an edited or malformed line degrades this to UNVERIFIED rather than reporting green.
Loading /status-codebook.json ...
Observed
Measured on this page load from /api/health and /api/status.
Probing ...
Unobserved
Nodes this page does not probe. They are listed as open questions rather than omitted, so a subsystem that is merely unwatched is never mistaken for one that is known to be healthy.
Waiting on the codebook ...
Verify a packet
Paste any packet from this page, or edit one character of it. Parsing, hashing, and symbol resolution all run locally in your browser.
Why packets and not sentences
A status page usually publishes an adjective somebody typed. That has no referent a machine can resolve, carries no evidence, and cannot be checked against the system it describes. This page publishes a typed, hashed wire format instead:
NRL1 <OP> @<agent> #<node> [<slot>:<value> ...] ~<hash> NRL2 <OP> @<agent> #<node> [<slot>:<value> ...] ~<16 hex>
#node is a pointer, not a phrase. Each symbol is interned
against a generated map of this system's components, and a packet naming
one the map lacks is rejected with the nearest known symbol suggested.
The vocabulary is generated, so renaming a component breaks this page's
build instead of quietly leaving it pointing at nothing.
The trailing seal is recomputed in your browser for every line shown:
FNV-1a (8 hex) for NRL1 packets, the first 64 bits of SHA-256 (16 hex)
for NRL2. cf: is quantized confidence, and
ASK is a real result: it marks a node the page has a
question about rather than a finding, which is what an unprobed
subsystem honestly is. NRL2 adds tree binding (tr:),
authority (au:), hypotheses (hy:) and proof
obligations (ob:) - and its one load-bearing rule is that
a witnessed statement must name the tree it was witnessed on.
The parser and sealer this page runs in your browser are ported verbatim from the ones used to produce the packets, so a packet rendered here parses and seals identically on both sides.