Tells

A tell is a default the thesis never asked for.

That sentence is the module. The rest explains how to recognise one, how to write one down, and what to do with it once found. Nothing here names a replacement: a replacement would only be the next default, and genjutsu does not ship a look.

The rule: the thesis is the only authority

A pattern is a tell when the validated thesis does not name it. Nothing else decides.

• Named means named. The thesis has to name the pattern itself: "the header shows the Paris and Tokyo clocks, because the studio works across both". A mood word unlocks nothing. "Editorial", "agency", "premium" or "bold" do not name a numbered eyebrow or a display serif, and most tells are precisely the clichés those words summon. In practice the pattern is named in the thesis's Allowed patterns: line, which cast and paint write under the thesis before the user validates it.
• An explicit request goes through the thesis. When the brief asks for something specific (a weather strip, a version badge, a live counter), write it into the thesis by name before you build it. The thesis is what allows it, not the brief. A request that never reached the thesis still reads as a tell at audit time, because afterwards nobody can tell the two apart.
• An unvalidated thesis allows nothing. When no human could validate the thesis, every tell counts, and the report says why.

How an entry is written

Every entry, here and in the references, has exactly three fields. Never a fourth.

• Marker - what you can see: a literal string, a pattern, a structure.
• Why it is a tell - the model behaviour that produces it. Not a judgement of taste.
• The question - one question that sends you back to the thesis or to the project's own data. Never a replacement.

Report a tell in the same shape: the marker as found (file:line and the text), then your answer to its question.

The four families