Contributions should improve factual reliability, decision usefulness, verified compatibility, or maintainability without widening the runtime contract implicitly.
- Read the product contract and architecture.
- Set up the locked environment and gates in Development.
- For runtime behavior, follow Changing Skills.
- For user, concept, governance, or maintainer content, follow Documentation.
- For model-backed work, understand the Evaluation CLI, adapter protocol, quality policy, and benchmark policy.
Keep each change scoped and preserve unrelated work in a dirty worktree. Pair behavior changes with a failing canonical case and a rejecting near-neighbor where routing can widen. Use deterministic checks for facts that can be checked deterministically; an LLM judge cannot override a blocker.
Update CHANGELOG.md for user-visible behavior, packaging, compatibility, or safety changes.
Update MIGRATION.md when existing users or integrations must act. Run the
full deterministic gate before requesting review and
report exactly which checks ran.
Required review and protected checks remain authoritative. Missing model credentials cannot be replaced with fabricated or hand-authored evidence.
Report exploitable behavior, credential exposure, unsafe state changes, or private prompt leakage through SECURITY.md, not a public issue. Only maintainers operating the protected release runbook may create release, marketplace, support, or Production claims.