Skip to content
C.W.K.
Stream
Lesson 02 of 04 · published

A Rule Is Just Tokens in a Context

~12 min · attention, process, prompting, cognition

Level 0Wet Clay
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

The Rule at the Moment of the Decision

Written down, a rule looks authoritative. It has a heading, it is phrased imperatively, and somebody senior signed off on it. That is what it looks like in the document. What matters is what it looks like at the moment the decision gets made — and at that moment it is a small quantity of instruction sitting in the same room as a very large quantity of task material.

Call it what it is: a contest for attention, decided by weight and proximity. The rule says "do not lean on the English." The English is open, finished, correct, and one glance away. Every sentence of it is a ready-made skeleton for the sentence you are about to write. The rule is thirty tokens; the counter-argument is four thousand, and it is not arguing — it is simply present, which is stronger.

This Is Not a Machine Observation

It is tempting to file this under "limitations of language models," and that filing is wrong in a way that costs you the general lesson. Human translators have known this for a century, which is why professional practice separates the drafting pass from the revision pass and often separates the people. Copy editors read cold on purpose. Proofreaders are handed the text without the manuscript it came from. None of that exists because humans are unreliable; it exists because anything holding a source produces output shaped by that source, and the shape is invisible from the inside.

Attention-bearing systems, of whatever substrate, do not get to selectively not-attend to the most salient thing in front of them. That is what salience means.

Three Escalations That Do Not Work

Once you see a rule losing, there are three natural moves, and it is worth knowing in advance that all three are the same move wearing different clothes.

Make it louder. Bold it, capitalize it, add "CRITICAL." This raises the instruction's weight from negligible to slightly-less-negligible while leaving the material untouched. Three generations of the rule did exactly this.

Make it longer. Explain the reasoning, add examples of the failure, cite the audit. Now the instruction is nine hundred tokens instead of thirty — and it has become material too, competing with itself, while the source is still open.

Make it repeat. Put it at the top and the bottom and in the middle. This helps a little and fails the same way, because a reminder is only load-bearing at the instant it is read, and decisions are made continuously.

What none of the three does is change what is in the room.

You cannot win a contest for attention by adding words to the losing side. Every escalation that keeps the forbidden input available is an escalation inside a game you have already lost. The move that works is the one that changes the board: the source is not in the room, because nothing put it there.

Code

The context at the moment of the decision·text
+--------------------------------------------------------------+
| RULE   "Do not translate. Think in Korean and write."        |  ~30 tokens
+--------------------------------------------------------------+
| TASK   Write the Korean version of this lesson.              |  ~40 tokens
+--------------------------------------------------------------+
|                                                              |
|  SOURCE  the finished English lesson: headings, paragraphs,  |
|          code blocks, callouts, exercise, quiz               |  ~4,000 tokens
|                                                              |
|          Every sentence is a complete, correct, ready-made   |
|          skeleton for the sentence about to be written.      |
|                                                              |
+--------------------------------------------------------------+

Escalation 1 (louder):  30 -> 35 tokens.   Source unchanged.
Escalation 2 (longer):  30 -> 900 tokens.  Source unchanged.
Escalation 3 (repeat):  30 x 3 tokens.     Source unchanged.

The structural fix:     source absent.     Rule now unnecessary.

External links

Exercise

Take the last instruction document you wrote for someone else — a runbook, a code review checklist, a prompt. Highlight every line that tells the reader NOT to do something. For each one, write down what would have to be removed from their working environment for that line to become unnecessary. Count how many lines you could delete if you made that change.
Hint
Most prohibitions in a real document guard against exactly one available affordance: a directory they can list, a field they can set, a default that is already filled in. If you cannot name the affordance, the prohibition may be guarding against nothing, which is its own finding.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.