Render the delegation topology: child-role everywhere lineage shows (v1.22.0) #46
Loading…
Reference in a new issue
No description provided.
Delete branch "obs-brain-role"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Pairs with zcode-dispatch v0.3.6 (
--child-role {pinky,brain}): the dispatcher now stamps a child role into every record it writes, and the observatory renders the master → sub-brain → pinkies topology from it.Payload: every session in
/api/sessionscarriesrole(pinkydefault /brain= delegation node), resolved by declared precedence — live spawn flag/resultchildRole(newlive_child_roles()/proc reader) → dispatch lifecycle ledger → bell ledger (rolenow parsed) → pinned-title[🧠]prefix fallback (survives ledger rotation). Usage-graph series carry the role too. Resolution order documented inchild_role_map's docstring and the README.Rendering: panel info strips badge brain-children as 🧠 BRAIN-CHILD (cyan — orchestration structure, not family hue); the table's brain-child parent links wear the 🧠 glyph + stronger glow (the delegation backbone vs the worker swarm); usage-graph brain-child series lines render thicker with a 🧠 tooltip marker. Note: the observatory has no node-edge lineage graph — lineage lives in the table family accents and the usage graph's brain-grouped series lines, so 'stronger brain-child edges' lands on exactly those surfaces.
Gates: unittest 31/31 (4 new in tests/test_role_payload.py), boot check, social-preview byte-check, pinned Super-Linter slim-v8.7.0 EXIT 0 (all six lanes, PYLINT 10.00/10). README: delegation-topology section under 'The orchestration it rides on', edge-source list + strip + usage-API notes, install URL → v1.22.0.