Medication Is a Trail

"'What was Dad taking in March?' is a question you answer from evidence — not a table that erased February to show today."

A Sequence of Dated Statements

The obvious way to model medication is a table: current drugs, doses, a schedule. Forge does the opposite. The regimen is a trail — a sequence of dated statements, each an ordinary crumb. A screenshot of the supplements Mom prepared. "Got prescribed this." "Going to try this health supplement." "Stopped that one." None of these is a schedule row; each is a dated fact in the stream. The canonical first example is exactly the everyday one: Mom's daily supplement list, captured as a single screenshot crumb.

The Current Regimen Is a Reconstruction

So where does "what is Dad taking right now" come from? Analysis reconstructs it from the trail. Walk the dated statements forward, apply the starts and stops, and you have the current picture — and, just as easily, March's picture, or last year's. A table that stores only the current regimen answers "now" and silently erases its own history; a trail answers "now" and "then" because it never threw the past away. For a domain with no completion, the reconstruction is the honest form.

The regimen is a trail reconstructed from dated statements, never a hand-maintained table. There is no schedule entity, no adherence machinery, and no row that overwrites what came before. 'What was Dad taking in March?' is answered by replaying the trail, not by reading a field that forgot.

The Intake Module Answers a Different Question

Do not confuse the trail with the intake module from the next lesson. A regimen statement — a prescription, a screenshot, "started this" — is medication/supplement trail evidence: what Dad is on. An intake module chip (tapping Protein Powder today) records something else entirely: what he actually consumed on this date. Analysis may count those recorded consumption events, but it must never manufacture an expected frequency, a missed dose, or an adherence score from them. Recording what happened is care; grading what should have happened is the exact machinery Forge refuses to build.

Code

The trail, and the reconstruction from it·text

the trail (each an ordinary dated crumb):
  2026-02-10  screenshot: "Mom's daily supplement list"
  2026-03-04  "got prescribed a short course of X"
  2026-03-18  "finished the course"
  2026-05-01  "going to try a magnesium supplement"
  2026-06-20  "stopped the magnesium, no difference"

reconstruct "what was Dad taking in March?":
  -> walk the trail up to 2026-03-31, apply starts/stops
  -> Mom's daily list + the short course (03-04 to 03-18)

# no current-regimen row was overwritten to get here.
# the past is intact because the trail only ever grew.

Exercise

Picture your own medication or supplement history two ways: as a table that stores only what you take now, and as a trail of dated 'started / stopped' statements. Which one can answer 'what were you taking last spring?' — and which one quietly erased that answer the last time you edited it?

Hint

The current-only table overwrites the past on every change; the trail keeps every start and stop, so last spring is still reconstructable. Health has no 'current' that isn't just a projection of the trail.

A Sequence of Dated Statements

The Current Regimen Is a Reconstruction

The Intake Module Answers a Different Question

Code

External links

Exercise

Progress

Comments 0