ai-collaboration-governance

What problem does it solve?

Prevents unbounded or fragile Claude MCP collaborations by enforcing deterministic timeouts, request size controls, healthchecks, and explicit fallback flows so implementations and reviews do not hang or produce inconsistent results.

Core Features & Use Cases

• Request Classification: Classifies requests as heavy or light based on prompt length, item count, file count, and MCP references.
• Healthchecks & Timeouts: Runs responsiveness checks and enforces a 5-minute per-call timeout with cooldown and fallback logic for repeated failures.
• Fallback & Handoff Flows: Defines split-flow handoffs, two-session fallback behavior, and structured inputs/outputs for investigation, implementation, and review stages.
• Delegated Logging & Policy Resolution: Delegates review output schema and logging format to a separate cross-review protocol while mandating CLAUDE as the policy source for review profiles.
• Use Case: Apply these rules when orchestrating Claude-based cross-reviews for code changes or document audits to ensure resilience and auditable handoffs.

Quick Start

Apply the governance rules to classify a Claude MCP request, run healthchecks for heavy requests, enforce request size limits, and follow the timeout fallback flow if needed.