One week, one job, one card you will open again. That is the track. Not a personal-AI manifesto. The week you already had, reviewed on Friday, bound so Monday-you does not start from a blank chat.
Why this matters
The last three lessons produced parts. Parts do not survive a bad Wednesday. A Job Card you never pasted, a cycle you ran once for class, a never-store list you cannot find — that is a course, not a desk.
This capstone binds them. You leave with a reusable card (job + never-store + voice + the weekly loop) and a Friday review of a real week. If you finish in one sitting before seven days have passed, you still review this week: the cycle you already ran, plus the other times the trigger fired whether or not Grok was open. Empty days are allowed. Fake work is not.
The standard is Russell Tech: you could leave this on a table for a partner. No theater. No invented SLA. No drone, no map projection, no repository. Realtor, cook, clerk, teacher, student, shop owner, church secretary — same shape, their facts.
If you will not open the card the next time the trigger fires, the packet is a class exercise. Write the date.
Teach
Work in one thread named capstone — week of [date] — [job]. Paste the Job Card, the cycle (before / after / refused), and the Privacy and Voice Card as sources. Tell Grok to reconcile, not to replace your never-decide line or your first sentence.
Product A — Reusable card (one page)
- Job name (verb + object):
- Desk:
- Trigger:
- Inputs:
- Output:
- What Grok may draft:
- What Grok must never decide:
- Who sends:
- Never-store (core + this desk):
- Stand-ins:
- Voice rails (first sentence, “I” is me, no slogans, I send):
- Thread name I will use:
- Stop when:
- NEED / UNKNOWN:
This is what you paste at the top of next week’s thread. If it could belong to anyone, it belongs to no one.
Product B — Friday review (this week only)
- Week of:
- Times the trigger fired (count, or UNKNOWN):
- Cycles I actually ran in Grok (count):
- After I used or sent (name the artifact):
- What I refused:
- What Grok invented or tried to decide:
- What I almost pasted (class, not the secret):
- What I will cut from the card:
- What I will not paste next week:
- Empty days (allowed):
- Next open date:
Friday is a review, not a new epic. Do not ask for a six-month roadmap. Do not add a second job. If the review and the card disagree — you delayed every inquiry, the card says reply same day — you decide. Grok does not average.
Short week. If you only have one cycle, say so. Still list the other firings you handled without Grok. “Trigger fired four times; Grok ran once; three I did by hand” is honest. “I also could have used it for groceries and Instagram” is not.
QA. After A and B exist, Grok hunts invented policy, unsigned decision, stolen voice, a secret in the card, a second job. You accept or reject each action. Reprint once.
Scope. One job. One week. Not a handbook. Not Memory stuffed with the week. Redaction still holds: roles and working titles; See listing sheet or See signed allergen list, not hallway-unfit numbers.
Done. You will open the card the next time the trigger fires. You could hand Product B to a partner and they would know what this week was.
Worked example
A shop owner. Job: reply to vendor and customer texts that need a yes, a no, or a hold. Capstone thread gets the Job Card, Monday’s cycle (late insulator shipment), and the privacy-voice card (no account numbers, no alarm, she sends, no “we value your partnership”).
Grok’s first merge added “we commit to 24-hour replies” and put the vendor’s phone back into the review. The owner: “Delete every SLA I did not give. Replace the number with VENDOR. Cut the slogan.”
Reprint:
- Reusable card: trigger = a text that needs a yes/no/hold; inputs = what they asked and what she already promised in writing; may draft = 8-line reply and a NEED list; never decide = refund, a new price, Saturday hours she did not offer; never-store = account numbers, alarm, employee Socials; voice = she writes the first sentence; thread =
cycle — vendor texts — [date].
- Friday review: week of the 11th; trigger fired six times; Grok ran twice; she sent the shipment-hold reply after cutting an invented discount; refused “we can do Saturday”; almost pasted the vendor portal password (did not); empty Wednesday; next open = Monday.
A student’s week: one quiz card. Trigger fired once; one cycle; refused “this will get an A”; never-store = classmate’s notes she did not paste; next open = the next posted quiz.
A county clerk: four notices, one cycle in Grok, three by the old template; refused an invented statute; next open = the next intake slip.
That is a week they can run. A ten-page “AI operating system for any role” is not.
Your turn
Open grok.com. One new thread. Use this week’s real desk and the same job as the rest of this track. Redact as you paste.
Exercise d-any-l04-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 35 min |
Copy-ready prompts
Message 1:
I am in Grok Mastery (Russell Tech), Pathway D, Any desk, capstone.
Reconcile these sources. Do not invent policy, counts, or a second job.
[paste Job Card]
[paste Before, After, Refused list, three-line log]
[paste Privacy and Voice Card]
Week of:
Job name (verbatim):
Write:
A) Reusable card (the required lines from this lesson)
B) Friday review (the required lines from this lesson)
If a count or date is missing, write UNKNOWN or NEED.
Do not add a second job. Do not write a handbook.
Stop there.
Message 2:
QA both A and B.
Table: line, problem class (invented fact / unsigned decision / stolen voice / leak / second job / none), evidence, action.
Fail if invented policy, a secret in the card, or Grok still sends.
Do not rewrite yet.
Message 3 (after you accept actions):
Accepted actions: [list]
Reprint A and B only.
Then:
- Monday check: the first thing I will paste the next time the trigger fires
- Refuse check: the one line I will still not let Grok decide
- Session stamp: today's date and "Week card written by Grok in this thread."
Artifact to paste
- The reprinted Reusable card.
- The reprinted Friday review.
- The QA table and the session stamp.
- Two lines from you:
I will open the card on: plus a date.Grok still may not decide: plus the hold.
Rubric
- Pass: Both products are Grok-authored and stamped. Card has trigger, never-decide, never-store, voice rails, and a human sender. Review has a real week (empty days allowed) and at least one refused line or a defended none. QA exists. You name a date you will run this. Job is the same one as the rest of the track.
- Fail: A generic productivity system. No Friday review. A second job. You typed it offline. Clerk allowed to send or to decide. Unredacted secrets. Missing stamp. A hypothetical week.
Common failure
The common failure is the strategy deck. Pillars, north stars, five new use cases. Nothing runs the next time a text arrives. Cut until one job and one week remain.
The other failure is a review with no date. You described a beautiful card and did not say when you will open it. Fluency is not a desk. Write the date. Then open the thread that day.
What’s next
This track is done when the card is the block you paste, not when the thread feels finished. Education, business, and geospatial are separate four-hour tracks if those are also your jobs. You do not need them to finish a week at this desk.
