Two things are still missing from the workspace you built in Lesson 1.
First, a rule about what may enter 10-data/ at all. Right now the answer is "whatever I
export". That is how a file with 911 contact rows, mobile numbers included, ends up inside the
perimeter for a job that needed account identifiers.
Second, the folder knows nothing. Every session starts from zero, so you restate your role and your rules Monday, Tuesday, and again next week. Module 1 showed you why: there is no memory between sessions. So give the folder a memory instead.
What you will be able to do
- Run a five-question gate on any export before it enters the granted tree, and record the decision.
- Write standing instructions at two levels and say which rule belongs at which level.
- Prove your folder file is actually being read, rather than assuming it.
The redaction gate
This is our policy, not a product claim. Nothing in Cowork asks for it. The directory boundary
only helps if you are deliberate about what goes inside it, and this gate stands in front of
every Part B lab in this course. Five questions, each with a default. Run them on every export
before it enters 10-data/.
| Question | Default | Why the default |
|---|---|---|
| Do I need direct contact identifiers for this analysis? | No. Use IDs. | Most revenue analysis joins on account_id and contact_id. Names, emails and phone numbers ride along out of habit, and they are the part you least want to see in an output file. |
| Do I need amounts at deal level? | Often yes. That is the job. | Do not over-redact. A pipeline analysis without amounts is not an analysis. Redaction that makes the work impossible gets abandoned within a week. |
| Is anything here restricted by a customer agreement or a regional rule? | Check, do not assume. | Some contracts and regions restrict where customer data may be processed. A question for your legal or privacy owner, not for you and not for this course. |
| Is anything here about employees rather than customers? | Fence it. | Comp, performance, headcount and personnel go to ~/revenue-private/ and are never granted. |
| Would I be comfortable if this file were copied verbatim into an output file by mistake? | If no, it does not enter. | The honest version of the four above, and the one that catches the file the others missed. |
Applied to the practice dataset: contacts.csv in your pack's data folder carries
contact_name, email and phone alongside contact_id, persona and last_activity_date
(see DATA-DICTIONARY.md in the same folder). In the
Module 1 snapshot work, personas and last activity dates earned their place. The phone numbers
were never needed once. The habit: name the columns the job needs, and know why the others came
along.
Check yourself: for the last export you pulled, which columns would not have entered?
Standing instructions, at two levels
A standing rule can live in two places, and putting it in the wrong one is the most common configuration mistake in this course.
Global instructions apply to every Cowork session: tone, output format, role background, standing safety rails. Third-party setup guides place them under Settings, then Cowork, with an edit control next to global instructions. That path comes from those guides, not from Anthropic's own documentation, so confirm the exact wording on your build.
Per-folder context files carry the rules that belong to this body of work. The documented
conventions are preferences.md or CLAUDE.md in the working folder. At session start, Claude
reads MEMORY.md for cross-project learnings and, inside a project folder, that folder's own
CLAUDE.md and MEMORY.md.
The split, as a rule you can apply without thinking:
Global for who you are and how you write. Folder for what this work is and what it must never do.
Worked both ways:
| Rule | Where | Why |
|---|---|---|
| "I am a RevOps analyst at a B2B SaaS company. Write plainly. No marketing adjectives." | Global | True in every session, including ones with nothing to do with revenue. |
| "Dates as YYYY-MM-DD. Money with its currency code. Never mix currencies in a total." | Global | A formatting habit you want everywhere. |
"Output goes to 30-output/<workflow>/<YYYY-MM-DD>-<name>.md." |
Folder | Only true inside this workspace. |
"Amounts in opportunities.csv are in the account's local currency. arr_usd is USD. Convert before comparing." |
Folder | A fact about this data, not about you. |
"Anything you cannot resolve goes to exceptions.csv with the row id and the reason. Do not guess." |
Folder | The single highest-yield line in this course. Module 4 teaches it properly. |
| "Never contact a customer directly." | Neither | It is an instruction, and instructions are not boundaries. Lesson 3 explains the real control. |
Worth knowing: memory here is a file convention, not a product feature. Cowork does not carry state between sessions. The folder does not remember. The folder is read.
Check yourself: which two of your own standing rules are at the wrong level right now?
Prove the folder file is being read
Most people write a CLAUDE.md, get a good output, and conclude it worked. Not evidence: a good
output is what you would have got anyway. You need a rule the agent could not have guessed and an
output that visibly obeys it.
So put a rule in CLAUDE.md that is arbitrary on purpose:
Output convention: every file you produce goes in 30-output/, named
<YYYY-MM-DD>-<workflow>.md, and its first line is exactly:
Source files: <comma-separated list of every file you read>
Nothing about that is guessable. If it appears, the file was read.
Then make a request that mentions none of it:
Count the accounts in 10-data/accounts.csv by region and by segment.
Write it up.
What you should see: on our run, 30-output/2026-08-02-account-counts.md, first line
Source files: accounts.csv. The obvious conclusion: the folder file is live. The better one:
you now get a provenance line on every output for free, permanently. It catches the case
where you are looking at last week's output and cannot remember which export it came from.
Module 4 builds the heavy version with run records.
Do not put the source-files rule in global instructions. It refers to a folder most of your sessions do not have, and a global rule that is usually wrong gets quietly deleted.
Worked exercise
Situation. You have the Lesson 1 scaffold and the practice dataset in 10-data/. Write the
two files that make the workspace yours, then prove one is being read. Budget five minutes. The
full build is Part A of the exercise sheet in labs/LAB-02 of your practice pack (start with its
README).
Setup
- Folder to grant:
revenue-workspace/. - Files in play:
10-data/accounts.csv,10-data/contacts.csv,10-data/opportunities.csv. - Connectors needed: none.
- Blast radius: read-only. One output file, inside your own
30-output/.
Steps
Try this now
- Open
templates/M2/data-boundary.mdfrom your practice pack and fill the granted list, the fenced list and the redaction defaults. One line of reason per folder. The reason is what counts, not the list.- Open
templates/M2/CLAUDE.mdand fill the four gaps below.- Start a session, grant
revenue-workspace/, and run the request in the starter brief, which mentions none of your conventions.- Open the output. Check it against your conventions, one rule at a time.
- If a rule was not obeyed, do not add emphasis. Ask why it was ambiguous, and rewrite it so it is checkable. A rule you cannot check from the output is a hope, not a rule.
Starter brief, with gaps marked
In CLAUDE.md:
# Standing instructions for revenue-workspace
## Role and voice
<<GAP 1: one or two lines. Who you are and how output should read. Keep this short:
anything true of every session belongs in global instructions, not here.>>
## What this folder holds
10-data/ holds working copies of exports. 20-briefs/ holds durable briefs.
30-output/ holds everything you produce. 50-runs/ holds run records.
<<GAP 2: two lines about THIS DATA that an agent could not know from the files alone.
Look at DATA-DICTIONARY.md for the two facts most likely to produce a wrong total.>>
## Output conventions
<<GAP 3: a naming and location rule specific enough that you can tell from the
output whether this file was read.>>
## Standing rules
- Do not modify anything in 10-data/. Write only to 30-output/.
<<GAP 4: the exceptions rule. One sentence. What happens to anything you cannot
resolve.>>
And the request to run, which mentions none of the above:
Using the files in 10-data/, tell me how many accounts are in each lifecycle
status, and what the total ARR is for the ones that are customers.
Hints
Hint 1, Concept. Three gaps are about you, one is about the data, and the data one is the only one that changes whether the answer is numerically right. Which numbers in the output could be wrong for reasons that have nothing to do with the agent's competence?
Hint 2, Move. Open DATA-DICTIONARY.md: the Conventions section and the opportunities
table. Two conventions there silently produce a wrong total if unknown: one about which currency
a money column is in, one about a type value whose amounts must not be added to another type's.
Write both into GAP 2 as facts about this folder.
Hint 3, Shape. A correct GAP 2 has two sentences, each naming a column. A correct GAP 3 produces something visible in the output that the request did not ask for: that is what makes it a test. A correct GAP 4 is one sentence and contains "do not guess". If your GAP 1 is longer than your GAP 2, you have written a personality profile, not a working configuration.
Reference artifact
The filled version ships with the LAB-02 solution in your pack's answer-keys/ folder, which
you open only after attempting the exercise. The two data facts GAP 2 is looking for, traced
to DATA-DICTIONARY.md:
opportunities.amountandpipeline_snapshots.amountare in the account's local billing currency, whileaccounts.arr_usdis in USD. Converting is the analyst's job. The fixed rates used to build the data are EUR = 1.08, GBP = 1.27, USD = 1.00.opportunities.type = Renewalamounts restate current ARR and must not be added to New Business when computing ARR.
Your role line, naming scheme, tone rules, choice of CLAUDE.md or preferences.md, and rule
count may all differ. What may not: if your CLAUDE.md contains no statement about this data
that changes a number, it is a style guide, and it will not stop the first wrong total.
The takeaway: the test of a folder file is not whether the output is good. It is whether the output shows you something you did not ask for in the request.
What you keep
revenue-workspace/data-boundary.md: granted list, fenced list, one reason per folder, redaction defaults. The pre-flight record and connector inventory come in Lesson 3.revenue-workspace/CLAUDE.md: role, folder map, the two data facts, output conventions, the exceptions rule.30-output/<date>-account-counts.md: the evidence that the folder file is read.
Check yourself
- Sort these into global, folder or neither: (a) "Never mix currencies in a total"; (b) "This company's fiscal year equals the calendar year"; (c) "Never send anything to a customer"; (d) "Write in British English". For any you put in "neither", say what the real control is.
- Your
CLAUDE.mdsays output goes to30-output/. A run wrote to the folder root instead. Give two explanations, and say which one you can rule out by looking at the file rather than by guessing. - An analyst redacts every column except
account_idandamountbefore granting the folder, then cannot answer any of the questions they were asked. Which of the five gate questions did they apply badly, and what does that cost in practice?
Answers
1, one line per option:
- (a) "Never mix currencies in a total": global. An arithmetic habit for every session.
- (b) "Fiscal year equals calendar year": folder. A fact about this body of work; noise anywhere else.
- (c) "Never send anything to a customer": neither. An instruction, and instructions are not
boundaries. The real control: no connector with send scope was authorised, recorded in
data-boundary.md. Keep the line anyway, to document intent. - (d) "Write in British English": global. How you write, true everywhere.
2. Either the folder file was not read at all (moved, renamed, or the session pointed at a
different folder), or it was read and your naming rule was ambiguous. Rule out the first by
looking at the file: if the output carries the Source files: line, which also comes from
CLAUDE.md, the file was read and the rule is the problem.
3. They applied question 1's default ("use IDs") to every column instead of to direct contact
identifiers, and never asked question 2, which exists to stop exactly this. Nothing in the gate
asks you to drop stage, segment or renewal_date. The real cost: over-redaction gets the
whole gate abandoned within a week, after which nothing is redacted.
Where this goes next
Next lesson: connectors at minimum scope, the dated pre-flight record, and the disclosed sandbox escape that makes the folder decision in Lesson 1 the control that survives a bad day.
Track labs: LAB-02 Part A proves CLAUDE.md works by running a request that depends on a
convention declared in it. CP-02, the module quiz in the
interactive app, sorts eight candidate rules across the
two levels.
Checked against Cowork in August 2026.