RAGE #54: trusted delegated Auto-Dig session registration - #55
Draft
lost-rob0t wants to merge 2 commits into
Draft
RAGE #54: trusted delegated Auto-Dig session registration#55lost-rob0t wants to merge 2 commits into
lost-rob0t wants to merge 2 commits into
Conversation
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.
Tests-first owner-boundary slice for #54.
The RED contract requires a disabled-by-default trusted registration seam that can accept an already-authenticated StarIntel human principal/scopes/workspaces from an internal service adapter, register only canonical fixed Auto-Dig capabilities, and produce a short-lived WebSocket session without ever receiving a user OAuth bearer token.
Initial tests require:
No production registration endpoint or gateway enablement is included on this initial head. Expected state is RED.