Get AI summaries of any video or article — Sign up free
Capacities' Three Fundamental Pillars thumbnail

Capacities' Three Fundamental Pillars

Capacities·
4 min read

Based on Capacities's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Capacities replaces file-and-folder storage with a network of connections so notes can relate to multiple contexts without being tied to one path.

Briefing

Capacities is built around three pillars designed to replace rigid file-and-folder thinking with a more brain-friendly system for capturing, organizing, and retrieving information. The centerpiece is a “network” approach to note-taking, where notes aren’t locked to a single location in an absolute file path. Instead, information can be connected to multiple contexts—so a note can link to the people, meetings, projects, or books it relates to. That flexibility reduces the friction of deciding where content “belongs,” and it supports staying in flow because creating links between ideas is faster and more natural than hunting through nested folders.

The second pillar adds structure without sacrificing connectivity: object-based note-taking. Rather than treating everything as generic pages scattered across folders, Capacities treats every piece of content as an object with a type. Built-in types exist (including “pages”), but users can also define object types that match real-world categories they work with—such as meetings or people. These object types can include custom properties, layouts, and templates, making the system feel tailored to how someone actually organizes their life and work. Importantly, these object types don’t replace the network; they live inside it. That means the same meeting can still connect to a relevant book and a specific person, while the repeated structure of object types makes common categories easier to browse and manage.

The third pillar is time-based note-taking, anchored by a calendar at the core of the system. Every item created is automatically time-stamped, and the app maintains a daily note that refreshes each day, along with a daily section that holds everything produced during that day. Users can review information through the daily view, but the calendar also supports longer-range perspectives through multi-day and weekly views. This removes the need to manually organize by date, while still enabling a “go back through time” way to revisit what happened and what was captured.

Taken together, the three pillars create three complementary routes to a personal knowledge base. The network makes retrieval connection-driven—finding content through relationships rather than memory of a file path. Object types make discovery category-driven—surfacing all meetings or all books by type. The calendar makes review time-driven—allowing users to track their notes across days and weeks. The result is a “studio for your mind,” aimed at building a knowledge system that fits how people naturally relate information, group it, and revisit it over time.

Cornell Notes

Capacities organizes knowledge around three pillars: network, object types, and time. Network note-taking replaces file paths by letting notes connect to multiple contexts, making retrieval feel relationship-based instead of location-based. Object-based note-taking adds structure by treating every piece of content as an object with a type, including custom types like meetings or people, complete with properties, layouts, and templates. Time-based note-taking anchors everything to a calendar, automatically time-stamping content and maintaining daily notes plus multi-day and weekly views. Together, these pillars support three ways to find and review information: by connections, by type, and by time.

Why does Capacities move away from file paths and folders in its note-taking approach?

File paths force information into a single “home,” implying it can only be useful in one place. That rigid structure makes it harder to decide where notes should live and harder to find them later if they relate to multiple contexts. The network approach avoids this by letting notes connect to everything they touch—so a note can be linked to multiple related items without being stored in one absolute location.

How does object-based note-taking introduce structure without breaking the network of connections?

Capacities treats every piece of content as an object with a type. Users can rely on built-in types like “pages,” or define their own types for categories they frequently work with (for example, meetings and people). These types can include custom properties, layouts, and templates. Crucially, these object types still exist within the network, so connections remain possible—for instance, linking a meeting to a book and a person while keeping category-based structure for easier browsing.

What does time-based note-taking add, and how is it implemented?

Time-based note-taking centers on a calendar core. Every item created is automatically time-stamped. The system maintains a daily note that refreshes each day and a daily section holding content created during that day. Users can review through daily, multi-day (e.g., 3 days), and weekly views, enabling a time-based way to revisit notes without manual organization.

What are the three main routes for rediscovering information in Capacities?

First, the network route: find content through connections rather than remembering a file path. Second, the object route: rediscover content by type, such as viewing all meetings or all books in a space. Third, the time route: review notes through the calendar, going back through days and weeks to see what was captured over time.

How do the pillars work together to support “flow” while capturing knowledge?

The network pillar makes linking content to relevant contexts quick and intuitive, reducing the overhead of deciding where something should be stored. Object types then provide reusable structure for common categories, avoiding repetitive navigation through deeply nested folders. Time-based features handle date organization automatically via the calendar and daily notes, freeing attention to focus on thinking and capturing rather than filing.

Review Questions

  1. How does network note-taking change the way users decide where information “belongs” compared with file paths?
  2. What benefits do object types provide, and how do they coexist with network connections?
  3. How does the calendar-based time system enable both daily review and longer-term reflection?

Key Points

  1. 1

    Capacities replaces file-and-folder storage with a network of connections so notes can relate to multiple contexts without being tied to one path.

  2. 2

    Network note-taking supports faster retrieval by finding content through relationships rather than remembering where it was stored.

  3. 3

    Object-based note-taking treats every content item as an object with a type, enabling category-specific organization.

  4. 4

    Custom object types can be created for real-life categories like meetings and people, including custom properties, layouts, and templates.

  5. 5

    Object types live inside the network, preserving the ability to connect items across categories (e.g., meeting ↔ book ↔ person).

  6. 6

    Time-based note-taking uses a calendar core with automatic time-stamping and daily notes that refresh each day.

  7. 7

    Multi-day and weekly calendar views provide a time-driven way to revisit notes beyond the daily view.

Highlights

Network note-taking removes the need to choose a single “home” for information by letting notes connect to multiple related contexts.
Object types add reusable structure—every item is an object with a type—while still allowing cross-linking through the network.
A calendar-centered system automatically time-stamps everything and supports daily, multi-day, and weekly review.

Topics