1. Bind the handoff
A workflow owner registers an acyclic handoff with requester, provider, responsibility, exact breach criteria, principal, provider bond, and deterministic consequence rules.
Loading finalized state…
VerdictGraph is deliberately narrow: it adjudicates a specific registered handoff. It does not claim that a URL is authoritative merely because its bytes match a hash, and it does not let an LLM choose payout amounts.
A workflow owner registers an acyclic handoff with requester, provider, responsibility, exact breach criteria, principal, provider bond, and deterministic consequence rules.
Each workflow points to a sealed policy fingerprint containing approved issuer wallet identities, approved HTTPS publisher boundaries, freshness/expiry rules, corroboration thresholds, and recovery timing.
The GenLayer leader and validators fetch the same hash-pinned evidence independently, reapply the registered criteria, and must exactly agree on every field that can change downstream consequences.
A reviewed verdict enters a bounded response window. A fresh revision supersedes it. Only the latest still-current verdict can queue a finality-only external message to the deterministic EVM Vault.
An acceptance authority registers the accepted project trust root plus durable mirrors and approved evidence origins; a sponsor references it, a beneficiary submits a hash-pinned change, and GenLayer reviews the exact criteria before bounded windows, challenge/re-review, and deterministic settlement.
SHA-256 proves the fetched bytes match the registered bytes. Authority comes from the sealed issuer identity and publisher policy.
Accepted results remain appealable. The explorer separates provisional accepted workspaces from finalized protocol state.
The frontend checks transaction execution outcome as well as consensus status before treating a write as successful.
The Authority binds a project reference to its accepted baseline, durable mirrors, acceptance record, and approved public evidence origins. The Registry owns lifecycle and exact finalized callbacks; the Adjudicator owns validator-equivalence review; the dedicated Vault only executes one exact pre-registered consequence after finality. Visit Milestones or Acceptance authority.
VerdictGraph can enforce that corroboration comes from different approved wallet identities, different publisher boundaries, different stable record IDs and different content digests. It cannot cryptographically prove that two approved organizations are economically or operationally independent. Integrators must choose authorities whose independence they are prepared to trust.