Add Domain

You are extending an existing knowledge system with a new domain. This is composition, not replacement. The new domain must coexist with existing domains while maintaining its own vocabulary, schema, and processing patterns. The shared graph (wiki links, hub MOC, description fields) connects everything.

Your Task

Add a new knowledge domain: $ARGUMENTS

Reference Files

Read these during derivation phases:

Composition rules:

• ${CLAUDE_PLUGIN_ROOT}/reference/derivation-validation.md -- Test 4 (Multi-Domain Composition) validates the pattern
• ${CLAUDE_PLUGIN_ROOT}/reference/three-spaces.md -- three-space architecture (shared across domains)
• ${CLAUDE_PLUGIN_ROOT}/reference/interaction-constraints.md -- coherence validation for domain config

Domain configuration:

• ${CLAUDE_PLUGIN_ROOT}/reference/vocabulary-transforms.md -- domain-native term mapping
• ${CLAUDE_PLUGIN_ROOT}/reference/tradition-presets.md -- pre-validated domain configurations
• ${CLAUDE_PLUGIN_ROOT}/reference/use-case-presets.md -- 3 presets with configurations
• ${CLAUDE_PLUGIN_ROOT}/reference/dimension-claim-map.md -- research backing for dimension positions
• ${CLAUDE_PLUGIN_ROOT}/reference/failure-modes.md -- domain vulnerability matrix

Validation:

• ${CLAUDE_PLUGIN_ROOT}/reference/kernel.yaml -- the 12 non-negotiable primitives
• ${CLAUDE_PLUGIN_ROOT}/reference/validate-kernel.sh -- kernel validation script

---

PHASE 1: Scan Existing System

Automated. Understand what exists before adding to it.

1a. Read system configuration

Read ops/derivation.md for:

• Current dimension positions
• Vocabulary mapping
• Platform and automation level
• Active feature blocks

Read ops/config.yaml for live configuration values.

1b. Inventory existing domains

Identify all current knowledge domains:

• Primary notes folder and its domain vocabulary
• Any existing secondary domains (folders, templates, MOCs)
• Schema fields in use per domain