Project brief — seven-day operating system

This is the capstone packet. The lesson taught you to build the machine. This page is the week you run it. Read it after Seven-day operating system. Do the work on grok.com.

Why this matters

A playbook you never ran is a poster. Seven dated logs are the proof. Pathway A ends when the packet exists, not when you finish reading.

Teach

Outcome. For seven consecutive calendar days you run the daily loop from your playbook on work you already had. You leave with: (1) the playbook as of Friday, (2) seven logs, (3) a Friday review that changes one line of the playbook.

Constraints.

• Desk is grok.com. Phone is allowed for field notes. Grok on X is not the desk.
• Real work only. If a day has no Grok-shaped work, run Morning brief + Close and write empty on the task line. That counts. Invented homework does not.
• Every verify uses HOLD / WRONG / UNVERIFIED. At least two days must include opening a source or challenging a claim.
• Imagine (Still / Clip) only if the playbook allows it and the consent card would say Go. No third-party likeness, no minors, no sexualized generations.
• You send every message that leaves the shop. Grok does not.
• Do not paste secrets, student records, medical data, passwords, or anything you would not put on a shared machine.
• Session stamps stay in the threads. The packet can quote them.

Schedule.

Missed day: add one day to the end. Do not double up to “catch up.” Two missed days: restart the clock and say so on the packet.

Worked example

The one-person shop from the lesson. Days 1–3 are inbox and the vendor window. Day 4 is empty (she still writes a three-line brief and a close). Day 5 she verifies a fee on the primary page; blog figure is WRONG. Day 6 no Imagine — nothing to list. Day 7 she cuts Clip from the playbook because she never had a still worth moving. Packet is two pages plus seven short logs. That passes. A cinematic week of unused video does not.

Your turn

Print or pin this brief next to the playbook. Start the clock on the day-one date you already wrote. Do not wait for a quieter week.

Exercise a8-l01-e1 (week packet)

Copy-ready prompt (Friday only)

I am in Grok Mastery (Russell Tech), Pathway A, capstone Friday review.

Here is my playbook as of day one, and my seven logs (or six plus a named missed day).

Answer only my three Friday review questions, using the logs, not a pep talk.
Then propose exactly one playbook edit (one heading, old line, new line, one-sentence reason from the logs).
If the logs do not support an edit, say "no edit" and why.

End with a Session stamp: today's date and "This Friday review was written by Grok in this thread from my logs."

Artifact to paste (end of day 7)

Paste, in this order:

1. Playbook as of Friday (with the one edit visible, or “no edit”).
2. Seven Day logs (date, task, verify label, minutes). Empty days included.
3. Friday review with session stamp.
4. One sentence you wrote: what you will still run in week two.

Redact clients as needed. Keep dates and labels.

Rubric

• Pass: Seven dates (or six plus one named restart). Playbook still has refuse-lines and no third-party likeness. At least two verifies that opened a source or challenged a claim. Friday review answers the three playbook questions and makes one evidence-based edit or a justified “no edit.” You can point at at least three real artifacts (reply, outline, still, audit, plan). Stamps on playbook, day one, and Friday.
• Fail: Seven motivational paragraphs and no work. All verifies “looks good.” Imagine of other people. Secrets in the packet. A playbook that grew every day and a log that did not. No Friday review. You stopped after day one and called the pathway done.

Common failure

The common failure is restarting the system instead of running it. Day three feels messy, so you rewrite the playbook from scratch and throw out the logs. Keep the logs. Change one line on Friday.

What’s next

Pathway A is complete when the packet is complete. Keep the desk. If you want projects, files, memory, and a reusable workflow library, that is Pathway B. If you want repos and Grok Build, that is Pathway C. If you have a classroom, a field program, or a shop OS to install, that is Pathway D. None of those replace the seven-day loop you just proved you can run.

I am in Grok Mastery (Russell Tech), Pathway A, capstone Friday review.

Here is my playbook as of day one, and my seven logs (or six plus a named missed day).

Answer only my three Friday review questions, using the logs, not a pep talk.
Then propose exactly one playbook edit (one heading, old line, new line, one-sentence reason from the logs).
If the logs do not support an edit, say "no edit" and why.

End with a Session stamp: today's date and "This Friday review was written by Grok in this thread from my logs."