integrations: xChk registry — approval-outcome crosswalk, fixtures and receipt verifier (from trace-spec#560; stacked on #338) by minitru · Pull Request #350 · agentrust-io/integrations

xchk-registry: the approval-outcome crosswalk, fixtures and receipt verifier, moved here from trace-spec#560 (19 Oct 2026)
minitru
committed
36375fa
xchk-registry: an amendment is what the sealed record commits to; the fixture verdict reads the verifier's structured result (19 Oct 2026)

minitru
and
claude
committed
9a326a2
xchk-registry: CodeQL clear-text-logging alert; a pinned private key is refused; an amendment on a record that seals no digest is pending, not a failure (19 Oct 2026)

minitru
and
claude
committed
c0d9d22
xchk-registry CROSSWALK: the TRACE spec link at the top points at the public specification, not a path that does not exist from this directory (19 Oct 2026)

minitru
and
claude
committed
735d23d
xchk-registry: verifier obligations 5-6, the conformance-fixture description and the 07 README aligned with the boundary: decision.amendment is informational, its scope not yet authenticated (19 Oc…

minitru
and
claude
committed
fd4514a
xchk-registry: strict approval also requires the seal chain; an approval without it is approval-unsealed, never confirmed (20 Oct 2026)

minitru
and
claude
committed
b43b884

Navigation Menu