Template Overview

Tags are easy to create and even easier to ruin. Without strict discipline, vaults degrade into a mess of overlapping, obsolete, and misspelled tags. The Tag Taxonomy Controlled Vocabulary establishes an authoritative dictionary of approved tags, defines nested parent-child hierarchies, and provides deprecation rules in plain Markdown.

Markdown Template Structure

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

---
title: "Tag Dictionary: [Vault Name] Controlled Vocabulary"
date_updated: [YYYY-MM-DD]
taxonomist: "[[Your Name]]"
total_approved_tags: 32
deprecated_tags_purged: 45
tag_format_standard: "Nested Kebab-Case (#parent/child-name)"
tags: [pkm, taxonomy, tags, controlled-vocabulary, vault-maintenance]
---

# Tag Taxonomy Controlled Vocabulary — [Vault Name]

## 1. Tagging Philosophy & The Rule of Parsimony
- **The Golden Rule:** If an idea can be connected via a direct wikilink (`[[Note Name]]`), do **NOT** create a tag for it.
- **What Tags Are For:** Classifying **broad status**, **media types**, and **cross-cutting domains**.
- **Syntax Standard:** Strict lower-case, kebab-case, with forward slashes for nesting (e.g., `#status/seedling`).

## 2. Approved Canonical Tag Hierarchies

### Hierarchy 1: Note Maturity & Lifecycle Status (`#status/*`)
*Used in frontmatter to track the evolutionary stage of a note:*
- `#status/seedling` — Raw, unverified capture or fleeting thought.
- `#status/budding` — Actively developing note with initial evidence and links.
- `#status/evergreen` — Mature, atomic permanent note validated through spaced review.
- `#status/archived` — Inactive, preserved for historical reference only.

### Hierarchy 2: Structural Note Types (`#type/*`)
*Identifies the architectural category of the document:*
- `#type/concept` — Atomic synthesized evergreen note.
- `#type/literature` — Book excerpt, paper extraction, or media highlight.
- `#type/meeting` — Synchronous meeting record, briefing, or debrief.
- `#type/hub` — Map of Content (MOC) or Zettelkasten Hub index.
- `#type/journal` — Daily, weekly, or seasonal reflection log.

### Hierarchy 3: Cross-Cutting Knowledge Domains (`#domain/*`)
*Broad intellectual umbrellas (Max 8 root categories):*
- `#domain/systems` — Operating systems, compilers, low-level memory, hardware.
- `#domain/privacy` — Cryptography, zero-cloud architecture, local-first computing.
- `#domain/pkm` — Knowledge management, cognitive ergonomics, learning theory.
- `#domain/product` — Product discovery, UX research, strategy, customer empathy.
- `#domain/craft` — Technical writing, typography, software aesthetics, minimalism.

## 3. Deprecated Tags & Migration Mapping (Blacklist)
*Do NOT use these legacy tags; replace immediately during weekly audits:*

| Deprecated / Banned Tag | Reason for Deprecation | Approved Replacement |
|---|---|---|
| `#articles`, `#article` | Duplicate plurals & vague | `#type/literature` |
| `#quick_thoughts` | Broken snake_case | `#status/seedling` |
| `#apple-silicon` | Too specific; use wikilink | `[[Apple Silicon]]` |
| `#action-item`, `#urgent-task` | High noise; use markdown checklist `- [ ]` | `- [ ]` checklist item |

## 4. Quarterly Tag Pruning Protocol
> [!TIP] Pruning Procedure
> 1. Run global search for untracked tags using `#` in vault search.
> 2. Check tag list against this dictionary.
> 3. Batch-rename rogue tags using global regex search and replace.

## 5. Maintenance Checklist
- [ ] Verify zero uppercase letters in all vault tags.
- [ ] Confirm no tag has fewer than 3 associated notes (prune one-off tags).

Filled Real-World Example

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

---
title: "Taxonomy: Research Vault Controlled Vocab"
date_updated: 2026-10-06
taxonomist: "[[Elena Rostova]]"
total_approved_tags: 28
tags: [taxonomy, pkm]
---

# Tag Taxonomy Controlled Vocabulary — Research Vault

## 1. Summary
Elena Rostova purged 68 redundant one-off tags across the research vault, collapsing them into 4 clean nested hierarchies (`#status/*`, `#type/*`, `#domain/*`, `#project/*`).

## 2. Outcome
Vault search precision improved instantly; zero tag clutter in sidebar panels.

When to Use and When to Avoid

When to Use

  • Use to establish and maintain an authoritative list of permitted tags in your vault.
  • Use during monthly or quarterly vault cleanup sessions to eliminate tag proliferation.
  • Use to onboard team members to shared corporate or open-source documentation vaults.

When to Avoid

  • Avoid using as a replacement for conceptual thinking and direct associative wikilinks.
  • Avoid creating a taxonomy with hundreds of rigid tags that feel like a bureaucratic burden.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the existing vault tag index:
1. Identify tag sprawl, casing inconsistencies, duplicate plurals, and one-off rogue tags.
2. Group approved concepts into clean nested hierarchies (#status/*, #type/*, #domain/*).
3. Generate an authoritative Tag Taxonomy Controlled Vocabulary with deprecation mapping in Markdown.

Your data remains securely on your Mac with zero cloud exposure.

Frequently Asked Questions

What is tag sprawl in note-taking?

The chaotic proliferation of inconsistent, duplicate, or near-identical tags (e.g., #writing, #write, #articles, #blogging) that makes filtering notes useless.

What is a controlled vocabulary?

A carefully curated, authoritative list of standardized terms and nested hierarchies that users commit to using across all files.

Should I use nested tags like #dev/swift?

Yes. Nested tags (e.g., #domain/subdomain) allow you to filter notes broadly at the parent level or narrowly at the child level in Obsidian and other tools.