patch-cadence ยท diff
git:20260912.5f6e976 to git:20260913.a964369
23 added, 13 removed. Audit A to A.
---
name: patch-cadence
- description: How often rules may change. Ask frozen-slice vs weekly-live vs season-flip. A patch that shrinks input windows is a feel change, not a silent live-ops tweak.
+ description: Use when client builds, content/config revisions, balance changes, staged rollouts, schema migrations, or rollback plans need an explicit compatibility and change-management contract.
---
# Patch cadence
- Ask the column:
+ Cadence is project policy, not a fixed statement about which content is allowed to change weekly or seasonally.
- | Column | What may move |
- |---|---|
- | frozen-slice | content only, clock stays |
- | weekly-live | offers, cosmetics, sinks |
- | season-flip | track + published rule card |
+ ## Change record
+ For each release/config change publish:
+
+ ```text
+ release/config revision
+ minimum client / supported client range
+ schema or data-version changes
+ behavior/content changes + owner
+ rollout policy / cohort if staged
+ rollback target + rollback trigger
+ save/economy compatibility notes
+ telemetry comparison window
+ ```
+
## Rules
- 1. Combat columns (hitstop, cancel, boxes) need a patch note. Silent nerfs fail accept.
- 2. Prices and passes end on the published date. See live-ops and season-track.
- 3. Save-integrity: a patch may not rewrite slot 0 flags to fake a clear.
- 4. Telemetry windows reset or they stay comparable. Pick one and write it.
- 5. Clients that cannot read the new grant table must fail closed, not grant all.
+ 1. User-visible rule changes are attributable to a version/revision; do not silently mutate core behavior behind an old build label.
+ 2. **Minimum client** and data/config **schema** compatibility are checked before activation.
+ 3. A staged **rollout** has a stable cohort rule and an observed health gate; 100% is not assumed from one healthy sample.
+ 4. A **rollback** names the last compatible revision and how newer persistent data is handled. Rollback must not corrupt saves or duplicate economy/entitlement transactions.
+ 5. Persistent progression follows `save-integrity`; do not hardcode any particular numbered slot.
+ 6. Live event activation stays in `live-ops`; this skill owns cross-version rollout/compatibility policy.
## Accept
- Player can name what changed this week vs what the verbs still are.
+ Given any active client/build and config revision, a reviewer can determine compatibility, rollout state, data/schema expectations, rollback target, evidence window and unresolved migration risk.