Exhibits

These exhibits hold the details behind the story. Read them when a story page points here.

About this case, in full

• The story is fiction. The firm, the client, the bank, the people, the figures and the times are made up.
• The product facts were checked. What each part of Claude can do comes from Anthropic's help pages, checked in November 2026 for this case and for the earlier sections it builds on. Each fact has a note with its source.
• The joining was not replayed. Nobody ran this exact setup on a Team plan for this case. The run times (25 minutes, 6 minutes) and the line counts are illustrative. The practical run sheet says how to test it.¹
• Eight things the story assumes. A chat in a project can read a connected drive, and save a file there. It runs the matching as a program on the cloud computer.² A run updates existing artifacts when it is given their links.³ Three people on a Team plan can share one project, one skill and the four pieces. The worker in Slack can run one more routine, as it does in Case 3, and read the latest run note in the drive.⁴ A sheet can hold the month's 6,800 lines. The lab's free path works as written. The run sheet tests each one.
• The matching rule is simplified. Real matching also uses reference numbers, payment types and names, and treats every unclear pair as a question for a person.
• It is not accounting advice. A real bank reconciliation, and a real promise to a lender, have more detail than one figure. A real bank would usually date a returned check in October, the day it came back. The story dates it September 30 to keep the sums simple. And a real promise to a lender is usually tested in a more detailed way than one adjusted bank balance. The $195,000.00 rule here is made up for the case.

Exhibit 1: Where the earlier sections appear in this case

Exhibit 2: The setup, part by part

Exhibit 3: The project's instructions

Lakeshore month-end. You prepare the month-end pack for Lakeshore Supply, Cleveland. The pack is for Lakeshore's bank.

Files. The month's bank lines and ledger are in the shared drive, in Lakeshore/ and then the month, for example 2027-09. Use the newest bank file. If it was downloaded more than a day ago, stop and say so. The bank's letter and the layout the bank wants are in this project's files.

Method. Match each bank line to a ledger line with the same amount and a date no more than five days apart. Use the name or check number too, where there is one. If a bank line could match more than one ledger line, pair it with one, and list the pair under Needs a look. List every line that has no match. Work out reconciled cash: the bank's closing balance, plus deposits the bank has not shown yet, minus checks the bank has not paid yet. Save the matched list to the month's folder.

The pack. Update these four pieces, and do not make new ones: the sheet [link], the memo [link], the slides [link], the cover [link]. Write the memo with the month-end memo skill. Slide 2 shows reconciled cash and the bank's minimum, side by side. The bank's minimum is $195,000.00.

Run note. After every run, save a note to the month's folder: the files you read, the number of lines matched, the lines left over, reconciled cash, and the pieces you updated. If this is not the first run for the month, say what changed.

Never. Never send anything to anyone. Never change a file in the drive that you did not make. If the bank and the books do not agree, say so in the first line. Nisha or Sana approves every pack before it leaves the firm.

Two sentences were added during the week: the one about slide 2, on Tuesday, and the one about the age of the bank file, on Friday.

Exhibit 4: Sana's skill

Month-end memo. Use this when asked for a month-end memo.

1. The first line is the status. Write READY when reconciled cash agrees with the cash balance in the ledger and nothing is unrecorded. Write NOT READY when anything is unrecorded.
2. A timing item is in the ledger and not yet at the bank: a deposit the bank has not shown yet, or a check it has not paid yet. Count them. Do not list them unless asked.
3. An unrecorded item is at the bank and not in the ledger: a returned check, a bank fee the company has not entered yet, a payment nobody entered. List each one directly under the status, with its date and amount.
4. Then give reconciled cash, and how far it is above or below any minimum the client must keep.
5. Never write that the books are correct. Write what was compared, and what agreed.

Exhibit 5: The request and the run note

The request, Tuesday, 10:05 a.m.

"Prepare the September 2027 month-end pack."

The run note, Tuesday, 10:30 a.m. (illustrative)

The run note, Wednesday, 10:00 a.m. (illustrative)

Exhibit 6: Two runs

Exhibit 7: The week

Cleveland is nine hours behind Karachi in October.

Exhibit 8: By hand, and with the setup

All times are illustrative.

Exhibit 9: Hamza's four tests

None of them uses Claude.

Exhibit 10: A document editor and a workplace

This table is fair only if you read it both ways. A firm can also build a job like this around other tools. We did not test Google's AI features for this case. The point is not which editor is better. It is the difference between a place to write and a setup that does the job.

Exhibit 11: Three answers for the owner

All figures are made up. Twenty packs a month: four companies, each with one month-end pack and four weekly packs.

And the line Nisha drew, for how far a task may run alone.

Exhibit 12: Before you trust a setup

1. Can you say what each part is for? One line for each: the project, the skill, the files, the schedule, the artifacts.
2. Where does each file live, and which jobs can reach it? A job that must run without you cannot rely on a folder on your computer: it can be read only while the desktop app is open.
3. What lasts after the desk is cleared? The method, the matched list and the run note must be saved somewhere else.
4. Which rules are sentences, and which are settings? For example, which connected apps are turned on is a setting. A sentence asks. A setting stops. Know which rules have only a sentence.
5. Does every run update the same pieces? Give the run their links, and check that it did not make new ones.
6. Do the pieces agree? No piece reads another.¹⁵ Open each one.
7. Who checks, and without what? At least one check must not use the AI.
8. Who approves, by name, and what does the approval name? The pack and its figure.
9. What does the morning check do when it finds something? Reports, and changes nothing, is the safe answer.
10. How many times has it run? A setup that has run three times has not been tested by a strange month yet.
11. Who may change the method, and who reviews the change? The instructions and the skill are the method. Keep a record of each change: who made it, when, and who agreed. 15.3 GitHub and the pull request shows one way.

Exhibit 13: Claude and ChatGPT side by side

Lakeshore works in ChatGPT. The same setup can be built there.

The ChatGPT names come from ChatGPT 2.0, Set up the apps and Build Something. The names differ, and so do the plans that include each part. The four rules in The case at a glance are the same.