One job, two products a crew and an office can both stand behind: the SOP they run on the ground, and the brief they are allowed to say out loud about the map. That is the track.
Why this matters
A comms SOP without a brief is a safe crew with nothing to hand the superintendent. A pretty analysis without a SOP is a paragraph that does not know whether the south line was flown. The packet from last lesson is the spine. Today you bind the three.
The standard is the same as a Russell Tech deliverable. A person could take this to the tailgate Monday, and a person could take the brief into a call without repeating a number nobody measured.
Teach
Work in one thread named capstone — [job]. Paste the comms SOP, the analysis brief, and the ops packet as sources. Tell Grok to reconcile, not to replace site facts.
Product A — Field SOP (crew-facing, one to two pages)
Not a new novel. A cleaned SOP that a VO or rover can hold:
- Trigger, roles, steps, hold points, comms, abort, sign.
- The collection facts that affect the ground (mission file name, dictionary version, what “done” means before you leave the pad).
- Still no clearance sentence. Still no invented frequency, wind number, airspace class, buffer, or CRS.
If your job is not a flight, the SOP is still a field SOP: rover loop, scout walk, construction check, student field day. Same shape.
Product B — Analysis brief (office-facing, one page)
- What the image or layer is (date, type, what you measured).
- What you think you see, in language someone can refute on the PNG.
- Hypotheses and next measurements.
- Claim table: HOLD / WRONG / UNVERIFIED / NOT IN IMAGE / NEED-TO-MEASURE.
- Map contract pulled forward: what this product will not be used for.
If you have not flown yet, the brief is a pre-brief: what you will and will not claim after the collection, plus the measurements you will run before anyone talks to a client. Label it PRE-BRIEF. Do not write as if the mosaic exists.
Reconciliation rules
- If the SOP says the south lots were not flown, the brief cannot discuss those lots as if they were.
- If the packet says UNKNOWN CRS, the brief cannot publish coordinates.
- If the analysis invented 14.2 acres, it dies again here.
- If the SOP and the packet disagree on headcount or instrument, you decide. Grok does not average them.
Attack pass. After both products exist, Grok plays a careless analyst and a careless PIC: where would a fluent reader think they were cleared to launch, spray, or grade? Which number looks measured? You patch one rail — usually a hold point or a claim-table line — and reprint.
What you still own. Launch, land, spray, enter, deliver. Signatures. Whether this product is good enough to send. Grok drafts. You sign.
What stays out of the thread. Gate codes, live frequencies if your shop treats them as controlled, client legal names if you need a stand-in, student last names, unpublished site photos you do not have rights to. Use a working title for the site.
Done. You could hand Product A to the second person on the crew without a speech. You could read Product B on a call and survive a “where did that number come from.” The ops packet is attached or summarized so the file on disk is not an orphan.
Worked example
Prairie-edge mapping job. The capstone thread gets the three sources.
Grok’s first merge put “Class G, clear to launch if wind < 15” back into the SOP and “14.2 acres, well drained” back into the brief. The lead sent one message: “Delete every clearance and every quantity not in my sources. If the south line is NOT COLLECTED, the brief may not describe it as mapped.”
The reprint:
- SOP: two functions, phone comms, holds for road, cattle, airspace check, superintendent same-day yes, correct mission file
prairie_edge_v3, abort if cattle on the pad. Sign line empty.
- Brief: Thursday ortho v1, slough on the south line as a wet signature, access off the county road, three GIS measurements before the Monday call, claim table with acres UNVERIFIED and floodplain NOT IN IMAGE, contract: not a grading plan, not a survey, south lots not in product.
- Packet summary at the top: no GCPs, GSD from the report only, CRS as the lead typed it.
That pair can go to a tailgate and a call. The first merge could not.
Your turn
Open grok.com. One new thread. Same real job as the rest of this track. Attach the PNG or say PRE-BRIEF if the collection has not happened.
Exercise d-geo-l04-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 35 min |
Copy-ready prompts
Message 1:
I am in Grok Mastery (Russell Tech), Pathway D, Geospatial, capstone.
Reconcile these sources for one job. Do not replace my site facts.
[paste Field Comms SOP]
[paste Analysis Brief or write PRE-BRIEF — collection not done]
[paste Ops Packet]
Job name:
What I will hand the crew:
What I will say on the call:
Write:
A) Field SOP (crew-facing, the six parts, plus the collection facts that affect the ground)
B) Analysis brief or PRE-BRIEF (one page, claim table required)
C) Five-line join note: how SOP, packet, and brief cannot contradict
Fill only facts in the sources. NEED otherwise.
No clearance. No invented quantity, CRS, frequency, or buffer.
Stop there.
Message 2:
Attack pass. Play a careless PIC and a careless analyst.
List:
- Any sentence that sounds like a clearance
- Any number or official status that looks measured but is not
- Any place the brief assumes a collection the SOP/packet said did not happen
Do not rewrite yet.
Message 3 (after you name the patch):
Patch I accept: [one rail].
Reprint A, B, and C only, cleaned.
Then:
- Monday check: three lines the second crew person needs
- Call check: the one sentence I will not say
- Session stamp: today's date and "SOP and analysis brief written by Grok in this thread."
Artifact to paste
- The reprinted Field SOP.
- The reprinted Analysis brief or PRE-BRIEF (with claim table).
- 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 say: plus the sentence you killed.
Rubric
- Pass: Both products are Grok-authored and stamped. Same job. No clearance. No unmarked invented quantity. Brief respects NOT COLLECTED / UNKNOWN from the packet. Attack pass exists. Job is real.
- Fail: Two unrelated documents. A pamphlet SOP. Acres or flood zone as fact. You typed it offline. PRE-BRIEF written as if the mosaic exists. Missing stamp. Generic “ag drone lesson” with no site.
Common failure
The common failure is two jobs in one capstone. A flight SOP and an analysis of a different county’s NAIP. Bind them or drop one and start the thread over.
The other failure is polishing the brief until it sounds like a report. Reports hide UNVERIFIED. Your brief should still show the table. If a client cannot see a HOLD, you are selling fluency.
What’s next
This track is done when the SOP is on the clipboard and the brief is the one you will actually read. If your other job is a classroom or a shop inbox, the Education and Business tracks are separate four-hour paths.
