Book workflow, introduction to The Archive, & saved searches • The Archive App Notes #3

Deep-work “debug days” drive a two-track workflow inside The Archive: a constant stream of incoming notes and a focused, book-centered mode for processing annotations into a structured knowledge system. On deep-work mornings, the workflow starts with a specific book and a specific topic—here, analytical psychology and archetypes—then funnels those reading notes into tightly organized “department” notes so the archive stays coherent instead of turning into a searchable dumping ground.

The process begins with an overview entry point. The user opens the archive’s omnibox and triggers a quick command (e.g., “qq1”) to land on a set of overview notes that function like a category system. For the book being worked on, a “bookmark” mechanism is used: typing a short trigger (e.g., “qp1”) reveals a curated set of linked nodes (the six bookmarked nodes) that act as the starting map for where new notes from the book should go. This avoids repeatedly re-choosing where content belongs and keeps the reading-to-writing loop tight.

A key decision shapes how the book is integrated. Some books get a dedicated “book note” that mirrors chapters and includes page numbers and links to related notes. But not every book earns that treatment. If the book is unlikely to be revisited, the workflow favors integrating insights into a broader department (for example, “psyche” or “deep psychology”) rather than creating a permanent, book-specific structure. In the example, archetypes like “King” and “Boy” are treated as psychological material tied to the collective unconscious, so notes are anchored to the psyche department instead of the book itself.

When creating new notes, the workflow distinguishes between “ontological” notes (focused on the energy or theme of a concept) and topic-tagged material. The user argues that heavy reliance on broad keyword searching becomes impractical at scale—citing an example where searching a general term could yield an unmanageable number of results. Instead, notes are written with intentional tags and placed under the right conceptual department so retrieval happens through structure and triggers, not brute-force search.

Finally, saved searches are introduced as a performance and convenience layer. Rather than typing the same search repeatedly, the archive supports “save searches” that bind a search definition (title and search terms) to a hotkey. The workflow emphasizes that this is especially valuable when working within a small, recurring department: saved searches jump directly into the relevant subset of notes, reducing friction and keeping attention on synthesis.

Overall, the workflow treats the archive like an instrument for deep work: bookmarks and department notes provide navigation, ontological framing preserves conceptual cleanliness, and saved searches turn repeat retrieval into one keystroke—so reading annotations become durable, connected knowledge instead of scattered fragments.