Skip to main content

Governance Reading Guide

Purpose​

  • This page explains how contributors should read Origo governance without turning prose into a competing authority source.

Required reading​

  • AGENTS.md
  • contracts/governance/governance-authority.json
  • contracts/governance/contract-applicability.json
  • docs/Developer/README.md

Process​

  1. Classify the requested outcome by primary task type.
  2. Load contracts programmatically with origo.governance.contract_loader.read_contracts(task_type=...).
  3. Read universal contracts first, then task-admission contracts, then task-specific contracts, then shared-domain overlays.
  4. Only after that should you use prose docs to orient yourself around implementation or operator-facing context.

Checklist​

  • Requested outcome matches the routed primary task type.
  • Shared-domain contracts are loaded for the touched surface.
  • Governance prose is treated as explanation only.
  • Runtime docs are updated only after governance authority is correct.

Failure cases and review notes​

  • Do not infer task type from implementation instinct alone.
  • Do not use raw grep over governance surfaces as a substitute for structured contract reading.
  • Do not let developer docs restate governance as if they were authoritative.
  • docs/Developer/Contributing.md
  • docs/Developer/Proof-And-Evidence-Workflow.md
  • docs/Developer/Documentation-System.md