NFL DFS research
How SLAITIQ Projections and Updates Work
SLAITIQ normalizes projection inputs into a slate-specific player pool and publishes a reviewed snapshot. The current multi-input workflow uses the median of available player projections. Raw input files and provider comparisons remain private; customers see the published SLAITIQ output.
By SLAITIQ · Updated · Meet founder Chuck Morrison
From inputs to a published slate
Incoming player names, teams, positions and salary fields are normalized before comparison. The current multi-input import computes the median of available projections for a player, and the median of available ownership estimates. Missing input coverage and conflicting records require review; a combined estimate is not evidence that all inputs agree.
An authenticated administrator ingests and reviews a draft before publishing it. Draft uploads do not automatically replace the public slate. Publishing makes a snapshot current while preserving prior snapshots in the database. Routine projection updates are data ingestion rather than application deployments.
What our timestamps mean
The projection timestamp is SLAITIQ's own ingestion/update time associated with the published snapshot. It is not a claim about when every underlying provider last changed its model. Schedule freshness and ownership freshness are tracked separately.
An ownership-only update preserves the projection timestamp. A schedule refresh also cannot refresh old projections. The application blocks optimization when required data is stale or the slate is locked.
What is and is not established
Deterministic optimizer tests validate the lineup algorithm against defined inputs and constraints. They do not measure the accuracy of those inputs or prove that the lineups are profitable.
The public Accuracy Lab is still building its record. SLAITIQ does not yet publish a completed comparative accuracy benchmark. Unavailable confidence, floor, ceiling or simulation statistics must not be interpreted as measured results.
Evidence and corrections
The founder's playing record is described separately and linked to third-party coverage on the founder page. Personal tournament success is not used as a substitute for product accuracy evidence.
Guides distinguish explanations from product capabilities and link back to the desk or methodology where those capabilities can be inspected. Editorial updates should change the page's review date only when its substance is reviewed or changed, not whenever the site deploys.
Common questions
Does SLAITIQ publish private source files?
No. Raw projection files and model comparisons belong to the authenticated admin workflow. Public pages explain the process without exposing those files.
Can a new schedule timestamp make old projections look fresh?
No. Schedule, projection and ownership freshness are separate. A schedule refresh does not reset projection freshness.