Surface form matched instead of meaning

What goes wrong

A check decides what something is from its surface shape - a suffix, a fragment, a run of characters - rather than from its role or its context. Anything that happens to share the shape is treated as a member of the class and handled accordingly. The reader relies on the shape being a reliable sign of the category it usually accompanies.

Example

A rule that treats every word ending in a certain suffix as a modifier also fires on ordinary nouns with that ending, and the surrounding text is rewritten around a word it misread.

Not to be confused with

Not Indirect check misses the real property, where the stand-in is wrong for every input; here the stand-in is usually right and fails only on items that happen to share the same outward form.

Discovered by

@sks24git GitHub

Field notes · 12

@sks24git2026-11-04

A text check flags any quoted token in certain sentences as a forbidden name. Quote an ordinary word there next month and the check fails for no real reason.

Match a text rule against an explicit list, not a shape. Shape heuristics false-fail on new prose.

@sks24git2026-11-04

A filter meant to drop names that pose as the service drops any name that merely mentions it. The most common clients put the service's name in their own label, so every one of them turns nameless.

Check an anti-spoof rule against real client names. The honest ones mention you too.

@sks24git2026-11-04beat 2 review rounds

A table column sorted its rows by the raw timestamp text, which only matches time order while every value carries the same zone suffix. Once one source writes a different offset, rows sort out of order with no error.

Sort time by its parsed moment, not its text. String order and time order agree only by accident.
Test with mixed zones. Uniform fixtures hide the bug.

@sks24git2026-11-02beat 4 review rounds

A guard that refuses any reply with a digit in it, meant to catch money typed as words, also hits a plain no that names a year. The client answers clearly and the answer cannot be saved.

Match the shape you fear, not one trait of it. A single trait also shows up in harmless input.
Narrow where a new path applies first. Each extra case it covers needs its own patch later.

@sks24git2026-11-01beat 4 review rounds

A new flag was set by the message's opening reason, while a different rule let the offer out. When a row opened with another reason, the offer showed without the flag, and a later retry read it as a refusal.

Key a side effect on the rule that caused it. A label shared by two paths marks only one of them.
Test every path that reaches a new flag. One green path hides the silent one.

@sks24git2026-11-01beat 2 review rounds

A fix keyed a gate on the label an answer led with instead of the rule that opened it. Any case with a different label then lost the decision that rule owed it, though the offer still went out.

Gate on the rule, not on its label. Labels describe; rules decide, and they drift apart.
Test the case whose label differs. That is where a gate keyed on text breaks.

@sks24git2026-11-01beat 1 review round

An ignore rule meant for one tool's output matched a common folder name at any depth. A later copy of a real project would lose its own source folder of that name from commits, green on one machine and red on all others.

Anchor ignore rules to where the output lands. A bare folder name at any depth hides real files too.

@sks24git2026-10-30beat 6 review rounds

Two timestamps were turned into text before being compared, and the text form drops the milliseconds. Two moments in the same second compare as equal, so a cutoff can land on the wrong side.

Compare times as numbers, never as printed text. Printing throws away precision.
Push window math into the query. One clock and one type leave less to round.

@sks24git2026-10-17beat 1 review round

A spec adds a short hex hash to every outbound name and also makes a leak scan block any long run of digits. Some hashes contain such a run, so those items fail the scan on every send and never leave.

Test each new filter on the ids you already emit. A filter and an id format can clash.
Draw ids from an alphabet the filter ignores. Then no id can look like the data it blocks.

@sks24git2026-10-12beat 3 review rounds

A router treated any command with a word starting with 'review' in its name as a code-review request. A weekly process retrospective that commits and edits tickets matched it and went to the review-only model.

Match commands by an explicit list, not a word in the name. A name tells the topic, not what the command does.

@sks24git2026-09-08beat 3 review rounds

A mask read a -ly suffix as "adverb" and bridged over it to the verb, but "apply", "monthly" and "family" end in -ly before a noun. The client's own figure vanished from the report.

A suffix is a shape, not a part of speech. Decide by what follows the word, not by how it ends.

@sks24git2026-09-08beat 9 review rounds

A regex treated any word ending in -ly as an adverb before a verb, but the client's own nouns end in -ly too. "monthly spend $12,000" lost its figure from the very text the mask existed to protect.

Bind an open class by its context, never by a denylist. Each named exception only catches the words someone thought of.