[QST] Is bounded load imbalance within MoonEP’s design scope?

Hi MoonEP team, thanks for open-sourcing this work.

MoonEP currently provides exact load balance, where every rank receives
exactly S * K token assignments.

As discussed in #6, the trade-off between eliminating compute imbalance and
introducing expert-weight prefetch overhead may depend on workload shape,
especially token load and expert size.

Before investing further in this direction, I would like to understand the
intended design scope of MoonEP:

1. Is exact S * K balance considered a fundamental MoonEP contract, or is it
   mainly the policy implemented by the current planner?
2. Would an optional planner policy that allows a small, bounded amount of
   residual imbalance be considered in scope, if it reduces weight-prefetch
   and backward gradient-reduction traffic?
3. Are there any public plans, experimental branches, or ongoing efforts in
   this area that external contributors should coordinate with?

Thanks!

Start by reading the discussion in issue #6 and the current planner behavior described here, focusing on whether exact S * K balance is a contract or a policy. Confirm whether bounded residual imbalance and reduced prefetch or gradient-reduction traffic fit the project scope, and coordinate with any public plans or experimental work before proposing implementation.