tutorial

## 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.reduce` for the extraction verb - Use `vocabulary.reflect` for the connection-finding verb - Use `vocabulary.topic_map` for MOC references - Use `vocabulary.inbox` for the inbox folder name 2. **`ops/config.yaml`** — processing depth, domain context If these files don't exist, use universal defaults. ## EXECUTE NOW **Target: $ARGUMENTS** - If `ops/tutorial-state.yaml` exists and `current_step` <= 5: resume from saved step - If target is "reset": delete `ops/tutorial-state.yaml` and start fresh - If no state file exists: begin new tutorial with track selection **START NOW.** Reference below defines the flow. --- ## Resume Detection Read `ops/tutorial-state.yaml`. If it exists and tutorial is incomplete, display: ``` --=={ ars contexta : tutorial }==-- Welcome back. Track: [track] [step-progress] Step [N] of 5 Resuming where you left off... ``` Skip to the saved `current_step`. Do NOT re-ask for track. If `current_step` > 5, tutorial is complete — offer to reset. **Progress indicator format:** - Step 1 of 5: `[=> ]` - Step 2 of 5: `[==> ]` - Step 3 of 5: `[===> ]` - Step 4 of 5: `[====> ]` - Step 5 of 5: ...