mechanic-ablation
mechanic-ablation
Fires when asked whether a mechanic matters, when a change produces no measurable effect on the board, or as a routine pass before a milestone.
Requires a headless sim of the real loop, seeded determinism, and a policy/bot set. All four surveyed projects already have these.
Sources: Ablation as a method is borrowed from experimental science and from machine learning, where removing a component to measure its contribution is standard. Its application to game mechanics here is this plugin's own framing, developed against working simulations. Every threshold is posture B under the Numbers Policy in game-design.
Why
Ablation found a dead mechanic in all four projects: flasks (removing the entire system changed 1 seed in 24), the lantern (lanternWard: 1 silently zeroed a whole upgrade line), tribe.goal (displayed to the player as intelligence, read by nothing that decides movement), radar countermeasures (present in no shipped archetype). Highest-yield technique available, ad-hoc in every project.
It is also the technique most likely to produce a confident wrong answer, because "no change" has four causes and only one of them is "the mechanic is inert." One project nearly misread it three times in a single session.