docs(compliance): bundle stance declarations #220 + #225 + #226#240
Merged
Conversation
Plan for the three compliance-posture stance declarations: - #220 / MCP-01: MCP host UX dependency (OWASP LLM-07) - #225 / NIST-RMF-01 + AI-ACT-02: prohibited-uses declaration - #226 / SOC2-02: availability stance (operator-run-only) All three bundle naturally because they share docs/policies/ + a single README cross-reference section. Pure-doc surface fully disjoint from in-flight code PRs (#237, #238, #239) — safe as a parallel PR. Audit: round 1 PASS (L1, doc-only). Doctrine interpretation locked: for markdown policy artifacts, the unit IS the document content; read_text() + assert "<commitment>" in content is genuine unit invocation per qor/references/doctrine-test-functionality.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… tests (#220 #225 #226) Three new policy documents declaring bicameral-mcp's compliance posture: - docs/policies/host-trust-model.md (closes #220 / MCP-01) — declares what's enforced server-side vs. what depends on host UX (tool-call visibility, denial path, stdio surfacing, mid-call intervention, destructive-action confirmation surface). Per-host operator checklist for Claude Code / Cursor / Codex / generic-host. Cross-reference to the #217 epic that adds an out-of-band confirmation primitive. - docs/policies/acceptable-use.md (closes #225 / NIST-RMF-01 + AI-ACT-02) — declares intended purpose (limited-risk decision-support for software engineering) and four prohibited-use categories: HR/legal/ medical/financial substitution, regulated-data ingestion (PHI/PAN/etc), multi-tenant deployment without auth shim, automated decisions without HITL. Cross-framework mapping table. - docs/sla.md (closes #226 / SOC2-02) — declares operator-run-only as the active commitment (no uptime/MTTR/support targets). Activation requirements section locks the future-hosted-tier upgrade path so a hosted offering cannot ship without the SLA section being filled in. README.md gets a "Compliance posture" section linking all three policy docs + the research brief. docs/research-brief-compliance-audit-2026-05-06.md gets gap-status pointers marking MCP-01, NIST-RMF-01, AI-ACT-02, SOC2-02 as closed by their respective policy docs (bidirectional cross-reference). 5 functional content-contract tests verify each load-bearing section and cross-link is present; per the test-functionality doctrine, these are genuine unit invocation against doc content (the unit IS the doc). 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 |
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
Three compliance-posture stance declarations bundled. Closes:
Plan / Audit
plan-D-compliance-stance-docs-220-225-226.mdWhat ships
docs/policies/host-trust-model.mddocs/policies/acceptable-use.mddocs/sla.mdREADME.mddocs/research-brief-compliance-audit-2026-05-06.mdtests/test_compliance_policy_docs.pyTest plan
ruff check+ruff format --checkclean (no Python file changes)Doctrine interpretation locked
For markdown policy artifacts, the test-functionality acceptance question resolves: the unit IS the document content;
read_text() + assert "<commitment>" in contentis genuine unit invocation perqor/references/doctrine-test-functionality.md. The doctrine's<substring> in <file_text>flag applies only when the substring is a proxy for testing a SEPARATE unit; here the doc IS the unit, so the file-read is genuine invocation.Disjoint from in-flight PRs
This PR's surface (
docs/policies/,docs/sla.md, README addition, research brief edits, new test file) is fully disjoint from #237 (cosign + SBOM), #238 (ingest middleware bundle), and #239 (preflight regex) — no merge conflict risk.🤖 Generated with Claude Code