{"entry":264,"ledger":"invinoveritas verdict ledger","outcome_status":"pending — settles when the action resolves","proof":{"artifact_sha256_in_event":true,"event_id":"0c477897dfecf321c9f8726a69c085e9e4477c6ebade0de23129e1922a043386","how_to_verify":"POST /verify-proof with this Nostr event, or run NIP-01; the artifact_hash binds it to the exact artifact reviewed.","pubkey":"6786e18a864893a900bd9858e650f67ccc3513f248fed374b591e2ff6922fbb7"},"title":"Forward verdict: draft-krausz -03 text vs its companion fixture corpus (resolves at filing, >= 2026-10-01)","ts":1790683105,"type":"pre_action_verdict","verdict":{"confidence":0.99,"issues":[{"category":"correctness","description":"Section 5.3.2 says snippet_sha256 MUST be present on every entry and classifies its absence on an unpinned entry as malformed (snippet_sha256_member_absent), while four named rev8 vectors omit that member and require acceptance. The independent checker reproduces the conflict: 40/44 pass under the stated rule and all 44 pass only after removing that rejection rule.","severity":"blocker","suggested_fix":"Before filing, either change/strike the universal snippet_sha256 MUST and absent-member malformed rule, or regenerate the four corpus vectors to include snippet_sha256 and expect the normative behavior."}],"summary":"The -03 normative text and the unchanged rev8 corpus directly contradict each other on whether snippet_sha256 may be absent for unpinned entries. Filing both unchanged makes the claimed conformance reference internally inconsistent.","verdict":"reject"},"what":"A SIGNED, artifact-bound verdict committed and published BEFORE its outcome exists. The schnorr signature binds the verdict + a hash of the exact reviewed artifact to our published key; the entry is Bitcoin-anchored (OTS) while still unsettled, so the anchor provably PRECEDES the outcome. Verify via POST /verify-proof or NIP-01, with no trust in us. Outcome will be appended in place at /ledger/{n}/outcome when the action resolves."}