Houston Rockets
2022-23When several roster decisions share a planning window, where do basketball, roster, reported salary, cap, trade, exception and draft constraints overlap?
HOU has 1 multi-player planning windows and 4 fully enumerated conditional branch combinations. Overlap counts identify review pressure, not preferred outcomes.
Alperen Sengun + Josh Christopher
A planning window — decisions sharing a staff planning date, never a claimed simultaneous deadline.HOU has 2 actionable player decisions sharing the 2023-08-06 planning anchor. All 4 bounded branch combinations are enumerated for stress testing, but the anchor is not claimed as an exact simultaneous contract deadline.
Compare
Two combinations side by side — differences, not a verdict.| A — keeps 0, exits 2 | B — keeps 0, exits 2 | |
|---|---|---|
| Branches | No extension recorded ×2 | No extension recorded ×2 |
| Basketball | 2 supported dependence case(s) | 2 supported dependence case(s) |
| Roster spots | 0 stay occupied · 2 unchanged | 0 stay occupied · 2 unchanged |
| Reported salary | 2 with unknown salary effect | 2 with unknown salary effect |
| Current cap context | Cap position observed; no apron trigger | Cap position observed; no apron trigger |
| Trade / execution | Simultaneous execution not claimed | Simultaneous execution not claimed |
| Exception reference | 0 visible · 2 withheld | 0 visible · 2 withheld |
| Draft capital | 2 visible · 0 withheld | 2 visible · 0 withheld |
Neither combination is a recommendation. Clear comparison
Scenario explorer
Every enumerated combination, grouped by what it does to the roster. None is recommended.Retain or continue all1 combination
HOU scenario 0 keeps or continues 2 decisions and exits or defers 0. It exposes overlapping planning work, not a recommended or legally executable roster plan.
Extension agreed ×2
Constraint lanes and evidence gaps
- Exact decision timing unresolved
- Salary consequence incomplete
- Current exception wallet unavailable
- Combined cba legality unresolved
- Scenario probability not estimated
- Basketball outcome not evaluated
Mixed keep-and-exit combination2 combinations
HOU scenario 1 keeps or continues 1 decisions and exits or defers 1. It exposes overlapping planning work, not a recommended or legally executable roster plan.
Extension agreed ×1 · No extension recorded ×1
Constraint lanes and evidence gaps
- Exact decision timing unresolved
- Salary consequence incomplete
- Current exception wallet unavailable
- Combined cba legality unresolved
- Scenario probability not estimated
- Basketball outcome not evaluated
HOU scenario 2 keeps or continues 1 decisions and exits or defers 1. It exposes overlapping planning work, not a recommended or legally executable roster plan.
Extension agreed ×1 · No extension recorded ×1
Constraint lanes and evidence gaps
- Exact decision timing unresolved
- Salary consequence incomplete
- Current exception wallet unavailable
- Combined cba legality unresolved
- Scenario probability not estimated
- Basketball outcome not evaluated
Exit or defer everything1 combination
HOU scenario 3 keeps or continues 0 decisions and exits or defers 2. It exposes overlapping planning work, not a recommended or legally executable roster plan.
No extension recorded ×2
Constraint lanes and evidence gaps
- Exact decision timing unresolved
- Salary consequence incomplete
- Current exception wallet unavailable
- Combined cba legality unresolved
- Scenario probability not estimated
- Basketball outcome not evaluated
What the scenarios cannot prove
Where the constraint lanes refuse a conclusion across these scenarios.Shared planning anchors are staff workflow dates, not automatically exact simultaneous contract deadlines.
All bounded branch combinations are enumerated; none is assigned a probability or recommendation.
Player-specific possessions and ratings are not summed across players.
Only directly reported option salary is added across decisions.
Every scenario needs a new dated cap, roster, trade and CBA execution test.
Prior exception receipts are reference evidence, not the scenario wallet.
Scenario branches do not alter pick ownership or prove tradability.
Team-season counts summarize conditional branch-space coverage. They are not probabilities, rankings, cap projections, legal opinions or front-office grades.