Capacities – Object-Based Notes for a Personal Knowledge System
Capacities is an object-based note-taking tool — meaning you don’t just create “pages,” you create
things: people, projects, meetings, books, ideas, sources, and more.
Instead of a pile of notes, you build a connected personal knowledge system where information stays structured
and reusable over time. In a browser workflow, Capacities is great for research capture and “second brain” organization.
Capacities helps you organize knowledge as objects with properties, links, and relationships.
It’s built for people who want structure, but don’t want the complexity of a full database tool.
Link and reference knowledge so it stays connected
Create a personal knowledge base that grows over time
Capture research and keep sources attached to insights
When Capacities is useful
Capacities is strongest when you’re doing knowledge-heavy work and want information to stay structured:
research, writing, learning, and project work with lots of context.
Research capture with sources linked to notes and insights
Meeting notes that connect to people and projects
Personal knowledge base for learning, reading, and ideas
Project dashboards built from connected objects
Long-term note systems that need clarity over time
How Capacities fits into a browser workflow
Capacities is a “capture and connect” layer. Use it to store context and knowledge,
then push action items into a task tool for execution. This keeps your brain clear and your work moving.
Capture
Collect notes from browsing: snippets, summaries, and links to sources.
Goal: stop losing useful info
Connect
Attach notes to objects: person, project, meeting, or source.
Goal: build reusable context
Review
Use object views to review open projects, recent meetings, or saved sources.
Goal: stay oriented
Execute
Move tasks into a task manager and complete them in focused time blocks.
Object-based organization keeps knowledge structured and reusable
Great for research, learning, and long-term notes
Links between people, projects, meetings, and sources feel natural
Helps prevent “random notes pile” syndrome
Limitations and things to know
Has a learning curve if you’re used to plain pages
Over-structuring can slow capture if you overthink it
Not a full project management tool (pair with tasks)
Best results come from consistent capture + review habits
Capacities works best when you keep capture fast and structure minimal — then evolve the system slowly.
Who Capacities is best suited for
Capacities is best for people who want a personal knowledge system that stays organized:
researchers, writers, learners, and builders who need context to remain connected over time.
Researchers collecting sources and insights
Writers organizing ideas and references
Managers linking meetings to people and projects
Anyone building a “second brain” with structure
If you prefer linked block notes, also see:
Tana and
Obsidian.
If you want a more all-in-one workspace, see
Notion.
A Simple Capacities Setup: Projects, People, Meetings, Sources
Object-based notes sound complex, but the “secret” is to keep the number of objects small.
Capacities becomes powerful when your knowledge is connected — not when you build a complicated schema.
Here’s a setup that works for most knowledge work without turning your notes into a science project.
Start with four object types
Project – goals, status, links, next steps
Person – who they are, context, notes from conversations
Meeting – agenda, notes, decisions, action items
Source – articles, videos, docs, references, research links
Rule:
Every new note should attach to at least one object (Project, Person, Meeting, or Source).
That’s how your system stays connected.
Browser research workflow (fast and clean)
If you do research in the browser, Capacities works best when you keep your capture friction low:
1) Find sources: use Perplexity to locate 2–3 good sources.
2) Capture highlights: paste key points + the link into a Source object.
3) Add your take: write 2–5 bullets of what matters to you (not a summary of everything).
4) Link to a Project: connect the source to the project it supports.
Turn notes into outcomes
Capacities keeps context — but tasks need a task tool.
When you find action items, move them into
Todoist or
TickTick,
and execute using a focus timer like
Pomofocus.
Weekly review (the habit that makes it work)
A short weekly review keeps your knowledge system alive:
check active projects, skim recent meetings, and tag/clean anything that feels messy.
Without review, even the best system becomes a pile.
Final thoughts
Capacities is a strong tool if you want your notes to behave like a connected system.
Keep objects few, capture fast, and review weekly.
That’s enough structure to stay organized — without slowing you down.
FAQs
Quick answers to common questions people have when evaluating Capacities.
What is Capacities used for?
Capacities is used for object-based notes and personal knowledge management: connecting people, projects,
meetings, sources, and ideas into a structured system.
What does “object-based notes” mean?
Instead of writing isolated pages, you create “objects” (like Project, Person, Meeting, Source) and attach notes to them.
This keeps your information structured and reusable across your workspace.
Capacities vs Notion — what’s the difference?
Notion is an all-in-one workspace with docs and databases.
Capacities focuses on personal knowledge management with object-based linking and a “second brain” feel.
If you want a dedicated knowledge tool, Capacities is a strong alternative.
Capacities vs Obsidian — which should I choose?
Obsidian is a local-first, markdown-based notes tool with linking and plugins.
Capacities is more object-based and guided.
Choose the one that matches your preference: “markdown vault” vs “structured objects.”
How do I keep Capacities from becoming complicated?
Keep object types minimal, capture quickly, and review weekly.
Add new object types only when you see a repeated pattern that needs structure.