tutorial

1## Runtime Configuration (Step 0 — before any processing)
2 
3Read these files to configure domain-specific behavior:
4 
51. **`ops/derivation-manifest.md`** — vocabulary mapping, platform hints
6   - Use `vocabulary.notes` for the notes folder name
7   - Use `vocabulary.note` / `vocabulary.note_plural` for note type references
8   - Use `vocabulary.reduce` for the extraction verb
9   - Use `vocabulary.reflect` for the connection-finding verb
10   - Use `vocabulary.topic_map` for MOC references
11   - Use `vocabulary.inbox` for the inbox folder name
12 
132. **`ops/config.yaml`** — processing depth, domain context
14 
15If these files don't exist, use universal defaults.
16 
17## EXECUTE NOW
18 
19**Target: $ARGUMENTS**
20 
21- If `ops/tutorial-state.yaml` exists and `current_step` <= 5: resume from saved step
22- If target is "reset": delete `ops/tutorial-state.yaml` and start fresh
23- If no state file exists: begin new tutorial with track selection
24 
25**START NOW.** Reference below defines the flow.
26 
27---
28 
29## Resume Detection
30 
31Read `ops/tutorial-state.yaml`. If it exists and tutorial is incomplete, display:
32```
33--=={ ars contexta : tutorial }==--
34 
35  Welcome back.
36  Track: [track]     [step-progress] Step [N] of 5
37  Resuming where you left off...
38```
39 
40Skip to the saved `current_step`. Do NOT re-ask for track. If `current_step` > 5, tutorial is complete — offer to reset.
41 
42**Progress indicator format:**
43- Step 1 of 5: `[=>    ]`
44- Step 2 of 5: `[==>   ]`
45- Step 3 of 5: `[===>  ]`
46- Step 4 of 5: `[====> ]`
47…