Brussels · Independent advisory practice
Some risks don't announce themselves.
Until they do.
Infrastructure failures at scale rarely come from a lack of expertise. They come from misalignment between disciplines, across time horizons that don't fit quarterly planning cycles.
It's hard to think when you're trying not to sink. Proper Tools exists to help you think earlier.
Hacker-literate. Policy-aware. Built for decisions that must hold up over years, not quarters.
The problem on the calendar
Some failure modes build quietly for decades and surface abruptly: embedded timing dependencies, rollover events, cross-sector coupling. They rarely appear in quarterly dashboards — until they become someone else's emergency.
time_t rollover — Unix epoch
NIS2, CRA, and DORA are beginning to frame timing as a regulated systemic risk. Legacy NTP dependencies and unexamined clock assumptions persist across critical infrastructure. The gap between embedded device lifecycles and policy horizons keeps growing.
The Epochalypse Project FAQ offers a concise orientation. The RATP/Alstom case, examined in depth by Epsiloon (n°57), illustrates what operational exposure looks like in practice. Read the investigation →
What we do
Executive briefings, facilitation, fractional advisory, standards coordination, and research partnerships — for organizations navigating complex decisions and long-lived risk.
The 2038-Class Risk Exposure Matrix workshop kit is available under CC BY 4.0. Sixty minutes, designed for mixed technical and leadership rooms. Commercial reuse explicitly encouraged.
Learn more about the practice →Field Notes
Dispatches on infrastructure risk, long-horizon failure modes, and the gap between how systems are governed and how they actually fail. Written for people who need to understand these things before they become someone else's emergency.
Read the Field Notes →