The routing table

A workspace that gets read start to finish is just a big prompt with extra steps. The saving doesn't come from making files smaller, it comes from never assembling the oversized context in the first place, and that requires you to say out loud which files a given task needs. The half everybody writes is the read list. The half that does the work is the skip list — because without it the model has permission to open anything, and given a large folder, it will. Write both columns, then test it. A routing table you never checked is a description of what you hoped would happen. And know what it is: a routing preference. It steers which files get read; it doesn't stop anything. If a file must never be read — because of an NDA, or because it's misleading — enforce that with a permission deny rule (B3), or keep the file out of the workspace entirely. Firmer wording helps routing; it is not a lock.

The long version: The routing table ↗

Checkpoints

• ▸You should now see a table with task, always load and never load columns.
• ▸You should now see three rows using real file names.
• ▸You should now see a never-load cell filled in on every row.
• ▸You should now see the list of files Claude opened in a fresh session.