seed

## EXECUTE NOW **Target: $ARGUMENTS** The target MUST be a file path. If no target provided, list {DOMAIN:inbox}/ contents and ask which to seed. ### 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.** Seed the source file into the processing queue. --- ## Step 1: Validate Source Confirm the target file exists. If it does not, check common locations: - `{DOMAIN:inbox}/{filename}` - Subdirectories of {DOMAIN:inbox}/ If the file cannot be found, report error and stop: ``` ERROR: Source file not found: {path} Checked: {locations checked} ``` Read the file to understand: - **Content type**: what kind of material is this? (research article, documentation, transcript, etc.) - **Size**: line count (affects chunking decisions in /reduce) - **Format**: markdown, plain text, structured data ## Step 2: Duplicate Detection Check if this source has already been processed. Two levels of detection: ### 2a. Filename Match Search the queue file and archive folders for matching source names: ```bash SOURCE_NAME=$(basename "$FILE" .md | tr ' ' '-' | tr '[:upper:]' '[:lower:]') # Check queue for existing entry # Search in ops/queue.yaml, ops/queue/queue.yaml, or ops/queue/queue.json grep -l "$SOURCE_NAME" ops/queue*.yaml ops/queue/*.yaml ops/queue/*.json 2>/dev/null # Check archive folders ls -d ops/queue/...