13 lines
992 B
Markdown
13 lines
992 B
Markdown
### Standards
|
|
1. Same git ref + source + toolchain + build inputs must yield identical artifact bytes and metadata.
|
|
2. Use one canonical `dist/` layout and semantic naming convention that never changes once released.
|
|
3. Keep a machine-readable distribution contract (format, compatibility matrix, assumptions, checksum policy, deprecation policy) as a first-class interface.
|
|
4. Always emit reproducibility metadata in every release artifact: version, target, profile, build time inputs, git rev, and content checksums.
|
|
5. Centralize release behavior in one versioned orchestration script/config; avoid scattered shell snippets and hidden paths.
|
|
6. Gate releases through CI checks (tests, lint/build, artifact determinism, manifest validity, docs sync) before publishing.
|
|
7. Treat compatibility, retention, and migration steps as part of the contract to reduce future operational risk.
|
|
|
|
## Quality Gate Annotations
|
|
|
|
- Iteration-aware review note: confirm long-term ownership and cleanup path.
|