Repository navigation
Add: judge-gated-finding-exchange-between-sub-agents - #159
Merged
Merged
Conversation
|
@qybaihe is attempting to deploy a commit to the nkkko's projects Team on Vercel. A member of the Team first needs to authorize it. |
Assisted-by: Claude Opus 5.5
Rebuild generated aggregates after rebasing onto current main. bun run build:data output. Co-Authored-By: Claude Code <noreply@anthropic.com>
nibzard
force-pushed
the
add-judge-gated-finding-exchange
branch
from
October 14, 2026 22:36
ab1f892 to
0fccc29
Compare
Owner
|
Merged — thank you. I regenerated the catalog data ( 🤖 Generated with Claude Code |
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.
PR intent
Reviewer checklist
What this adds
A pattern for parallel sub-agents that share a board. Instead of broadcasting everything or reporting only to the parent, a small judge answers three narrow questions: is this message news for the others, does this note matter to this particular sibling, and does a new note overturn an earlier one. An overturned note becomes a correction for everyone who received it.
The closest existing patterns are Board-Mediated Async Inter-Agent Coordination, which routes by explicit addressing, and Non-Generative Judgment Routing, which is about sending single decision steps to a judge. This one is about what crosses between agents, and how a retraction follows the note it retracts.
Conflict of interest
The implementation I reference is my own project, mu. That is stated in
authors,based_onand Known implementations, and Hearsay-II is cited as the non-self reference for the blackboard idea.AI assistance
Claude (Anthropic), through Claude Code, drafted the pattern and this description. I read the draft, asked for a plainer rewrite, and approved this version. What the pattern describes was checked against the public README ("The hive") and
packages/kyrn-judge/src/decisions/hive.ts. The commit carries anAssisted-by:trailer.