Expand description
RegistrySlice — the reply type of the introspect procedure (RFC 08 §6).
Every producer’s registry file has declared reply = "RegistrySlice" since
the convention was ratified, and every sensor has answered introspect with
the raw registry TOML — but the type it named did not exist, so no consumer
could read the answer. This is that type.
A slice is what one build says it serves. The point of having it is the
diff: compare a host’s served slice against the slice this build compiled
in (the application’s zenkey-build-generated REGISTRIES table) and a
disagreement is a
finding — a version skew, a subject the fleet serves that we cannot
name, or a subject we expect that nothing out there publishes. RFC 08 §6 is
explicit that this is a finding and not an ambiguity, which is why the
parser below is strict about the header and forgiving about nothing.
Structs§
- Deprecation
Decl - One
[[deprecated]]entry — RFC 08 §3’s append-only retirement ledger. - Procedure
Decl - One
[[procedure]]entry of a served registry slice. - Registry
Slice - What one build says it serves: the payload of an
introspectreply. - Slice
Error - Why a slice would not parse.
- Subject
Decl - One
[[subject]]entry of a served registry slice.
Enums§
- Slice
Finding - A disagreement between a served slice and the slice this build compiled in.
Functions§
- diff
- Diff a served slice against the slice this build compiled in.
- parse_
slice - Parse an
introspectreply — the raw registry TOML a build serves.