Note

Personal Knowledge Base Principles

Core rules for how this knowledge base should evolve over time.

Purpose

This repository is the single source of truth for decisions, experiments, and active learning.

Rules

  1. Capture context before details. Explain why something matters before implementation notes.
  2. Keep notes linked by tags so ideas can be discovered across domains.
  3. Prefer small frequent updates over large polished rewrites.
  4. Record next actions for any entry that is still active.

Quality checks

  • If a note has no tags, it is likely hard to discover.
  • If a project entry has no status, it is likely hard to prioritize.
  • If a journal entry does not end with one next action, momentum drops.