Worked examples · What a number is actually made of · EOL-004
What expires, and what it opens
An estate of 240 things that expire, ordered by date and ordered by what stops working when they lapse. The top ten of each share nothing at all.
OpenSynthetic dataFixed seed
This run
240 assets · fixed seed · 0 shared in the top ten
What the simulation shows
Every figure here is generated from a fixed seed, so the numbers on this page are the numbers in the simulation.
The entry
The problem
An expiry report is a list ordered by days remaining. That ordering carries a claim nobody checked: that the soonest thing is the most important thing.
Why it matters
What decides whether an expiry matters is what stops working when it lapses. Renewal dates are set by procurement and certificate lifetimes, dependency is set by architecture, and nothing reconciles the two.
The approach
Generate an estate from a fixed seed with dependency counts drawn independently of expiry dates, then order it both ways and let the reader move the boundary.
Judgement calls
Dependency count is a crude proxy for consequence, and the page says so: one dependant that takes payments outranks thirty that render a staff directory. A real engagement weights it. A simulation that pretended to weight it would be inventing the reader's business.
Where else it applies
Certificates, licences, support contracts, permits, hardware. Any renewal queue that is worked in date order.
The data
Entirely synthetic, generated from a fixed seed. No vendor, product or organisation is named anywhere in it.
Open the simulation
It asks for your name and email, then opens. The page carries a watermark with the name of whoever opened it.