Operational Policies Baseline
Short summary of operational policies for release discipline.
Breaking changes policy (v1.*)
Default for minor trains: avoid breaking changes.
If breaking change is unavoidable, the required package is:
- RFC/design note;
- migration notes;
- release notes with impact/steps.
On-disk changes require strict upgrade discipline:
- update
crates/angarabase/src/on_disk.rs; - update
src/operations/upgrade-and-migration.md; - attach upgrade rehearsal evidence.
Breaking budget registry
The breaking surfaces registry must explicitly record:
- status (
no change/changed with notes/planned); - evidence path;
- updates within each train with potential impact.
SLO/SLA methodology
Measurements are based on a reproducible profile and pinned evidence:
- latency;
- throughput;
- saturation/backpressure signals.
Runner baseline:
tools/perf_pack/run.sh
Evidence policy
- Heavy artifacts: locally in
artifacts/.... - Pinned evidence: compact reports in
docs/planning/evidence/.... - RM/release notes link only to pinned evidence.
Triage entry points
src/operations/observability-metrics.mdsrc/operations/troubleshooting.md
Next
- Configuration schema reference — specific keys referenced by policies.
- Security operations baseline — security part of operator policies.
- Testing and validation baseline — how policies are verified in CI.