Journal an initializing event during model load - #156
Open
johnsabath wants to merge 1 commit into
Open
Conversation
johnsabath
force-pushed
the
john/initializing-journal-event
branch
from
August 27, 2026 19:57
78b2f6b to
c079dd2
Compare
The runner emits nothing on /events between boot and initialization_success, so the model-load window reads as silence — a consumer replaying the journal cannot tell a loading runtime from a dead one. Add a SessionEvent.INITIALIZING self-loop, legal only in CREATED, sent once at boot before the (blocking) load. It changes no state and touches no side effect (the bridge is not built yet), so a consumer replaying /events observes the loading phase directly, ahead of initialization_success. Signed-off-by: John Sabath <john@reactor.inc>
johnsabath
force-pushed
the
john/initializing-journal-event
branch
from
August 27, 2026 20:10
c079dd2 to
f13658e
Compare
johnsabath
marked this pull request as ready for review
August 27, 2026 20:11
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.
Between boot and
initialization_success, the runner emits nothing on/events, so the model-load window reads as silence — a consumer replaying the journal cannot tell a loading runtime from a dead one.Add a
SessionEvent.INITIALIZINGself-loop, legal only inCREATED, sent once at boot before the (blocking) load. It moves no state and touches no side effect — the bridge is not built yet — so it is a pure journal record. A consumer subscribed to/eventsnow observes the loading phase directly, ahead ofinitialization_success.Proved by a unit test that replays the boot journal over SSE —
initializing, theninitialization_success— plus the transition-table test covering legal-in-CREATEDand rejected-elsewhere.