Seven-day operating system

A pathway you cannot run next Monday was a tour. This lesson is the operating system you keep: a playbook, a daily loop, and a seven-day proof. The project brief is the week. This page is how you build the machine.

Why this matters

You now have the pieces: a desk on grok.com, a phone for the field, search with citations you open, a way to say WRONG, Imagine when the job is a still or a short clip, an inbox loop, and a way to learn without skipping the closed book.

Pieces are not a system. A system is named workflows, rules that survive a bad day, and a log. Without those you will open a blank chat every morning and improvise. Improvisation is how invented fees and coworker deepfakes get into the work.

The capstone is not a speech about AI. It is seven days of real work, on the real tool, with an artifact you could hand to a partner: the playbook and the dated log. If the week is quiet, you still run the loop on the quiet. Empty days are allowed. Fake work is not.

Teach

An operating system, here, is four objects.

1. Surfaces. grok.com is the desk. The app is the field. Grok on X is optional and public-ish. Grok Build is not this pathway. Write that down so you do not re-decide it when you are tired.

2. Named workflows. Not “use Grok more.” Names you can say out loud:

• Morning brief — calendar + must-do + one risk, ten minutes, Fast.
• Inbox one — the email-and-planning loop on a single message.
• Verify — five-claim brief or a three-claim audit; you open sources; you label HOLD / WRONG / UNVERIFIED.
• Learn — questions first, outline, closed book.
• Still / Clip — Imagine only after the likeness card says Go.
• Close — what moved, what is UNVERIFIED, what tomorrow inherits.

Three to six names is plenty. If everything is a workflow, nothing is.

3. Rules. These are refuse-lines, not aspirations.

• I do not send a Grok draft unread.
• I do not paste secrets, student records, medical data, or passwords.
• I do not generate a third-party likeness.
• I do not treat an X post as a regulation.
• Think for research and grades. Fast for briefs and extracts.
• If I cannot check a number today, it is UNVERIFIED, not a fact I repeat.

4. Log. One short entry per day. Date. Workflows run. Artifact produced (reply, outline, still, audit). One HOLD or one WRONG / UNVERIFIED. Minutes spent. That is enough for Friday review.

Daily loop — keep it small enough to run on a bad Wednesday:

1. Morning brief (10 min). What must move. What must not.
2. One real task (20–40 min). Inbox, learn, still, or a work brief. One, not four.
3. One verify (10 min). Open a source, or challenge a line you are about to use. If the day’s task was already a verify, write that down. Do not fake a second research project.
4. Close (5 min). Log. Name tomorrow’s first task.

Friday (or day seven) is a review, not a new epic: which workflow you actually used, which rule you broke, what you will cut from the playbook. Shorter playbooks get kept.

Write the playbook with Grok, from your answers, then edit it until you would tape it beside the monitor. Do not accept a generic “AI productivity system.” If the playbook could belong to anyone, it belongs to no one.

The seven calendar days are the project. Today you write the playbook and run day one. If you cannot run day one on a real task, the playbook is still a poster.

Worked example

A one-person shop. Playbook fits on a page.

Surfaces. grok.com for all written work. Phone for voice on the drive and for photos of labels. No Grok on X for clients.

Workflows. Morning brief. Inbox one. Verify (any number that will leave the shop). Still for listing frames, faceless. Close.

Rules. The six refuse-lines above, plus: Imagine only on Tuesdays and Thursdays unless a listing is due. Weekly usage is not a video playground.

Day one. Morning brief names the vendor slip from last week. Inbox one produces a reply she sends after cutting a invented “thanks for your patience.” Verify opens the vendor’s own tracking page; delivery date HOLD, fee change on a blog UNVERIFIED. Close: tomorrow is the gate window, not a new chat about strategy.

Friday she drops Still from the daily list because she did not have a listing. The playbook gets smaller. That is a win.

Your turn

Open grok.com. New thread named Grok OS — [your name or shop]. Have in front of you: this week’s real work, the Surface Map from A1 if you still have it, and one task you can finish today.

You will make Grok interview you, write the playbook, and run day one in the same thread (or a clearly linked follow-up). Then read the project brief and start the seven-day clock.

Exercise a8-l01-e1

Copy-ready prompt

I am in Grok Mastery (Russell Tech), Pathway A, lesson A8 — seven-day operating system.

Interview me, one question at a time, exactly seven questions:
1) What real work must move in the next seven days? Name jobs, not vibes.
2) Which surfaces I will use (grok.com, iOS, Android, Grok on X) and which I refuse.
3) Which of these workflows I will actually run: Morning brief, Inbox one, Verify, Learn, Still, Clip, Close. I may add one name. I may drop some.
4) What I will never paste into Grok.
5) Likeness rule I will keep (must include: no third-party likeness).
6) When I will use Fast vs Think.
7) What "day one" task I can finish in the next half hour.

Then write a Playbook with exactly these headings:
- Owner and week of (date):
- Surfaces:
- Workflows (name, when, Fast or Think, output):
- Refuse-lines (at least five, in my voice, not slogans):
- Daily loop (morning / one task / verify / close):
- Friday review questions (exactly three):
- Day-one task:
- Session stamp: today's date and "This playbook was written by Grok in this thread."

Do not add mindfulness, gamification, or workflows I did not choose. Do not invent meetings.

Answer honestly. Edit any line that does not sound like you. Then run day one — morning brief, the task, one verify, close — using the playbook. Paste the day-one materials into the same thread or start Grok OS — day 1 and point at the playbook thread. Then send:

Format a Day-one Log from my notes. Do not upgrade the work.

- Date:
- Morning brief (three lines max):
- Workflow run / artifact:
- Verify (what I opened or challenged; HOLD, WRONG, or UNVERIFIED):
- Close (what tomorrow inherits):
- Minutes:
- Session stamp: today's date and "This log was formatted by Grok in this thread from my notes."

My notes:
[paste]

Artifact to paste

Paste, in this order:

1. The Playbook with session stamp (after your edits, if any — say what you changed).
2. The Day-one Log with stamp.
3. One sentence you wrote: the date you will treat as day one, and the date of day seven.

Rubric

• Pass: Playbook has surfaces, named workflows, at least five refuse-lines in the first person, a daily loop, three Friday questions, and a day-one task that is real work. Likeness refuse-line present. Day-one log shows a brief, a task artifact (described), a verify with a HOLD / WRONG / UNVERIFIED, and a close. Stamps present. Day-seven date is six days after day one. You opened Grok; you did not hand-write a poster and skip the thread.
• Fail: A generic “7-day AI challenge” that could be anyone’s. No day-one task. Verify skipped or faked (“looks good”). No refuse-lines. Third-party likeness allowed. No stamps. Seven days of planned chatting with no work output. You treated this lesson as the whole capstone and ignored the week.

Common failure

The common failure is a beautiful playbook and an empty log. You enjoy the interview. You never send the vendor reply. Friday has nothing to review, so you start a new chat called “week 2 system.”

The fix is day one before you decorate the playbook. If day one does not fit the playbook, change the playbook, not the definition of “done.” The second failure is seven unrelated chats and no names. Use the workflow names in the thread titles. Future you is the audience.

What’s next

The lesson is the machine. The project brief is the week: seven dated logs, the playbook as you actually used it, and a Friday review. Pathway A ends when that packet exists. Pathway B is there if you want projects, files, and a workflow library. The operating system does not require it.

I am in Grok Mastery (Russell Tech), Pathway A, lesson A8 — seven-day operating system.

Interview me, one question at a time, exactly seven questions:
1) What real work must move in the next seven days? Name jobs, not vibes.
2) Which surfaces I will use (grok.com, iOS, Android, Grok on X) and which I refuse.
3) Which of these workflows I will actually run: Morning brief, Inbox one, Verify, Learn, Still, Clip, Close. I may add one name. I may drop some.
4) What I will never paste into Grok.
5) Likeness rule I will keep (must include: no third-party likeness).
6) When I will use Fast vs Think.
7) What "day one" task I can finish in the next half hour.

Then write a Playbook with exactly these headings:
- Owner and week of (date):
- Surfaces:
- Workflows (name, when, Fast or Think, output):
- Refuse-lines (at least five, in my voice, not slogans):
- Daily loop (morning / one task / verify / close):
- Friday review questions (exactly three):
- Day-one task:
- Session stamp: today's date and "This playbook was written by Grok in this thread."

Do not add mindfulness, gamification, or workflows I did not choose. Do not invent meetings.

---

Format a Day-one Log from my notes. Do not upgrade the work.

- Date:
- Morning brief (three lines max):
- Workflow run / artifact:
- Verify (what I opened or challenged; HOLD, WRONG, or UNVERIFIED):
- Close (what tomorrow inherits):
- Minutes:
- Session stamp: today's date and "This log was formatted by Grok in this thread from my notes."

My notes:
[paste]