Skip to content

A must claim is never unmet for a missing result, a near-zero pair, a within-noise pair or an unknown item #3

Open

Description

@mklarmann

A scope entry with expect: must says each covered pair must move. Today:

  • a pair that is within noise gets within noise, and a near-zero pair gets not judged, so a must that did not move beyond the noise or the floor is never reported as unmet;
  • a missing result gets not judged (right: it cannot be judged), but nothing counts the must entries left unjudged;
  • an item id in a scope that no state holds (a typo) gives no verdict at all and still counts in reach.

SPEC 6 has two rows (claimed, not moved and within noise / not judged) that both hold for such a pair and gives no order.

Made-up case: scope must down on p; p goes 1.0 → 1.0000001 with noise 1e-3 → within noise, never claimed, not moved.

Proposed: under a must entry, a pair that agrees, is within noise or is near zero is claimed, not moved; a missing pair stays not judged. chain.build refuses a scope item that no state holds. SPEC 6 gives the order.

Needs a decision. The fix on first-version takes the option above; Manuel confirms it or picks another in review.

Found by sentier-bafu's agent review of pull request #2 (head 5c19866), confirmed again on 0e1f5be. Being fixed on the same branch, first-version.

Activity

  1. added
    bugSomething isn't working
    needs-triageMaintainer needs to evaluate this issue
    on Nov 16, 2026
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

    bugSomething isn't workingneeds-triageMaintainer needs to evaluate this issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions