Field Guide
a field guide for daily signals
Not a diet app. Not a fitness tracker. A quiet place to write down what you noticed.
The Journey
documentation over infrastructure
BioFeedbackLoop started as a habit of documentation — logging meals not to count anything, but to see what happened afterward. The patterns that emerged weren’t dramatic. They were practical.
“You already know more about your own patterns than any algorithm does. This is just the place to keep it.”
Where it started
Logging meals not to count anything
BioFeedbackLoop started as a habit of documentation — logging meals not to count anything, but to see what happened afterward. A timestamp. A description. A note about energy two hours later.
The first pattern
Seeing what happened afterward
The patterns that emerged weren't dramatic. They were practical. Certain meals reliably extended the satiety window. Others produced a predictable afternoon dip. The data wasn't surprising — it was just finally visible.
What emerged
Reliable meals. Predictable windows.
Reliable meals. Predictable energy windows. A clearer sense of what a useful day felt like from the inside. None of it required a new protocol. It required a place to write things down.
The result
A tool grew around the habit
The logging didn't stop — it just got quieter and easier to return to. BioFeedbackLoop is what grew around that. You already know more about your own patterns than any algorithm does. This is just the place to keep it.
BioFeedbackLoop grew around that habit. Nothing was added that didn’t already exist in the practice.
— Built from a documentation habit, not a product brief
Documented Experiments
What the data actually showed
Each card is a timestamped experiment — a specific observation and the pattern it revealed. Not conclusions. Starting points.