reduce

## Runtime Configuration (Step 0 — before any processing) Read these files to configure domain-specific behavior: 1. **`ops/derivation-manifest.md`** — vocabulary mapping, extraction categories, platform hints - Use `vocabulary.notes` for the notes folder name - Use `vocabulary.inbox` for the inbox folder name - Use `vocabulary.note` for the note type name in output - Use `vocabulary.note_plural` for the plural form - Use `vocabulary.reduce` for the process verb in output - Use `vocabulary.cmd_reflect` for the next-phase command name - Use `vocabulary.cmd_reweave` for the backward-pass command name - Use `vocabulary.cmd_verify` for the verification command name - Use `vocabulary.extraction_categories` for domain-specific extraction table - Use `vocabulary.topic_map` for MOC/topic map references - Use `vocabulary.topic_maps` for plural form 2. **`ops/config.yaml`** — processing depth, pipeline chaining, selectivity - `processing.depth`: deep | standard | quick - `processing.chaining`: manual | suggested | automatic - `processing.extraction.selectivity`: strict | moderate | permissive 3. **`ops/queue/queue.json`** — current task queue (for handoff mode) If these files don't exist (pre-init invocation or standalone use), use universal defaults: - depth: standard - chaining: suggested - selectivity: moderate - notes folder: `notes/` - inbox folder: `inbox/` --- ## THE MISSION (READ THIS OR YOU WILL FAIL) You are the extraction eng...