Stats
Actions
Tags
From rulake-witness
Recomputes SHAKE-256(32) witness over table.rulake.json bundle and compares to embedded witness. Outputs match/mismatch status with details and CI-friendly exit codes (0 match, 1 mismatch).
How this command is triggered — by the user, by Claude, or both
Slash command
/rulake-witness:rulake-verifyThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /rulake-verify Local-only — no MCP server, no backend registration, no cache. Just reads the bundle, recomputes the witness preimage, and compares. Sample output (match): Sample output (mismatch): Returns exit code 0 on match, 1 on mismatch — useful in CI gates.
Local-only — no MCP server, no backend registration, no cache. Just reads the bundle, recomputes the witness preimage, and compares.
/rulake-verify path/to/table.rulake.json
Sample output (match):
✓ WITNESS_MATCH
data_ref: gcs://my-bucket/segment-001.parquet
dim: 384
rotation_seed: 42
rerank_factor: 20
generation: 17
expected: b1f4a2c8e3d5...
computed: b1f4a2c8e3d5...
Sample output (mismatch):
✗ WITNESS_MISMATCH_REFUSED
expected: b1f4a2c8e3d5...
computed: 9d8e7c6b5a4f...
diff: data_ref differs (bundle was rewritten, generation tag bumped, or someone tampered)
Returns exit code 0 on match, 1 on mismatch — useful in CI gates.
npx claudepluginhub ruvnet/rulake --plugin rulake-witness