rigorix-verifier
Protocol-only verification of Rigorix audit envelopes and the frozen contract
surface. Independent, self-contained, and engine-free (strategy freeze D-1):
it depends on rigorix-schemas for the contracts, never on rigorix-engine.
- HMAC-SHA256 integrity over the documented canonical form
(
signaturenulled) — byte-exact with the engine'scompute_signature. - JSON Schema conformance (draft 2020-12) for envelope / claims / policy / catalog / errors / events / ADR-016 anchor artifacts.
- ADR-016 chains: per-producer sequence +
prev_hashcontinuity, with gaps accepted iff covered by a valid Ed25519-signed compaction checkpoint. - Native-API catalog integrity + the closed-namespace
verify_catalog_subsetguard (ADR-0001 D3). - Engine-signed fixture verification, byte-exact, from any language.
Resolution (self-contained)
The verifier reads contracts from, in order:
RIGORIX_SDK_SCHEMAS— an explicit external corpus (CI/local override).- The embedded
rigorix-schemascorpus — the published path.
There is no repo-relative fallback, so a published/cargo packaged verifier is
self-contained: cargo test passes with RIGORIX_SDK_SCHEMAS unset.
Usage
use ;
// Byte-exact HMAC check of an engine-signed envelope.
verify_signature?;
// Schema conformance.
validate_schema?;
// Closed `rigorix.*` namespace: a server may only serve declared methods.
verify_catalog_subset?;
// ADR-016 local chain (sequence monotonic + prev_hash continuity).
verify_chain?;
# Ok::
Packaging
A published verifier carries no schema files: it embeds them through
rigorix-schemas (publish that crate first).
License
Apache-2.0 (repo-wide, matching the workspace).