Plan: Mirror privilege boundary + evidence broker - #5
Draft
jackye426 wants to merge 2 commits into
Draft
Conversation
Document distillates-by-default architecture: credential split, Mirror vs ops tool profiles, retrieve_supporting_evidence broker, audit, and rollout order. Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
Two MCP endpoints, no raw Mirror tools, broker-only sessions, sanitised calendar, policy-gated capabilities, ops-issued restricted access, separate vault credential for compilers, stronger portrait protection. Co-authored-by: jackye426 <jackye426@users.noreply.github.com>
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.
Summary
Planning doc for the Mirror security model, with decisions locked:
/mcpMirror,/mcp/ops)See
docs/mirror-privilege-plan.md.No runtime code in this PR.