Why this log exists
The field log keeps the process, not the tidy conclusion. Here is what goes in it and what stays out.
This track is not where finished thinking goes.
The other tracks are written after the conclusion holds. Work Automation gets written once I can actually judge what works and what doesn’t; Tech Notes gets written after I’ve stepped on the trap myself. Both are slow by design.
What gets lost is everything in between. What I built this week, what broke, why a call I was sure of yesterday changed today — none of it is tidy enough to publish anywhere, so it evaporates. And that is usually the part I want back later.
What goes here
- What I actually built this week, and where it stalled
- Calls that turned out wrong, and what changed my mind
- Why a schema or structure got torn up again
- Real requests from academies, and the gap that appears when they meet a system
What stays out
- Conclusions that look good without evidence
- Numbers I haven’t verified
- Any detail that would identify a specific academy
No length target. If it’s three lines, it’s three lines.