Lessons

Six lessons, drawn first from accounts written since June 2026. Each one names the accounts it rests on, so you can read the evidence for yourself.

  1. Choose a question worth answering

    Before asking an agent to tackle a research problem, ask who would care about the answer and what it would tell them. Revisit those questions when the first results come in. A calculation can become feasible long after specialists know what answer to expect.

    Read the lesson and its examples

    Rests on

  2. Build the method and its checks together

    An agent can help build the tools a research method needs. Decide while building how you will tell whether the method works. For a new search, compare what it returns with existing searches. For a simulation you want to repeat, review the setup before reusing it on new inputs.

    Read the lesson and its examples

    Rests on

  3. Use a council of models

    When I have a decision that matters, I give several models the same question and brief and ask them to answer separately. I compare their reasons, especially where they disagree, before deciding what to do.

    Read the lesson and its examples

    Rests on

  4. Start with a known result and keep an independent check

    Try the method first on a result you already know. Before moving on to new work, decide how you will check an answer when there is no published result to compare it with. Where possible, make that check independent of the code that produces the answer.

    Read the lesson and its examples

    Rests on

  5. Keep enough of the work to resume, audit and undo it

    Keep the original material, the last usable output and a record of what failed. If a long run stops or a correction goes wrong, you need to know what you can reuse and what you have to do again. A saved decision can also keep a new session from repeating a failed approach.

    Read the lesson and its examples

    Rests on

  6. Routine research work is a useful place to start

    Try an agent on a recurring task whose output you can check against the project files, such as preparing for a meeting from past notes or flagging inconsistencies in a manuscript. A task you do often gives you a reason to spend time explaining it and a chance to see whether the next attempt takes less work to check.

    Read the lesson and its examples

    Rests on

Search the collection

↑ ↓ move · Enter open · Shift+Enter original source · Esc close · Search index for agents

Keyboard shortcuts

Single keys work when you are not typing and no dialog is open. Turn them off if stray key presses move the page. ⌘K / Ctrl+K and Esc keep working.

/
Search the collection
⌘K / Ctrl+K
Open or close search
?
Show these shortcuts
h
Home
l
Lessons
a
Accounts
r
Replications
p
Papers
g
Guides and tools
d
Timeline
b
Bookmark the record you are reading (press again to remove it)
s
Your saved list and notes
← →
Previous and next record on an account, lesson, replication or paper page, and in a quick look
m
Switch between system, light and dark theme
t
Back to the top of the page
Open full page