feat(digest): status changes are news (0.14.2)#77
Merged
Conversation
…in one cycle (0.14.2) Review question: will agent A ever see agent X's status and think "I need this"? The injection mechanism existed, but statuses only rode along when something ELSE was news — a status change alone stayed invisible until unrelated traffic fired. The digest snapshot now records statuses; changes surface as "now working — X: <status>" and count as news on their own; steady statuses stay silent. Clearing an ask announces the return to plain work (no CTA). Tests pin all three moments: change breaks silence once, ask-clear announces, steady state is quiet. Co-Authored-By: Claude Fable 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
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.
A status CHANGE alone now triggers the digest ('now working — X: designing the auth schema') so 'oh, I need this' moments happen within one cycle; ask-clears announce the return to work; steady statuses stay silent. Green-before-commit enforced.