Skip to content

The repo-graph freshness gate compares committed == fresh and passes when both are 356 triples short — assert a floor from binding.yaml entries / main's count, not self-consistency #3641

Closed

Description

@noahgift

What

the_tracked_repo_graph_is_fresh passes when contracts.nt (committed) == fresh extraction. Both being 356 triples short — as on #3350's branch after a one-character binding.yaml corruption (see the producer-side row) — passes. Equality with a fresh extraction is a consistency check, not a correctness check: it cannot see a shrink that the producer reproduces deterministically.

done_when

Refs #3350, the producer row (pv extract must refuse), #3639.

Activity

  1. added this to the 0.70.0 milestone on Sep 20, 2026
  2. noahgift commented on Sep 20, 2026

    @noahgift
    MemberAuthor

    d4's discriminator, in their words, for the shape of the floor: the reason the binding.yaml defect was catchable at all is that main's committed graph was a known-good 15,600 and the branch produced 15,244 — a count against a reference found it, where committed == fresh could not. The tell is a drop against something outside the run, never agreement with yourself. Same discriminator as the stale-pv case (#3635/#3600).

  3. modified the milestones: 0.70.0, 0.71.0 on Sep 23, 2026
  4. noahgift commented on Sep 23, 2026

    @noahgift
    MemberAuthor

    milestone → 0.71.0 per docs/roadmaps/milestone-triage-2026-09-23.md (#4024), operator approval 2026-09-23 (relayed by aprender-cf). Reason: repo-graph freshness floor, with #3640: debt ratchet pillar C (#3997), slice 2

  5. noahgift commented on Sep 24, 2026

    @noahgift
    MemberAuthor

    Closed by paiml-implement — folded into epic #2556 (triage evidence/triage-1623.md)

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 working

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions