Capacities Note Taking: Organize Research You Can Reuse

Capacities note taking organizes knowledge as objects, such as a book, person, or project, that you connect rather than place in a folder tree. It suits research where the same source matters to several questions. Tools like fenbs can hold the selected project decisions and next steps that need to reach your connected AI assistants afterward.

The useful distinction is between collecting material and making it usable. A saved article is a source. Your explanation of why it matters is a note. A choice to change the project is a decision. Keeping those meanings visible helps you find information without treating everything you collected as an instruction.

How do objects change the way you organize notes?

In Capacities, an object is an individual note with a type. Types can have different properties and layouts, so a book can hold different information from a project. The official getting started guide↗ (opens in a new tab) explains this structure and the object templates used to begin.

Say you are a designer researching a community website. You might create a source object for an accessibility guide, a concept note about clear navigation, and a project note for the website. The source can support several concepts without being copied into several folders. Each connection gives you another way back to the material.

This approach asks a different first question: what kind of thing am I saving? If that is easy to answer, organization can feel natural. If every new note triggers a debate about types and properties, your system is probably more detailed than your current work requires.

Which object types should you start with?

Start with three or four types you can explain in one sentence. You can design a richer system after you have used real notes. A modest structure makes it easier to notice which information you actually retrieve and which fields you repeatedly leave empty.

Treat these as a starting design, not mandatory labels. A student may prefer sources and questions; a consultant may need organizations and engagements. Add a property when it helps you filter, compare, or check something. A field that merely repeats the note title does little useful work.

How do links make research easier to retrieve?

Capacities lets you link objects with an at sign or double brackets, and backlinks show where an object has been referenced. Its networked note-taking tutorial↗ (opens in a new tab) also describes references to individual blocks. Those connections can lead from a project to an idea and from the idea to its source.

Write the reason for the link in the sentence around it. “This source challenges our assumption about the menu” tells you more than an isolated link labeled “navigation.” A useful connection explains whether the other note supports, questions, illustrates, or updates the present one.

Keep one object for a source you consult repeatedly. Add your new observations there or connect a separate idea note when the interpretation deserves its own explanation. Copying the same passage into several project notes creates several places to correct if you later discover that you misunderstood it.

What should a research note contain before AI uses it?

Give an assistant enough information to distinguish the source from your interpretation. Record the title and location, the relevant section, your summary, and the limits of the claim. If the source only describes one organization, do not rewrite it as a universal rule for every project.

• Source statement: what the original material actually says, with its location.
• Your interpretation: what you think follows from that statement.
• Open question: what evidence would change or qualify your interpretation.
• Project relevance: the particular decision or task this might inform.

For the website example, a note might say that a guide recommends descriptive link text, while your project question is which labels need revision. That does not prove that the whole design is accessible. Ask an assistant for candidate changes, then check them against the source and the actual pages.

The broader AI brain explanation covers how saved working context reaches an assistant. Here, the practical goal is smaller: make each selected note understandable when it is read outside the surroundings of your notebook.

When should a note become a project decision?

Promote a finding when a person has chosen what happens next. “Consider clearer labels” remains a suggestion. “The project owner approved replacing these three labels” is a decision. Preserve the source reference, who chose, why, and any condition that still needs checking.

You do not need to copy the entire research collection into the project record. Carry over the conclusion, its supporting location, and the next action. If that action eventually becomes a public change summary, the release notes template helps describe what actually changed without publishing your exploratory notes.

Keep exploratory thinking open in your notebook and the agreed work current in one place. In fenbs, AI context gives connected assistants the project rules, notes, and Where we left off, so a research suggestion need not be mistaken for an approved instruction.

What makes an object system harder to maintain?

Too many types create unnecessary choices. Too many links create reading without explanation. A project note that lists every interesting source can still fail to answer the ordinary question: what should I read before doing the next task? Keep that starting point short and explicit.

Review a small sample during your regular project review. Can you reopen the source? Does your summary still match it? Is the project decision current? Remove misleading connections and explain changed conclusions. A tidy graph matters less than a note another person can understand correctly.

For another structured notebook approach, see the Tana note-taking guide. Use the second-brain hub and AI second-brain introduction when you need the wider context for keeping knowledge useful.

How to do this with fenbs

1. Create a free account, free for one person with no credit card, and add the project your research supports.
2. Choose one verified conclusion from Capacities. Manually add its short explanation and useful source reference as project context; leave unrelated research in your notebook.
3. Create the next task and record any decision a person has made in Decisions and rules. Keep unapproved suggestions clearly open.
4. Connect a supported assistant through Integrations. Ask it to read the project context before work and save progress, remaining checks, and the next step before stopping.

fenbs does not import your Capacities notebook or provide its object editor. If your only need is personal research and connected notes, stay with the notebook. Add a shared work record when the conclusions need to survive changes of assistant, teammate, or chat.