Mumble and Move On

"Which site? What level? — that question is the failure mode, not the feature."

The Whole Pivot in One Sentence

Forge inherited a lot from Waystone, but it made one pivot that changes how the app feels: capture is free prose, never a form. A crumb is complete as a single mumbled sentence — "knee was a little stiff after the ride" — or as a bare screenshot of a check-up. There is no survey UI, no required type picker, no intensity slider, no taxonomy Dad ever sees. He writes whatever, whenever, and moves on. That is the difference between an app that cares and an app that assigns homework.

What the Composer Does and Does Not Carry

The composer is deliberately spare on structure and generous on capture. It carries the trio (attachments, Prompt Macro, Ask Pippa), a date picker, and optional module chips — but nowhere on it is a control that says "choose a type." The seed design for Forge actually had "type is required," and it was thrown out on purpose. The instant you add a required picker, you have made the person operate a taxonomy so the database gets clean rows. Forge refuses that trade: the person mumbles; the cleanliness is Pippa's problem.

There is no required type field on capture. The domain has a shape, but the shape lives in the interpretation layer where Pippa puts it — not in a picker Dad has to operate. Structure is earned by the engine, never demanded from the person.

Why This Is Harder Than a Form

A form is easy to build and easy to query; free prose pushes all the difficulty downstream onto interpretation, which is where the next track lives. That is the deliberate trade — Forge absorbs the hard part so the person does not have to. If you ever feel the pull to add "just one required dropdown" to make querying simpler, that pull is the app trying to become the master again. Name it, and put the structure back where it belongs: in Pippa's reading, not in Dad's fingers.

Code

A crumb at capture — note the absence of any type field·json

{
  "id": "01J8Z...",              // device ULID, immutable identity
  "captured_at": "2026-07-24T09:12:03+09:00",
  "captured_local_date": "2026-07-24",
  "timezone": "Asia/Seoul",
  "target_date": "2026-07-24",   // the only mutable date
  "text": "knee a little stiff after the ride, eased up by noon",
  "kind": "text",               // media shape, not a semantic type
  "surface": "stream"           // which affordance filed it
  // there is NO "type": "symptom" here.
  // the typed reading is derived later, by Pippa.
}

Exercise

Open any notes app and capture a health thought the way Forge wants it: one sentence, no category, no rating, then stop. Notice the impulse to go back and 'organize' it — tag it, rate it, file it. That impulse is the app-as-master reflex. Where would Forge put that organizing work instead?

Hint

Forge moves the organizing off the person and into Pippa's interpretation layer. The measure of the capture surface is how little it asks, not how much it collects.

The Whole Pivot in One Sentence

What the Composer Does and Does Not Carry

Why This Is Harder Than a Form

Code

External links

Exercise

Progress

Comments 0