Prepare, then decide
Turn scattered inputs into a clear choice, tradeoffs, risks, and the one action that moves things forward.
Point Reyes field class · 101 → 301
Tune Your Muse
Teach your personal agent how to work your way—then give it enough trust to be useful, not enough to be reckless.
30-Second Class · 101–301
Choose your stop
Three full courses. One quick start.
Start with the 30-second overview, or take any full narrated course.
101
The basics · Start human
Talk to it like a person.
Muse is a personal AI agent with its own computer, memory, and files. Plain-language direction becomes the operating manual it uses to help you.
The three-part brief
- 01Give the outcome.
Say what you want to be true when the work is finished, not just the first task you can think of.
- 02Name the constraints.
Add timing, budget, format, preferences, and anything that is off-limits.
- 03Define done.
Ask for the finished shape: a shortlist, a call brief, a polished page, or a cited recommendation.
201
Power moves · Delegate the pattern
Turn friction into a workflow.
The leap is not prompting more. It is delegating a repeatable outcome, letting Muse prepare the ground, and keeping the decision that matters.
Work like a chief of staff
- 01Hand over the pre-work.
Let Muse collect sources, organize notes, compare options, and prepare a concise decision brief.
- 02Attach research to reminders.
“Remind me” can arrive with the context, open questions, and next step already assembled.
- 03Schedule what repeats.
Morning briefings and recurring checks are useful when the format and reporting rule are explicit.
Evidence before opinion
Build source trails, compare claims, and separate verified facts from a confident guess.
Briefs with momentum
Prepare call scripts, appointment notes, document checklists, and follow-up plans before they are needed.
Ideas become artifacts
Shape a loose thought into a useful guide, lesson, deck, page, or prototype another person can use.
301
While you sleep · Trust with edges
Let the quiet jobs run.
Background work is powerful when it watches for a meaningful change, troubleshoots intelligently, and stays inside a clear approval boundary.
The reliable background pattern
- 01Watch the exception.
Inbox replies, ticket changes, deadlines, and tracked statuses should ping you only when something actually changes.
- 02Troubleshoot twice.
If the first route fails, try two more sensible approaches. If all three fail, explain what blocked each route instead of looping or pretending.
- 03Protect the consequence.
Research can move quickly. Money, messages, filings, access changes, and exact amounts wait for explicit approval.
The traffic-light test
Match the guardrail to the consequence.
Speed is useful until an action leaves your hands. Then clarity wins.
GREEN summarize, brainstorm, organize, draft
AMBER connect accounts, inspect sensitive records, schedule work
RED send, buy, publish, file, delete, or change access — confirm first