Governance

Governor

Vision, goals, guardrails, and ADRs. The contracts all execution must honor.

pip install governor-md

View on GitHub 356 downloads/mo v0.4.1 May 14, 2026

What it does

Governor is the static St. Peter of your project. It records what the project has committed to — the vision, the goals, the guardrails — and enforces those contracts across every agent session. If a task would violate a guardrail, St. Peter has already said no.

What enforcement looks like

Every project has contracts: vision, guardrails, ADRs. They usually live in a wiki nobody reads and drift silently. Governor makes them readable by agents — and asks them the question before the work starts. If the task violates a guardrail, St. Peter has already said no. The agent doesn't get to decide otherwise.

1. Agent proposes a fast fix — Governor cites the contract

agent · migration

  # agent drafts a migration: DROP users.legacy_email, backfill NULL › visionlog_boot project_id=checkout-svc vision "trusted checkout — no data loss under any refactor" guardrails 3 active · GR-01 soft deletes only adrs ADR-014 column removal requires 2-phase migration  › guardrail_inject action="drop_column users.legacy_email" BLOCK violates GR-01 + ADR-014  why: we got burned in the 2025-Q4 incident — hard deletes  broke CSAT replay. Soft-delete, then drop in a later ADR.   

2. After reframing to honor the contract — proceeds cleanly

agent · migration (reframed)

  # agent rewrites: add deleted_at, backfill timestamps, keep the column › guardrail_inject action="add users.deleted_at; soft-delete legacy rows" vision ✓ no data loss guardrails ✓ GR-01 soft deletes only adrs ✓ ADR-014 two-phase respected (phase 1 of 2) ALLOW proceed — queue ADR-015 for eventual column drop  agent: writing migration + scheduling phase 2 review.   

Vision doesn't drift. Guardrails stay active until explicitly deprecated. ADRs are immutable once accepted — new ADRs supersede rather than overwrite. Every agent session starts with visionlog_boot and honors whatever it reads there.

Key features

Vision documents — set the north star once, reference it everywhere
Goals with DAG — goals depend on and unlock other goals
Guardrails — constraints the system must never violate, with rule/why/violation examples
ADRs — architectural decision records that persist across sessions
SOPs — standard operating procedures agents follow consistently
MCP server — agents read and write governance through tool calls

Install

pip install governor-md

Quick start

# As MCP tool calls from an agent:
project_set  path: "/path/to/project"    # returns project_id
visionlog_boot  project_id: "..."        # active guardrails + goal state
visionlog_guide  project_id: "..."       # vision + decisions + goal map

# Create governance artifacts:
vision_set       title: "..." body: "..."
guardrail_create title: "No hard deletes"
goal_create      title: "Launch MVP" status: "available"

Vision remains sticky across sessions — it doesn't drift. Guardrails are active or deprecated, never deleted. ADRs are immutable once accepted — new ADRs supersede rather than overwrite.

The trilogy

Governor is the governance pillar of the Eidos trilogy. The flow is one-way: research.md earns decisions with evidence, Governor records those decisions as contracts, and Docket executes tasks within those contracts.