Read more notes

← All journals
August 18, 2026

A promise with no writer

Our application form said: “If given, we will send the application code here too.” Clean, reassuring microcopy. A parent enters their email, gets their code on screen, and trusts the inbox copy exists. It didn’t. No send function, no template, no call site. The sentence shipped; the feature never existed. I caught it by doing what no test suite does — reading the screen and then checking my inbox.

This was the second no-writer bug in the same codebase in one week, and the rhyme is what makes it an insight rather than an anecdote. The first: application_fee — a column on the admission cycle. The database had it. The service layer accepted it. The data layer wrote it. And the Zod validation schema, the one layer nobody re-read, silently stripped the field from every request. Four layers, three of them ready, one silently discarding — and a school literally could not set the fee the entire payment flow depended on. Every layer passed its own tests, because each layer’s tests check that layer’s promises, and the gap was between layers.

The cost profile of a no-writer bug is nasty precisely because it’s silent. Nothing errors. Nothing logs. The fee column would have surfaced weeks later as “why is every application free?” — a revenue bug reported by an accountant, not a stack trace. The email promise surfaces as quiet erosion: a parent who trusts the inbox copy, loses the screen, finds no email, and becomes a front-desk visit plus a family that now believes the school’s software says things that aren’t true. Trust decay doesn’t show up in dashboards until it shows up as adoption numbers.

The naive shape — copy promising, backend shrugging:

{ "emailHint": "If given, we will send the application code here too." }
const application = await createDraft({ phone, email });
return { application_code: application.code };

The fix has two halves, and the second matters more. First, the send exists now. Second — because a mint must never fail over a mail server, and a screen must never claim what didn’t happen — the send is best-effort and the response says honestly whether it went. The confirmation screen only renders “the code has also been sent to your email” when email_sent is true:

let emailSent = false;
if (input.email) {
  try {
    await sendApplicationCode(input.email, {
      application_code: code,
      phone_last2: phone.slice(-2),
      continue_url: trackUrl,
    });
    emailSent = true;
  } catch (err) {
    console.error(`apply: code email failed:`, (err as Error).message);
  }
}
return { application_code: code, fee, email_sent: emailSent };

Two working rules fell out of this. One: every null column has two possible explanations — old data, or no writer — and you must rule out the second before assuming the first. Asking that one question found both bugs. Two: UI copy is an API contract. Every future-tense sentence on a screen — “we will send,” “you will receive,” “the school will contact you” — names an endpoint that had better exist. Nothing in any toolchain type-checks a promise made in a JSON strings file against the service layer. The only checker is a person reading the product the way a user does, which is why clicking through my own wizard found in an afternoon what a green CI pipeline never would.