Repository navigation
Preserve inbox wakes during automatic report delivery - #66
Merged
marvin-bitterlich merged 5 commits intoJul 12, 2026
Conversation
marvin-bitterlich
deleted the
marvin-bitterlich/pardes/coordinate-inbox-wakes-with-automatic-report-delivery
branch
July 12, 2026 01:50
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.
Why?
A Pardes inbox wake arriving between canonical report parts—or while
report_getwas still reading its artifact—could silently cancel or stall automatic delivery.How?
Lease the conversation from report permit acquisition through read/start, defer or roll back unsent wake cursors while reports own it, and model one exact manager-registered wake as a bounded interlude whose full Pi lifecycle resumes delivery deterministically.
Decisions
message_startpermits one report retrieval in that manager turn; part one waits for wakeagent_end.Callouts
message_start,message_end,agent_end, compaction, stop, reload, and timeout.