logbook field guide · reviewed 2026-09-12

Separate Food Notes From Symptom Guesses — Free

Record a meal, timing, observation, and question without asking a tool to decide what caused what. This guide treats food and symptom log as a physical working surface, so you can inspect the relationship instead of accepting a generic paragraph.

The proof surface

The ordinary version gives you a list. The logbook makes the missing relationship visible and leaves a named next step.

INPUTMeal or ingredient, observation count, and observation date

RARE DEVICEpreserves timing and uncertainty so a pattern board does not turn one observation into a diagnosis

OUTPUTa logbook with meal lines, time offsets, neutral observations, and a question tab for a clinician

COST$0 · local-first · no account

Why the flat version breaks

A flat checklist hides the decision that makes this job hard. For food and symptom log, the missing detail is not more advice; it is the relationship between the source, the measurable field, the date, and the note you will act on. The companion card keeps those layers separate and lets you change one input without rewriting the whole page.

Use the logbook in four passes

01 · Bring the smallest useful sourceEnter a specific meal or ingredient, a non-negative observation count, a date, and one concrete note. Do not paste identifying details you do not need.

02 · Let the physical metaphor sort the workThe card turns the inputs into a logbook with meal lines, time offsets, neutral observations, and a question tab for a clinician. Its spacing, columns, or route order carry meaning; the result is not a raw paragraph.

03 · Change one field and compareUse the second or third starter record, then edit one value. The result should change for a reason you can name. That is the useful check against false confidence.

04 · Keep the next action modestUse the printed or copied result as a handoff, review prompt, or planning surface. Verify outside facts with the source before you commit to a high-stakes decision.

Sample data, not a verified claim: Sample: lentil soup with sesame · 2 observation count · 2026-09-10 · Bloating noted 90 minutes later; no cause assigned. These values are illustrative so the first card has something concrete to show; replace them with your own source.

What breaks first

Empty or vague input

If there is no subject or note, the app leaves the card in an empty state and tells you what to add. It does not invent a result.

A number that does not fit

Negative, fractional, or oversized counts stay in the fields and produce an actionable input message. Check the unit before you rely on the number.

Outside facts

The local card organizes what you entered; it does not confirm a deadline, rate, rule, diagnosis, or booking. Keep the source beside the result.

Try the free logbook

The companion opens with the same sample shape, three starter records, a reset state, a copyable result, and a state link. Nothing is sent to a server.

Open the free food and symptom log card →

Keep the work if you will use it again

FREE COREComplete on-screen result at $0

Run the card repeatedly, edit the source, and copy the result without creating an account.

$4 ONE-TIMEPrint and retain the structure

Printable observation log with the same 2 entries; estimate: 2 rows × ~3 minutes of manual summarizing = ~6 minutes avoided. The paid tier extends the result; it does not remove the free core.

Go deeper in the companion app →

Use the boundary as part of the result. this organizer does not diagnose, prescribe, or replace a clinician. Take the dated observations and questions to a qualified clinician, and seek urgent care for urgent symptoms.