--- title: "Working Session: Scope, Owned Files, and Build Credit." description: "Map one recurring job in a working session with files you own. The session is the first step of a paid engagement. Start with a written brief." canonical: "https://scalewithsearch.com/audit" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [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) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Stop re-introducing your business to the AI you already pay for. When the job needs working through first, one session on your screen maps one recurring job as files you own. [Send your brief](/work#send-your-brief) Your current AI product may preserve a useful session history. It is held in the vendor's account, under the vendor's terms, and it cannot tell you which model read what. The missing piece is a record you maintain: the facts, decisions, corrections, and boundaries the work needs. A new task can still begin with reconstruction: which client this is, what you charge, what changed last month, and which exceptions control the answer. The model remains replaceable. The operating record stays with you, and it names what touched it. CLIENT / CONTENT MAP source:: crawl 2026.08.02 decision:: consolidate service pages correction:: blog post pricing page canonical boundary:: approved briefs only Loaded before response PERSONAL / HOME PURCHASE source:: loan estimate 08.12 decision:: 33yr fixed, locked OPERATIONS / SALES DB source:: crm export 08.11 decision:: reassign stale at 30d OPERATIONS / SALES DB source:: crm export 08.11 decision:: reassign stale at 30d PERSONAL / HOME PURCHASE source:: loan estimate 08.12 decision:: 33yr fixed, locked CLIENT / CONTENT MAP source:: crawl 2026.08.02 decision:: consolidate service pages correction:: blog post pricing page canonical boundary:: approved briefs only Loaded before response ## Already running an AI assistant on your own notes? Then the setup is behind you. One person, one business, one folder of notes the model reads first, and a month in it holds most of what you know. That arrangement works until the second thing arrives. A second client, or a second business, is where a one-person vault leaks. Corrections written for one account start steering answers for another. Sources nobody named get read anyway. There is no line that says this job may see these files and stop here. The folder grew; the boundary never did. The session draws that line for one job, tests it against real output, and hands you the files that hold it. ## Three contexts. One source boundary. My work moves between client content, business systems, and personal projects. The useful separation comes from files that identify the active context, allowed sources, current decisions, corrections, and approval boundary before an agent begins. Without that record, the same job begins with search and reconstruction. With it, the agent starts from a named source set, produces an output that can be checked against a written finish line, and leaves a line saying which sources it read to get there. The model never got better at knowing me. The files did. ## The re-explanation disappears. Same request, two arrangements. On the left, the constraint is typed again and still missed. On the right, it lives in a file the model reads first, and the correction outlives the chat. Before · every session typed again I run an SEO agency. My client is a chiropractic practice. Last month we crawled the site, found 41 thin service pages, and decided to consolidate them instead of publishing new ones. The pricing page is canonical for any cost query, not the blog. Standard brief format is problem, evidence, structure. Also remember the client tone is plain, no hype. OK so now: write me a content plan for their knee pain services. Great idea! Here is a 12-post blog series targeting knee pain keywords, starting with "How Much Does Chiropractic Care Cost?" as a new blog post to capture pricing searches ... The decision it was just told, missed in the same session. After · the owned record grounded 2026.08.02-crawl-findings.md decision:: consolidate 41 thin service pages decision:: pricing page canonical for cost queries boundary:: no new posts without an approved brief client-context.md source:: [[2026.08.02-crawl-findings]] governs content decisions grounded-output.md Plan: fold the knee pain service pages into one canonical page per the 08.02 crawl decision. Cost questions route to the pricing page, not a new post. One brief attached for approval. corrections.md survives the next run 2026.08.05 model proposed a pricing blog post; corrected: pricing page canonical. This entry loads on every future run. Demonstration specimen. Synthetic, drawn from the shape of real work; no client material. Inspect the files 2026.08.02-crawl-findings.md client-context.md grounded-output.md corrections.md ``` --- type:: crawl-findings date:: 2026.08.02 client:: [demonstration] --- # Crawl findings - 41 thin service pages splitting one topic's authority - decision:: consolidate service pages into canonical topic pages - decision:: pricing page is canonical for any cost query, not the blog - boundary:: no new posts without an approved brief ``` ``` --- type:: client-context last_verified:: 2026.08.11 --- # Client context - tone:: plain, no hype - source:: [[2026.08.02-crawl-findings]] governs all content decisions - brief format:: problem, evidence, structure - correction history:: [[corrections]] The model reads this file before answering anything about this client. ``` ``` # Content plan: knee pain services Per [[2026.08.02-crawl-findings]]: 1. Consolidate the knee pain service pages into one canonical page. 2. Cost questions route to the pricing page, not a new post. 3. One brief attached, awaiting approval per the no-new-posts boundary. Every claim above cites its source. Nothing here was re-explained. ``` ``` # Corrections - 2026.08.05 :: model proposed a pricing blog post; corrected: pricing page canonical for cost queries. Entry loads on every future run. A chat forgets this by tomorrow. A file never does. ``` Demonstration specimen. Synthetic, drawn from the shape of real work; no client material. [Download the specimen (.zip)](/specimen/working-session-specimen.zip) ### Not buying today? The specimen. Download it, read the file order, and apply the shape to one of your own recurring jobs. Name the job. List the sources it is allowed to read. Write the stopping point. The step where your own sources refuse to fit the shape is the step people give up on. That step is the session. ## You already know the tax. "I know we solved this before. I can't find it." "The information is somewhere. I'm still the only search engine." "It gave me a clean answer that missed why the situation is complicated." You carry more than one operation in your head. Your depth is why everything works, and why nothing moves without you. That's not a discipline problem. You can't search your own thinking. ## What you are about to ask. "I'd have to send you client files." You send one bounded sample for the one job, with credentials and unrelated material removed. Anything you mark excluded in the intake is never requested. My working copy is deleted when the files ship. "I already have a vault." Then you have the folder, not the boundary. A vault built for one person and one business starts leaking at the second client: shared corrections, unnamed sources, no stopping point. This draws the line the vault never had. "Where does my material actually run?" Read the next section. It runs in hosted accounts, and I name them before you send anything. Nothing about that arrangement is hidden, and none of it changes without this page changing first. "All that for markdown files?" For the decision of which files, holding what, read in what order, tested against one real output. The markdown is what the decision fits in. The working session is part of the scoped price, not a separate fee. "Async, so who do I ask when it breaks?" Me, by email, with a reply within one business day. The work opens with a session on your screen, so the person answering has already watched your setup run. ## Start with the brief. If the result and the acceptance line are already clear, skip the session and [send your brief](/work#send-your-brief). Scope and prices are on [/work](/work). Download the free [Business Memory Starter Kit](/kit/business-memory-starter-kit.zip). You can prepare the six-question brief without buying anything. ## What the working session is. One working session on your screen, then the files, then me on email with a reply within one business day. The working session is the first step of a paid engagement. It happens after you accept the written scope and pay. For an AI system, it is the study included in the first function. For a website, it is part of the build price. It starts with a map of where your context lives and a list of your most expensive recurring reconstructions. Those pick the job. Then one path runs to the handoff: map-of-your-context.md + task-brief.md → pick the job ARCHIVE SAMPLE You send a bounded sample; the map and task brief pick the job. your-archive/ RECURRING JOB The thing you re-explain most, written into files the agent reads first. client-context.md sources/ GROUNDED OUTPUT One real output produced through the path, claims cited. grounded-output.md HANDOFF Run it, correct it, stop it. In writing. Yours. handoff.md harness-prompt.md install-plan.md corrections.md ARCHIVE SAMPLE You send a bounded sample; the map and task brief pick the job. your-archive/ RECURRING JOB The thing you re-explain most, written into files the agent reads first. client-context.md sources/ GROUNDED OUTPUT One real output produced through the path, claims cited. grounded-output.md HANDOFF Run it, correct it, stop it. In writing. Yours. handoff.md harness-prompt.md install-plan.md corrections.md You keep the delivered files, retrieval method, correction path, approval rules, and stopping point. ## Run your number. What does an hour of your judgment bill at? Count the hours this month you spent re-introducing yourself to software you already pay for. Then compare it to the prices below. A prompt is a sticky note. This is a filing cabinet the agent reads on its way to the keyboard. This month Hours re-introducing yourself ___ hrs × your hourly judgment rate $___ Your number $_______ AI function, study included in the first from $7,500 Small website, SEO setup included $1,500 to $2,500 Gallery, CMS, or multi-location website $3,500 to $5,000 Website changes after two revision rounds Priced in the written scope Compare that to your number. Start with the brief. The written scope states the fixed amount before work starts. Yes ✓ You re-explain the same context to software you already pay for, every session. ✓ You'll open real files, not a sanitized folder. ✓ You run more than one client, brand, or business out of the same head. ✓ You can name the one job you would hand over first if it were safe to hand over. ✓ You want the work to end in a build, not a report. No × You want AI to run the business unattended. This prepares the work; you keep the judgment. × You want a prompt pack. Prompts set behavior. A business record sets the facts. This builds the second one. × You cannot share real material yet. A session on a sanitized folder returns a sanitized result. ## What happens to your material. intake.md → you draw the boundary STAYS LOCAL Anything you mark excluded in the intake is not sent and is not requested. excluded/ BOUNDED SAMPLE SENT What you send is processed in hosted accounts I run my own business on, and I will name which ones before you send anything. I do not resell or republish your material. If where it runs changes, this page says so first. your-archive/ WORKING COPY DELETED My working copy is deleted when the files ship. working-copy/ ORIGINALS + OUTPUTS KEPT You keep the originals, the context files, the outputs, and the instructions. That's the point. client-context.md grounded-output.md handoff.md corrections.md STAYS LOCAL Anything you mark excluded in the intake is not sent and is not requested. excluded/ BOUNDED SAMPLE SENT What you send is processed in hosted accounts I run my own business on, and I will name which ones before you send anything. I do not resell or republish your material. If where it runs changes, this page says so first. your-archive/ WORKING COPY DELETED My working copy is deleted when the files ship. working-copy/ ORIGINALS + OUTPUTS KEPT You keep the originals, the context files, the outputs, and the instructions. That's the point. client-context.md grounded-output.md handoff.md corrections.md ## Evidence. In search since 2013. The method is public and the reference repositories are open. I run this architecture in my own operation, on my own hardware where the hardware can carry it, and the parts that are still hosted are named above. Client results are not published as proof. [pretool-memoryPre-tool retrieval from local search indexes; handled failures exit clean.pretool-memory.shReads the live transcript, hashes the last thinking block, searches a local BM25 index and an FTS5 session record, injects matches as context. If the index is unavailable the run continues without injection.Inspect →](https://github.com/b2bvic/pretool-memory)[safe-apiEvery write leaves a receipt.safe_api.pyDry-run default, one record per transaction, duplicate guard, circuit breaker, JSONL audit trail, incident file on breaker trip.Inspect →](https://github.com/b2bvic/safe-api) [Inspect the architecture on GitHub](https://github.com/b2bvic/owned-record) ## Stop being the only search engine for your own judgment. After the session The job you named opens from a file instead of from your memory. The sources it may read are listed, and the ones it may not are listed too. You have one output that was checked against those sources, and an install plan that says where each file goes. When the next correction comes, it goes in the record once and stays there. map-of-your-context.md + task-brief.md → pick the job → handoff What you receive map-of-your-context.md context map task-brief.md task brief client-context.md the facts, decisions, and boundaries for this job grounded-output.md grounded output, checked against the named sources handoff.md handoff harness-prompt.md system prompt file install-plan.md install plan corrections.md corrections You keep the delivered files, retrieval method, correction path, approval rules, and stopping point. Session terms The working session is the first step of a paid engagement. It happens after you accept the written scope and pay. For an AI system, it is the study included in the first function. For a website, it is part of the build price. Every engagement is paid in full before work starts. All sales are final. [Send your brief](/work#send-your-brief)[Prepare your six-question brief](/work#prepare-your-six-question-brief) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```