Skip to main content

Evidence, Verdict & Settlement

Verification produces structured evidence that is tied to the exact funded job and submitted deliverable.

Evidence chain

funded task + policy commitments

worker execution evidence

exact commit + pull request

GitHub Check Runs when required

independent verifier report

report/evidence commitments

Arc settlement transaction

Exact PR consistency

Before settlement, Veyra checks that the pull request still matches the signed worker evidence.

Important checks include:

  • expected branch;
  • exact commit SHA;
  • expected base branch;
  • pull-request URL/number;
  • changed-file set.

A PR that no longer matches the submitted evidence cannot be treated as the same deliverable.

Required GitHub checks

If the funded job policy requires GitHub Check Runs:

  • pending checks keep verification pending;
  • failing/unknown mandatory conclusions block approval;
  • checks must correspond to the exact submitted commit.

If the policy does not require GitHub checks, their absence is not itself a payment blocker.

Independent verification still applies in both cases.

Final approved path

When deterministic gates and the independent verifier both approve the exact deliverable:

APPROVED
→ verification report hash
→ evidence commitment
→ verifyAndPay(...)
→ Arc confirmation
→ worker earnings/reputation reconciliation

Rejected path

When the final result is rejected:

REJECTED
→ reason/report commitment
→ rejectAndRefund(...)
→ Arc confirmation
→ client refund path completed

Inconclusive is not approval

An inconclusive verifier result does not release payment.

Veyra keeps the job unresolved until the configured recovery/review path produces a final valid outcome or the applicable contract recovery window is reached.

Settlement is receipt-driven

Veyra does not treat "transaction submitted" as "settlement complete".

The execution layer reconciles the Arc transaction until the authoritative receipt confirms the final state.