Repository navigation
docs(policy): keep investigation records in built-in memory - #3
Merged
Merged
Conversation
Keep research trails, code-evidence inventories and routine verification checkpoints in each agent’s built-in memory. Preserve essential rationale and supporting references for substantive documented claims, with chat continuity when memory is unavailable.
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.
AGENTS.md directs agent investigation notes, external comparisons, code-evidence inventories and routine checkpoints to each agent's own built-in memory outside Git. Authorized documentation retains current guidance, essential rationale and necessary supporting references; unavailable memory falls back to chat without claiming persistence. External-state verification dates are retained where readers need them to interpret a substantive documented claim.
Only agent instructions change. Existing product documentation and runtime behaviour are unchanged.
Validation: Exact shared-policy comparison, three instruction links/headings, publication-boundary review and git diff --check passed. All required documentation checks passed: 22 unit tests, content/type check, production build, 84 generated links and 12 browser tests. Independent review found no actionable issues.