Loading DraftADynasty…
Loading DraftADynasty…
Model card
What the draft-room recommendation score is, what goes into it, and what it does not claim. This card describes mechanics only; it makes no accuracy claim.
draft-model-card/v0 · draft-intelligence/v6-phase-aware-utility · updated 2026-09-24
The draft intelligence engine recomputes one roster-building answer after every recorded pick: the best candidate for your roster right now, two credible fallback plans, and what each plan costs if you wait. It exists to help you build the strongest whole roster across an entire draft, not to name the highest static rank.
One engine serves every draft surface. Sleeper, ESPN, and Fleaflicker public drafts normalize into the same board state, and manual recovery produces the same decisions when a live feed is unavailable. The war room, draft assistant, and manual assistant all render output from this model version.
Every input is visible with the recommendation that used it. The engine starts from the current board: which picks are recorded, which players remain, your roster, and your league's exact scoring and lineup rules.
The engine runs a seeded, deterministic simulation of the picks between now and your next turn. The overall score blends the five inputs on fixed weights: current value 36%, roster fit 23%, availability urgency 18%, positional scarcity 13%, and modeled opponent demand 10%. Because the simulation is seeded, the same board revision always produces the same answer, which is what makes the output reproducible and contract-testable.
While you are waiting, the model discounts candidates unlikely to survive and promotes realistic next-turn targets. While you are on the clock, it compares taking a player now with the modeled cost of waiting one more pick.
Every recommendation card carries its model version, board revision, seed, simulation count, and confidence grade. Plans name a verdict, a fallback, and the expected drop if you wait. Every number links back to the input list above, and a drafted player is never recommended again.
The opponent model treats the rest of the room as aggregate market behavior: it assumes seats draft near current market order, leaning toward need where the board pressures them. It assumes recorded values are fresh, your league settings are correct, and the recorded board is complete. When a value feed is stale or unavailable, the affected surfaces fail visibly rather than substitute a fabricated number.
Trades, sleepers, and reaches happen. The opponent forecast describes what the market is likely to do, not what any specific manager will do. Values move with injury and news faster than any cache refresh. A high score is a roster-building argument, not an outcome promise: injuries, coaching, and luck dominate single-season results.
Compare with the site methodology and the track-record policy.