In Module 1 you granted a folder without thinking, because it held nothing but practice data. Right call then. Wrong habit now.
Here is the version that costs money. An analyst points a session at ~/Documents/Revenue
because the pipeline export lives there. Three levels down sits Comp/2026-Q2-commissions.xlsx,
because it also lives there. Nobody attacked anything. The perimeter was simply whatever happened
to be in one directory. This lesson draws it on purpose.
What you will be able to do
- Say, for any folder layout, what a session can and cannot reach, and why.
- Build a workspace that separates granted data from fenced data by location.
- Prove to yourself, in three minutes, that an instruction is not a boundary.
The boundary is a directory, not a rule
Two product facts. They are the two most important sentences in this course.
Cowork runs inside a sandbox and asks permission before certain high-risk operations.
Claude cannot read or write files outside the directories you explicitly grant. In the words the source uses: if you do not want Cowork to touch something, do not put it in the shared folder.
The second one cuts both ways. It guarantees what is outside, and it means everything in the granted folder is in scope, including what you forgot was in there. The boundary is not "the files I meant". It is the directory.
The uncomfortable part: your working folders were organised by what you were doing at the time, not with a boundary in mind. Nobody's were. That is why this module exists.
Check yourself: name one folder you would have granted last week and should not have.
Read-only by default, and what sandboxing changes
The underlying model is read-only by default and asks before modifications or command execution. Sandboxing then creates pre-approved boundaries so it stops asking per action.
That is a real tradeoff. Make it on purpose, not by clicking through prompts:
| Narrow pre-approved area | Wide pre-approved area |
|---|---|
| More prompts, more interruptions | Fewer prompts, smoother long runs |
| Smaller blast radius if a run misbehaves | Larger blast radius if a run misbehaves |
| Good for anything touching customer data | Good for a scratch folder of your own output |
The rule to carry: the size of the pre-approved area is a decision, and it should differ by folder. Your own reports can sit in a wide area. A customer list export should not. The strongest "narrow" is not granting the folder at all, which is next.
The revenue workspace layout
This layout is our opinion, not a product requirement. The principle underneath is not opinion: fencing is done by location.
revenue-workspace/ <- this is the folder you grant
00-inbox/ raw drops, nothing trusted, cleared weekly
10-data/ working copies of exports, redacted per the boundary rules
20-briefs/ the durable briefs. This is where reusable work lives.
30-output/ everything Claude produces, by workflow and date
40-reference/ ICP rules, field definitions, stage definitions, policies
50-runs/ run records, one line per run
CLAUDE.md the folder's standing instructions
data-boundary.md the fence decision record
And, outside the workspace and never granted:
~/revenue-private/ comp, personnel, legal, board, anything under a restriction
Why each folder earns its place:
00-inbox/: so "somebody sent me a file" does not silently become "the agent has a file". Files leave on purpose, after the Lesson 2 gate.10-data/: copies, never originals. If a run modifies something, let it be a copy.20-briefs/: no memory between sessions means a brief that lives only in a chat is thrown away. Reusable work survives here.30-output/: generated files stay separate from sources, so "what did it produce" is answered by looking, not remembering.40-reference/: the definitions that make outputs comparable across weeks.50-runs/: your own audit trail, because the enterprise one does not cover Cowork yet.
The line that matters most is the last one. ~/revenue-private/ is not protected by a rule.
It is protected by not being in the granted tree. "Do not read the comp file" is a request. A
folder that was never granted is a boundary.
Try this now Create the seven folders and the two empty files, plus
~/revenue-private/outside the tree. Four minutes. You fill them in Lesson 2.
Check yourself: for each of your seven folders, one sentence on why it is inside the boundary.
Run the visibility probe
The single most useful thing you will do in this module.
Try this now
- Put a copy of your practice pack's
data/folder in10-data/.- Start a session. Grant
revenue-workspace/and nothing else.- Paste this:
List every file you can read under this folder, as a tree, with the size of each.
Do not read the contents of any file. Do not summarise anything.
Just the inventory.
If it starts summarising anyway, say: "Stop. Do not read any file contents. Only list the tree."
Why this prompt? An inventory, not a summary, so you learn what is reachable before anything is read. A tree, because the item that catches people is never at the top level: it is three levels down inside a folder somebody copied in whole. And do not read the contents, because the point is the perimeter, not the data.
What you should see: on our run, eight CSV files and DATA-DICTIONARY.md at the top of
10-data/, plus 10-data/notes/call-notes/ and 10-data/notes/qbr/ holding sixteen call notes
and three business reviews. That last part is the finding: one copied-in data folder also handed
over nineteen unstructured documents nobody had thought about. On a real revenue laptop, that is
the whole problem in one sentence.
Now read the tree against your intent, line by line, and mark each line keep, move or fence. The line you skim past is the one you would have skimmed past on your own machine.
When this goes wrong
You will create the hazard yourself: your file, invented on the spot, nothing sensitive, same result for everyone.
Try this now
- Inside the granted tree, create
revenue-workspace/10-data/_private/decoy-comp-sheet.mdand paste exactly these three lines:
Rehan Osei, Enterprise AE, on-target earnings 180000
Marta Lindqvist, Enterprise AE, on-target earnings 175000
Q3 accelerator threshold, 108 percent of quota
Invent nothing further and use no real name.
- Add this line to
revenue-workspace/CLAUDE.md:
Never read anything under 10-data/_private/.
- Start a new session, grant
revenue-workspace/, and ask:
Summarise everything in this working folder, one line per file, including
anything under subfolders.
What you should see: the summary references the decoy, by filename or by content. If it does not on your first try, ask: "list every file that contains a person's name". The instruction did not create a boundary, because an instruction is a request and the folder grant is the boundary.
Note what did not happen. Nothing malfunctioned. Nothing was bypassed. The agent did what a diligent colleague would do with a folder you handed over and a polite note asking them not to look in one drawer.
The guard. Move _private/ into ~/revenue-private/. Re-run the identical request. The
decoy is not summarised. Notice the difference in kind: nothing blocked it and no rule was obeyed.
The file was outside the perimeter, so there was nothing to obey. That is a boundary, and it is
why data-boundary.md is about locations, not rules.
Delete the decoy when done. Write one line in data-boundary.md recording that you ran this and
what happened.
What you keep
revenue-workspace/, scaffolded: seven folders,CLAUDE.mdanddata-boundary.mdcreated (near-empty is fine until Lesson 2), and~/revenue-private/outside the tree.data-boundary.md, started: granted list, fenced list, and one dated line recording the decoy test and its result.
Check yourself
- A colleague says their setup is safe because their
CLAUDE.mdtells the agent never to open the commission folder. Give the shortest accurate response, then the fix. - You are handed this tree and asked what must leave before access is granted:
revenue-workspace/10-data/holdingpipeline-export.csv,contacts-full.csv, andprojects/renewals-q3/which itself containsrenewals-q3.xlsxandlegal/msa-redlines.pdf. Name what leaves, what may stay but should be read-only, and the one item most people miss. - Someone widens the pre-approved area to stop the permission prompts on a long hygiene run. Name what they bought and what they paid.
Answers
1. That is an instruction, not a boundary, and you watched one fail in this lesson. The fix
is location: move the commission folder into ~/revenue-private/ and re-run the visibility probe
to confirm it is gone. Keep the CLAUDE.md line as documented intent, but stop counting it as
the control.
2. Leaves: contacts-full.csv (direct contact identifiers are not needed for renewal
analysis) and projects/renewals-q3/legal/msa-redlines.pdf (contract material under a
restriction). May stay, read-only: pipeline-export.csv and renewals-q3.xlsx, which are
the job. Most missed: the redlines PDF, two levels down inside a copied-in project folder,
not at the top where you would see it.
3. They bought fewer interruptions on one run. They paid a permanently larger blast radius on every run in that area, including ones not yet written.
Where this goes next
Next lesson: what may enter 10-data/ in the first place (the redaction gate), and standing
instructions at two levels so the folder itself carries the rules.
Track labs: Part A of the exercise sheet in labs/LAB-02 of your practice pack (start with
its README) runs the visibility probe, the decoy test and the guard as a measured sequence.
CP-02, the module quiz in the interactive app, hands
you a folder tree and asks what comes out.
Checked against Cowork in August 2026.