--- title: "CLAUDE.md vs context.md: Rules and Business Records." description: "Compare CLAUDE.md vs context.md for business work. Separate instructions, current facts, task briefs, and enforced permissions, then test the scope." canonical: "https://scalewithsearch.com/articles/context-file-vs-claude-md-business-project" date: "2026-08-26" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Context File vs CLAUDE.md: Business Facts or Agent Work Rules. A business puts prices, client status, shell commands, style rules, and private exclusions into one `CLAUDE.md`. Every coding session loads the file. Prices go stale beside stable tool rules. Client details cross into unrelated tasks. A prose warning looks like an enforced permission, but nothing enforces it. Use `CLAUDE.md` for concise standing instructions about how Claude should work in a scope. Use context files for current business facts a job may need. Use a task brief for the job, source order, output, test, and stopping point. Use permissions and operating-system controls for enforced denial. ## CLAUDE.md tells the agent how to work Claude Code's documentation describes `CLAUDE.md` files as user-written persistent instructions. It supports organization, user, project, and nested scopes. The documentation also says this content is context, not enforced configuration. [Claude Code: Memory](https://code.claude.com/docs/en/memory) Good standing instructions include: - repository layout and build command; - naming and formatting conventions; - required tests before handoff; - canonical source directories; - output and receipt locations; - broad approval and stopping rules; - pointers to narrower job briefs. Do not turn the file into a company encyclopedia. Every standing line competes for attention and may apply to tasks that do not need it. The [business CLAUDE.md template](/articles/claude-md-template-business-context) provides a full example with sources, exclusions, outputs, approval, and verification. ## Context files tell the agent what is true A context file contains maintained facts for a business, client, project, or job. Examples include the current offer, approved client state, active decision, glossary, service boundary, or work log. Each consequential file needs an owner, effective date, source role, and correction path. The file should say whether it is current, reference-only, superseded, or synthetic. Context should load only when the job needs it. A global instruction file does not need the current price for every client, nor every project's open blocker. The [context manifest template](/articles/ai-context-manifest-template) lets several agents share a structured inventory of sources, roles, scope, load conditions, and exclusions. ## Use a task brief for the recurring job Neither `CLAUDE.md` nor a general context file fully defines a recurring result. The task brief names the job, reader, inputs, source precedence, output, acceptance checks, approval owner, stopping point, and receipt. It can reference the standing instructions and current context without duplicating them. For example, `CLAUDE.md` may require draft-only external communication. `clients/ACME/current.md` holds the approved client state. `jobs/weekly-update.md` tells the agent to prepare this week's draft from that state and names the exact acceptance list. When the current fact changes, edit the context record. When the job changes, edit the brief. When the workspace-wide work rule changes, edit `CLAUDE.md`. Keep a change receipt for each class. An instruction change should name the repositories and workflows it affects. A context correction should name the superseded fact and downstream outputs. A brief change should name the acceptance behavior that changed. Then one edit cannot silently change unrelated work. ## Inspect `context-vs-instructions-map.csv` Route each item by responsibility. ```csv item,class,scope,authority,load_condition,owner,update_trigger,destination run_npm_test,work_rule,repository,standing,every_code_change,engineering,toolchain_change,CLAUDE.md current_offer_price,business_fact,offer,current,quote_job,offer_owner,approved_price_change,context/offers/current.md client_approval_status,business_fact,client_job,current,active_client_only,account_owner,status_change,clients/CLIENT-ID/current.md prepare_weekly_update,job_contract,client_job,approved,weekly_update_run,account_owner,workflow_change,jobs/weekly-update.md deny_production_write,enforced_control,system,policy,all_runs,system_admin,permission_change,.claude/settings.json ``` The last row matters. A sentence in `CLAUDE.md` can instruct the agent to avoid production writes. The actual denial belongs in permission configuration, sandboxing, credentials, or tool design. Do not place secrets in any of these files. Point to a sanctioned secret-management route without printing the value. ## Keep volatile facts out of standing instructions Volatile facts create stale global context. Prices, availability, owners, campaign status, and client decisions change on their own schedules. Move them into current records. Let `CLAUDE.md` say, “Use the current approved offer from `context/offers/current.md`.” The standing rule stays stable while the owned source changes through review. This makes errors diagnosable. If a quote uses an old price, inspect retrieval and the offer record. If the agent skipped the test, inspect instructions and the harness. If a prohibited tool ran, inspect the enforced control. Do not copy the same fact into several scoped instruction files. Multiple copies create hidden precedence disputes. ## Route global, project, task, and client scope Use the narrowest scope that serves every intended reader. Organization instructions cover mandatory enterprise conventions. User instructions cover personal preferences that do not weaken organization policy. Project instructions cover one repository. Nested rules cover a subdirectory. Task briefs cover one job. Client context covers one resolved client identity. Claude Code documents recursive discovery for `CLAUDE.md` and path-scoped rules. When you diagnose scope, run `/memory` to list the instruction files that loaded. Keep files concise and specific. Resolve the active business and client before reading their context. Do not search every client directory and ask the model to choose. Treat examples as a separate source class. Label them `format_only`, `synthetic`, or `approved`. A polished old example should not supply current facts. If the agent cannot tell whether an example's contents are reusable, the task brief should require a stop. The [minimum-context guide](/articles/what-context-should-an-agent-read) shows how to load required sources first and widen only on a grounded miss. ## Run the routing test list 1. Create synthetic global, project, task, and client files. Put a 47-dollar offer in `context/offers/current.md`, standing rules in `CLAUDE.md`, and the quote job in `jobs/quote.md`. 2. Map every item to one responsibility. 3. Start a fresh session at the repository root. 4. Inspect which instruction files loaded. 5. Run the task and cite the current context file. 6. Change the approved price to 52 dollars without editing `CLAUDE.md`. 7. Apply a correction and rerun. 8. Add an archived 47-dollar price. Require the 52-dollar current value, source path, and correction ID. 9. Request a production write denied by the test permission configuration. Confirm zero writes, not merely refusal text. 10. Start from a nested directory and inspect scope. 11. Remove one required context file and expect a blocked receipt. 12. Give the task brief and context to another agent. Pass requires the changed fact, stable standing rules, archive rejection, enforced denial, missing-source stop, and equivalent replacement result. ## Approval and stopping boundary The setup may create synthetic instruction files, context records, task briefs, test permissions, local drafts, corrections, and receipts. It stops before granting production access, weakening permissions, loading broad client folders, storing secrets, changing organization-managed policy, or applying the template across repositories. The repository owner approves instructions. The business owner approves current facts. The system administrator approves enforced controls. Some items fit none of the four classes: work rule, current fact, job contract, or enforced control. Leave those items out until their owner and scope are resolved. ## Sources - [Claude Code: Memory and CLAUDE.md](https://code.claude.com/docs/en/memory) - [Claude Code: Permissions](https://code.claude.com/docs/en/permissions) - [Claude Code: Settings](https://code.claude.com/docs/en/settings) ## Questions about Context File vs CLAUDE.md: Business Facts or Agent Work Rules? ### What should go in CLAUDE.md, and what should stay out? Put stable agent work rules, project conventions, required commands, and routing instructions in CLAUDE.md. Keep volatile business facts, current status, client records, and task-specific state in maintained context files or briefs that CLAUDE.md can point to when needed. ### Can I keep shared identity and project-specific context in Claude Code? Use the broad instruction layer only for rules that truly apply across projects, then keep each project's facts and work rules in its own scoped files. Test from the intended working directory to confirm that one changed fact is retrieved from the context source without leaking another project's state. ### Should project status and business facts live in CLAUDE.md? Keep current status and changing facts out of standing instructions because they become stale and consume the startup context on every task. Store them in a dated context file or task brief, name the update owner, and route the agent to that source only when the job needs it. ## Related: Agent Governance - [CLAUDE.md Template for Business Context: What Claude Code Should Read Before Work](/articles/claude-md-template-business-context) - [Stop AI from inventing client details with a verified client file and a stop rule](/articles/ai-keeps-hallucinating-my-details) - [Remove the context setup step that makes AI slow down your work](/articles/ai-workflow-bottleneck) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```