The week ends. You book two weeks off. You come back empty on Monday and call it a mystery. The usual diagnosis is that you did not rest hard enough. Often the company never had a spec for the thing that ran out.
The Psychology of Founder Resilience already named the phrase on its introduction: capacity is infrastructure. That page sells the book. This page is the spec.
Infrastructure has named parts
RESILIENT is blunt. Capacity is treated as infrastructure you train and budget, not as a mood that returns after a holiday. The work it names in public is specific: sleep, recovery, decision quality, and the social cover that lets a founder tell the truth.
Those four are load-bearing. A company that tracks runway and ignores them is flying with one panel missing.
You do not need the nine-letter walkthrough to start. The framework page has the dashboard. This page asks whether the four have a spec at all.
A spec says what “good enough” is, what slack you keep, and who notices when it is gone. “I will sleep more” is not a spec. “Consequential calls do not land after a short night” is.
Slack is a design choice
Infrastructure that runs at one hundred percent is not impressive. It is one incident from a crack.
The book treats capacity with the same seriousness as the cap table and hiring. You would not run cash at zero on purpose and call it commitment. You would not hire the last person the company can survive losing and call it lean. Sleep, recovery, decision quality, and the one person who can hear the truth without a performance are the same class.
Slack is unused on purpose. An empty hour after a hard call. A person who does not need a metric. A night that is not a recovery project. If every hour is already sold, you did not budget capacity. You sold it.
The live book is also blunt about machines. AI does not need to recover. You do. Matching uptime is not a founder virtue. It is a way to break the biology that still has to direct the system.
A holiday is not the protocol
A holiday can help. It is not a refill protocol.
If the only time the four parts refill is when the company is forced to stop, you do not have infrastructure. You have an outage. The mood that returns in week two of August is not a system. It is weather.
Recovery, in the live book, is not what you earn by finishing. It is what lets you finish. Get the order wrong and you spend years blaming the instrument.
This is an operator claim, not a lab result. RESILIENT is an authorial dashboard: proposed and applied. It is not a validated clinical scale. Full, low, and empty are metaphors. They are still useful if you refuse to treat them as lab readings.
This is not medical advice. If judgment is impaired, or the distress is clinical, the next step is professional care, not a tighter spec.
Who owns the spec
Infrastructure has an owner. If the four parts belong to “whenever I can,” they belong to nobody.
Write the owner. It can be you. It cannot be a mood. Put the last inspection date next to each part. If you cannot name the date, the part is already uninspected.
The worksheets already exist. Do not invent a second dashboard so you can avoid looking at the first.
A fifteen-minute spec
Pick this week, not the week you wish you were having.
- Write the four parts: sleep, recovery, decision quality, social cover. One line each on what “good enough” is.
- Circle the part with no slack. If you cannot choose, they are all sold.
- Write the owner and the last inspection date. “Whenever” is not a date.
- Write one booking you will refuse this week because that part is already red.
- Write the person who can hear the truth without a performance. If the line is blank, social cover is not infrastructure. It is a hope.
If step 2 or 3 is empty, you do not have a holiday problem. You have an unowned spec. Write it. Then the week has something to fail against besides your character.