[Refactor] Isolate task-memory projection from Brain outbox draining - #2611
Open
roomote-roomote[bot] wants to merge 1 commit into
Open
[Refactor] Isolate task-memory projection from Brain outbox draining#2611roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
September 12, 2026 23:36
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.
What changed
Extracted deterministic task-memory request parsing, initiator attribution, pull-request outcome modeling, and Brain page rendering into a focused projection module. The projection assertions now live in a dedicated test suite, while the outbox drainer composes the projection from its database lookups.
Why this change was made
PR #2585 added content-shape policy directly to an already large outbox orchestration module. Separating deterministic page modeling from claim, retry, replay, and drain-loop behavior reduces the risk that memory-content changes affect queue lifecycle code.
Impact
There is no intended user-visible behavior change. Task-memory content and backfill behavior stay unchanged, while the Brain outbox drainer returns to orchestration ownership and the projection contract can evolve behind focused tests.