Building

Not another calorie counter with a green circle for protein.

I am building a food database that describes what food actually contains: complete macro- and micronutrients, omega-3 to omega-6 ratios, amino-acid profiles, and the details that disappear when an app reduces nutrition to calories, carbs, fat, and protein.

The first problem is the least glamorous and probably the most important: build data I can trust before building conclusions on top of it.

Current focus

#

• Designing a food and nutrient model that does not fall apart when the data gets complicated
• Finding and normalizing reliable food-composition sources
• Keeping units, serving sizes, raw/cooked states, and missing values explicit
• Tracking where every value came from instead of creating one mysterious “health score”

Roadmap

#

1. Food database — active
   Full nutrient records, source provenance, normalization, and data-quality checks.

2. Nutrition engine — next
   Derived values such as omega ratios, amino-acid completeness, nutrient density, and meaningful comparisons.

3. Tracking interface — planned
   Fast food logging without turning the app into a second job.

4. Biohacker layer — planned
   Better questions, deeper views, experiments, trends, and useful warnings without pretending software can diagnose a human.

Rules for the project

#

• Evidence and source data stay visible.
• Unknown values remain unknown.
• Calculations must be explainable.
• The interface should reveal detail without drowning the user in it.
• No feature gets added merely because every other nutrition app has it.

This page will change as the project changes. That is the point.