Guides and resources for AI engineers: an agents course, five handbooks, a hands-on second-brain project and a vetted reading list.
Research reports
A research report is what you produce when a question needs more than the vault currently holds. The vault is the starting point, not the whole answer.
Scope against what exists first
I need to understand how companies are deploying agent harnesses in production.
What does my vault already cover, what is thin, and what is missing entirely?
That answer is your research plan. Most of the work in a good report is knowing what you do not need to look up, and starting from the vault means you are not re-reading things you read last year.
Fill the gaps deliberately
Go find sources for the gaps, ingest them properly through raw/, and let them
build pages the same way everything else does.
Resisting the shortcut matters. Pasting a fresh article straight into the report draft gets the report written and leaves the vault no better, which means the next report on an adjacent topic starts from the same place.
Structure
Question
What I found (with page citations)
Where sources disagree
What I could not establish
What would change the conclusion
The last two sections are what make a report worth rereading. A report that presents only findings looks stronger and is less useful, because the reader cannot tell where it is load-bearing and where it is thin.
Store it as a source
Reports go in output/, then get ingested back as sources.
A report is a dated snapshot of your understanding, and having it in the vault as a source means later material can contradict it explicitly rather than quietly superseding it. See supersession.