Captures, reviews, and promotes Note entities — the lightweight knowledge capture primitive in processkit. Notes are quick-capture units (thoughts, insights, questions, references) that are reviewed periodically and promoted to WorkItems, DecisionRecords, or other primitives when they ripen. Use when the user says "remember this", "note that", "I had an idea", or when running a periodic note review session.
Notes are processkit's capture layer — the place where ideas land before they are ready to become backlog items, decisions, or artifacts. Inspired by the Zettelkasten model: capture fast (fleeting), refine deliberately (permanent), link explicitly, and promote when something becomes actionable. The review cycle is what gives notes their value — unreviewed notes are just noise.
Note types map to the Luhmann/Ahrens Zettelkasten taxonomy:
| Type | Luhmann equivalent | When to use | Review horizon |
|---|---|---|---|
| fleeting | Fleeting note | Quick thought, idea, or observation — not yet refined | Within 1 week |
| insight | Permanent note | A self-contained conclusion or realization; part of the knowledge base — never discarded | Evergreen (not discarded, only promoted or refined) |
| Literature note |
| Pointer to an external source, with your own summary |
| Evergreen |
| question | — | An open question you want to revisit | Until answered |
Start with fleeting when in doubt. If a note survives a review
session unchanged and seems worth keeping, refine and set to insight
or reference. Insight notes are permanent — they are never
discarded, only promoted or further refined.
Notes live in context/notes/ as individual Markdown files with YAML