Ask: a consumable signing-verification surface — per-ref/per-record verification results (who signed, against which allowed_signers entry, verified/unverified/unknown) as JSON — reachable by CLI (e.g. trust verify --json or sync --verify-report).
Motivation (downstream methodology consumer): our conformance designs bind disposition-authorship checks to 'verified over server-synced state'. The grounded audit of the current surface found exactly two anchors: the local-only issue intervene fingerprint path, and hub-event SSH signatures against the trust store — whose rich v2 enforcement report was retired with the v2 write path (#754), leaving only the dashboard badge as a consumer. A machine-readable report lets downstream CI verify 'this SO disposition comment was authored by a trusted human key' as a named capability instead of an assumed one.
(Filed per our channel policy; the consuming designs hold their affected legs at could-not-check until this exists.)
Ask: a consumable signing-verification surface — per-ref/per-record verification results (who signed, against which allowed_signers entry, verified/unverified/unknown) as JSON — reachable by CLI (e.g.
trust verify --jsonorsync --verify-report).Motivation (downstream methodology consumer): our conformance designs bind disposition-authorship checks to 'verified over server-synced state'. The grounded audit of the current surface found exactly two anchors: the local-only
issue intervenefingerprint path, and hub-event SSH signatures against the trust store — whose rich v2 enforcement report was retired with the v2 write path (#754), leaving only the dashboard badge as a consumer. A machine-readable report lets downstream CI verify 'this SO disposition comment was authored by a trusted human key' as a named capability instead of an assumed one.(Filed per our channel policy; the consuming designs hold their affected legs at could-not-check until this exists.)