Contributing To Origo

Purpose

This page explains how to contribute safely to Origo without relying on tribal knowledge.

Read the relevant task type and shared-domain contracts through origo.governance.contract_loader.read_contracts.
Confirm the canonical docs and runtime/reference pages that govern the touched surface.
Check git status --short before editing and avoid reverting unrelated work.
Make the smallest coherent slice that closes the user-visible or maintainer-visible gap.
Update docs when the touched surface changes.
Run the most relevant local validation before handing work off for review.

Match the requested outcome to the correct primary task type.
Preserve machine governance authority in AGENTS.md and contracts/governance/*.json.
Update docs/Developer before docs when the change affects documentation.
Prefer real proofs, real workflows, and real examples.
Keep historical slice records as provenance, not as the primary explanation.

Do not ship prose that conflicts with machine governance authority.
Do not silently reuse slice-history material as if it were current runtime truth.
Do not introduce a new package README that lacks outward routes to canonical docs.