Governance overview
Authoritative governance repo
xrtm.org summarizes governance for contributors and newcomers. The binding schemas, compatibility rules, and review policies live in xrtm-org/governance.
The governance repo is where XRTM keeps cross-repo rules stable while implementation repos evolve.
Quick ownership map
| Topic | Authoritative home | Public summary on this site |
|---|---|---|
| Forecast Object schemas and compatibility | governance/schemas/ | Forecast Object standard |
| Release labeling and feature graduation | governance/policies/feature-status-and-graduation-policy.md | Next release track |
| Release gates and acceptance policy | governance/policies/ | this page plus Contributing |
| Shipped CLI/product behavior | xrtm repo | released workflow pages |
What is authoritative there
- Forecast Object schemas:
schemas/forecast_object_v1.1.jsonandschemas/forecast_object_v1.json - Compatibility rules:
schemas/compatibility-policy.md - Review and acceptance policy:
policies/pr-acceptance-policy.md - Triage and release policy:
policies/triage-matrix.mdandpolicies/release-readiness-policy.md - Cross-repo compatibility policy:
policies/cross-repo-compatibility-policy.md - Feature status and graduation policy:
policies/feature-status-and-graduation-policy.md
Practical change flow
- If you want to change a schema or cross-repo compatibility rule, open it in governance first.
- Once governance accepts the change, update the affected implementation repos such as
xrtm,forecast,eval,data, ortrain. - Update
xrtm.orglast so the newcomer-facing explanation mirrors the accepted source of truth. - When a feature exists in source but is intentionally unreleased, summarize it on the site's Next release track instead of slipping it into release-pinned docs.
- Treat release-pinned docs as published-surface mirrors. If the owning repo has not published or accepted the change yet, this site should not present it as shipped behavior.
What this site should do
- explain why the standards exist
- point contributors at the right owning repo
- summarize accepted governance decisions without becoming the only copy
What this site should not do
- introduce new schema requirements here first
- act as the only location for contributor policy
- imply that package behavior can be changed from this repo alone