Carter's Knowledge Base

SCHEMA

2 min read

Wiki Schema

Domain

Personal knowledge base for Carter — notes, research, ideas, projects, references, and useful information worth preserving and cross-linking over time.

Conventions

  • File names: lowercase, hyphens, no spaces (e.g., project-ideas.md)
  • Every wiki page starts with YAML frontmatter
  • Use [[wikilinks]] to link between pages when related
  • When updating a page, always bump the updated date
  • Every new page must be added to index.md under the correct section
  • Every action must be appended to log.md
  • Prefer concise, scannable pages over long dumps of raw text
  • Keep raw source material in raw/; do not rewrite it there

Frontmatter

---
title: Page Title
created: YYYY-MM-DD
updated: YYYY-MM-DD
type: entity | concept | comparison | query | summary
tags: [from taxonomy below]
sources: [raw/articles/source-name.md]
---

Tag Taxonomy

  • personal
  • notes
  • idea
  • project
  • software
  • ai
  • research
  • learning
  • writing
  • workflow
  • tool
  • reference
  • concept
  • people
  • company
  • product
  • school
  • career
  • health
  • finance
  • media
  • comparison
  • summary
  • question
  • habit
  • planning

Rule: every tag on a page must appear in this taxonomy. Add new tags here before using them.

Page Thresholds

  • Create a page when an idea, project, person, tool, or topic becomes important enough to revisit
  • Add to existing page when new material extends something already covered
  • Don’t create a page for a passing mention with no likely future value
  • Split a page when it exceeds ~200 lines or starts mixing unrelated ideas
  • Archive a page when it is obsolete and fully superseded

Entity Pages

Use for notable people, companies, products, tools, apps, courses, or organizations. Include:

  • What it is
  • Why it matters
  • Key facts
  • Relationships to other pages
  • Sources or context

Concept Pages

Use for ideas, themes, methods, questions, or areas of interest. Include:

  • Definition or framing
  • Key takeaways
  • Open questions
  • Related concepts

Comparison Pages

Use for side-by-side analyses, tradeoffs, and decisions. Include:

  • What is being compared
  • Criteria
  • Summary verdict
  • Links to supporting pages

Update Policy

When new information conflicts with existing content:

  1. Prefer newer and better-sourced information
  2. If both views matter, note both with dates/context
  3. Flag meaningful contradictions explicitly in the page
  4. Surface unresolved conflicts for review

Graph View