Every tracker I have used scores the day as one thing. Ten habits, seven done, 70%. A bad week shows up as a red streak, the red streak becomes a story about who you are, and the story is the second dip.
The day is not one thing. It is two layers that behave differently under load, and once you see them separately the whole problem changes shape.
The two layers
| Layer | What's in it | Under load |
|---|---|---|
| Base | Sleep, food, movement, contact with one close person, one anchor ritual, one focus task | Should hold. Independent of state |
| Top | Energy, mood, attention, initiative, the volume of what you get done | Collapses. Fully dependent on state |
Top is the layer everyone measures and nobody controls. It rises and falls with sleep, with the news, with one conversation. Trying to hold Top steady on a bad day is trying to hold water in your hands.
Base is small, boring, and the only thing that actually matters. It is what keeps a bad day from becoming a bad week.
The classic breakdown is not Top collapsing — Top collapses all the time. The breakdown is contagion: Top's collapse starts eating Base. You feel flat, so you skip the walk. You skipped the walk, so you sleep badly. You slept badly, so tomorrow's Top is lower, and now it's a loop.
What "success" means once you see this
If the two layers are decoupled, the definition of a good day changes:
A day where Top collapsed and Base held is a successful day.
That is not a consolation prize and it is not self-deception. It is the system doing its one job. Mood fell, output fell, initiative fell — and you slept on time, ate three meals, moved for ten minutes, spoke to your person, did the ritual, closed one task. The dip stayed in the layer where dips belong.
This also tells you what to stop watching. Top is data: interesting, worth logging, not actionable. The only signal that means something is wrong is Base slipping two days in a row. One day is noise. Two is a trend. Top can fall as far as it likes.
Why the base has to be stated in minimum form
There is a trap in how base items get written down. "Gym session." "Eight hours of sleep." "A proper dinner." Written at full size, each of these gets dropped whole on the day it can't be met — and that day is exactly the day the base was for.
So every base item is stored in its minimum form:
- Sleep → bedtime hour, not duration. Timing is the lever you control.
- Food → three meals, no quality requirement.
- Movement → ten minutes, anything.
- Partner → one real contact.
- Ritual → the same one, always. Portable, no equipment.
- Focus → one task, any, closed.
The floor is low on purpose. A floor you can hold on your worst day is a floor. A floor you can only hold on a good day is a ceiling with the wrong name.
The ordered shed list
When resources run out, people cut at random — and they usually cut the things holding them up, because sleep and movement look postponable. The fix is not discipline. It is a list, written in advance, in a normal state, of what gets dropped and in what order:
1. Content — consuming and producing
2. Learning
3. Side projects
4. Social
…
─────────────────────────
NEVER DROPPED: Base
Two rules carry all the weight. The order is decided now, with resources, and it is not rewritten in the dip — in a dip you don't decide, you read the next number. And the base sits under the line, visually apart, not editable when things are bad.
This is the principle underneath the whole thing:
Decisions are made by the version of you that has resources. The system executes them when resources are gone.
Anything that requires judgment in a bad state is a design failure — one you made earlier, when you had the judgment to spare. Any setting you can renegotiate while depleted will be renegotiated. Lock it.
The detector
There is no observer available inside a dip to notice the dip. That is what a dip is. So detection has to be external and dumb:
Base slipped two days in a row → drop item 1 from the shed list.
Not "how are you feeling". Not a mood score. Mood is Top-layer data and it is the last thing to trust on a bad day. The detector counts one thing, and it counts it with a calendar.
The exit
The most common second mistake is turning everything back on at once, failing, and dipping again. Recovery is a sequence:
- Sleep first, alone, for two or three days. Nothing else comes back yet.
- Then bring things back bottom-up — the last thing dropped is the first restored. One item a day, no exceptions.
- Let the weekly review restore the rest by itself. Don't rush it.
- Debrief: what was the trigger, what held, what didn't. That goes into your principles, not your to-do list.
And the rule that sits over all of it: protection beats training. The capacity to observe is defended in advance — with sleep, with load, with buffer. Training it during the crisis is too late.
In LucinOS
This is what the Base card does. You mark the handful of habits that are your base, stated in minimum form. The card shows whether the base held today and the last two weeks as held or slipped — not a percentage of everything, just the floor. Two slipped days in a row and it proposes Reduced mode, which shows the base and nothing else; the shed list you wrote in a normal state is read-only until you're back. Lucian names the slip and proposes the switch — it never asks how you feel.
The number it watches is not how much you did. It is whether the floor held.