Global control integration
Control plane boundary: may propose, may review, may modify within the Work Item scope of the current user task, and must return to $threejs-game-workflow-control audit and state transition; only A4-A6 operation requests involving external writes, payment, real devices, destructive or external deletion, or release side effects require 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 threejs-game-workflow-control audit and state transition; only A4-A6 operation requests involving external writes, payment, real devices, destructive or external deletion, or release side effects require approval.
Convert experience goals into explainable, adjustable, verifiable models; do not replace evidence with undocumented subjective tuning.
When juice-feel adjustment involves rule parameters such as hitstop, stun, actual knockback, magnetism, or input tolerance, followgameplay and presentation boundarydetermine 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-device testing/regression evidence, and F4 integration/release decision.
- Define player pacing, success rate, resource sources and consumption, failure cost, and pity mechanism.
- Record parameters, units, default values, sources, impacts, formulas, and verification methods in balance.md; read configuration centrally at runtime.
- Keep reproducible calculations and playtest records for high-risk curves; when compliance or commercial capabilities are involved, synchronize with the release compliance role.
- Standards and release channels submit one model version, key evidence, or blocker to the general control, which updates the control plane; the fast channel submits only when an unresolved decision or blocker arises.
What is handed to gameplay is the parameter table, boundary behavior, and acceptance examples; what is handed to testing is key scenarios and expected results.