Organize the business context
Keep this job’s scope, people and requests together in a saved record.
See the job recordBusiness Repository / Product demonstrationFour notes. One clarification.
Controlled synthetic demonstration
Four notes. One clarification.
A crew handoff.
A flooring job has an extra request, an outdated approval rule and an unconfirmed arrival time. See the saved business context—and the handoff a fresh AI reader drafted from it.
Fictional business. Actual files and AI output. This operator-directed example uses the Existing Business Starter Kit’s document workflow. It is not a customer case study.
01 / Before
The details exist. They need to be understood together.
Cedar & Slate Flooring is a fictional six-person company. Its office note records accepted flooring work and a threshold replacement the homeowner only asked about. The old guide permits small extras; the office says that rule has changed.
- Owner orientation
Who does what and where job information lives.
- Office job note
Accepted scope, an extra request and details to confirm.
- Old crew guide
A historical extras allowance with disputed applicability.
- Supplier note
Material allocated; collection time still unknown.
One clarification resolves the old rule.
In a separately recorded, scripted owner reply, Maya states that every addition needs her written scope and price, followed by homeowner acceptance. The historical guide stays in the sources; its date alone does not decide which rule applies.
Read the scripted clarification02 / Repository
A record people can check and reuse.
The bounded build produced company and job records, a change-handling workflow, source references, open questions and a saved next step. These are readable files. The full Starter Kit build remains incomplete.
- Accepted work
- Living room and hallway flooring.
- Requested only
- Utility-room threshold replacement.
- Still unknown
- Collection time, arrival time and checked room clearance.
Read the complete job record, including correction history
Inspect the sources and change-handling workflow
The source register records all five inputs. These images show selected columns and complete workflow sections; the reading frame is an editorial presentation, not included product software.
03 / Use
A fresh AI reader drafts the handoff.
A new Codex process received a file-reading task without the earlier conversation or business facts in its prompt. It read the saved context and returned this crew card with source references.
“Arrival time: Not confirmed”
From the actual final handoff below.
Read the actual AI output as text
Unedited Markdown response from the final fresh-reader run. A draft for review, not authority to perform work.
> **CONTROLLED SYNTHETIC DEMONSTRATION** — Fictional company, job, and people. Not customer evidence or technical installation guidance. # Crew Handoff Card — CS-104 **Crew:** North — Owen and Lena **Visit day:** Thursday **Arrival time:** **Not confirmed** *Support: `knowledge/job-cs-104.md`; SRC-002, SRC-004, SRC-005.* ## Approved work - Install engineered oak in the living room and hallway. - Finish: Natural oak. - Keep existing skirting. - Stair work is excluded. *Support: `knowledge/job-cs-104.md`; SRC-002, SRC-005.* ## Requested, but not approved - Utility-room threshold replacement. - Maya has not approved or priced it. - The homeowner has not accepted revised scope or price. - **Do not perform this work unless the accepted change is recorded in the job folder.** *Support: `knowledge/job-cs-104.md` and `knowledge/scope-to-crew-visit.md`; SRC-002, SRC-005.* ## Responsibilities and change authority - **Crew/Owen:** Read the accepted scope and current job notes before the visit. Record any new request and refer it to Maya. - **Maya:** Provide written scope and price for every addition. - **Homeowner:** Accept the revised scope and price before added work begins. - **Nina:** Coordinate the visit and materials, then place any accepted change in the shared job folder. - The old guide’s under-$250 allowance is obsolete. There is **no small-extra allowance**. *Support: `knowledge/scope-to-crew-visit.md`; SRC-001, SRC-002, SRC-003, SRC-005. Contradiction history: `control/OPEN-ITEMS.md`, OPEN-001.* ## Unresolved details - Supplier collection time is not confirmed. - Neither the requested 8:30 arrival nor the old guide’s usual 9:00 time is confirmed. - Material is allocated, but allocation does not establish collection or arrival time. - The homeowner says the living room should be clear by Thursday; Nina has not confirmed that it is clear. - Access is reported through the side gate; no key code is supplied. *Support: `knowledge/job-cs-104.md`; SRC-002, SRC-004, SRC-005. Open matters: `control/OPEN-ITEMS.md`, OPEN-002 and OPEN-003.* ## Saved next step When Repository work deliberately resumes, ask Nina whether the supplier collection time is confirmed before stating an arrival plan. No contact is authorized by this demonstration. *Support: `control/NEXT-STEP.md`, CS-NEXT-001; linked to OPEN-002 and SRC-002/SRC-004.*Open the output file
Review caught a detail worth preserving.
An earlier saved job record compressed “should be clear by Thursday” into “reported clear.” The first AI draft repeated it. We restored the planned-versus-present distinction from the source, retained the earlier output in the audit evidence, and ran a fresh reader again. The final card above uses the corrected record.
What the example shows
Useful context, with a way to inspect it.
Show what supports it
Keep the old guide and the clarification behind the current rule visible.
See the source referencesKeep open questions visible
Record that material allocation has not established an arrival time.
See the unresolved detailsReuse the context for a task
Give a fresh AI reader saved files to work from, then review the draft.
See the actual handoffHow the demonstration was made—and what it does not prove
We extracted the unchanged released Existing Business Kit (Package.4) into an isolated workspace. The primary file-capable Codex session followed its document workflow with operator-written fictional sources and a scripted owner reply. This was an operator-directed build, not an independent customer trial.
A standalone startup attempt reported that it could not write files and stopped; no write attempt was logged. Follow-up testing reproduced a write denial and restored file access by correcting the test launcher’s Windows sandbox configuration. The released Kit was unchanged. The later fresh-reader task succeeded with read-only access to the saved records. That demonstrates bounded context reuse; it does not verify a full Kit restart or universal AI compatibility.
Screenshots are real browser captures of the actual Markdown artifacts in a plain editorial reading frame. Selected sections and source-table columns are identified in their captions. The frame is not an included application, dashboard or Viewer.
No customer results, measured savings, automatic updates, flawless AI, complete business coverage or New Kit concept-building performance are established by this example. Human review remains necessary. This is not technical flooring or safety guidance.
Read the method, file hashes and reuse limitsA controlled example of one reviewed workflow. No customer results, measured savings or guaranteed accuracy are claimed.
Choose your starting point
Build context around your business.
A Starter Kit gives you files and a guided workflow for a compatible AI environment. You supply the business knowledge and review what is saved.
Already operating?
The Existing Business Starter Kit starts with the business you run today. It is the Kit used for this example.
Explore Existing Business$199 one-time
Starting something new?
The New Business Starter Kit works from your developing business direction and evidence still needed. This example does not verify that separate workflow.
Explore New Business$199 one-time
Need help deciding where to begin? Book a complimentary 15-minute consultation.