What Red Sentra did

Red Sentra designed, built and operates the whole system: the Go services, the Flutter client, and the bounded assistant that resolves written meals into foods.

• Architecture
• Backend & services
• Client applications
• AI & agent layer
• Production operation

The operating context

Nutrition trackers are abandoned because logging is work. The usual answer is a barcode scanner and a database of packaged goods, which handles the meals people least need help with and none of the ones they cook.

NutriSense takes the input people actually have — a sentence, a voice note, a photo — and does the resolution itself. What it records is not a calorie count but the full picture: macros plus over forty vitamins, minerals, amino acids and fatty acids.

What we built

Go services behind a Flutter client on Android, and a bounded assistant, Nova, that turns written food into specific foods with specific quantities.

The resolution step is the hard part and it is where the product either earns trust or loses it. "Chicken breast 200 g and rice" has to become identified foods with quantities, and the numbers are shown before anything is written. Nothing enters the diary until it is confirmed.

Hard limits on the assistant

The assistant has explicit limits on what it is allowed to claim. That constraint is a feature rather than a caveat: an assistant that guesses a nutrient profile confidently is worse than one that declines, because a diary is a record and a wrong record is carried forward.

The same rule governs measurement. What a watch measured and what was eaten are kept as separate facts, so an estimate is never quietly promoted into an observation. Samsung Health and Health Connect are integrated on Android under the same rule; Apple Health is not supported.

What the product does not keep

A photograph of a meal is analysed and then dropped. It is never stored, which removes an entire category of data the product would otherwise be holding on behalf of its users and answering for.

Deletion is one step with no waiting period. Both are product decisions before they are engineering ones, but they constrain the architecture: nothing downstream may assume a photo is still available.