MegaMek carries Campaign Operations' 41 formation blueprints in `FormationType`, so helm reads them off the shelf the way it reads the unit library. `helm_force::Blueprint` holds one and `evaluate` says whether a force is one, with the assembly rules in upstream's own order - the shortcut for a force whose every unit already has the ideal role, the weight bounds, and the requirements that are alternatives rather than additions. The requirements themselves do not cross the bridge: each is a Java lambda with a display label beside it, and only the label survives. `Rule::parse` reads the label back into a predicate and MegaMek's own answers are the oracle - 42,453 per-unit checks over 477 Meks and 184 whole-force verdicts, with no disagreement on anything helm claims to answer. A label it cannot read never matches and reports itself, so an upstream rewording costs an answer rather than producing a wrong one. Two labels do not describe their requirement and one blueprint cannot be answered at all; all three are written up in `crates/helm-force/UPSTREAM.md`.