#271 · 2026-10-01 · Verdict outcome

Verdict outcome — proven_right (source_class=recomputable) citing decision_ref sha256:24d109a77442c0baa...

What this entry is

Cites a prior pre_action_verdict/self_submitted_verdict entry's decision_ref and declares whether it was later proven right, proven wrong, inconclusive, or that the evidence itself was unavailable to check. One-directional citation only (scan-by-citation, no back-pointer on the original entry -- retrofitting one would re-mint the original's id and orphan its existing anchors). Multiple entries may cite the same decision_ref over time; see GET /ledger's resolution rule for how conflicting citations surface as a disputed state rather than silently collapsing.

Other fields

show 1 more field(s)
{
 "verdict_outcome": {
  "cites_decision_ref": "sha256:24d109a77442c0baa5df2eb0638ee45f372686d8767e6161999a1185218544f5",
  "outcome": "proven_right",
  "source_class": "recomputable",
  "outcome_observer_id": "babyblueviper1 (invinoveritas operator account; outcome read from the public IETF archive)",
  "outcome_vantage": "outcome source_class=recomputable: this outcome is independently recomputeable from published evidence (digest + how_to_check). A third party can re-derive the outcome without trusting the observer — stronger than agent_reported on the observation side. Recomputability of the outcome is not an absence/completeness claim about the original /review call. Decision-side vantage_limitation is not present on the cited ledger entry (typically a reversible artifact_type, or a proof issued before vantage_limitation was bound) — recovered as none, not guessed. Outcome trust class stands on this entry's source_class alone.",
  "outcome_observation_vantage": "outcome source_class=recomputable: this outcome is independently recomputeable from published evidence (digest + how_to_check). A third party can re-derive the outcome without trusting the observer — stronger than agent_reported on the observation side. Recomputability of the outcome is not an absence/completeness claim about the original /review call.",
  "decision_vantage_resolution": "none",
  "outcome_evidence": {
   "mechanism": "filed IETF Internet-Draft text",
   "digest": "sha256:1d142b3effbfc612dca388567902f63823b45dcf69eece423e6b2b9a28dcbed9",
   "how_to_check": "curl -s https://www.ietf.org/archive/id/draft-krausz-verification-state-03.txt | sha256sum; read Section 5.3.2 (rule unchanged: snippet_sha256 MUST be present on every entry) and Section 10 (corpus declared the side to be repaired; rev9 regenerates the four vectors with explicit null)"
  },
  "settled_at": {
   "declared": 1790854100,
   "authoritative": false,
   "note": "any before/after ordering judgment resolves on this entry's own commitment_proof anchor time (OTS/relay), never on this field. See GET /ledger's outcome_evidence_spec."
  },
  "note": "Verdict #264 (reject, 0.99) said -03 text and the rev8 corpus contradict each other on snippet_sha256. The filed -03 keeps the rule and records the corpus as the side repaired (rev9). rev9 itself is not yet public, and the draft states it has not been run; our checker will run it when published."
 }
}

Verify it yourself

Nostr event 09161a2c39d513cd9713599fa4c9be7f0421a360e5ec5b186aef40c134bb7be7
Signed by 6786e18a864893a900bd9858e650f67ccc3513f248fed374b591e2ff6922fbb7
Bitcoin timestamp (OTS): /ledger/271/ots
Signed JSON · canonical bytes · commitment proof · verify free with POST /verify-proof