Verify

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.verify for the process verb in output
   • Use vocabulary.topic_map for MOC references
   • Use vocabulary.templates for the templates folder path
   • Use vocabulary.cmd_reflect for redirect when missing connections found

2. ops/config.yaml, processing depth, verification settings

   • processing.depth: deep | standard | quick
   • processing.verification.description_test: true | false
   • processing.verification.schema_check: true | false
   • processing.verification.link_check: true | false

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

Processing depth adaptation:

Depth	Verification Behavior
deep	Full verification: cold-read prediction, complete schema check, exhaustive link verification, MOC coverage, orphan risk analysis, content staleness detection, bundling analysis
standard	Balanced: cold-read prediction, schema check, link verification, MOC coverage
quick	Basic: schema check, link verification only. Skip cold-read prediction and health analysis

EXECUTE NOW

Target: $ARGUMENTS

Parse immediately:

• If target contains a note name: verify that specific note
• If target contains --handoff: output RALPH HANDOFF block at end
• If target is "all" or "recent": verify recently created/modified notes
• If target is empty: ask which note to verify

Anti-Shortcut Warning

Before marking verification as passed, you MUST complete ALL four categories: