Tests And Gates

Purpose

• This page tells contributors which local checks and CI gates matter for different kinds of Origo changes.

Required reading

• docs/Developer/Contributing.md
• docs/Developer/Governance-Reading-Guide.md
• contracts/governance/task-start-gate.json
• contracts/governance/task-end-gate.json

Process

1. Identify the touched surface: docs, API, event runtime, control plane, governance, or package orientation.
2. Run the narrowest meaningful local validation first.
3. Run contract tests when governance, authority, or documented runtime semantics change.
4. Check the corresponding GitHub workflows before review.

Checklist

• Governance or authority changes:
  • review tests/contract/*.py
• Performance or throughput claims:
  • review scripts/validate_performance_scope.py
  • review .github/workflows/performance-gate.yml
• Runtime replay and correctness claims:
  • review .github/workflows/replay-gate.yml
  • review .github/workflows/integrity-gate.yml
• Type and style changes:
  • review .github/workflows/type-gate.yml
  • review .github/workflows/style-gate.yml
• Docs changes:
  • run cd docs-site && npm ci && npm run build
  • confirm broken-link enforcement locally or through style-gate

Failure cases and review notes

• A passing static change is not enough if the touched surface requires proof or runtime validation.
• Do not claim documentation completeness if the docs-site build or internal link checks fail.

Related pages

• docs/Developer/Proof-And-Evidence-Workflow.md
• docs/Developer/Local-Environment-And-Stack.md
• docs/Developer/Documentation-System.md