Skip to content

A workspace sets the points from which the run keeps pairs (set floor) - #148

Merged
mvsbm merged 1 commit into
mainfrom
keep-floor
Nov 16, 2026
Merged

mvsbm merged 1 commit into
mainfrom
keep-floor

Conversation

@mvsbm

@mvsbm mvsbm commented Nov 16, 2026

Copy link
Copy Markdown
Owner

What and why

The run stored only pairs whose best case reached 0 points; the 0 was fixed in the code. A pair sharing a name and a phone but neither address nor ID could fall below it and never reach people.

  • nayose set floor --points -10 writes method.toml keep.
  • The best-case bound (Run._reaching), scoring and scored/ read it, 0 unless set. Increments follow it.
  • The oversized blocks' gate keeps its own floor (search_floor), so a low floor doesn't join giant blocks in full.
  • The floor enters the run's hash only when set: workspaces that never set it keep their hash (checked: ed75b34a69 on main and here), and setting it owes a rerun.

On a 20,000-record generated workspace, -10 stored 4,990 pairs instead of 2,365; the 2,532 pairs at 0 and up are unchanged. The test checks the same on the test population: identical pairs and points at 0 and up.

First slice of Run settings; describe scores and the page follow.

Checklist (CONTRIBUTING.md)

  • Reviewed before merging: a review pass on this pull request's changes (rule 10)
  • Unhappy paths tested at the real size: two at once, an input twice, the real data size, a lost server (rule 9)
  • Every new limit names itself (shortcut: …), and every store that grows says what bounds it (rules 3 and 4)
  • Docs and diagrams describe the code as it is

Real size: the default (0) is unchanged at any size. The cost of -10 at a million records is not measured yet; it is measured in the next slice before the page offers it. set floor runs under the run lock, so two at once write one after the other.

🤖 Generated with Claude Code

https://claude.ai/code/session_012o8JNBKSY1aREPbMQDG8g2

… writes method.toml keep, and the run scores and stores every pair whose best case reaches it, 0 unless set

The best-case bound and scored/ read the floor instead of a fixed 0, so a lower floor keeps pairs people can review that 0 drops. The oversized blocks' gate keeps its own floor. The floor enters the run's hash only when set, so a workspace that never sets it keeps its hash, and setting it owes a rerun.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012o8JNBKSY1aREPbMQDG8g2
@mvsbm
mvsbm merged commit e3ec3d4 into main Nov 16, 2026
6 checks passed
@mvsbm
mvsbm deleted the keep-floor branch November 16, 2026 04:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant