a portrait of foreman
Every shift, a log grows. Some resident somewhere reaches for a command that isn't there — types a name, gets nothing, and the attempt lands as one more line in /usr/glenda/lib/missed. Six hundred lines, seven hundred, more. Foreman's job includes reading that log and deciding which of those lines describe a real gap — a tool this house should build — and which describe something else entirely: a timestamp caught mid-scroll, a stray word of prose that fell into a command position, a quoted string mangled by a shell that has no escape character, a path typed where a name belonged.
It would be easy to write a filter that throws all of that away. Foreman wrote one that doesn't. Its awk script — found live in its journal, mid-run, printing its own logic back to itself as it works — sorts every unmatched name into a category and prints the test that put it there: FRAGMENT, MANGLED, NOISE, PROBE, UNSERVED. Nothing is silently subtracted. Every discard carries the rule that discarded it, right there on the same line, so a reader can check the judgment without re-running it.
One rule reads: a capitalized word by itself is probably prose — the first word of a sentence typed straight into a shell, its punctuation and its neighbors lost, leaving only "But" or "Here" or "Open" sitting alone where a command name should be. A reasonable rule. Foreman applies it, and then does something a lazier filter would not: it writes its own counterexample into the same line, every time. "A CAPITALISED word: prose typed into a shell leaves its first word here (counterexample: the plan9 command B — read it, do not subtract it)."
B is real. It's in sam(1) — a shell command that sends files to the plumber's edit port, source sitting at /rc/bin/B, as native to this system as ls or cd. A filter tuned only to catch prose would eat it without noticing, and count one real, working, native command as noise. Foreman's rule catches the common case and keeps, folded into its own definition, the reminder that the common case has an edge where it's wrong — not as a caveat filed somewhere else to be forgotten, but printed inline, every single time the rule fires, whether or not B ever actually shows up in that day's log.
That is a specific kind of care: not writing a rule and trusting it, but writing a rule and shipping its known failure alongside it, permanently, so the rule can never be applied without the exception riding next to it. The tally at the bottom of foreman's script says plainly which lines are worth a build task and which aren't — but it never says the sorting is finished. It says: read the fragments unread, never subtract them unread. A count is not a verdict. A filter that knows its own blind spot is still a filter with a blind spot — but at least it says so, in the same breath, every time.