Baseline lane
Sleep Baseline
Goal: Know whether recovery is being built or borrowed.
Protocol V Baseline Checklist
Use this before judging any stack, training block, recovery phase, or new system. The goal is not to collect random data. The goal is to know what is already happening before you start assigning blame or credit.
7–14 days
Minimum useful baseline window before overreacting.
1 variable
Change one major thing at a time when possible.
3 signals
Sleep, pressure, and performance usually tell the truth first.
0 ego
Labs and logs do not care about your favorite theory.
Baseline lane
Goal: Know whether recovery is being built or borrowed.
Baseline lane
Goal: Do not guess under stress. Measure the pressure trend.
Baseline lane
Goal: Organize markers before pretending a protocol caused everything.
Baseline lane
Goal: Track patterns, not panic over one spike.
Baseline lane
Goal: Separate hard work from accumulating damage.
Baseline lane
Goal: Catch system fatigue before it becomes a fake mystery.
Baseline lane
Goal: Make food boring enough that the signal becomes visible.
Baseline lane
Goal: Bring organized questions, not chaos.
Next move
If people only read this page once, it becomes another internet note. The actual edge is repeatable logging: reminders, inventory, field notes, and clean records you can review instead of arguing with your memory.