Summary
Move contract changes off the governance ticket queue and onto
GitHub-style PR review. Stewards review diffs, not tickets.
Proposal
- Every contract change is a PR against the contract repo.
- The platform posts a preview: schema diff, SLA diff, policy diff,
downstream consumers affected.
- A steward on the owning domain approves; an optional second
reviewer approves for cross-domain changes.
- Merge runs the promotion pipeline.
Open questions
- Auto-approve scope. Which changes are safe to auto-approve
(additive columns, SLA loosening) and which always need a human?
- Downstream block. Should a downstream consumer be able to
block a contract change, or only flag concerns?
- Emergency path. When a Restricted field is accidentally
exposed, the platform needs a rollback path that does not wait on
a PR review.
Why discussion, not committed
We have not agreed on auto-approve scope yet. Parked here for the
governance working group to resolve before April end.