Repository navigation
Phase 3 pilot: ingest srdcheck --trace as qc.verdict provenance records - #20
Merged
Merged
Conversation
…rovenance New event type qc.verdict (qc lane, dmcheck-ignored by design): tool@version, query_type, outcome, exit_code, sha256 verdict_id; optional request_id, adapter pins, duration, seat. New verb: `srdcheck query ... --trace 2>&1 | tablekit verdict [--seat S]` — keeps only request.completed observability lines, skips the human verdict JSON and prose, refuses (exit 2) when the stream carries no events. Provenance, never authority: verdicts stay advisory, nothing is scored. Verified live end-to-end: a real srdcheck 0.9.0 grapple verdict piped through one shell pipe landed in the ledger with adapter pins and verdict sha256. 7 new tests; suite green (jsonschema-dependent module needs CI's deps locally). Consumption gate per CHECK_FAMILY_TUNEUP_2026-08-09 §2.2: evaluate at the next live Bell session — family rollout only if these records get used. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tune-up doc's Phase 3, adapted to what upstream already built: srdcheck 0.9.0 ships
--traceobservability (request/verdict sha256 ids, engine+adapter versions) — so the pilot is pure consumption wiring on this side.What
qc.verdictevent type in the qc lane (dmcheck ignores unrecognized types by design — verified stance, not accident)srdcheck query ... --trace 2>&1 | tablekit verdict [--seat S]— one pipe, keeps onlyrequest.completedlines, exit 2 if the stream has noneGuardrails kept
Provenance, never authority — the verdict stays advisory, the ruling stays the GM's, nothing aggregates into a score. No player-facing surface at all.
Verification
tool: srdcheck@0.9.0, adapter pins,verdict_id: sha256:…, request idThe gate
Per CHECK_FAMILY_TUNEUP_2026-08-09 §2.2: run this at the next live Bell session; family rollout (charactercheck/dmcheck emitters) only if the records actually get consumed in retro/precedent lookup. If they sit unread, we stop at one tool.
🤖 Generated with Claude Code