Repository navigation
docs: propagate the v3.3 close-out receipt into HOW_TO_USE, README tree, and tutorials - #54
Merged
Merged
Conversation
…tree The release surfaced a downstream-doc completeness gap (Learning KJ5HST#7): - HOW_TO_USE.md §Phase 3 3D described "Update SESSION_NOTES.md" with no HANDOFFS receipt — and it is DISTRIBUTED, so it contradicted the synced SESSION_RUNNER. Now names the durable receipt + bin/check-handoff + the Phase 0 reconcile catch. - README.md Repository Structure tree now lists HANDOFFS.md (starter-kit) and bin/check-handoff. Docs-lag; no version event (v3.1->BL-6 pattern). check-links clean. Tutorials follow in the next commit. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- T2_worked_transcript: its Phase-3 close-out now completes a full ```handoff receipt (S1, status pending->complete), and the receipt joins the explicit git add in 3F. - T2_first_session: the 1B claim opens a status:pending receipt stub; 3D + the expected-result now name the durable HANDOFFS.md receipt. - T3_compounding_loop: the handoff is also a receipt carrying predecessor_score, so both halves of the compounding loop are machine-checkable, not just prose. Docs-lag; no version event. check-links clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jul 9, 2026
Add a 'completeness-critic' pass to reviews — flag what a change made stale outside its own diff
#55
Closed
rmsharp
added a commit
that referenced
this pull request
Jul 9, 2026
Promotes Learning #7 (cross-reference completeness at self-review) and Learning #8 (close-out-gate checklist propagation) from authoring-time self-checks to an explicit review-time lens: a review/audit pass now owes a whole-corpus sweep (not just the diff) for enumerations, worked examples, indexes, and count-claims a change made stale elsewhere. - SESSION_RUNNER.md: new Learning #10 - AUDIT_WORKSTREAM.md: new anti-pattern #9 "Diff-scoped blind spot", a new Verification Checklist bullet, and a note that /code-review, /review, /security-review are diff-scoped by design - ITERATIVE_METHODOLOGY.md: one sentence in Review/Audit Sessions citing the new Learning + the operative checklist step Motivated by the v3.3 doc-completeness gap (PR #54) that a clean 6-lens adversarial review missed. No new phase, gate, principle, or workstream; failure-mode count stays 27. Design adversarially checked by a 4-lens review before commit (2 clean, 2 raised real findings — a mis-anchored insertion point and a missing starter-kit/ citation prefix — both fixed). bin/tests.sh 84/84; bin/check-links clean. Closes #55
rmsharp
added a commit
to rmsharp/methodology
that referenced
this pull request
Sep 5, 2026
…ate REBUILT as cf15489 on cea3068, re-verified, not pushed The six-row fix-round from S147's self-review applied (fork halves first, 22c6cf0 and 544cfb0), two review lenses re-run (fourteen items on 46089f1, seven on c6577f2, every one re-derived), the branch rebuilt four times and every DONE-list figure re-measured on the last. One flagged site left alone on evidence: context_budget.py:409 is upstream's own 1.0.0 line (Learning KJ5HST#54). Records: the body file's header and fix-round section, the plan's Phase B record and re-stated blob criterion, both ledgers. Nothing pushed, nothing opened; Phases C and D still need their own go-aheads. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Re2oqcEUwV71gh5wrSbzab
rmsharp
added a commit
to rmsharp/methodology
that referenced
this pull request
Sep 21, 2026
…ntence about it A config row is one object in JSON but many lines in git. The note BL-78 P2 replaced opened "max_tokens 6,777 SINCE S177" and four clauses later dated the BYTE pin beside it to S177 as well. git blame splits the two adjacent lines by 17 days: max_tokens is 0e8c6ac (2026-09-16, S177), max_bytes is beffbd0 (2026-08-30, S129), and git log -S on the literal returns that one commit. The misdating inverted the note's own characterization -- pinned at S129 the figure was the file's measured size, stable 53 days, exactly the "measurement dressed as a budget" the note insisted it was not. Three sessions costed, ratified and executed against that warrant without blaming the line. D3 discharged by refusal, rows considered named: KJ5HST#86, KJ5HST#87, KJ5HST#88, KJ5HST#54, KJ5HST#56. None meets (a) -- no gate, test or failure mode enforces their lessons; none meets (b) -- KJ5HST#89 narrows the provenance lesson rather than generalizing it; none meets (c) -- every artifact they are about still exists. Verified: check-learnings 75 rows, contiguous 15..89, 0 over 1,500 B. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Downstream doc-completeness follow-on to #52/#53 (the v3.3 close-out receipt). No version event (docs-lag, matching the v3.1→BL-6 pattern).
HOW_TO_USE.md (distributed) §Phase 3 3D described
SESSION_NOTES.md+CHANGELOGwith no HANDOFFS receipt — it was inconsistent with the syncedSESSION_RUNNER.md. Now names the durable receipt +bin/check-handoff+ the Phase 0 reconcile catch.README.md Repository Structure tree lists
HANDOFFS.md(starter-kit) andbin/check-handoff.Tutorials — T2_worked_transcript (a full
handoffreceipt in Phase 3 + thegit add), T2_first_session (1B receipt stub + 3D/expected-result), T3_compounding_loop (the receipt carriespredecessor_score, making the loop machine-checkable). A completeness sweep found no other tutorial demonstrating close-out without the receipt (T5 only references a prior handoff).bin/check-linksclean. No principle/phase/gate/workstream/FM change.