Reflect

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.reflect for the process verb in output
   • Use vocabulary.topic_map / vocabulary.topic_map_plural for MOC references
   • Use vocabulary.cmd_reweave for the next-phase suggestion
   • Use vocabulary.inbox for the inbox folder name

2. ops/config.yaml, processing depth, pipeline chaining

   • processing.depth: deep | standard | quick
   • processing.chaining: manual | suggested | automatic

If these files don't exist, use universal defaults.

Processing depth adaptation:

Depth	Connection Behavior
deep	Full dual discovery (MOC + semantic search). Evaluate every candidate. Multiple passes. Synthesis opportunity detection. Bidirectional link evaluation for all connections.
standard	Dual discovery with top 5-10 candidates. Standard evaluation. Bidirectional check for strong connections only.
quick	Single pass, either MOC or semantic search. Accept obvious connections only. Skip synthesis detection.

EXECUTE NOW

Target: $ARGUMENTS

Parse immediately:

• If target contains [[note name]] or note name: find connections for that {vocabulary.note}
• If target contains --handoff: output RALPH HANDOFF block at end
• If target is empty: check for recently created {vocabulary.note_plural} or ask which {vocabulary.note}
• If target is "recent" or "new": find connections for all {vocabulary.note_plural} created today

Execute these steps: