validate

1## Runtime Configuration (Step 0 — before any processing)
2 
3Read these files to configure domain-specific behavior:
4 
51. **`ops/derivation-manifest.md`** — vocabulary mapping, platform hints
6   - Use `vocabulary.notes` for the notes folder name
7   - Use `vocabulary.note` / `vocabulary.note_plural` for note type references
8   - Use `vocabulary.topic_map` for MOC references
9   - Use `vocabulary.templates` for the templates folder path
10 
112. **`ops/config.yaml`** — processing depth
12   - `processing.depth`: deep | standard | quick
13 
14If these files don't exist, use universal defaults.
15 
16**Processing depth adaptation:**
17 
18| Depth | Validation Behavior |
19|-------|---------------------|
20| deep | Full schema validation. All checks enabled including composability analysis and cross-reference verification |
21| standard | Full validation — all checks enabled |
22| quick | Basic schema validation only — required fields, YAML validity, enum values |
23 
24## EXECUTE NOW
25 
26**Target: $ARGUMENTS**
27 
28Parse immediately:
29- If target contains a note name: validate that specific note
30- If target contains `--handoff`: output RALPH HANDOFF block at end
31- If target is "all" or "notes": validate all notes in {DOMAIN:notes}/ directory
32- If target is empty: ask which note to validate
33 
34**Execute these steps:**
35 
36### Step 1: Locate Template
37 
38Determine which template applies to the target note:
39 
401. Check the note's location — notes in {DOMAIN:notes}/ use the standard note template
41…