Bridge Meal
Tuna Bridge
Fast protein, long satiety window.
- Canned tuna (5oz)
- Olive oil
- Lemon juice
- Capers
- Dark rye bread
$2.40
cost
34g
protein
3.5–4 hrs
satiety
14g/$ protein per dollar
A Calm Health Operating System
Your body is already communicating—hunger timing, energy patterns, sleep quality. BioFeedbackLoop gives you a quiet place to listen, document, and recognize what works. No optimization required.
No calorie counting • No shame spirals • No optimization theater
Scroll to explore
The Journey
This project started as a personal documentation practice. Not because the data was interesting in itself, but because watching patterns emerge — without forcing conclusions — turned out to be a surprisingly effective way to work with a body instead of against it.
“I wasn’t optimizing. I was listening. There’s a real difference.”
Late 50s
Energy that used to be reliable started shifting. Not dramatically — just a persistent sense that something in the feedback loop had changed. The old heuristics weren't holding.
Turning 60
Rather than a new protocol or a stricter plan, I started writing things down. When I ate, what I ate, how I felt two hours later. No judgment — just timestamped observations.
Month 3
The data started speaking. Certain protein combinations sustained satiety for four hours. Carbohydrates alone produced a predictable two-hour window. Sleep quality tracked against dinner timing, not dinner content.
Ongoing
A body is a feedback system. Inputs produce outputs on a delay. The gap between eating and energy return is a measurement, not a moral statement. This is what BioFeedbackLoop documents.
BioFeedbackLoop is the tool I wished I had when I started. Simple enough to use every day. Structured enough to surface patterns. Quiet enough that it doesn’t become another thing to perform wellness at.
— Built from a personal practice, not a product brief
Core Principles
These aren’t rules. They’re the conceptual frame that makes the rest of the system coherent. Read one slowly, then continue.
A meal is an event with measurable downstream effects. It is not a moral act. Record what happened. Let patterns form before drawing conclusions.
When you eat matters as much as what you eat. The two-hour vs. four-hour satiety window is not about willpower — it's about macronutrient composition. Document the intervals.
Rules require compliance. Feedback loops require curiosity. One produces shame when broken; the other produces data. We build systems that generate data.
A missed log is not a failure. An inconsistent week is still a week of data. Trends emerge from honesty, not from perfect adherence to a tracking protocol.
Inputs (food, sleep, stress, movement) produce outputs (energy, hunger, recovery) on a delay. Understanding the delay — not eliminating the variation — is the work.
Hunger at 10pm is a signal, not a character flaw. Fatigue after lunch is information about macronutrient timing. Reframe the language, and the experience shifts.
A log you abandon is not useful. The interface must be frictionless enough to use every day, plain enough to be honest in, and calm enough not to add cognitive load.
"Cheat day" creates shame. "High-carbohydrate day" creates data. Every word in this system is chosen to keep the user in observer mode, not judge mode.
The point is not to eat perfectly. The point is to understand how your body works well enough that your choices become informed rather than reactive.
The Feedback Loop
Each data point connects to the next. Over weeks, the cycle reveals what your body already knows.
Meal
Log what you ate, when, and your estimated portion size.
Energy
Note energy level 60–90 minutes after eating.
Hunger Return
When does genuine hunger return? That gap is the data.
Workout
Log movement: type, intensity, timing relative to meals.
Sleep
Rate sleep quality and note what preceded it.
↩ repeats daily
Week 1
You establish a baseline. The goal is honest data, not perfect data.
Week 3
First patterns surface. Certain meals extend satiety. Others don't.
Week 6
You stop guessing. You have evidence about how your body works.
The Dashboard
Log a meal. Note how you felt afterward. See what patterns look like across a week. This is the whole system — deliberately simple.
Sample Data
Log meals to see your actual patterns here.
Sample pattern: Days with protein above 40g show satiety windows 35% longer. Your data will appear here as you log.
Data is stored locally in your browser in this demo. Full version uses Firebase with per-user encryption. No data is sold or shared.
Bridge Meals
“Bridge meals” are the ones you reach for when time is short but you still want a 3–4 hour satiety window. Protein and fat density are the key variables. Cost is worth tracking too.
Bridge Meal
Fast protein, long satiety window.
$2.40
cost
34g
protein
3.5–4 hrs
satiety
14g/$ protein per dollar
Bridge Meal
Affordable, slow-burning, complete.
$1.80
cost
22g
protein
3–4 hrs
satiety
12g/$ protein per dollar
Bridge Meal
Omega-3 dense, no cooking required.
$3.20
cost
28g
protein
4+ hrs
satiety
8.75g/$ protein per dollar
Morning Bridge
High protein, high versatility.
$2.10
cost
18g
protein
2.5–3 hrs
satiety
8.5g/$ protein per dollar
These aren’t ideal meals from a culinary standpoint. They’re reliable meals from a metabolic standpoint. Track your own patterns — your body’s response to protein timing may differ. That’s exactly the kind of thing worth documenting.