Team Governance

Two-layer scope hierarchy with conflict detection and amendment workflows. Enforce team standards while allowing individual developers flexibility.

The two scopes

Scope	Who owns it	Override rules
Team	The whole engineering team	Cannot be overridden by individual decisions without an approved amendment
Individual	A single developer	Can extend team decisions; cannot contradict them

Conflict detection

You: "I want to use MongoDB for the analytics module"

AI:  ⚠️ Governance Conflict Detected

     Your proposal conflicts with Team Decision #23:
     "Standardize on PostgreSQL for all data storage"
     Scope: Core Architecture (Team-level)

     This is a hard block. Would you like to propose an amendment?

Amendment workflow

You: "Propose an amendment to allow InfluxDB for time-series metrics"

AI:  Amendment proposal created:
     Amendment #2 to Decision #5
     Proposal: Allow InfluxDB for time-series metrics data
     Rationale: PostgreSQL isn't optimized for high-volume time-series
     Status: Pending team review

Individual strategies

You: "When I say I'm ready to create a PR, compare my branch with main
      and generate a succinct summary for the PR description. Then run
      autoflake and npm run lint -- --fix."

AI:  Individual strategy #4 created:
     Code summarization, import cleanup, and JS linting on PR creation.

Effective context

get_effective_context merges team and individual decisions, applying the correct precedence rules. Your AI always sees the right combined view.

MCP tools

• create_scope / get_scopes
• log_governance_rule / get_governance_rules
• check_compliance
• get_scope_amendments / review_amendment
• get_effective_context