Governance Principles
- Core semantics are stable and intentionally conservative.
- Behavior changes require explicit proposal and compatibility review.
- Conformance evidence is required for impactful changes.
- Release notes must describe migration impact and version policy implications.
Decision Flow
- Open an issue with reproducible problem statement and scope.
- Propose a change with compatibility impact analysis.
- Attach fixture updates proving expected behavior.
- Review in governance queue and record decision publicly.
- Ship in release channel with migration notes where required.
Roles
| Role | Responsibility |
|---|---|
| Maintainers | Steward releases, compatibility policy, and core semantics. |
| Implementers | Adopt artifacts, report integration gaps, and submit fixture evidence. |
| Contributors | Propose changes, improve docs, and participate in review. |
Release Cadence and Deprecation
- Minor versions for additive, backward-compatible enhancements.
- Major versions for breaking semantic or schema changes.
- Deprecations require migration guidance and clearly published timelines.
- Implementers should pin versions and plan upgrades through published release manifests.
Accountability Artifacts
- Release manifest:
releases/manifest.json - Standards package:
tensor-core-v1.0.0.json - Compatibility policy:
compatibility-policy.md - Repository: tensor-framework on GitHub
Governance next: Contribute workflow · Conformance expectations · Standards policy