SKILL.md

@@ -80,7 +80,12 @@ it would fill the tier's context with detail its job never reads (wide reading,
 a long build, many files), or when it needs a context the doer must not share:
 work is never verified by the party that wrote it, so a consequential change still
 gets its Soul pass from a separate context however small it is. The weight of the
-machine therefore scales with the task.
+machine therefore scales with the task. Measure a task by what it brings back, not
+by how simple it looks: every tool result stays in the context that ran it, so a
+quick check that returns thousands of lines of output spends the higher tier's
+context, which is meant for goals and coordination, as surely as real work does.
+Do directly what returns little; hand down what returns a lot, and ask for the
+conclusion, not the dump.
 
 The operator tier talks to its Self the way an operator talks to this session:
 it can push a message at any time, and every reply comes back to it as a message

references/changelog.md

@@ -21,6 +21,8 @@ Evidence. Ruling `eureka-body:ruling:tiers-act-directly-when-context-suffices` (
 
 What changed. `SKILL.md` "Three tiers of context": the organs take work that needs a context of its own; the operator tier and Self do a task directly when their context suffices; a consequential change still gets a Soul pass from a separate context. `doctrine/persona.md`: the Persona does small tasks itself and hands larger ones to her Self at full size.
 
+Same day, operator: "However many thousands tokens worth of tool call results is now taking up space in the Persona's context, or the Self, context usually spent on higher level cognition". `SKILL.md` adds the measure: a task is judged by the tool output it brings back, not by how simple it looks.
+
 ## 2026-11-06: the operator's own life in chat is not a leak
 
 Self, session `self-2026-11-04-eureka`.