# One place for Lakeshore (/claude-and-chatgpt-2/case-4-nishas-month-end/one-place-for-lakeshore) --- type: Document title: "One place for Lakeshore" description: "In one afternoon the firm builds the setup: a project for the rules, a skill for the method, files where a job can reach them, a borrowed desk for the matching, four artifacts for the result, and a scheduled task for the time." status: stable order: 0.82 ksor: owner: team:panaversity audience: [ public ] approval: by: process:panaversity at: 2026-11-12T13:13:29Z chapter: "F00G" part: Front expert_status: required concepts: [ "One place" ] last_verified: 2026-11-12 sources: - id: projects title: "Anthropic, What are projects? (Claude Help Center)" resource: https://support.claude.com/en/articles/9517075-what-are-projects - id: skills title: "Anthropic, How to create custom skills (Claude Help Center)" resource: https://support.claude.com/en/articles/12512198-how-to-create-custom-skills - id: local-task title: "Anthropic, Schedule recurring tasks in Claude Code Desktop (Claude Code Docs)" resource: https://code.claude.com/docs/en/desktop-scheduled-tasks - id: sandbox title: "Anthropic, Claude Cowork architecture overview (Claude Help Center)" resource: https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview - id: deck-export title: "Anthropic, What are artifacts and how do I use them? (Claude Help Center)" resource: https://support.claude.com/en/articles/17153992-what-are-artifacts-and-how-do-i-use-them - id: artifact-link title: "Anthropic, Share session output as artifacts (Claude Code Docs)" resource: https://code.claude.com/docs/en/artifacts - id: no-source title: "Anthropic, Get started with Claude Sheets (Claude Help Center)" resource: https://support.claude.com/en/articles/18324300-get-started-with-claude-sheets - id: tag-routine title: "Anthropic, Set up routines (Claude Tag)" resource: https://claude.com/docs/claude-tag/users/proactivity - id: owner-connectors title: "Anthropic, Use connectors to extend Claude's capabilities (Claude Help Center)" resource: https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities - id: docs-outside title: "Anthropic, Get started with Claude Docs (Claude Help Center)" resource: https://support.claude.com/en/articles/16923645-get-started-with-claude-docs generated: at: 2026-11-12T13:13:29Z by: process:panaversity trust_tier: unverified build_id: sha256:ee289d75a60f3acc7dc4cab134056c3f9c1ab9c4abdba810061b7f3810eb4d15 dirty: true ksor_version: 0.0.60 --- ## Monday afternoon > **New words on this page.** **Instructions:** text that Claude reads in every chat in a project. **Skill:** saved instructions that teach Claude one kind of job. **Borrowed desk:** a temporary computer in the cloud that Claude uses for one session. **Run note:** a few lines Claude saves after each run. **The morning check:** a job that looks at the bank's lines each morning. Nisha, Sana and Hamza sat at one screen, in the Claude desktop app. Then they built the parts, one at a time. Each part answers one question ([Exhibit 2](exhibits.md#exhibit-2-the-setup-part-by-part)). ## 1. Where do the rules live? In a project They made a project called **"Lakeshore month-end"**, and shared it among the three of them. It was an ordinary project, the kind on every plan, not the newer kind in beta.[^projects] A **project** keeps files and **instructions** together. Instructions are text that Claude reads in every chat in that project.[^projects] Nisha wrote the instructions in plain sentences ([Exhibit 3](exhibits.md#exhibit-3-the-projects-instructions)). They said who the client is, what the pack contains, where the files are, what the bank's minimum is, and what Claude must never do: *"Never send anything. 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."* *"Now nobody pastes the rules again,"* she said. *"And when a rule changes, we change it in one place."* ## 2. Where does the method live? In a skill Sana had a way of writing a month-end memo. She had saved it as a **skill**: instructions that teach Claude to do one kind of job her way.[^skills] She shared it with Hamza and Nisha. Her skill set the memo's first line. The line says **READY** when the bank and the books agree. It says **NOT READY** when they do not. Anything the bank shows and the books do not yet show is listed under it, as an **unrecorded item** ([Exhibit 4](exhibits.md#exhibit-4-sanas-skill)). *"A project is about one client,"* said Sana. *"A skill is about one kind of work. My memo method is the same for every client, so it is a skill."* ## 3. Where are the files? Where they already are The job needed two kinds of file. - **The files that change every month.** The bank's lines and the ledger. The worker already saved the bank's lines to the **shared drive** every Friday, and Lakeshore's ledger was there too, and the drive was connected to Claude. So Claude could read them there. - **The files that do not change.** Dana had emailed the bank's letter, the layout the bank wanted and last quarter's pack from her old accountant. Hamza had saved them in a folder on his computer. In the desktop app, he let Claude read that folder. Hamza wanted to keep everything in his folder. Nisha asked one question. *"What can read your folder when your laptop is closed?"* Nothing reliable. Claude reads a folder on a computer through the desktop app, and only while the app is open and the computer is awake. Some jobs started from the desktop app can use the folder too, but they lose it when the app closes.[^local-task] The worker in Slack cannot reach it at all. The morning check had to run at 9 a.m. every day, whether Hamza's laptop was open or not. So the monthly files stayed in the shared drive. There, any of the three people, and any job, could read them. They also copied Dana's three files into the project, so the setup did not depend on Hamza's laptop. The folder kept one job. Hamza downloaded the bank's own statement, its official list of the month's lines, into the folder himself. Later he would compare the setup's work with this file. So his test would not depend on the setup's own work. ![Where a file lives decides who can read it. A table with two columns, a folder on your computer and a connected shared drive. You, in the desktop app: yes for both. A job started from the desktop app: only while the app is open for the folder, yes for the drive. The worker's routine in Slack: no for the folder, yes for the drive. When your laptop is closed: no for the folder, yes for the drive. A band at the foot says your folder is for work at your desk, and a connected drive is for work that runs without you.](img/where-a-file-lives.png) > **Rule to remember:** where a file lives decides which jobs can read it. A folder on your computer is for work you do at your desk. A connected drive is for work that must run without you. ## 4. Where does the heavy work happen? On a borrowed desk Nobody can match 3,400 lines well by reading them. Claude does it another way. It writes a small program and runs it on a temporary computer in the cloud. This book calls that computer a **borrowed desk**. Claude uses it for one session. Then it is wiped clean.[^sandbox] *"Then next month it starts from nothing,"* said Hamza. *"The desk does,"* said Nisha. *"So the method must not live on the desk."* They added one line to the project's instructions: the matching rules, in words, and *"save the matched list to the drive folder for this month"*. ## 5. Where is the result? In four artifacts The pack would be four artifacts: a **sheet** for the numbers, a **doc** for the memo, a **deck** for the three slides, and a **design** (a one-page picture) for the cover. Hamza made an empty one of each, shared them with Nisha and Sana, and pasted their links into the project's instructions. Why artifacts, and not ordinary files? Sana could write comments on the memo in Claude. Every run would update the same piece, so there was never a folder of old copies. And the memo, the slides and the cover can each be saved as a PDF file when it is time to send.[^deck-export] Pasting the links into the instructions matters. A new chat makes a new artifact unless it is given the link of an old one.[^artifact-link] With the links in the instructions, every run should update the same four pieces. If a run ever made a new piece instead, Hamza would change the link in the instructions, so the list always showed which piece was current. Sana noticed one more thing. A doc or a deck cannot read its numbers from a sheet.[^no-source] *"So the figure is written into the sheet, the memo and the slides. They are three copies."* *"Written by one run, from one result,"* said Nisha. *"And checked by you. That is your first test: do the pieces agree?"* ## 6. When does it run? On a schedule The last part was time. A bank does not always finish the month on the first morning of the next one. Late lines can still arrive. So the firm needed **the morning check**: a job that looks at the bank's lines again each morning. The worker in Slack could already read the bank's lines. So Nisha gave the job to the worker, as one more **routine**. Remember: the worker is Claude running inside Slack, and a routine is a scheduled task that the worker runs.[^tag-routine] Her instruction said: - Every morning at 9:00 a.m., download the month's bank lines again. - Start the day after a pack is sent. Stop after Dana's meeting with Lakeshore's bank. - Compare the bank's closing balance with the one in the latest run note in the drive. - Post what you find in the firm's channel. *"If something changed, say what. Change nothing in the pack."* A routine is allowed to do whatever the worker is allowed to do.[^tag-routine] The worker can send email. Nisha wanted nothing in Claude itself to be able to send the pack. On a Team plan, members can use a connected app only after an Owner turns it on for the firm.[^owner-connectors] Nisha is the Owner. She turned on the shared drive and nothing else: no email, no Slack. So no chat in Claude, in this project or any other, can send an email or reach Slack. When a run needed new bank lines, a person asked the worker to download them. The worker is set up separately, in its Slack channel. ![One place for Lakeshore: the parts, joined for one job. On the left, three boxes feed the run: the project, the client's rules written once; the skill, the firm's method; the shared drive, the month's files. In the middle, the run, on a borrowed desk in the cloud, where Claude matches the lines with a small program and then builds the pack; the desk is cleared afterward. On the right, four pieces: the sheet, the memo, the slides and the cover. Below, two boxes beside the run: a folder on Hamza's computer, with the bank's statement he downloads himself, for tests the setup never touched; and the worker's routine in Slack, which every morning compares a fresh download with the latest run note. A band at the foot says people check, approve by name and tell the client.](img/one-place-for-lakeshore.png) ## What it cost The afternoon took the three of them about two hours each. Nothing in it was programming. Every part was a sentence, a file or a setting. The pack would go to Dana as PDF files, from `reports@`, as everything did.[^docs-outside] On Monday evening the setup had never run. Nisha did not trust it yet. *"Tomorrow we find out what we forgot."* [^projects]: As verified on November 11, 2026, Anthropic says projects "are available to all users, including those with free Claude accounts", that free users can make at most five, and that each project can have its own instructions and files. What are projects?, Anthropic. [^skills]: As verified on November 11, 2026, Anthropic says skills "are available for users on Free, Pro, Max, Ultra, Team, and Enterprise plans" and that this "requires code execution to be enabled". How to create custom skills, Anthropic. [^local-task]: As verified on November 9, 2026, Anthropic says a task on your own computer "only fires while the app is open and your computer is awake", and a cloud task "runs even when your computer is off". Whether a cloud session started from the desktop app can also use the folder while the app is open, this case has not checked; the practical run sheet tests it. Reading a folder on your computer needs a paid plan, as [Set up the apps](../new-way-of-working/set-up-the-apps.md) says. Schedule recurring tasks in Claude Code Desktop, Anthropic. [^sandbox]: As verified on November 9, 2026, Anthropic says that in cloud sessions "the agent loop and code execution run in an isolated, temporary sandbox on Anthropic-managed infrastructure", and that each session's sandbox is "created when the session starts and destroyed when it ends". Claude Cowork architecture overview, Anthropic. [^deck-export]: As verified on November 12, 2026, Anthropic says "Decks export to PowerPoint and PDF, or go straight to Google Slides as editable files." A doc exports as Word, PDF or Markdown, and a design as a PDF. What are artifacts and how do I use them?, Anthropic. [^artifact-link]: As verified on November 11, 2026, Anthropic says that to update an artifact from a different session, you give Claude its link: "Without either, a new session creates a new artifact instead of updating one." Anthropic's guide says this about artifacts made in the Code tab. This case assumes the same for a chat in a project, and has not tested it. Share session output as artifacts, Anthropic. [^no-source]: As verified on November 12, 2026, Anthropic says "Sheets can't pull live data from connected apps, and docs, decks, and dashboards can't use a sheet as a data source." Get started with Claude Sheets, Anthropic. [^tag-routine]: As verified on November 10, 2026, Anthropic says a routine in Claude Tag "uses that channel's connections with the same permissions as a typed request." [Case 3](../case-3-nishas-firm/overview.md) describes the worker and its channel. Set up routines, Claude Tag docs, Anthropic. [^owner-connectors]: As verified on November 12, 2026, Anthropic says that on Team and Enterprise plans "an Owner or Primary Owner needs to enable" connectors "for the organization" before members can use them, and that each person still signs in. Owners can also set each connector's actions to Always allow, Needs approval or Blocked, and members cannot override this. Connectors belong to each person's account, not to a project. Use connectors to extend Claude's capabilities, Anthropic. [^docs-outside]: As verified on November 12, 2026, Anthropic says "Docs can't be shared by email invitation on any plan" and "On Team and Enterprise plans, they can't be shared outside your organization by link either." Get started with Claude Docs, Anthropic.