A note titled “Interesting ideas from chapter 4” asks you to remember why it was interesting. A note titled “Decision records need a reason as well as an outcome” gives you something to examine, challenge and use.
A visual Zettelkasten starts with that difference. Write notes that can stand beyond the reading session, connect them for a reason, then bring the relevant ones onto a canvas when you’re working on a question.
We make Acres. Its cards and boards fit this practice, but a useful Zettelkasten doesn’t depend on our app or on following one rigid method.
Keep the idea durable and the board flexible
In Luhmann’s 1981 essay, available in translation, stable note addresses and cross-references let entries connect beyond one fixed subject arrangement. We adapt that principle to digital cards; the workflow below isn’t a reconstruction of his filing system.
In Acres, a card has its own body. The same card can appear on several boards. Use a board for a temporary question, outline or comparison, while the underlying notes remain useful elsewhere.
This means you don’t need a single enormous map of everything you know. A board for “How should we record decisions?” and another for “What belongs in onboarding?” can draw on some of the same cards. Each arrangement expresses a different question.
Separate capture from a note worth keeping
Use these distinctions when they’re helpful:
| Working material | Purpose | What happens next |
|---|---|---|
| Quick capture | Save a thought before you lose it | Clarify, discard or turn it into a fuller note |
| Source note | Record what a particular work says, with a location | Preserve the source and distinguish your reading from its words |
| Durable idea note | Explain a claim you expect to revisit | Add support, limits and links to related ideas |
| Structure card | Offer an entry point into several notes | Explain an order, question or developing argument |
“Permanent” doesn’t mean unchangeable. It means the note should make sense when the context of today’s project has faded.
A useful card explains the idea, why you think it holds, where it may fail and what prompted it. A quotation alone is still source material. If you can’t explain the point in your own words, leave it as a reading note until you can.
A miniature example: from capture to reusable idea
The following is a hypothetical working example, not a research finding.
Your quick capture says:
People keep asking why we chose option B.
A durable note might become:
Decision records need a reason as well as an outcome
Recording “we chose B” preserves the result, but not the constraint or tradeoff that produced it. A later reader needs enough of that reasoning to judge whether the decision still applies.
Working hypothesis: a short record should include the decision, the main reason and the condition that would justify reconsidering it.
Limit: the record can become misleading when circumstances change and nobody updates it.
Origin: this idea came from the capture above. It needs evidence before being presented as a general claim about teams.
The title gives you a proposition. The body explains it and avoids pretending that a plausible idea is established fact.
You might connect it to an existing note about changing assumptions, and another about the maintenance cost of documentation. Write why each connection matters: “An outdated assumption is one reason to reopen a decision” is more useful than a bare list of related titles.
For a real reading source, include its bibliographic details and page reference. The PDF highlights guide shows how to retain the excerpt and source link before writing your interpretation.
Make links carry part of the explanation
In an Acres card, type [[ and choose an existing card from the picker. You can also use Copy link from a card’s menu. The editor displays a card link; the saved Markdown uses an Acres deep link tied to the card’s ID.
Add a sentence around the link:
This qualifies the earlier note on decision records: a record stays useful only while its assumptions can be checked.
The referenced card’s Linked references can show notes that mention it. That gives you a route back to the context in which the idea was used.
A canvas arrow is different. It describes a relationship between items on that board. If the connection matters to the note itself, put a link and explanation in the card body as well.
Mindmap branches, sticky notes and labels are useful for sketching an arrangement. Use cards for the durable notes you want to retrieve, link and reuse.
Reuse cards instead of making project copies
When a new project needs an old idea, place the existing card on its board. The body is shared across placements, so editing it changes the note wherever you view it.
Create a separate project card for context such as “How this applies to the onboarding draft.” Link it to the durable note. That keeps a general idea readable without filling it with details from every project.
If a board is crowded, remove an unneeded placement rather than deleting the library note. Check the action’s scope: taking a card off one board and deleting the underlying card are different operations.
A structure card can link to the strongest notes and explain a reading order. For the example above, it might start with the reason for recording decisions, then assumptions, then maintenance. Use the canvas to try another order before writing the draft.
Maintain the notes when you use them
Don’t make a daily quota the main measure of progress. A week spent improving an important note can be more useful than a week spent generating dozens you never revisit.
When you reopen a card, ask whether its title still matches its claim, its evidence supports the wording, and its links explain real relationships. Split it when two arguments need separate treatment. Keep the qualification that prevents an attractive claim from becoming false.
Leave room for disagreement. A counterargument card can stay linked to the idea it challenges. If the comparison grows into a research project, use the literature review canvas to distinguish source evidence from synthesis.
Let AI suggest connections you can inspect
An agent can search for related cards or propose how several notes disagree. A useful request is:
Find notes that support or challenge this card. Read them before suggesting links. Explain each proposed relationship, identify gaps and show me the suggestions before editing anything.
Review the suggestions against the notes. Similar vocabulary can hide different meanings, and a model can make a connection sound stronger than the evidence allows. The MCP note-taking guide describes a small retrieval-and-draft workflow.
Finally, keep the storage distinction clear. Acres cards are Markdown, but internal navigation uses acres:// links. A separate editor can read the prose without reproducing the same link behavior or board arrangement. Back up the complete vault. If you’re moving existing linked notes into Acres, the Obsidian import guide covers that migration rather than requiring you to rebuild them by hand.