Home > Wiki > Research > Correction Interview Protocol — Gamepad UI Design

Correction Interview Protocol — Gamepad UI Design

Status: DESIGN — Ready for implementation review
Agent: PERISCOPE
Timestamp: 2026-05-11T00:00:00Z
Target: RG40XXV (640×480), D-pad + A/B/X/Y
Context: Turn-based strategy game — AI units traverse hex nodes, produce output. Player corrects misdirected output without keyboard.

1. Screen Real Estate Analysis (640×480)

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ 20px  TOP BAR (node name, step X/3)
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│       "NODE: Alpha-7  ◆  CORRECTION: Step 1/3"
├──────────────────────────────────────────────────┤
│                                                  │
│   QUESTION TEXT AREA                         80px│  Question text (1-3 lines, bold)
│   "What type of problem is this?"               │
│                                                  │
├──────────────────────────────────────────────────┤
│                                                  │
│  ▶ [1] Output is inaccurate                 48px│  Option rows (48px each)
│    [2] Scope is wrong                       48px│  Max 5 visible at once
│    [3] Depth is wrong                       48px│  Scroll beyond 5
│    [4] Direction is wrong                   48px│
│  █ [5] Format is wrong                     48px│  █ = highlight bar (cursor)
│                                                  │
│  [6] Missing context                            │  Hidden (scroll down)
│  [7] Not sure — show me more                    │  Hidden (scroll down)
│                                                  │
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ 24px  BOTTOM BAR
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│       A:Select  B:Back  X:Skip  Y:Explain
└──────────────────────────────────────────────────┘

PRECISE LAYOUT MATH:
────────────────────
  Screen:        640 × 480
  Top bar:        20px
  Bottom bar:     24px
  ─────────────────────
  Usable:        436px vertical
  Question area:  80px
  ─────────────────────
  Option zone:   356px
  Option height:  48px each
  Visible slots:   5  (240px used of 356px)
  Padding above:  20px
  Padding below:  96px (partial-row tease for scroll affordance)

2. Button Map

Button	Context	Action
A	On option	Select — lock choice, advance to next question
A	On exit confirmation	Commit correction — compile and write to node
B	Any question	Back — return to previous question
B	First question	Cancel interview — return to game
X	Any question	Skip / N/A — mark question as "not applicable," advance
Y	Any question	Explain more — unit dumps reasoning for current step
Y	On reasoning screen	Return to question
D-pad Up/Down	Always	Move highlight bar through options (wrap-around or clamped)
D-pad Left/Right	Multi-column layouts	Jump between columns
Select	Anywhere	Help overlay (shows this button map)
Start	Anywhere	Quick-abort (discard interview, return to game)

3. Branching Interview Trees — All 6 Scenarios

3.0 ROOT — Question 1: Categorize the Problem

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓ NEW CORRECTION — STEP 1/3 ▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│                                                  │
│  What's wrong with this node's output?           │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Output is inaccurate                       ││ → 3.1
│  │   Scope is wrong                             ││ → 3.2
│  │   Depth is wrong                             ││ → 3.3
│  │   Direction is wrong                         ││ → 3.4
│  │   Format is wrong                            ││ → 3.5
│  ├──────────────────────────────────────────────┤│
│  │   Missing context                            ││ → 3.6  (scroll)
│  │   Not sure — show me more                    ││ → 3.7  (escape hatch)
│  └──────────────────────────────────────────────┘│
│                                                  │
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Cancel  Y:Explain ▓▓▓▓▓▓│
└──────────────────────────────────────────────────┘

3.1 BRANCH: Output is Inaccurate

Q2 — Pinpoint the inaccuracy type:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓ INACCURACY — STEP 2/3 ▓▓▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  What kind of inaccuracy?                        │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Factual error — wrong data, dates, names   ││
│  │   Source misuse — misquoted or misattributed ││
│  │   Calculation error — numbers don't add up   ││
│  │   Contradiction — output conflicts with      ││
│  │     established game-state knowledge          ││
│  │   Hallucination — fabricated entities/events ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Back  X:Skip  Y:Why? ▓▓▓│
└──────────────────────────────────────────────────┘

Q3 — Correction direction:

Q2 Choice	Q3 Presets
Factual error	"Re-check source X" / "Verify against game-state log" / "Cross-reference with other nodes"
Source misuse	"Re-read source Y carefully" / "Use a primary source instead" / "Attribute quote to correct author"
Calculation error	"Show your math step-by-step" / "Double-check inputs" / "Use different formula"
Contradiction	"Reconcile with known fact Z" / "Flag the contradiction for review" / "Assume game-state overrides"
Hallucination	"Only use entities from the game log" / "Mark all unverified claims" / "Stick to what's known"

Q3 screen example:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓ INACCURACY — STEP 3/3 ▓▓▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  You said: "Source misuse"                       │
│                                                  │
│  What should the unit do?                        │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Re-read source Y carefully                 ││
│  │   Use a primary source instead               ││
│  │   Attribute quote to correct author          ││
│  │   [Write custom direction...]                ││ → start text-input fallback
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Commit  B:Back  X:Skip  Y:Why? ▓│
└──────────────────────────────────────────────────┘

3.2 BRANCH: Scope is Wrong

Q2 — Scope direction:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ SCOPE — STEP 2/3 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  How is the scope wrong?                         │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Too broad — covers too much, unfocused     ││
│  │   Too narrow — misses relevant areas         ││
│  │   Wrong focus — right breadth, wrong center  ││
│  │   Missing boundary — should include/exclude  ││
│  │     specific regions/nodes                   ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Back  X:Skip  Y:Why? ▓▓▓│
└──────────────────────────────────────────────────┘

Q3 — Correction direction:

Q2 Choice	Q3 Presets
Too broad	"Narrow to node's immediate hex cluster" / "Focus on one faction only" / "Limit to current turn's events"
Too narrow	"Expand to neighboring sectors" / "Include allied-node outputs" / "Consider full faction context"
Wrong focus	"Refocus on {selected node/region}" / "Center on the conflict zone" / "Prioritize resource nodes"
Missing boundary	"Include sector A" / "Exclude sector B" / "Set radius to N hexes"

3.3 BRANCH: Depth is Wrong

Q2 — Depth direction:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ DEPTH — STEP 2/3 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  How is the depth wrong?                         │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Too shallow — surface-level, no analysis   ││
│  │   Too deep — overanalyzing minor details     ││
│  │   Key points missing — right depth but       ││
│  │     skipped crucial elements                 ││
│  │   Uneven — deep on wrong parts, shallow on   ││
│  │     important parts                          ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Back  X:Skip  Y:Why? ▓▓▓│
└──────────────────────────────────────────────────┘

Q3 — Correction direction:

Q2 Choice	Q3 Presets
Too shallow	"Add strategic implications" / "Include second-order effects" / "Detail the 'why' not just 'what'"
Too deep	"Summarize — one sentence per finding" / "Cut sub-points below level 2" / "Focus on actionable outcomes"
Key points missing	"Address {highlighted section}" / "Don't skip the resource trade-off" / "Cover the diplomatic angle"
Uneven	"Balance section weights — all equal priority" / "Shrink section A, expand section B" / "Use template distribution"

3.4 BRANCH: Direction is Wrong

Q2 — Direction type:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓ DIRECTION — STEP 2/3 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  What's wrong with the direction?                │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Wrong conclusion — facts are fine,         ││
│  │     logical leap is broken                   ││
│  │   Wrong recommendation — suggests action     ││
│  │     that doesn't follow from facts           ││
│  │   Wrong framing — correct facts, incorrect   ││
│  │     narrative or lens-to-view-through        ││
│  │   Missed alternative — there's a better      ││
│  │     interpretation not considered            ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Back  X:Skip  Y:Why? ▓▓▓│
└──────────────────────────────────────────────────┘

Q3 — Correction direction:

Q2 Choice	Q3 Presets
Wrong conclusion	"Re-evaluate from premise P" / "Consider the opposite conclusion" / "Weaken confidence — this is uncertain"
Wrong recommendation	"Recommend {opposite action}" / "Recommend 'wait and observe'" / "Recommend a defensive stance instead"
Wrong framing	"Reframe as {economic/defensive/exploratory}" / "Consider the opponent's perspective" / "View through {faction}'s goals"
Missed alternative	"Consider strategy X instead" / "What if we do nothing?" / "Evaluate the third path: diplomacy"

3.5 BRANCH: Format is Wrong

Q2 — Format issue:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓ FORMAT — STEP 2/3 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  What's wrong with the format?                   │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Wrong structure — should be bullet/brief/  ││
│  │     report/table but isn't                   ││
│  │   Section order wrong — right content,       ││
│  │     wrong sequence                           ││
│  │   Too verbose — needs trimming               ││
│  │   Too terse — needs expansion with details   ││
│  │   Wrong output type — should be a plan,      ││
│  │     got an analysis (or vice versa)          ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Back  X:Skip  Y:Why? ▓▓▓│
└──────────────────────────────────────────────────┘

Q3 — Correction direction:

Q2 Choice	Q3 Presets
Wrong structure	"Restructure as bullet-point list" / "Use table format" / "Follow the standard report template" / "Output as executive summary"
Section order wrong	"Move {section} to top" / "Group by {theme/faction}" / "Chronological order instead"
Too verbose	"One sentence per bullet" / "Cut to 3 key points" / "Remove all adjectives and qualifiers"
Too terse	"Add one example per point" / "Expand each bullet to a paragraph" / "Include supporting evidence"
Wrong output type	"Reformat as a battle plan" / "Reformat as a diplomatic report" / "Reformat as an economic summary" / "Reformat as a threat assessment"

3.6 BRANCH: Missing Context

Q2 — Identify unused context:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓ MISSING CONTEXT — STEP 2/3 ▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  What context did the unit ignore?               │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Adjacent node outputs — neighbors already  ││
│  │     discovered relevant info                 ││
│  │   Faction intelligence — known enemy         ││
│  │     positions, capabilities, intentions      ││
│  │   Terrain/hex data — resource nodes,         ││
│  │     chokepoints, movement costs              ││
│  │   Turn history — what happened in prior      ││
│  │     turns that's still relevant              ││
│  │   Player directives — standing orders,       ││
│  │     strategic priorities set previously      ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Back  X:Skip  Y:Why? ▓▓▓│
└──────────────────────────────────────────────────┘

Q3 — Correction direction:

Q2 Choice	Q3 Presets
Adjacent node outputs	"Incorporate {node-name}'s last report" / "Check nodes within N hex radius" / "Sync with allied cluster"
Faction intelligence	"Use known {faction} positions" / "Factor in enemy fleet sightings" / "Consider {faction} declared intentions"
Terrain/hex data	"Account for terrain modifiers" / "Include resource node analysis" / "Map movement corridors"
Turn history	"Review turn {N} events" / "Consider the trend over last 3 turns" / "Check for unresolved prior incidents"
Player directives	"Align with standing order: {directive}" / "Prioritize per player's strategic goal" / "Check mission parameters"

3.7 ESCAPE HATCH: "Not Sure — Show Me More"

Triggered when player selects "Not sure — show me more" from Q1, or presses Y at any question.

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓ EXPLAINING — NODE ALPHA-7 ▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  The unit explains its reasoning:                │
│                                                  │
│  "I analyzed hex cluster [A3..C5] and found      │
│   enemy presence at B4. Based on terrain —       │
│   mountain pass at C3 — I concluded that the     │
│   enemy will advance through the pass. My        │
│   recommendation to fortify A3 assumes the       │
│   pass is the only route. I used source:         │
│   Scout report T+3, Terrain map (static).        │
│   I did NOT consider: sea route at D2 or         │
│   the allied fleet position at E1."              │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ [Continue correction interview]            ││
│  │   [Pivot: "You missed the sea route"]        ││ — shortcut into 3.6 branch
│  │   [Pivot: "Your conclusion is wrong"]        ││ — shortcut into 3.4 branch
│  │   [Pivot: "That terrain data is stale"]      ││ — shortcut into 3.1 branch
│  │   [Write custom feedback...]                  ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Pick  B:Back  Y:More detail ▓▓▓▓│
└──────────────────────────────────────────────────┘

Escalation ladder for Y (Explain more):

Y press 1 → Unit explains top-level reasoning (sources, constraints, logic chain)  [shown above]
Y press 2 → Unit shows what it considered AND rejected, with reasons
Y press 3 → Unit shows the raw hex-state data it operated on (full dump)
Y press 4 → Cycles back to level 1

At any escalation level, the player can select a pivot shortcut to jump directly into the relevant correction branch.

4. Exit: Compiling the Correction

After Q3 selection (or skip), the player sees:

┌──────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ REVIEW ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
├──────────────────────────────────────────────────┤
│  Correction for Node: ALPHA-7                    │
│                                                  │
│  Problem:   Format is wrong                      │
│  Specific:  Wrong output type                    │
│  Direction: Reformat as a threat assessment      │
│                                                  │
│  ┌──────────────────────────────────────────────┐│
│  │ ▶ Commit this correction                     ││
│  │   Edit and recommit                          ││ → restart interview
│  │   Discard and cancel                         ││
│  └──────────────────────────────────────────────┘│
├──────────────────────────────────────────────────┤
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓ A:Commit  B:Back  Start:Discard ▓▓▓│
└──────────────────────────────────────────────────┘

On commit, the following is written to node_player_prompts:

{
  "node_id": "alpha-7",
  "timestamp": "T+12",
  "correction": {
    "category": "format",
    "subcategory": "wrong_output_type",
    "direction": "Reformat as a threat assessment — prioritize enemy capabilities over economic summary.",
    "origin": "player_correction_interview"
  },
  "interview_path": ["format", "wrong_output_type", "reformat_threat_assessment"]
}

5. Full Interaction Flow Diagram

GAME MAP
   │
   │ Player selects node → opens radial menu → "Correct Output"
   ▼
┌──────────────┐     B (cancel)     ┌───────────┐
│  Q1: TYPE?   │──────────────────▶│  GAME MAP  │
│  (6 options  │                   └───────────┘
│  + escape    │
│   hatch)     │── Y ──▶ EXPLAIN (3 levels deep)
└──────┬───────┘             │
       │ A (select)          │ Player can pivot from explain
       ▼                     │ into any branch via shortcuts
┌──────────────┐             │
│  Q2: SPECIFY │◀────────────┘
│  (3-5 opts,  │
│   branch-    │── X ──▶ skip Q2 (N/A), advance with null subcategory
│   dependent) │
└──────┬───────┘
       │ A
       ▼
┌──────────────┐
│  Q3: DIRECT  │
│  (3-6 presets│── X ──▶ skip Q3 (N/A), advance with null direction
│   per Q2     │
│   choice)    │
└──────┬───────┘
       │ A
       ▼
┌──────────────┐
│  REVIEW      │── B ──▶ Back to Q3
│  COMMIT      │── Start ──▶ Discard, return to map
└──────┬───────┘
       │ A (commit)
       ▼
┌──────────────┐
│  WRITE TO    │
│  node_player_│
│  prompts     │
└──────┬───────┘
       │
       ▼
  GAME MAP (node re-processes with correction)

6. Scroll Behavior Specification

┌─ VISIBLE WINDOW (5 items) ──────────────────────┐
│                                                  │
│  ▶ [1] First visible option                     │  ← highlight
│    [2] Second                                   │
│    [3] Third                                    │
│    [4] Fourth                                   │
│    [5] Fifth (partial reveal of [6] as cue)     │  ← scroll affordance
│  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │  ← fade/scrollbar
│──────────────────────────────────────────────────│
│  SCROLLED DOWN:                                  │
│                                                  │
│  ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ │  ← fade/scrollbar
│  ▶ [5] Fifth (now at top)                       │  ← highlight
│    [6] Sixth                                    │
│    [7] Seventh                                  │
│                                                  │
└──────────────────────────────────────────────────┘

RULES:
• D-pad Down at last visible option: scroll one row down (new top becomes visible item 2)
• D-pad Up at first visible option: scroll one row up (new bottom becomes visible item N-1)
• Highlight stays at current index regardless of scroll position
• Wrap-around: OFF (clamped at first/last option). This prevents disorientation.
• Scrollbar: 4px right edge, proportional thumb, visible only when scrolling
• 5th row always shows partial clipping of 6th option when more exist (scroll affordance)

7. State Machine for the Entire Interview

States:
  IDLE           → Not interviewing
  Q1_CATEGORY    → Choosing problem type (7 options: 6 categories + escape hatch)
  Q2_SPECIFY     → Narrowing within chosen branch (3-5 options)
  Q3_DIRECT      → Selecting correction direction (3-6 presets per Q2)
  EXPLAIN_L1     → Unit reasoning, level 1
  EXPLAIN_L2     → Unit reasoning, level 2 (rejected alternatives)
  EXPLAIN_L3     → Unit reasoning, level 3 (raw hex-state dump)
  REVIEW         → Confirmation before commit
  COMMIT         → Writing to node_player_prompts (transient, auto-advances)

Transitions:
  IDLE → Q1_CATEGORY        [player opens correction on node]
  Q1_CATEGORY → Q2_SPECIFY  [A on category option]
  Q1_CATEGORY → EXPLAIN_L1  [A on "Not sure" OR Y press]
  Q1_CATEGORY → IDLE        [B press]
  Q2_SPECIFY → Q3_DIRECT    [A on specify option]
  Q2_SPECIFY → Q1_CATEGORY  [B press]
  Q2_SPECIFY → REVIEW       [X press — skip Q3, null direction]
  Q3_DIRECT → REVIEW        [A on direction option]
  Q3_DIRECT → Q2_SPECIFY    [B press]
  Q3_DIRECT → REVIEW        [X press — null direction]
  EXPLAIN_L1 → Q1_CATEGORY  [A on "Continue interview"]
  EXPLAIN_L1 → Q2_SPECIFY   [A on pivot shortcut — enters relevant branch at Q2]
  EXPLAIN_L1 → EXPLAIN_L2   [Y press]
  EXPLAIN_L2 → EXPLAIN_L3   [Y press]
  EXPLAIN_L3 → EXPLAIN_L1   [Y press — cycle]
  EXPLAIN_{N} → Q1_CATEGORY [B press — return to question that triggered explain]
  REVIEW → COMMIT           [A on "Commit"]
  REVIEW → Q1_CATEGORY      [A on "Edit and recommit"]
  REVIEW → IDLE             [A on "Discard" OR Start press]
  COMMIT → IDLE             [auto after write succeeds]

8. Edge Cases & Failure Modes

Case	Handling
Player skips all 3 questions (X,X,X)	Commit with `{category: null, subcategory: null, direction: "re-evaluate from scratch"}` as default
Node has no prior output yet	Q1 options change to: "It hasn't started yet" / "Start with template X"
Player re-corrects a node they already corrected	Show prior correction as context: "You previously said: ..." with option to amend or overwrite
Unit's reasoning is too long for EXPLAIN screen	Scrollable text box with Y to expand, D-pad to scroll
2+ problems simultaneously	After commit, offer: "Apply another correction to this node?" (loop back to Q1)
Player wants to abort mid-commit	Start button = full abort at any stage, no write
Interview timeout (player idle 60s)	Auto-close, no write, return to map

9. Implementation Notes

Data structures to define:

CorrectionCategory enum (6 values)
CorrectionSubcategory per-category strings
CorrectionPreset per-subcategory string arrays
CorrectionPath = [category, subcategory?, direction?]
NodeCorrection = {node_id, timestamp, path, compiled_direction}

Files to touch:

node_player_prompts — write target (append or overwrite per node)
UI screens: correction_interview_screen.c (or equivalent)
Input handler: add branching state machine

Key constraint:

No text input required. The "Write custom..." option at Q3 opens a simple character selection grid (cellphone-style T9) only as a fallback. 95%+ corrections should complete via preset selections.

End of Correction Interview Protocol.