One job, three artifacts a crew can stand behind: the SOP they run, the list they buy from, and the text the customer actually gets. That is the track.
Why this matters
An SOP with no list will send a van missing the part. A priced list with no SOP will invent a helper. A cheerful text with no list will promise an arrival the truck cannot make. This capstone binds them.
The standard is a Russell Tech deliverable. A person could take Product A to the van, Product B to the counter, and Product C to the phone without repeating a number nobody typed.
This is still not geospatial. No CRS, no LAANC, no spray map, no flight card. If that is the job, you are in the wrong track.
Teach
Work in one thread named capstone — [job]. Paste the job SOP, the list table, and the customer text as sources. Tell Grok to reconcile, not to replace site facts.
Product A — Job SOP (crew-facing, one page)
Trigger, roles, steps, holds, comms, abort, sign. Headcount still matches the people you have. Still no clearance sentence. Still no invented permit, hour, or second tech. Pull forward the collection facts that affect the floor (ticket name, allergen card, which van).
Product B — List (parts or estimate)
The table from lesson 2, cleaned. NEED remains NEED unless you typed the cell. Header still says NOT A BID if you did not fill dollars. If the SOP says you do not have a helper, the list cannot include a second labor line as if you do.
Product C — Customer text (send-ready)
Four to eight lines. True now. No clock you did not type. If the list says the part is NEED, the text cannot say “we have it on the truck.”
Reconciliation rules
- If the SOP is two people, the list does not staff a third.
- If the list has hours NEED, the SOP does not print a 90-minute standard.
- If the part is not on the truck, the text does not give an on-site clock.
- If SOP and list disagree on the product (tank vs element, 80 vs 60), you decide. Grok does not average.
Attack pass. After the three exist, Grok plays a careless lead and a cheerful texter:
Attack this pack.
List:
- any person, permit, or "clear to start" the SOP should not have
- any SKU, price, hour, or tax nobody typed
- any ETA or "we have the part" the text should not have
- any CRS, LAANC, spray, or flight line that wandered in
Do not rewrite yet.
You patch one rail — usually a NEED that got filled — and reprint.
What you still own. Start, bill, send the text. Signatures. Whether this is a bid. Grok drafts. You sign.
What stays out. Gate codes, alarm PINs, the customer’s full phone if a job name will do, photos of kids or neighbors. Use a working title for the site.
Done. You could hand A to the second person without a speech. You could take B to the counter. You could send C. Write the date you will run them.
Worked example
Same water-heater job. Capstone thread gets the two-person SOP, the NEED-heavy list, and the “no clock, no element on the truck” text.
Grok’s first merge put “clear to start if the customer is home,” a $1,149 total, and “we’ll be back at 2:15” into the pack. The lead sent one message: “Delete every clearance, every dollar I did not type, and every clock. If the element is NEED, the text may not claim we have it.”
The reprint:
- SOP: two functions, holds for plate match, lockout, customer home; comms = text when leaving the shop; abort if the replacement does not match the plate. Sign line empty.
- List: NOT A BID; tank/plate match; expansion tank is a question; all prices and hours NEED.
- Text: behind; element not on the truck; will text when we leave; no dollars.
That pack can go to a van and a phone. The first merge could not.
Your turn
Open grok.com. One new thread. Same real job as the rest of this track — a changeout, a rush, a clean, a load-in, a bay. Not a mapping flight.
Exercise d-trades-l04-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 35 min |
Copy-ready prompts
Message 1:
I am in Grok Mastery (Russell Tech), Pathway D, Trades & local work, capstone.
Reconcile these sources for one job. Do not replace my facts.
[paste Job SOP]
[paste List table]
[paste Customer text]
Job name:
What I will hand the crew:
What I will send the customer:
Write:
A) Job SOP (six parts, crew-facing)
B) List (NEED remains NEED unless I typed the cell)
C) Customer text (4–8 lines)
D) Five-line join note: how SOP, list, and text cannot contradict
No clearance. No invented person, SKU, price, hour, or ETA.
No CRS, LAANC, spray map, or flight card.
Stop there.
Message 2:
Attack pass. Play a careless lead and a cheerful texter.
List invented people, permits, SKUs, prices, hours, ETAs, and any geo/flight line.
Do not rewrite yet.
Message 3 (after you name the patch):
Patch I accept: [one rail].
Reprint A, B, C, and D only.
Then:
- Van check: three lines the second person needs
- Phone check: the one sentence I will not text
- Session stamp: today's date and "Job pack written by Grok in this thread."
Artifact to paste
- The reprinted SOP, list, and text.
- The join note, the attack list, and the session stamp.
- Two lines from you:
I will run this on: plus a date or “already ran.”I will not text: plus the sentence you killed.
Rubric
- Pass: All three products are Grok-authored and stamped. Same real job. No unmarked price, SKU, hour, or ETA. No invented person. Attack pass exists. Not a drone/GIS pack.
- Fail: Three unrelated documents. A priced bid Grok filled. “We’ll be there in 20.” You typed it offline. Missing stamp. A flight SOP.
Common failure
The common failure is two jobs in one capstone. A kitchen SOP and a plumbing list. Bind them or drop one and start the thread over.
The other failure is polishing the text until it sounds like marketing. The customer needed the missing part and the missing clock. If they cannot see a NEED, you are selling fluency from the cab.
What’s next
This track is done when the SOP is on the clipboard and the text is the one you will actually send. If you also write public pages or run an inbox, Writing & comms and Business are separate four-hour paths.
