docs(security): #215 Track 1 — declare MCP-transport trust boundary (SOC2-01)#324
Merged
Merged
Conversation
Closes Track 1 of #215 (SOC 2 audit gap SOC2-01, P0/H). Track 2 (auth shim design) remains open; gated on team-mode evolving into a server-mediated tier per the operator's 2026-05-14 team-server priority directive. New canonical doc: docs/policies/threat-model-and-trust-boundary.md - Load-bearing scope statement: "bicameral-mcp is a local-install developer tool. The trust boundary is the OS user account. Multi-user, hosted, or shared-machine deployments are out of scope; team-mode requires the Track 2 auth shim before such activation." - In/out-of-scope deployment table covering single-laptop, team-mode via Google Drive / local-folder backends, shared dev VM, shared CI runner, hosted multi-team instance, future team-server tier. - Team-mode posture clarified: v0 BackendAdapter (per #279 Phase 2) inherits filesystem-ACL trust from the shared backend but does NOT elevate the MCP-transport trust boundary; only Track 2 does. - Track 2 deferral language is explicit about activation gate (team-mode evolution, not a calendar date). Anchors from existing surfaces (cross-refs only, no duplication): - SECURITY.md gains a "Threat model and trust boundary" section with the load-bearing sentence + link. - docs/policies/acceptable-use.md § 3 (multi-tenant deployment) links to the canonical doc. - docs/policies/host-trust-model.md disambiguates host-side vs transport-side concerns and points at the new doc. Compliance brief follow-up: - docs/research-brief-compliance-audit-2026-05-06.md SOC2-01 row annotated with Track 1 completion + Track 2 status. Per #205 doctrine, governance-gates.yaml is NOT updated in this cycle: there is no deterministic enforcement code to point at until Track 2 ships the auth shim. Adding a gate entry now would invert the doctrine. Plan: plan-215-trust-boundary-track1.md (qor-judge PASS at L1) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Merged
3 tasks
9 tasks
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.
Summary
Closes Track 1 of BicameralAI/bicameral-daemon#9 (SOC 2 audit gap SOC2-01, P0/H). Track 2 (auth shim design) remains open; gated on team-mode evolving into a server-mediated tier per the operator's 2026-05-14 team-server priority directive.
This PR ships docs only — the compliance posture statement that closes the perception gap an SOC 2 reviewer flags immediately. The substantive gap (no auth on shared-deployment MCP transports) is closed by Track 2's auth shim, which depends on team-mode evolving past the v0 pull-based BackendAdapter posture.
What's in the canonical doc
`docs/policies/threat-model-and-trust-boundary.md` (new, ~140 lines) contains:
Anchors (cross-refs only — no duplication)
Compliance evidence
BicameralAI/bicameral-daemon#34 doctrine
`governance-gates.yaml` is intentionally not updated in this cycle. There is no deterministic enforcement code to point at until Track 2 ships the auth shim. Adding a no-enforcement gate entry would invert the doctrine. Track 2's plan will be the cycle that adds the gate entry.
Test plan
Plan + audit
🤖 Generated with Claude Code