LOCAL-FIRST · OPEN SOURCE · RELEASE 0.3
Your meals are not a score. They are a feedback loop.
MealCircuit connects what you ate, how the day actually felt, what changed, and what you can realistically do next—then keeps every conclusion traceable and yours to accept.
Desktop and Android clients are offline-first. Optional sync remains self-hosted.
DEFAULT STORAGE
Local SQLite
No account required
DECISION WINDOW
14 days in context
Not one meal in isolation
MODEL ACCESS
Opt in, bring your own
No API key by default
THE LONG-HORIZON LOOP
Facts first. Context next. Advice last.
A daily plan cannot be published from one model response. MealCircuit separates evidence, case understanding, professional limits, strategy, planning, and independent review before you accept anything.
-
RECORD
Capture reality
Record meals, photos, ingredients, hunger, sleep, training, symptoms, and corrections without forcing missing details into fake precision.
-
UNDERSTAND
Read the person
Bring current goals, personal doctrine, recent patterns, daily constraints, and confirmed preferences into the same decision context.
-
DESIGN
Compare real choices
Balance safety, portions, recovery, meal mode, preparation time, and ingredient reuse before designing a reviewed next-day draft.
-
CALIBRATE
Learn from outcomes
Keep corrections and execution feedback as history. Promote recurring needs only through visible, reversible, evidence-backed learning.
SOVEREIGNTY BY DEFAULT
Your history stays useful without becoming someone else’s cloud.
The local database is the source of truth. Sync and model calls are separate choices, with explicit boundaries for what leaves the device.
Read the privacy noticeLocal by default
Desktop and Android read and write their own local database. Core features work offline.
Encrypted optional sync
A self-hosted compatible relay stores encrypted revisions and photo chunks, not meal-planning logic.
Model access is explicit
You select the provider, model, and API key. Keys stay in the current process and are not persisted.
THREE EVERYDAY SURFACES
The machinery stays behind the decision.
Ordinary navigation focuses on what matters now: the day, the plan, and the personal context shaping it.
Notice change.
See today’s arrangement, record what shifted, answer only relevant questions, and negotiate tomorrow’s draft.
Act with context.
Open current and past plans, adjust one meal when reality changes, and record how the choice actually went.
Own the rules.
Manage goals, meal modes, safety boundaries, inventory, learned preferences, appearance, and advanced settings.
THE HONEST BOUNDARY
Useful support, without invented certainty.
MealCircuit is designed to make uncertainty visible. Safety and user confirmation are part of the product, not footnotes after generation.
No diagnosis
It provides general logging and decision support, not medical diagnosis or treatment.
No invisible facts
Oil, sauces, weights, brands, health states, and inventory stay unknown until evidence supports them.
No official hosted cloud
Accounts exist only for optional compatible self-hosted synchronization.
No silent publishing
A reviewed draft remains replaceable until the user explicitly accepts it as the formal plan.
SOURCE AVAILABLE NOW
Inspect the loop before you put your history into it.
MealCircuit is built in public under the MIT License. Its product boundaries, data model, sync protocol, threat model, tests, and release gates are available for review.