Repository navigation
gateway: an edit miss and a fresh create name the same-name file one directory away - #739
Merged
Merged
Conversation
…directory away cbp-being 2026-11-16 06:23Z: memory_edit on the bare name of scratch/xor_not_linearly_separable.py got "does not exist ... memory_write creates a file"; it did that, the receipt said "created ...", and the rest of the beat edited/read/ran a new 66-line top-level copy while the 401-line scratch/ file (the one an importing script reads) stayed unchanged. memory_read already names a same-name file on a miss (#140). memory_edit's absence now names it with the exact path to resend (and drops the route to memory_write when one exists); memory_write's "created" receipt says a same-name file exists elsewhere and was NOT changed. Matches listed neutrally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dp-web4
added a commit
that referenced
this pull request
Nov 19, 2026
…same-name notes Main's #739 added _same_name_note at the same two places (memory_edit absence, fresh create receipt). The facts are independent: a retired copy beside the name, and a file with the same name one directory away. Both are kept, retired copy first; the generic 'memory_write creates a file' line is used only when neither applies. New test covers a home with both. Docstrings now describe the being's stored memory and journal entry instead of quoting them (dp's 11-10 rule, as raised by Nomad on #746). Co-Authored-By: Claude Opus 5.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.
Measured 2026-11-16 06:23Z, cbp-being beat heartbeat-5d75f0a150eb. The seat (15966) asked for two memory_edit range deletions on
scratch/xor_not_linearly_separable.py(401 lines). The being sent the bare name:memory_edit xor_not_linearly_separable.py→ "nothing to edit: ... does not exist. ... memory_write creates a file; memory_edit changes one that is there."memory_write xor_not_linearly_separable.py→ "created xor_not_linearly_separable.py with 2059 chars"xor-mlp-4-vs-64-32.pyimports.The absence text pointed it straight at making the duplicate.
memory_readalready names a same-name file on a miss (#140);memory_editand the create receipt did not.Change (
reference_f1a.py, reusing_same_name_elsewhere):createdreceipt: add "A file with this name already exists elsewhere: '...'. It was NOT changed; this write made a separate new file."Same family as #727 (an absence on a retired name names the retired copy) and the 11-13/11-14 bare-name vs scratch/ cases.
Tests: new
test_edit_absence_names_same_name.py(4 tests). On main source, 2 fail (the two new behaviours) and 2 pass (true absence, no namesake). Fullsage/gateway/tests: 2490 passed, 44 skipped, 1 xfailed (pre-existing).🤖 Generated with Claude Code