The delta is universal. The rule that binds is not.
The value of a roster move, the Team KR delta, is computed the same way everywhere, because the engine does not change when the league does. What changes is the constraint wrapped around it. The NBA binds you with a hard cap and aprons. The EuroLeague has no league cap at all, so the owner's budget is the ceiling. In China the money is abundant and the limit is a quota, two imports, one on the floor. The delta tells you the value of a move. The rulebook tells you whether it is even legal, and which rulebook depends on where the team plays.
One engine values the move, in any league.
Before any rulebook enters, the question is the same one College Roster and Trades ask: what does this move do to the team. The engine re-runs Team KR with the move made and reads the change. That number does not care what league it is in, a plus-three is a plus-three in Los Angeles, Barcelona, or Shanghai. Composite move.
This is the constant. Whatever the money rules, the on-court value of a player to a specific roster is one universal number, so a front office in any league is speaking the same currency. The delta is the part that travels. Everything else is local law.
Illustrative engine read on the real universal Team KR delta (the same computation across leagues). Composite move, demonstration figures.
Same move. Three leagues. Three completely different questions.
Once the delta is known, the league decides whether you can act on it, and the leagues could not be more different. The engine wraps the correct rulebook around the same plus-three move, and what was one clean decision becomes three unrelated ones.
The player is worth the same plus-three in all three, and the decision is unrecognizable across them: a cap-and-apron puzzle, a conversation with the owner's wallet, a two-slot quota bet. The engine does not force one league's logic onto another, it swaps the rulebook and keeps the delta. The value is global. The constraint is local, and it changes everything downstream of the number.
Illustrative engine read on the real per-league constraint structure (NBA cap and apron, EuroLeague owner budget, China import quota). Generic leagues, demonstration figures.
Value in, correct constraint around it, and the pieces that feed the ceiling.
A real build is the universal delta wrapped in the league's actual law, plus the two things that set the ceiling and fill the bench. The engine assembles all of it under one rulebook at a time. Here is a composite EuroLeague build.
In a hard-cap league the ceiling row would be the apron instead of the owner, and the money market would run through matching salaries instead of a fee. Same four pieces, different law in the middle. The engine builds the roster in whatever rulebook the team actually plays under, never a borrowed one. Universal value, local constraint, assembled correctly.
Illustrative engine read on the real wrapped-build structure (universal delta, league ceiling, cross-league money market, the operator). Composite build, generic league, demonstration figures.
Most tools are built for one league and quietly assume the whole world plays by its rules. The engine does the opposite. It computes the value of a move as one universal number, because a player's worth to a roster does not change when he crosses a border, and then it wraps that number in the actual law of the league the team plays in: a hard cap and aprons here, an owner's open checkbook there, a two-import quota somewhere else. The value is the constant and the constraint is the variable, and confusing the two is how you build a roster that is brilliant on paper and illegal in practice.
Value the move once. Bind it by the right rulebook.
Pro Roster computes the universal delta and wraps each league's actual constraint around it.