Home Base

Team Workflow

How the team works

Who does what, where it lives, and how one piece of work moves from a note to a decision. The rules themselves live in Workflow, in the vault (40 Work/Workflow.md).

The seats

Decides

Colton

Owns the gate. Answers the team in the work note. Approves anything that leaves the team. Merges the Colton tier.

Builder seat

Claude

Owns Workflow and every CLAUDE.md. Writes Briefs, sets handoffs, runs the refresh, brings your open questions to you. Merges Self, and Reviewed after Grok approves.

Reviewer seat

Grok

Checks every Grokbot return against its Brief: accept, fix or escalate. Pass 2 on everything Claude builds; approves PRs with GitHub's Approve button. Never reviews its own work.

Does the work

Firstmate and the Grokbot team

Firstmate routes every grokbot handoff to the right bot, keeps the Review Queue and does pass 1 on Claude's work. Scholar keeps the vault clean. The team works in Google Drive and files a return.

Seats, not models. The two seats swap together, so whoever builds never reviews.

The loop

Capture anything in 00 Inbox. When it becomes work, it gets a note in 40 Work, and from there every piece of work goes the same way.

  1. 01

    Note

    A note in 40 Work. No note, no work.

    Colton, shaped by Claude

  2. 02

    Brief

    Goal, Inputs, Do, Rules, Output, under ## Brief.

    Claude writes it

  3. 03

    Handoff

    assigned, handoff: ready, one handoff_id.

    Claude sets, Firstmate routes

  4. 04

    Return

    A new note in _Returns. Frozen once filed.

    The Grokbot team files it

  5. 05

    Review

    Accept, fix or escalate, added under the return. One fix round.

    Grok

  6. 06

    Decision

    Accepted returns move to _Returns/Accepted.

    Colton decides

On fix, the team fixes it once and Grok reviews again. Bots ask in the return; your answers go in the note, under ## Colton's decisions.

Review before anything merges

Everything is checked by someone who didn't build it. The Review Queue (40 Work/Review Queue.md) is the list that tells the reviewers what's waiting, and shows you each verdict without opening the PR.

  1. 01

    Opened

    A PR or return goes up and gets a line on the Review Queue.

    Whoever opened it; Firstmate adds anything missing

  2. 02

    Pass 1

    Checked against its Brief. Posted on the PR and in the queue.

    Firstmate, every hour at :00, 6 AM to 9 PM PT. Ledger or Scholar if Firstmate wrote the Brief

  3. 03

    Pass 2

    Checked again, independently. Approves with GitHub's Approve button, or comments what to fix. One-line verdict in the queue.

    Grok, every hour at :30, 6:30 AM to 9:30 PM PT

  4. 04

    Merge

    Only after review. Self: Claude. Reviewed: Claude, once Grok approves. Colton tier: you.

    Claude or Colton

Grokbot returns skip pass 1: Grok reviews them under the return, with one fix round.

Claude's work and rules changes always get both passes.

Every PR carries or links its five-field Brief. New repos invite GrokForColton before the first PR.

Run the agent routine

Say "run the agent routine" to Grok or Firstmate. It also runs on its own every night at 11 PM Pacific. It is Workflow section 9, and nothing else either of them runs.

  1. 1Read the rules, fresh from main.
  2. 2Find your work. Grok reviews returns and PRs first.
  3. 3Skip anything already returned.
  4. 4Check the limits. Stop on anything never handed off.
  5. 5Check the library for what helps.
  6. 6Do the work, where the Brief says.
  7. 7File one return note in _Returns.
  8. 8Add any lesson to 30 Prompts/Intake. "Lessons added" is never left out; "none" is fine.
  9. 9Commit to main. Pull first, never force.
  10. 10Report one line per handoff to Colton.

Where things live

The vault, "Colton"
Every note, on every device through Obsidian Sync. 00 Inbox is private capture. 40 Work holds the work notes, _Returns, the Backlog (the one ranked list) and the Review Queue.
colton-vault-publish
The vault on GitHub, minus 00 Inbox and 10 LYAI. What the agents read, and where they file returns and reviews.
claude-home-base
The binder (CLAUDE.md, TASKS, SESSIONLOG) and the desk app. Every change by PR.
home.coltonweeks.com
The desk. Built one way from the vault by a daily PR at 6:53 AM. Ways of Working is at /practice.
Google Drive
syaoakland.org for ashram work. coltonweeks@gmail.com for everything else.

Send your notes now

In Obsidian, open the command palette (Cmd+P, or Ctrl+P on Windows) and run Git: Commit-and-sync. It pushes your notes to GitHub and pulls in what the team filed. The plugin also does this on its own timer; use the command when you want the team to see something right away.

Three agreements

One channel

Bots ask in the return note, never in chat. You answer in the work note. Claude brings you every open question, and Grok flags any older than a day.

Three merge tiers

Self: Claude merges. Reviewed: Claude merges after Grok approves. Colton: money, ashram and client work, the website, and new permissions.

In place, then frozen

Agents edit existing work in place, so links hold. A filed return never changes; fixes go below it.