OHCAYGOMERGE PROOF

EXAMPLE PROOF · SYNTHETIC PUBLIC DATA

This demonstrates product behavior. It is not a customer result and is not evidence about a real repository.

ILLUSTRATION · LOOSE REQUIRED CHECKS · NO MERGE QUEUE

All required checks passed. Then main moved.

This is one supported GitHub configuration—not a universal merge path and not a claim that GitHub is broken.

  1. 1 · EVERY REQUIRED CHECK PASSED

    PR #41 was evaluated against main at M0.

    PR head
    ff6be1f9c318
    GitHub test-merge target
    a9aa3501363f
    Evaluated tree E0
    b1ec95450a69

    Required CI and approval evidence were bound to that exact evaluated state.

  2. 2 · MEANWHILE, MAIN MOVED

    An ordinary PR #40 advanced main.

    Before
    b9d4c5768e34
    After
    aa603530d21b

    PR #41's head did not change, but its combination with main did.

  3. 3 · PR #41 MERGED TOO

    Loose required checks did not require that new combination to be retested.

    Landed commit
    6bb4a8da2f46
    Actual landed tree L1
    13426dad6335

    No bypass or rogue actor is assumed.

  4. 4 · COMPARE

    The evaluated and landed trees differ.

    Evaluated E0
    b1ec95450a69
    Landed L1
    13426dad6335

    Merge Truth: FAIL · LANDED_MISMATCH

When this path does not apply: requiring branches to be up to date or using a merge queue makes GitHub form and check a current combined state before merge.

EXAMPLE MERGE-PROOF RECEIPT

The receipt below is the proof artifact. The illustration above only explains its facts.

MERGE TRUTH

Merge truth: FAIL

Different content landed.

The evaluated candidate evidence was VERIFIED, but the observed landed tree does not match the evaluated tree.

Evaluated merge-target treeb1ec95450a69
Actual landed tree13426dad6335

  1. 1Evaluated

    Bound

    Candidate ff6be1f9c318

    example/acme-service · PR #102

    Head tree 7b0e72f0c1a9 · evaluated target tree b1ec95450a69

  2. 2Evidence

    Bound

    5 evidence claims

    Required check test · 1 current approval · Repository rules

    Approval authority established

  3. 3Currentness

    Current

    Current when the merge event was recorded.

    At proof: Current

    Decision-time currentness is shown in details.

  4. 4Landed

    Different

    Different tree observed

    Commit 6bb4a8da2f46 · tree 13426dad6335

    Merge commit

  5. 5Conclusion

    FAIL

    Landed content differs from the evaluated candidate.

    Derived from the Merge Truth record above, not presentation state.

← View all example outcomesTRY IT ON A REAL PR
Evidence details and identifiers
Evaluated candidate
ff6be1f9c318 · tree 7b0e72f0c1a9
Evidence currentness
At proof: CURRENT · when merge event arrived: CURRENT · at merge decision: UNAVAILABLE
Landed content
Commit 6bb4a8da2f46 · tree 13426dad6335 · merge
Authoritative relationship
FAIL · LANDED_TREE_DIFFERS_FROM_PROVEN_TREE
Provider history
RECONCILED · PROVIDER_HISTORY_RECONCILED · through 2026-09-28T15:05:00.000Z

Bound claims

  • TARGET: evidence PROVEN · currentness CURRENT
  • CI_EXECUTED:test: evidence PROVEN · currentness CURRENT
  • APPROVAL_CURRENT: evidence PROVEN · currentness CURRENT
  • RULES_SNAPSHOT: evidence PROVEN · currentness CURRENT
  • REMOTE_DURABLE: evidence PROVEN · currentness CURRENT

Download Merge Truth JSON

Replay checks deterministic consistency of recorded evidence; it does not independently authenticate GitHub or establish present currentness.