Free tool · works now

Personal knowledge index builder

Build navigable plain-text Maps of Content without rigid hierarchies or prejudice against unassigned notes.

Vault Index & Map of Content (MOC) Builder

Generate an organized plain-text index from your note titles and topic rules without overcategorizing emergent thoughts.

Zero Cloud TelemetryRespects Unassigned IdeasObsidian & Markdown Native
Title rendered as the top-level H1 in the generated index document.
Choose between vault-native wikilinks or portable standard markdown links.
Structure by curated topical domains or alphabetical directory listing.
Respectful heading for notes that have not settled into a specific topic.
Accepts [[WikiLinks]], file paths, raw titles, and inline hashtags (#tag).
Format: "Topic Name: keyword1, keyword2". Notes matching zero topics go to Unassigned.
Total Notes10
Assigned Notes7
Exploratory Notes3
Topic Clusters3
Assignment Ratio70%
# Personal Knowledge Hub & Index
*Generated navigation index · 2026-11-19*
**Catalog Size:** 10 notes across 3 thematic areas

## Artificial Intelligence (4)
- [[Attention Mechanisms]]
- [[Positional Encoding in Sequence Models]]
- [[Notes/Graph Neural Networks.md]]
- [[Backpropagation Calculus]]

## Theoretical Computer Science (2)
- [[Notes/Graph Neural Networks.md]]
- [[P-vs-NP Problem Complexity]]

## Philosophy & Epistemology (2)
- [[Spinoza on Freedom and Determinism]]
- [[Epistemic Humility in Research]]

## Exploratory & Unassigned Notes (3)
> [!note] Epistemic Notice
> These notes are standalone exploratory ideas awaiting topic placement. Standalone thoughts are not low-quality notes; they reflect emerging ideas that have not yet settled into a specific cluster.

- [[Random Speculation on Microservices Architecture]]
- [[Quick Scratchpad on Local First Web Architecture]]
- [[Weekend Coffee Roasting Notes and Ratios]]
TitlePathStatusAssigned Topics
Attention Mechanisms—Assigneddeep-learning, transformers
Positional Encoding in Sequence Models—Assigneddeep-learning
Notes/Graph Neural Networks.mdNotes/Graph Neural Networks.mdAssignedgraphs, machine-learning
Backpropagation Calculus—Assignedmath, deep-learning
P-vs-NP Problem Complexity—Assignedcomputer-science, algorithms
Spinoza on Freedom and Determinism—Assignedphilosophy, ethics
Epistemic Humility in Research—Assignedphilosophy
Random Speculation on Microservices Architecture—ExploratoryAwaiting assignment
Quick Scratchpad on Local First Web Architecture—ExploratoryAwaiting assignment
Weekend Coffee Roasting Notes and Ratios—ExploratoryAwaiting assignment
Title,Path,Link Syntax,Status,Assigned Topics
"Attention Mechanisms","","[[Attention Mechanisms]]","Assigned","deep-learning; transformers; Artificial Intelligence"
"Positional Encoding in Sequence Models","","[[Positional Encoding in Sequence Models]]","Assigned","deep-learning; Artificial Intelligence"
"Notes/Graph Neural Networks.md","Notes/Graph Neural Networks.md","[[Notes/Graph Neural Networks.md]]","Assigned","graphs; machine-learning; Artificial Intelligence; Theoretical Computer Science"
"Backpropagation Calculus","","[[Backpropagation Calculus]]","Assigned","math; deep-learning; Artificial Intelligence"
"P-vs-NP Problem Complexity","","[[P-vs-NP Problem Complexity]]","Assigned","computer-science; algorithms; Theoretical Computer Science"
"Spinoza on Freedom and Determinism","","[[Spinoza on Freedom and Determinism]]","Assigned","philosophy; ethics; Philosophy & Epistemology"
"Epistemic Humility in Research","","[[Epistemic Humility in Research]]","Assigned","philosophy; Philosophy & Epistemology"
"Random Speculation on Microservices Architecture","","[[Random Speculation on Microservices Architecture]]","Unassigned (Exploratory)",""
"Quick Scratchpad on Local First Web Architecture","","[[Quick Scratchpad on Local First Web Architecture]]","Unassigned (Exploratory)",""
"Weekend Coffee Roasting Notes and Ratios","","[[Weekend Coffee Roasting Notes and Ratios]]","Unassigned (Exploratory)",""

Navigating Knowledge Vaults: The Architecture of Maps of Content (MOCs)

In personal knowledge management, one of the most persistent failure modes is the "taxonomy trap." When building a digital notebook, writers frequently begin by imposing rigid, mutually exclusive folder hierarchies—such as the Dewey Decimal Classification, Johnny.Decimal, or deep nested directories like Projects/2026/Clients/Acme/Research/Notes/.

Within months, these static folder taxonomies collapse under their own cognitive friction. Ideas are rarely mono-thematic: an essay on "Algorithmic Fairness in Medical Diagnostics" belongs simultaneously to Computer Science, Ethics, Healthcare Policy, and Philosophy of Science. Forcing the document into a single folder forces an arbitrary decision that conceals the note from future associative inquiry.

To resolve this dilemma without surrendering to complete disorganization, the digital gardening and Second Brain communities developed the Map of Content (MOC) pattern. Rather than relying on physical directory structures, an MOC is a fluid plain-text index note that curates links to related ideas within a specific conceptual domain.

1. What Makes a Map of Content Superior to Rigid Hierarchies?

A Map of Content functions like an intellectual hub or an annotated table of contents for your knowledge vault. It differs from a traditional folder in several fundamental architectural ways:

2. The Epistemic Value of Unassigned Notes: Refusing the "Orphan" Pejorative

A core philosophical mandate codified in our Master Plan (§TOOL-075) specifies that unlinked or unassigned notes must never be automatically classified as low quality.

Many automated note organizers and vault linters commit an epistemic error by labeling unassigned notes as "orphans," "abandoned," or "junk." This terminology creates psychological anxiety for the writer, prompting them to either delete embryonic thoughts or force them into premature categories where they lose their originality.

In serious intellectual inquiry, thoughts frequently begin in isolation:

  1. The Incubation State: An intuitive insight or counter-intuitive empirical observation often lacks an established theoretical framework. It sits as a standalone document for weeks or months before a subsequent paper reveals its underlying pattern.
  2. Ephemeral Scratchpads: Notes capturing sudden conversational remarks, dream recollections, or raw lecture fragments do not need immediate categorization to hold long-term utility.
  3. Epistemic Dignity: Our Personal Knowledge Index Builder isolates unassigned notes into a dedicated section titled Exploratory & Unassigned Notes, accompanied by an explicit epistemic notice. They are recognized as healthy seeds of future knowledge, not maintenance failures.

3. Link Syntax Standards: Obsidian Wikilinks vs Portable CommonMark Hyperlinks

When authoring index files in plain-text vaults, researchers face an operational tradeoff between editor convenience and cross-platform longevity:

The index builder supports both formatting paradigms, allowing you to generate an Obsidian-native MOC or an exportable, web-ready documentation hub with a single toggle.

4. Dynamic Dataview Queries vs Permanent Plain-Text Indexes

Many Obsidian users rely on community plugins like Dataview to generate automatic index tables using JavaScript queries (such as ```dataview LIST FROM #ai```). While convenient inside the application, dynamic queries have a major architectural vulnerability: they are not plain text.

If you open your vault in a standard text editor, on a mobile device without plugin support, or in a different markdown viewer ten years from now, a Dataview query renders as raw code. It contains zero actual links.

The Personal Knowledge Index Builder produces deterministic, static plain-text markdown lists. Every link is explicitly serialized into the file content. Even if the entire software ecosystem changes, your index remains 100% human-readable and navigable for decades to come.

5. Formula Injection Defense for Knowledge Catalogs

When exporting vault inventories to spreadsheet formats (.csv) for academic reporting or multi-contributor auditing, cells containing math formulas or command symbols (=, +, -, @) can execute malicious macros if opened in Excel or Google Sheets (CWE-1236). Our CSV engine sanitizes every title and path with leading apostrophe guards, guaranteeing safe spreadsheet inspection.

6. Privacy by Design: Zero Cloud Telemetry

Your personal knowledge graph contains your deepest intellectual curiosities, confidential research hypotheses, and personal journal reflections. The Personal Knowledge Index Builder runs completely in your browser’s local JavaScript sandbox. No note titles, topic keywords, or file paths are ever transmitted over the network.

7. Multi-Layer MOC Architecture: Higher-Order Maps (HOMOCs) vs Concept Clusters

As your knowledge vault matures from hundreds to thousands of notes, a single flat index becomes too lengthy to navigate efficiently. The digital gardening community addresses this by structuring knowledge across three distinct tiers of Maps of Content:

Our Personal Knowledge Index Builder allows you to generate either a top-level HOMOC or a targeted Domain MOC by adjusting your input note list and topic filters.

8. Transitioning from Legacy Folder Hierarchies to Associative Plain-Text Hubs

Writers transitioning from traditional hierarchical file trees often experience anxiety when flattening their folder structure. They fear that placing hundreds of notes in a single root folder or minimal directory structure will result in an unnavigable mess.

In practice, flat or shallow folder architectures (such as maintaining only Inbox/, Notes/, and Archive/) paired with explicit Maps of Content offer immense cognitive advantages:

  1. Elimination of Filing Hesitation: When capturing an idea, you never spend thirty seconds deliberating which folder it belongs in. You drop it into Notes/ and link it to an index when you perform your weekly review.
  2. Immunity to Path Breakage: Deeply nested folders frequently cause filesystem path limit errors on Windows (260-character MAX_PATH limit) and produce brittle relative hyperlinks. Flat vaults with descriptive titles completely eliminate path length collisions.
  3. Fluid Reorganization: Restructuring an academic discipline does not require moving fifty files across directories and praying your editor refactors the links. You simply edit the plain-text bullets inside the relevant Map of Content.

9. Long-Term Resiliency: Why Static Plain-Text Indexes Outlive Software Lifecycles

Over a multi-decade research career, note-taking applications inevitably come and go. Proprietary software systems (from HyperCard to Evernote, Roam Research, and venture-backed AI tools) routinely change pricing, alter data schemas, or shut down entirely.

A knowledge index constructed from static plain-text Markdown bullets and standard hyperlinks is mathematically immortal. It requires zero cloud databases, zero proprietary binary parsers, and zero server infrastructure. Even in thirty years, any standard Unix shell, text editor, or operating system file viewer will render your Map of Content with pristine clarity. Building indexes with our browser-local tool guarantees that your intellectual provenance remains completely sovereign and permanently accessible.

Questions

Why does this tool refuse to classify unassigned notes as "low quality"?

In creative writing and philosophical inquiry, nascent thoughts rarely fit neatly into predefined topical buckets. Automated taxonomy tools often label unassigned notes as "orphans," "abandoned," or "low quality," encouraging users to delete them or force them into ill-fitting categories. Our index builder preserves unassigned notes with full epistemic respect as exploratory ideas awaiting organic maturation.

What is a Map of Content (MOC) and how does it differ from a folder structure?

A Map of Content is a plain-text note that curates links to related notes within a specific domain. Unlike rigid filesystem folders—where a file can exist in only one directory—a note can appear across multiple Maps of Content simultaneously. For example, a note on "Game Theory" can naturally appear on both an Economics MOC and a Computer Science MOC.

Can I export both Obsidian wikilinks and standard Markdown hyperlinks?

Yes. The workbench allows toggling between native Obsidian [[WikiLinks]] (including piped aliases) and portable standard Markdown links [Title](path.md). This ensures your index remains fully readable in GitHub, static site generators, and standard text editors.

How does the tool map notes to thematic topics?

The engine uses transparent, deterministic matching: each topic definition declares keywords or hashtags (e.g. "Artificial Intelligence: deep-learning, transformers"). If a note title, path, or inline hashtag matches any declared keyword, it is placed in that topic bucket. Notes matching zero keywords are cleanly collected in the Exploratory & Unassigned section.

Are my private note titles, reading lists, or thoughts sent to external AI servers?

Never. All parsing, topic matching, and Markdown/CSV generation run 100% locally in your browser memory. No text or metadata is transmitted over the internet.

Organize Your Plain-Text Notes with Confidence on Oyma

Construct navigable knowledge indexes and durable Maps of Content without surrendering your private notes to cloud AI scanners.

tools personal knowledge index builder downloadDownload for Mac

No account needed. Intel Mac build