Plan: plugin architecture (D41–D46) — credential plane, sandboxing, harness admission, approval policy as plugins - #1
Open
itz4blitz wants to merge 1 commit into
Open
Conversation
…plane, sandboxing, harness admission, approval policy Core stays small and security-reviewable; deployment-specific concerns become capability-scoped plugins. First-party flagship plugins: 1Password CredentialProvider (service-account scoped, feeds the D23 session cache), container SandboxProvider (implements the D25 independent-enforcement rule), ACP HarnessAdapters (claude-code/codex/opencode/zcode admission per D17), and the ApprovalPolicy pack over the D12 4-way enum. - docs/DECISIONS.md: D41–D46 appended (house format), summary table gains plan/21 row - plan/21-plugin-architecture.md: new plan doc — trait seams, manifest & capabilities, out-of-process plugin host, threat-model mapping (credential readability + abuse-in-session), milestone mapping on the D40 spine, testing bars, open questions for adversarial review
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.
What
Turns today's security-architecture discussion into plan-level commitments: plugins are the extension mechanism for everything deployment-specific, and the first-party plugins ARE the security architecture.
New locked decisions (house format, consistent with D13/D17/D12/D23/D25/D40)
multiplexer-plugin-apiseams; users extend without forkingCredentialProvidertrait; 1Password as first-party flagship, service-account scoped to one automation vault, feeding the session cacheSandboxProvidertrait; container-first per-session isolation; the D25 independent-enforcement rule is implemented HEREHarnessAdaptertrait; claude-code/codex/opencode/zcode admitted as plugins over generic ACP; the process boundary is a security feature, not a limitationApprovalPolicyplugin chain over the D12 4-way enum; the approval gate is a security boundary, policy plugins held to core testing barsNew plan doc
plan/21-plugin-architecture.md— trait sketches (CredentialProvider, SandboxProvider, HarnessAdapter, ApprovalPolicy), manifest + capability model, out-of-process plugin host (v1), threat-model mapping covering both exposures (credential readability and abuse-in-session use), milestone mapping on the D40 dependency spine (plugin API in Phase 1; sandbox + remote enforcement pull-forward parallel-safe), testing bars (no mock-only security tests), and open questions framed for adversarial review.Why
The server-centric runtime makes
multiplexer-serverthe trust boundary — but only if the server core stays minimal and the per-deployment variables (which vault, which sandbox, which harnesses, which approval strictness) live behind capability-scoped seams. This also keeps D23 honest: no live user-sessionopreads, ever; the vault bridge is the plugin's own narrowly-scoped auth.Review notes