pipeline

## EXECUTE NOW **Target: $ARGUMENTS** Parse immediately: - Source file path: the file to process (required) - `--handoff`: output RALPH HANDOFF block at end (for chaining) - If target is empty: list files in {DOMAIN:inbox}/ and ask which to process ### Step 0: Read Vocabulary Read `ops/derivation-manifest.md` (or fall back to `ops/derivation.md`) for domain vocabulary mapping. All output must use domain-native terms. If neither file exists, use universal terms. **START NOW.** Run the full pipeline. --- ## Pipeline Overview The pipeline chains four phases. Each phase uses skill invocation or /ralph for subagent-based processing. State lives in the queue file — the pipeline is stateless orchestration on top of stateful queue entries. ``` Source file | v Phase 1: /seed — create extract task, move source to archive | v Phase 2: /reduce (via /ralph) — extract claims from source | v Phase 3: /ralph (all claims) — create -> reflect -> reweave -> verify | v Phase 4: /archive-batch — move task files, generate summary | v Complete ``` The pipeline is the convenience wrapper. /ralph is the engine. /seed is the entry point. --- ## Phase 1: Seed Invoke /seed on the target file to create the extract task, check for duplicates, and move the source to its archive folder. **How to invoke:** Use the Skill tool if available, otherwise execute the /seed workflow directly: - Validate source exists - Check for prior processing (duplicate detec...