Skip to content

A confident merge waits for no one, and a succession clashes with nothing #693

Description

@WaylandYang

On the Blackbaud lease bench (dev 0306d0c, two runs), the lease stayed split into several entities, so as-of questions came back with several answers. Three things held the merges that would have joined it:

  • The benches turn governance off. lease_bench.py and recall.mjs set governance = false. A new base has it on (0050), so the benches measure a configuration users don't run.
  • One confident pair in ten goes to a person (0026 decision 5). "Lease Agreement dated May 16, 2016, as amended" vs "Lease Agreement" was judged the same at 0.95 and held as escalate_sample.
  • The execution gate's contradiction ignores time (0027 decision 5). "Lease Agreement" and "Lease Agreement dated May 16, 2016" each hold one landlord, HPBB1 and then BBHQ1: a succession. The gate called it contradiction landlord and held the pair every run. The consistency check has read time since Two values clash only while both hold #635; the gate never followed.

Decided (2026-09-14): governance stays on in the benches, the sample is removed, and a contradiction is two values that still hold at the same moment once the temporal engine places them.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions