orbit backend: caller-named broker participant, 'engine' role - #87
Merged
Conversation
The broker draws every connected runtime as a participant, so the backend's anonymous `rhapsody.<uuid>` shows up as noise in a topology view -- two of them, unexplained, for a session with two engines. A caller which knows what the backend is for can now say so (`participant_name="rhapsody.<session>.<role>"`); uniqueness becomes that caller's contract. Unnamed backends keep the unique suffix and the old behavior exactly. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
'consumer' is the runtime's say-nothing default. A topology viewer now sees what the participant is: the engine side of the compute hand-off. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
AymenFJA
self-requested a review
August 25, 2026 13:25
AymenFJA
added
enhancement
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
2 participants
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.
Two small changes to how the orbit execution backend presents itself on the broker:
participant_nameconstructor argument: a caller which knows what the backend is for can name its broker participant (rhapsody.<session>.<role>); uniqueness becomes that caller's contract. Unnamed backends keep therhapsody.<uuid>unique suffix and the old behavior exactly.role="engine"instead of the runtime's say-nothingconsumerdefault, so a topology viewer sees what the participant is: the engine side of the compute hand-off.Motivation: the DTaaS service runs two engines per session (inference/learning); anonymous
rhapsody.<uuid>participants show up as unexplained noise in the broker topology view. The digital.twins service already passesparticipant_nameguarded by a signature check, so this PR is backward- and forward-compatible with it.Cherry-picked clean onto
mainfrom thefix/orbit-participant-namebranch (which is stacked on the flux/partitions work).tests/unit/test_backend_execution_orbit.py: 38 passed.🤖 Generated with Claude Code
https://claude.ai/code/session_016Npyz3Hbnwos12ESsdJ2YU