A card's finding is evidence; its scope and its stated fix are a guess - #37
Merged
Conversation
LRN-0033 was written after T-0207 and framed narrowly: a card goes stale because the decision it was filed under was superseded. Two more instances landed within the day and neither involved a supersession. T-0202's scope named the three sites its author had found; there was a fourth with a rule of its own, and it was the worst of them. T-0161's stated mechanism was simply wrong — `candidate.id` is not set when `validateCardCandidate` runs, and the sibling guard it cited as precedent does not catch the case it claimed to. Writing the branch that card asked for left the reported bug reproducing exactly as filed. So the record is generalised to what the three of them share, which is not why the card went stale but which part of it did: the finding is evidence, and the scope and the account of the fix are a hypothesis written by somebody who had not done the work. `occurrences: 3`. Renaming it turned up T-0223. `filename-stale` exists for cards, with `doctor --fix` to repair it and a comment explaining why a stale handle matters. Memory records, documents and fragments derive filenames the same way and have no such rule, so retitling this learning left it under its old name with doctor reporting 0/0. Renamed by hand, which is the only repair there is. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D3LTdq3mzMAQ98rwBegGjU
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Records only — no code.
LRN-0033 was written yesterday after T-0207 and framed narrowly: a card goes stale because the decision it was filed under was superseded. Two more instances landed within the day and neither involved a supersession.
candidate.idis not set whenvalidateCardCandidateruns, and the sibling guard the card cited as precedent does not catch the case it claimed to. Writing the branch it asked for left the reported bug reproducing exactly as filed.So the record now says what the three share, which is not why a card goes stale but which part does: the finding is evidence — somebody hit it — and the scope and the account of the fix are a hypothesis written before the work by someone who had not done it.
occurrences: 3.The failure mode is worth naming precisely, because it is not a card that looks wrong: it is a card that looks finishable, whose criteria can all be met while the reported defect survives. That happened once here and nearly happened twice.
T-0223 came out of renaming it
filename-staleexists for cards, withdoctor --fixto repair it and a comment explaining why a stale handle matters — it is what people and agents grep by. Memory records, managed documents and changelog fragments derive their filenames from their titles the same way and have no such rule. So retitling this learning left it sitting underLRN-0033-a-card-outlives-the-decision-it-was-filed-under-…withdoctorreporting 0 errors and 0 warnings.Renamed by hand, which is the only repair available. Filed as low.
doctor0/0,memory verifyclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01D3LTdq3mzMAQ98rwBegGjU