01. The First Crash
2020 was the year the world slowed down, but for me, the pressure accelerated.
A major motorcycle accident resulted in a shattered tibia. Two months later, the COVID-19 pandemic hit. Then, in 2021, I lost an uncle to cancer, and the Omicron wave came to claim my brother-in-law and youngest uncle — all within the same 60-day window as the birth of my first daughter. Just 60 days after her birth, Omicron came to claim my father as well.
That was not a setback.
That was a total system failure.
02. The Diagnostic
When your personal hardware fails at the same time your legacy support system is dismantled, you don’t “bounce back.” You undergo a diagnostic.
You find out what actually holds.
You find out what breaks.
You find out what was never built to survive in the first place.
03. The Load
Grief is not an emotion you process once. It is a background process that consumes resources continuously.
It takes CPU.
It takes memory.
It takes bandwidth away from everything else.
If your system requires constant attention just to function, it will fail under that kind of load.
04. The Adjustment
So you offload. You automate. You remove anything that doesn’t require you.
Because your job in that moment is not optimization.
It’s survival.
05. The Carry Forward
I didn’t come out of that period the same. That version of the system failed. What came after was built differently.
With fewer assumptions.
With tighter tolerances.
With a clearer understanding of what matters when everything else is stripped away.
06. The Principle
You don’t rebuild to restore what was.
You rebuild to survive what happened.
07. Continue
→ See how this becomes a system: The Reconstruction Protocol
[SYSTEM NOTES]
- Status: Physical Reconstruction In-Progress.
- Network: Legacy Backup Active.
Stay Resilient.
— Greg Scott Kirk (Tek)