Topic Map of Content (MOC) Index Hub

Template Overview

As a personal knowledge vault grows beyond hundreds of atomic notes, pure bidirectional links can become a bewildering graph of connections. Without thematic entry points, you know an idea exists somewhere in your vault, but you struggle to reassemble its broader narrative.

A Map of Content (MOC) acts as a cartographic hub. Rather than imposing rigid, static folders, an MOC creates a flexible, living dashboard where related atomic notes are assembled into logical sequences, thematic clusters, and developmental stages.

This template provides an MOC architecture: domain metadata, introductory thesis, navigational table of contents, thematic clusters of wikilinks with analytical annotations, and open research questions for future vault development.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "MOC: [Core Domain / Theme Name]"
date: [YYYY-MM-DD]
type: "map-of-content"
status: "active-hub"
domain: "[Computer Science / Economics / Philosophy / Health]"
total_linked_notes: [Number]
tags: [zettelkasten, pkm, map-of-content, moc, knowledge-graph]
---

# MOC: [Core Domain / Theme Name]

## 1. Domain Overview & Guiding Inquiry
- **Core Domain Question:** What fundamental mystery or operational capability does this knowledge cluster explore?
- **The Central Thesis of This Map:** A concise paragraph summarizing how ideas in this cluster connect and reinforce one another.
- **Parent Hub / Upward MOC:** [[Higher-Level-Master-MOC]]

## 2. Navigational Clusters & Thematic Tracks

### Cluster 1: Foundational Principles & Core Invariants
*The non-negotiable theoretical baselines that govern this discipline.*
- [[Atomic-Note-1]]: Brief explanation of how this foundational concept anchors the cluster.
- [[Atomic-Note-2]]: The mathematical or philosophical derivation of the invariant.
- [[Atomic-Note-3]]: Historical precedents and classical roots of the theory.

### Cluster 2: Mechanisms, Architectures & Implementation
*How foundational principles translate into practical systems and structures.*
- [[Atomic-Note-4]]: The primary architectural blueprint or methodology.
- [[Atomic-Note-5]]: Failure modes, bottlenecks, and recovery protocols.
- [[Atomic-Note-6]]: Tooling, syntax, and execution workflows.

### Cluster 3: Trade-Offs, Critiques & Dialectical Tensions
*Where competing theories clash and nuanced practitioner judgment is required.*
- [[Atomic-Note-7]]: The economic cost or operational overhead of this paradigm.
- [[Atomic-Note-8]]: The prevailing orthodox critique and counter-arguments.

## 3. High-Priority Literature Sources & Foundation Works
| Key Source | Author | Core Contribution to This MOC | Vault Literature Note |
| :--- | :--- | :--- | :--- |
| *Foundational Book A* | Author X | Established the primary vocabulary | [[Lit-Book-A]] |
| *Benchmark Paper B* | Author Y | Provided empirical validation | [[Lit-Paper-B]] |

## 4. Unexplored Frontiers & Open Inquiries
- [ ] *Open Question 1:* How does [Emerging Technology] alter the trade-offs described in [[Atomic-Note-5]]?
- [ ] *Open Question 2:* What empirical dataset can test the assertions made in [[Atomic-Note-7]]?
- [ ] *Drafting Backlog:* Notes needed for [[Candidate-New-Concept]].

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "MOC: Local-First Software Architecture"
date: [YYYY-MM-DD]
type: "map-of-content"
status: "active-hub"
domain: "Distributed Systems & Personal Computing"
total_linked_notes: 24
tags: [zettelkasten, pkm, map-of-content, moc, knowledge-graph]
---

# MOC: Local-First Software Architecture

## 1. Domain Overview & Guiding Inquiry
- **Core Domain Question:** How do we construct software that grants users full data sovereignty, zero-latency local execution, and seamless multi-device collaboration without surrendering ownership to centralized cloud silos?
- **The Central Thesis of This Map:** Software applications should be ephemeral lenses operating over durable, permanent local files. By adopting local storage as the primary source of truth, computing returns to an intimate, human-centric ergonomic baseline.
- **Parent Hub / Upward MOC:** [[Software-Engineering-Master-MOC]]

## 2. Navigational Clusters & Thematic Tracks

### Cluster 1: Foundational Principles & Core Invariants
*The non-negotiable theoretical baselines of local computing.*
- [[File-Over-App-Philosophy]]: Software vendors are temporary; portable files are permanent.
- [[Zero-Network-Dependency-Invariant]]: Core user workflows must function identically with network hardware disabled.
- [[Keystroke-To-Glass-Latency-Limits]]: Text editors must render below 16ms to maintain creative flow.

### Cluster 2: Mechanisms, Data Structures & Implementation
*How local systems handle persistence and convergence.*
- [[Conflict-Free-Replicated-Data-Types]]: Mathematical formulations for merging concurrent edits without central servers.
- [[Append-Only-Log-Storage]]: Durable on-disk persistence patterns using crash-consistent journaling.
- [[SQLite-As-Application-File-Format]]: Why embedded relational databases outperform bespoke binary formats.

### Cluster 3: Trade-Offs, Critiques & Tensions
*The real engineering challenges of local-first architectures.*
- [[End-To-End-Encryption-Key-Recovery]]: The hazard of permanent data loss when users lose private encryption keys.
- [[Storage-Budget-Constraints-On-Mobile]]: Managing gigabyte-scale local datasets on storage-constrained mobile devices.
- [[Collaborative-Presence-Overhead]]: The computational cost of peer-to-peer discovery without central routing servers.

## 3. High-Priority Literature Sources & Foundation Works
| Key Source | Author | Core Contribution to This MOC | Vault Literature Note |
| :--- | :--- | :--- | :--- |
| *Local-First Software* (2019) | Kleppmann et al. | Coined the seven ideals of local-first software | [[Lit-Kleppmann-2019]] |
| *A Philosophy of Software Design* | John Ousterhout | Deep modules and interface minimization | [[Lit-Ousterhout-2018]] |

## 4. Unexplored Frontiers & Open Inquiries
- [ ] *Open Question 1:* How can local vector search indices be updated incrementally without causing battery drain on laptops?
- [ ] *Drafting Backlog:* Need an atomic note on [[Automerge-Versus-Yjs-Performance]].

When to Use and When to Avoid

When to Use

• Organizing dozens of related atomic notes into a coherent thematic map.
• Creating intermediate dashboards for complex research domains, book outlines, or software systems.
• Navigating large personal knowledge vaults without relying on rigid folder hierarchies.
• Visualizing gaps in your knowledge and identifying missing atomic notes to draft.

When to Avoid

• Managing single, isolated tasks or daily grocery shopping lists.
• Documenting brief software pull request changelogs.
• Organizing a small vault with fewer than 20 notes where direct search is sufficient.
• Tracking financial invoices or receipts.

On-Device AI Integration

Construct comprehensive Maps of Content with Oyma on macOS:

Analyze the collection of atomic notes and domain topic:
1. Synthesize the core domain inquiry and central organizing thesis.
2. Structure thematic clusters grouping related atomic wikilinks with analytical context.
3. Assemble the key literature foundation table and citation references.
4. Formulate open research questions and identify missing notes for the drafting backlog.
Output in structured, navigational CommonMark.

Your personal knowledge maps and intellectual graph remain completely local on your Mac.