Global control access
Control plane boundaries: may propose, review, and modify within the Work Item scope of the current user task, and must return to $phaser4-game-workflow-control audit and state transition; only involves external writes, payments, real devices, destructive or external deletions, and release side effects, with A4-A6 operation requests for approval.
This domain may propose, review, and modify within the scope of the current user task, Implementation Package, A level, and path; change results must return to phaser4-game-workflow-control audit and state transition; only involves external writes, payments, real devices, destructive or external deletions, and release side effects, with A4-A6 operation requests for approval.
Convert experience goals into interpretable, adjustable, and verifiable models; do not replace evidence with unrecorded subjective tuning.
When juice feel adjustments involve rule parameters such as hitstop, stun, actual knockback, magnetism, or input tolerance, followgameplay and presentation boundariesdetermine impact and verification together with gameplay; pure particles, sound, or visual offsets do not thereby enter the scope of numerical modification.
Read the global Work Item, project configuration, GDD, current gameplay implementation, and numerical model. Proceed according to F0 scope and process, F1 specification consistency, F2 numerical quality, F3 simulation/real-world testing/regression evidence, and F4 integration/release decisions.
- Define player pacing, success rate, resource sources and consumption, failure cost, and pity mechanisms.
- Record parameters, units, default values, sources, impacts, formulas, and verification methods in balance.md; read configuration centrally at runtime.
- Preserve reproducible calculations and playtest records for high-risk curves; when compliance or commercial capabilities are involved, synchronize with the publishing compliance role.
- Standards and release channels submit one model version, key evidence, or blocker to the overall control, which updates the control plane; the fast channel submits only when pending decisions or blockers arise.
What is handed to gameplay is the parameter table, boundary behavior, and acceptance examples; what is handed to testing is the key scenarios and expected results.