Sample output · 1 of 6
Use when you have a folder of project notes or records and want an offline map: who owns what, what threatens what, tables that answer your questions, the source file behind every claim and a list of what the notes leave out.
The first task in a new project also sets up its computer (about 3 min).
A map of the people, decisions and documents in a project
Try this prompt
Notes for our community garden project. Permits: water, owner Sam, approved; shed, owner Lena, pending; events, owner Sam, not filed. Milestones: beds May 30, volunteer day Jun 14, harvest sale Aug 9. Risks: shed delay threatens beds and volunteer day (Lena); no events permit threatens the sale (Sam); May rain threatens beds (Ahmed). Files: permits.pdf, risk-log.xlsx, schedule.md. Make an offline map for new volunteers: who owns each permit and its status, which risks threaten which milestones and who handles them, and which file backs each fact. List what the notes leave out.
One offline web page built from your project notes: a column for each kind of thing (people, permits, risks), tables answering your questions, a marker where the notes have gaps, search and filters, and a panel naming the source file for each fact. Also a data file, a list of sources and a list of known omissions.
| Field | Required | Hint |
|---|---|---|
| archive | Yes | The text of the notes or records, with each file's path |
| entity types and verbs | No | Your own vocabulary, for example Person, Permit, Risk and owns, threatens, mitigates |
| questions | Yes | Two or three questions the atlas must answer, each becomes a table |
| known omissions | No | What you know the archive does not contain |
You say
Notes for our community garden project. Permits: water, owner Sam, approved; shed, owner Lena, pending; events, owner Sam, not filed. Milestones: beds May 30, volunteer day Jun 14, harvest sale Aug 9. Risks: shed delay threatens beds and volunteer day (Lena); no events permit threatens the sale (Sam); May rain threatens beds (Ahmed). Files: permits.pdf, risk-log.xlsx, schedule.md. Make an offline map for new volunteers: who owns each permit and its status, which risks threaten which milestones and who handles them, and which file backs each fact. List what the notes leave out.
None
Node 20+; Chromium for the rendered checks; no network at run time
None
archive (The text of the notes or records, with each file's path), questions (Two or three questions the atlas must answer, each becomes a table)
onlypro, claude-code, codex, cursor