docs: pin the memory title rule and a length target, and drop the provenance carve-out - #1159
Merged
Conversation
…venance carve-out The public-artifacts section ended by exempting memories from it — "rag-rat memories are the internal cross-agent layer and may record provenance freely" — which licensed phase codes, round numbers, and review play-by-play inside memories. That is the narration that goes stale first and buries the rule under it, so memories are now held to the same bar, for the staleness reason rather than the audience one. Two rules that were implied but not stated: - The title states the rule, not the story. "Write a concrete title" was satisfied by titles like "#407 E3a: …" and "V042 … (phase A5)", which name the work and force the reader into the body to learn whether it concerns them. - Terseness gets a number. "Be terse" is unfalsifiable on its own: aim under 900 characters, with most entries at 300–600.
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.
Three gaps in the memory-writing rules, each one something the guidance did not catch in practice.
The provenance carve-out contradicted the rest. The public-artifacts section closed with
"(This is about public artifacts; rag-rat memories are the internal cross-agent layer and may
record provenance freely.)" — which explicitly licensed phase codes, round numbers, and review
play-by-play inside memories. Whatever the audience argument, that is the material that goes stale
first and buries the rule underneath it. Memories are now held to the same bar, for the staleness
reason rather than the privacy one. Durable, checkable references — issue numbers, SHAs, test names,
paths — remain welcome in both places; the story does not.
The title rule was implied, not stated. "Write a concrete title" is satisfied by
#407 E3a: …,C4.3b, andV042 … (phase A5). Those name the work rather than the rule, so areader scanning attached memories has to open each body to find out whether it concerns them. The
title now has to name the constraint or the trap, with an issue number allowed only as a trailing
pointer, inside the existing 160-character cap.
Terseness had no number. As written it was unfalsifiable, and unfalsifiable guidance does not
hold a corpus to anything. The target is now under 900 characters, with most entries at 300–600 —
past that a memory is usually restating code the reader can go read.
plugin/test/verify-skill-parity.shpasses: the shippedplugin/skills/using-rag-ratcopy matchesits
.agents/skillssource.AGENTS.mdcarries the same three changes. Documentation only.