Every roster, exactly once
Each league roster must map to one valid two-team matchup with a finite score. Missing rosters, duplicate mappings, malformed groups, missing scores, and byes fail the current rule.
Published finality method
A final recap needs more than a Tuesday headline.
Leagueborn requires complete target-week coverage, an eligible provider context, and two matching source observations before it freezes a weekly recap.
Direct answer: the same complete canonical Sleeper source must be observed twice at distinct times at least 15 minutes apart, after the active scoring week has advanced or the league is complete.Four gates
A week earns publication.
No single label, date, or timer is enough. The current rule joins target-week evidence with provider state and repeated source agreement.
The scoring context has moved on
The active NFL scoring week must be later than the target week, unless the league itself is complete. Sleeper’s display-week value is never used as the finality trigger.
Two matching source reads
Leagueborn hashes the canonical weekly source and requires the same hash at two distinct observation times at least 15 minutes apart. Any source change starts a new observation sequence.
04 / Publication freeze: only a week that passes all gates becomes a published recap edition and eligible final-recap share. A live or candidate edition remains non-final and cannot masquerade as the frozen receipt.
Why the checks combine
Stable does not always mean final.
A Sunday score can remain unchanged for 15 minutes while games are still active. A league can be marked complete while source coverage is malformed. Each gate closes a different failure mode.
The target week stays in control
Leagueborn evaluates the requested scoring week itself. A season-status label does not substitute for its matchups, scores, coverage, and matching observations.
Before the provider advances, old observations are discarded. That prevents an unchanged live score from passing only because a clock ran long enough.
The receipt stays attributable
The published edition binds its final ledger to the verified source fingerprint and rule version. It is treated as immutable after publication.
Sleeper says stat corrections can arrive through Thursday. The current Leagueborn finalizer keeps its published snapshot and does not yet issue an automatic replacement edition after a later correction. Read the receipt as evidence frozen at its stated observation time, not a promise that the upstream source can never change.
Source: Sleeper Support, Stat Corrections.
Questions, answered
What does not count as proof?
Calendar shorthand and plausible narration are not substitutes for the source checks above.
- Does Tuesday automatically make a week final?
- No. The weekday is not a gate. Leagueborn checks the target week’s coverage, provider context, and matching observations.
- Can an unchanged Sunday score pass after 15 minutes?
- No. The provider must first advance beyond the target scoring week, or the league must be complete. Pre-advance observations do not satisfy publication.
- What happens when the second read changes?
- It produces a different source fingerprint. The prior candidate does not publish, and confirmation begins again from the new source.
- Can AI declare a result final?
- No. Finality is determined from normalized provider evidence. Optional AI language is downstream narration, not an evidence source or a finality signal.
- What happens in a bye week?
- The current complete-coverage rule expects two-roster matchups, so a bye blocks publication. That is a known limitation, not a result Leagueborn guesses around.
Bring your own league