War-game a knowledge base rewrite by testing whether article capacity, review gates, and freeze deadlines still shrink soft renames when several support surfaces share one corpus and the next deflection goal is close.
Knowledge base rewrites fail when "approved" means a checkbox without a decision artifact, when teams dual-count a draft as both reviewed and live, and when money-adjacent article paths still pin to one thin glossary because the map is incomplete. The review needs one written inventory of article classes, one owner who can deny a risky rename, and a documented consequence when a failed review ages past the deadline.
Assemble the rewrite packet
List article classes by surface, weekly rewrite volume, review gate, last freeze-skip reason, owner of record, and evidence required to keep the rule. Attach open findings, overdue drafts, and any emergency rewrite waiver in the last quarter. Name which classes are out of scope and why. If a billing-adjacent article class is omitted, show the residual risk in the same packet.
Decide allow, revise, or hold in advance. Include the fields that compute overdue-review status so two reviewers reach the same label from the same exports.
Claim matrix
| Claim | Evidence required | Fail condition |
|---|---|---|
| Class is staffed | Named reviewer roster and measured time-to-freeze check | Roster is empty or still points to a single untested operator |
| Definition is complete | Corpus export showing approved state for the claimed fields | Ticket closed while export still shows open |
| Priority is unique | Sample articles proving no double-booked topic | Priority invents uniqueness the glossary never enforced |
| Override is controlled | Logged use with time-bound restore of review | Shared override or unlogged use |
Walk four cases in Pingpong: a surface still pinned to one overloaded glossary, a rewrite that left a partner help center live without support review, a class that mixed batch and interactive articles, and a request to skip a billing article because volume is rare. Start from the documented rewrite language. Ask who can extend a freeze window and which export proves review. Any step that depends on an unnamed person becomes a freeze condition.
Replay one prior rewrite incident under the proposed rules. If the incident would still age without a reverse owner, revise the rules before calling the rewrite ready.
Pair with the support ops lead seat, a knowledge base cutover review, and a ticket deflection goal review. More operating decisions live in the war-game decisions hub.
Close only when approved and blocked labels can be reproduced from stored exports without a verbal override.