validate

## Runtime Configuration (Step 0 — before any processing) Read these files to configure domain-specific behavior: 1. **`ops/derivation-manifest.md`** — vocabulary mapping, platform hints - Use `vocabulary.notes` for the notes folder name - Use `vocabulary.note` / `vocabulary.note_plural` for note type references - Use `vocabulary.topic_map` for MOC references - Use `vocabulary.templates` for the templates folder path 2. **`ops/config.yaml`** — processing depth - `processing.depth`: deep | standard | quick If these files don't exist, use universal defaults. **Processing depth adaptation:** | Depth | Validation Behavior | |-------|---------------------| | deep | Full schema validation. All checks enabled including composability analysis and cross-reference verification | | standard | Full validation — all checks enabled | | quick | Basic schema validation only — required fields, YAML validity, enum values | ## EXECUTE NOW **Target: $ARGUMENTS** Parse immediately: - If target contains a note name: validate that specific note - If target contains `--handoff`: output RALPH HANDOFF block at end - If target is "all" or "notes": validate all notes in {DOMAIN:notes}/ directory - If target is empty: ask which note to validate **Execute these steps:** ### Step 1: Locate Template Determine which template applies to the target note: 1. Check the note's location — notes in {DOMAIN:notes}/ use the standard note template 2. Check the `type` field in frontmatter — ...