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

Ship the Text, Withhold the Path

~12 min · guardrails, design, sampling, architecture

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

The Strongest Seal Available

A guard in front of the tool call has to enumerate: which commands can print, which arguments narrow the scope, which shapes count as a breach. Enumeration is where guards leak, and the leak is always some ordinary command nobody thought of.

There is one stage in this workshop where the whole category disappears. A reading pass — one that scores material rather than editing it — does not need to write anything. So the engine draws the sample itself and puts the actual text inline in the brief. The session never receives a path, never learns the directory layout, never learns that a sibling file exists at all.

Contamination stops being forbidden and becomes impossible. Nothing to point a tool at, nothing to refuse, nothing to enumerate.

Why This Only Works Sometimes

The prerequisite is strict: the stage must not have to write files. A stage that produces edits needs paths, and no amount of design removes that. So this is not a technique that replaces the guard — it is the technique available at the one place where the guard would otherwise be doing the hardest work, and recognizing that place is the skill.

The general form is worth stating on its own: look for the stage where the output does not have to be a file. Scoring, triage, review, classification, estimation — all of these consume material and produce a small structured verdict. Every one of them can be fed as text.

Two Things That Come With the Sample

If the engine is drawing, it inherits two responsibilities that a self-selecting reader used to hold, and both improve the result.

The draw is seeded and recorded. A reader who picks their own excerpts lets bias in through the front door, and a score you cannot re-draw is a rumor. A recorded seed makes a run repeatable on a corpus that has not moved.

The brief has to declare the population. If the target has fewer passages than the sample size, it is scored on all of them and the brief says so — because a total of twelve means something different at six passages, where it is a perfect score, than at ten, where it is a middling one, and the reader must not have to guess which.

Before writing a guard, ask whether the stage needs paths at all. If it does not, hand it text and the entire class of failure the guard was built to catch stops arising. Keep the guard anyway — it now costs nothing and still covers the one path the design did not remove. Most reading and judging stages do not need paths, and nobody notices because handing over a directory is the default gesture.

Code

The same stage, briefed two ways·text
# WEAK - the brief hands over a location

  Score the Korean prose quality of ./content/<target>/.
  Read 10 paragraphs and rate each 0-2.

  -> the session now knows: the directory, the file naming
     convention, that an English sibling exists, and its title.
     A guard must now enumerate every command that could print it.


# STRONG - the brief hands over the material

  Score each passage below 0-2. 2 = natural, 1 = awkward but
  native-shaped, 0 = imported sentence shape.
  Draw: seed 1785204910, 10 of 47 pooled passages.

  [1] <passage text inline>
  [2] <passage text inline>
  ...

  -> the session cannot reach anything. There is no path in its
     context, so there is no command to write and none to block.
     The guard for this stage has almost nothing left to do -
     and it stays armed anyway, for the one way this can still
     go wrong: a reader reaching for the tree the engine hid.

External links

Exercise

Find one review or scoring step in your process where you currently hand over a link, a repository, or a directory. Rewrite the request so that everything the reviewer needs is inline and nothing they must not see is reachable. Then note what you had to decide in order to do it: which excerpts, how many, chosen how. Those decisions were always being made — by the reviewer, invisibly — and writing them down is most of the value.
Hint
If you cannot extract the material without also extracting the thing you are trying to hide, that is a finding about your storage layout rather than about the review. It usually means the two things are siblings in one directory, and the cheapest fix is often at that layer rather than in the review process.

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.