Repository navigation
feat(memory): 사용자의 지시는 메모리에, assignment 태그 노트로 (4.99.0) - #171
Merged
Merged
Conversation
…tes (4.99.0) The user's instructions, and what the user says matters, are kept in memory and nowhere else. 4.98.0 built a separate TASK layer (store contract, tables, Task tools, a board, host recording); this removes it and keeps one memory note: - The model keeps them itself when they matter: the memory guidance (only where the write tools are) asks it to save the work the user gives, the instructions to keep and what the user says matters as a note tagged `assignment`, in the user's words with the conditions and what was delivered, to rewrite that note as the work changes and to tag it `done` when finished or called off. - Memory brings them back every turn: open assignment notes are loaded whatever the message says (search is keyed on the message, and "continue" finds nothing), shown in their own `# Assignments` section, 40% of the memory budget, cut with markers naming the note, left-out notes listed by name, never repeated by search. - memory_write takes `filename` to rewrite that very note. - Pinned facts cut to fit say so and where to read them. - Removed: memory.tasks, Task/TaskRecall, the task board, turn-end task recording, the checkpoint-on-task, task_id on execution cards, provider tasks(). Event context.task_board retired; + memory.assignments_loaded (catalogue v20). Co-Authored-By: Claude Opus 5.5 (1M context) <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.
무엇을 바꿨나
사용자의 지시와 사용자가 중요하다고 말한 것은 메모리 안에서만 관리한다. 4.98.0 은 별도 TASK 층(저장 계약·표·Task 도구·판·호스트 기록)을 만들었다. 이 판은 그 층을 모두 걷어내고, 메모리 노트 하나(
assignment태그)로 바꾼다.assignment태그 노트로 남긴다. 사용자의 말 그대로와 정한 조건, 해 준 것을 담고, 일이 바뀌면 그 노트를 고쳐 쓰고, 끝나면done태그를 단다. 쓰기 도구가 없는 대화(읽기 전용·CLI 자동)에는 이 문구가 붙지 않는다.# Assignments절에 싣는다. 몫은 기억 주입 예산의 40%다. 맞지 않으면 노트 이름과 함께 잘렸다고 적고, 못 실은 노트는 이름으로 적는다. 같은 노트는 검색 층에 다시 싣지 않는다.memory_write(filename=...): 그 노트를 고쳐 쓴다.memory.tasks,Task·TaskRecall, TASK 판, 턴 끝 TASK 기록, 압축 요약의 TASK 보관, 실행 카드 task_id, providertasks(). 이벤트context.task_board는 은퇴시키고,memory.assignments_loaded를 더했다(카탈로그 v20).확인
tests/unit/test_assignment_memory.py7개: "계속" 에도 실린다, done·dropped 는 빠진다, 검색이 같은 노트를 다시 싣지 않는다(태그를 빼면 검색이 찾는 것으로 시험이 유효함을 확인), 잘림 표식, filename 고쳐 쓰기, 쓰기 도구 없는 지침에는 쓰라는 말이 없다, build_pipeline 요청에 실린다.gen_event_docs --check통과.🤖 Generated with Claude Code