Run one guided work session before opening another front.

Guided Work Session turns overwhelm into a 75-minute local loop with 6 session blocks, 4 checkpoints, 5 closeout questions, 8 stop rules, and a read-only import. It does not send, post, scrape, buy, open apps, run agents, or touch Gmail/OAuth.

Simple layer. Now Command Console chooses what matters. Guided Work Session gives you the next 75 minutes: orient, check source of truth, execute one action, move money, record proof, then close.

The generator reads existing Life OS JSON files, then writes guided-work-session.md, guided-work-session.json, and guided-work-session-import.json. It is local and read-only over generated outputs.

Run the session

node work/life-os-guided-work-session.mjs
# or
node work/life-os.mjs session

# then open:
outputs/life-os-command-center/guided-work-session.md

Follow 6 session blocks

0-5 OrientUse Now Command Console to choose one command, one file, one proof gate.

5-15 Source checkRead Organizer Refresh Gate before trusting stale task pressure.

15-40 Execute oneUse Action Queue for one bounded action, not another map.

40-55 Move moneyChoose one lead, proposal, invoice, diagnostic, or outreach move.

55-65 Record proofWrite the evidence or blocker in Proof Ledger.

65-75 Close seedStop with tomorrow's one action written.

Use the checkpoints

The 4 checkpoints are start gate, midpoint gate, proof gate, and closeout gate. If evidence is missing, reduce the unit instead of opening a new agent, course, project, or tab.

Close the loop

The 5 closeout questions ask what proves the session, what closed, what remains parked, what tomorrow's one action is, and what must not be opened now.

Guardrails

This is a read-only human guide. Commercial movement stays manual and reviewed. Public proof must be sanitized. Organizer stale data must pass the Refresh Gate before becoming current truth.