ear: thread tail + own-id in every pass — addressee judgment was blind - #11
Merged
Conversation
Live 2026-07-30: an ear pass whose whole batch was one mid-thread line
("LMK if you wanna get in on browserstack") had no parent, no earlier
replies, and no id map, so it read noah's offer to a teammate as aimed
at her, recorded the debt, and the next wake had her answer a question
that was never hers (C0AUG2ZGVC5 thread=1785455500.025059).
The ear design already mandates the context ("each pass reads only the
delta past ear_cursor plus the live threads that delta touches") — the
implementation dropped the second half. Prompt-only fix, no new tools:
- threadTailBefore (inbox.ts): the already-heard tail of a thread at or
before the ear cursor, root included via its own-ts match (threads.ts
convention). Speaker + text only — all a context line needs.
- runEarPass prepends one 'already heard' block per thread the batch
touches, so who-is-talking-to-whom is visible again.
- composeEarInstructions now names her principal id, so the ear can
tell a mention of her from someone else's voice (it attributed
pedro's reply to her at 00:12 for lack of this).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 31, 2026
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.
Why
Live 2026-07-30 (thread): Bevelina answered Noah's browserstack offer that was aimed at Pedro. The ledger chain:
open_ask: "noah is asking whether you want access to browserstack").<@U…>ids and didn't know which one is her own.The ear design already mandates the missing context — "each pass reads only the delta past
ear_cursorplus the live threads that delta touches" — the implementation dropped the second half. The soul's guidance ("a question aimed at another teammate is that person's to answer") was right; it just couldn't be applied blind.What
Prompt-only, no new tools, no schema:
threadTailBefore(inbox.ts): the already-heard tail of a thread at or before the ear cursor, root included via its own-ts match (same convention as threads.ts). Speaker + text only.runEarPassprepends onealready heardblock per thread the batch touches, so who-is-talking-to-whom is visible again.composeEarInstructionsnames her principal id ("In the room she is<@…>"), so a mention of her is distinguishable from someone else's voice.Tests: two new §-style rows in
test/ear.test.ts(one reconstructs the incident shape). Fullbun run checkgreen — 384 pass.🤖 Generated with Claude Code