Skip to content

process(docs): a ratchet raise question offers an equal cut first - #2748

Merged
antonsynd merged 2 commits into
devfrom
claude/stop-rule-net-zero
Nov 19, 2026
Merged

antonsynd merged 2 commits into
devfrom
claude/stop-rule-net-zero

Conversation

@antonsynd

@antonsynd antonsynd commented Nov 19, 2026 •

Copy link
Copy Markdown
Owner

Adds the owner's 2026-11-19 ruling to the rise rule in the goals document's §4: a ratchet-raise question names the measured delta and offers an equal cut first.

Owner's word, 2026-11-19: "both your recs". It answered the health watch's check 12, which recommended two things:

  • by default, a procedure-bytes raise comes with an equal cut elsewhere, and is raised only when none is found;
  • the owner's word is given on the measured number, never on an estimate.

Why. On 11-18, procedure bytes went from 142,860 to 145,560 in a day through two raises (#2743, #2746). Each followed the rule: each rise came to the owner, and the owner's words are quoted. One of the two answers was given on an estimate of about +1.5 KB; what landed was +1,853.

Change (docs/process/handoff-2026-11-17-arc.md §4, the rise rule): one sentence added after "(a raise lands only with it quoted in the pull request body)": "The question names the measured delta, never an estimate; for procedure or CLAUDE.md bytes it offers an equal cut in the same counted text as the default, and a raise is for when the lead finds no cut (owner, 2026-11-19: "both your recs")." The equal-cut default names only the byte rows: the bullet also covers the side-table pin and allowlist rows, where a cut would be compiler work or a bug fix, and the ruling did not cover them. No baseline changes, and the goals document is not counted text.

Measured @ 3d3889f2b: process_index --check up to date; scorecard_metrics.py --check OK; check_commit_subjects.sh origin/dev..HEAD: 2 subjects, no closing keyword.

Gate: .NET 10 run 44461068410 success, Python Build Tools 44461068245 success, Commit Subjects 44461068310 success @ 3d3889f (measured); ratchet --check OK
Independent review @ da18cbd: merge after fixes; 2 applied, 0 declined; fixes da18cbd..3d3889f read by the lead

Applied: the equal-cut default reached the side-table pin and allowlist rows, which the ruling did not cover (narrowed to procedure and CLAUDE.md bytes); "no cut is found" now says who looks ("the lead finds no cut").

sharpy-issues:
  closes: []
  files: []

https://claude.ai/code/session_01LGMKZXE9K8LiDXK2rj4doP


Generated by Claude Code

Two procedure-bytes raises landed on 11-18 (+2,700 bytes in a day), each
on the owner's word through the §4 stop rule, one of them answered on an
estimate 353 bytes below what landed. The owner ruled on 2026-11-19
("both your recs"): the question names the measured delta, never an
estimate, and offers an equal cut in the same counted text as the
default; a raise is for when no cut is found. §4's rise rule now says so.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01LGMKZXE9K8LiDXK2rj4doP
Review of the first commit: the owner ruled on procedure bytes, but the
rise rule's bullet also covers the side-table pin (a count of SemanticInfo
fields) and allowlist rows, where a "cut" is compiler work or a bug fix
the owner never chose as a default. The equal-cut default now names
procedure and CLAUDE.md bytes; "never an estimate" stays general. "No cut
is found" becomes "the lead finds no cut", which says who looks.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01LGMKZXE9K8LiDXK2rj4doP
@antonsynd
antonsynd merged commit edd400f into dev Nov 19, 2026
23 checks passed
@antonsynd
antonsynd deleted the claude/stop-rule-net-zero branch November 19, 2026 04:58
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.

2 participants