Every claim here carries its status, and every number its provenance.

Rensei deliberately publishes one redacted signed sample from its own platform for account-free offline verification. It includes a key-discovery link and a copy-pasteable verification command. It is a public example, not a complete chain export or evidence of continuous monitoring coverage. The verification protocol and key catalog describe the workspace-scoped key path. Signature presence and verification are distinct: the signature is evidence to check, not a verification result by itself. Authenticated audit reads use application-level organization/workspace authorization and query filtering. Project filtering is route-dependent and applies only on routes that accept project scope. These audit-read routes are not Cedar-gated, and this page does not claim production database RLS as their live runtime enforcement boundary.

The derivation is the public answer to how this is different. LLMs run as bounded operators inside workflow steps; the control loop is deterministic code. When the control loop is instead a model that can rewrite the steps it is about to run, the record of what ran is a claim, not a proof: tamper-evident audit requires a loop that cannot edit its own history. A deterministic graph forecloses that failure structurally. The structure that executed is the structure that was reviewed, and the chain that recorded it sits outside the reach of the thing it records.

The same property holds for workflow runs: graph, state transitions, and policy evaluations are deterministic and replayable. The strand generator is MIT licensed and ships alongside the verifier.