# Lessons

- [Choose a question worth answering](/lessons/choose-a-question-worth-answering/index.md): 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.
- [Build the method and its checks together](/lessons/build-the-method-and-its-checks/index.md): 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.
- [Use a council of models](/lessons/use-judgement-where-it-changes-the-work/index.md): 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.
- [Start with a known result and keep an independent check](/lessons/start-with-a-known-result/index.md): 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.
- [Keep enough of the work to resume, audit and undo it](/lessons/keep-enough-to-resume-and-undo/index.md): 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.
- [Routine research work is a useful place to start](/lessons/start-with-routine-research-work/index.md): 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.
