Keep the suspension in the timeline
A launch announcement alone does not describe availability for the whole week.
Retrospective field note for 2026-06-15, reconstructed on 16 November 2026. The archive date is not a claim of publication at the time.
Fable 5 and Mythos 5 launched on 9 June. Access was suspended on 12 June. Both dates belong in this week’s account.
Leaving out the second event would make a cleaner release story and a worse reference for anyone trying to understand what was available. A model’s capabilities and its availability to a particular account are separate facts.
An application needs a way to stop new work entering an unavailable route. Preserve inputs that can safely be resumed. If a fallback offers less, say what changed instead of quietly presenting it as equivalent.
There is no need to invent an explanation for a suspension. Report what the source establishes, which work is affected and what can happen now. A promised restoration remains a promise until it occurs.
This archive has the same obligation. Later updates cannot be smuggled into an earlier week’s perspective. Keep the sequence intact, including pauses and reversals. Otherwise a retrospective can accidentally give the past a certainty it never had.