docs(specs): away-operator notification channel design (roadmap item 2)#431
Open
sahuagin wants to merge 1 commit into
Open
docs(specs): away-operator notification channel design (roadmap item 2)#431sahuagin wants to merge 1 commit into
sahuagin wants to merge 1 commit into
Conversation
Design memo for the daemon-side out-of-band notification channel: the attached-frontend surface (OSC 99 in mu-solo) exists, but a detached operator gets nothing. Proposes a config-gated operator-owned relay command invoked per event with a JSON payload, event-driven at the forwarder fan-out, fail-open, rate-limited, journal-audited. Ends in explicit operator decision items; no code until those are made.
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.
Design memo for the missing half of roadmap item 2: the attached-frontend notification surface exists (mu-solo OSC 99, focus-gated, journaled — landed on the Jul-2 line), but a detached/away operator gets nothing; the daemon has no out-of-band channel at all (grep-verified).
Proposal v1 at specs/plans/mu-away-operator-notify.md: a config-gated [notify] section — an operator-owned relay command invoked per event (argv exec, JSON payload on stdin), hooked event-driven at the serve forwarder fan-out, fail-open with timeout, per-(session,kind) rate-limited, every attempt journaled, payloads id/kind/summary-only (shareable-log discipline, no vendor or endpoint hardcoded in mu).
Ends in 4 explicit OPERATOR DECISION items (transport seam, default event set, autonomy auto-enable, where the summary mapping lives) — no code until those are made. Build sketch included.
Verification: scripts/pre-pr-check.sh green in this workspace (docs-only diff on land-jul2-line). Stacked on #427; retarget to main after it merges.
🤖 Generated with Claude Code
https://claude.ai/code/session_012P4F7VoJPSQCvLy6duFH43