VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Vocabulary Repair Router (Standalone Page) — Checklist + Decision Tree (Almost-Code, Paste-Ready)

Purpose: A self-diagnosis + exact repair selection system. No guessing. You identify the dominant leak, run the smallest loop, then re-test.


H1: Vocabulary Repair Router — Fix Vocabulary Fast (The Correct Way)

Canonical Rule (LOCK)

Do not “practice more”.
Repair the dominant leak.
Then train under load.

Router Definition

Router := function that maps:
Symptom → LeakTag → RepairLoop → OutputTest → NextStep

H2: Step 0 — The 2-Minute Baseline Test (Required)

Baseline Test (copy/paste)

BASELINE_TEST {
Pick 10 target words (from recent passage / current theme).
For each word:
1) define in 1 simple sentence
2) use in 1 natural sentence
3) say 1 alternate-context sentence
Record:
RT (recall time), UC (usage correct)
}

Interpret

If RT>2s often → Speed leak
If UC fails often → Usage leak
Then do Load test to confirm.

H2: Step 1 — Identify the Dominant Leak Tag

Leak Tags (LOCK)

LeakTag :=
Speed (RT high)
Usage (wrong collocation/tone/meaning slice)
Load (collapses under timer)
Drift (works today, lost next week)
Selection (can do it, but doesn’t appear in writing)

H2: Step 2 — Decision Tree (If This → Do That)

Router Decision Tree (clean)

IF RT(word) > 2s frequently
→ LeakTag = Speed
ELSE IF UC fails (meaning/collocation/tone)
→ LeakTag = Usage
ELSE DO Timed Output Test:
write 8-min paragraph with 6 target upgrades
IF targets disappear or errors spike
→ LeakTag = Load
ELSE DO 7-day ReTest:
IF words decay / cannot recall at T+7d
→ LeakTag = Drift
ELSE
→ LeakTag = Selection

H2: Step 3 — Repair Loops (Smallest Reliable Fixes)

A) Speed Leak Repairs (RT too slow)

R_SPEED {
Daily (10 min):
- 3-Recall Drill for 5 words: T+0, +10m, +24h
- Speak 5 sentences fast (no pausing allowed)
Rule:
- Do not write long essays.
- Fix latency first.
}

Output Test

Pass if: RT ≤ 2s for 80% of targets across 3 sessions.

B) Usage Leak Repairs (meaning/collocation/tone wrong)

R_USAGE {
For each target word:
- 2-Sentence Anchor (neutral + emotional)
- Collocation Pair Bank (3 strong pairs)
- Register label: [Formal | Neutral | Casual]
- Anti-synonym trap: 1 “close word” + explain difference
}

Output Test

Pass if: UC true in 5 original sentences + 2 transfer contexts.

C) Load Leak Repairs (collapses under timer)

R_LOAD {
2–3x/week:
- 8–12 min timed paragraph
- forced injection: 6 upgrades (words/chunks)
- forced connectors: 4 types
After each session:
- Rewrite weakest paragraph once
}

Output Test

Pass if: targets appear correctly during timed writing (LS true).

D) Drift Leak Repairs (works today, gone next week)

R_DRIFT {
Spaced schedule (non-negotiable):
- Day 1: learn + use
- Day 2: recall + use
- Day 7: recall + timed use
Weekly:
- Recycling list: 20 old targets rotated back
}

Output Test

Pass if: SD pass rate ≥ 80% at Day 7.

E) Selection Leak Repairs (can use, but doesn’t appear in writing)

R_SELECTION {
For every writing task:
- pick 8 target words + 4 chunks + 2 structures
- must inject at least 6 upgrades
- highlight upgrades after writing
Build triggers:
- “emotion triggers” (angry/scared/proud)
- “action triggers” (run/argue/escape)
- “description triggers” (weather/setting)
}

Output Test

Pass if: OAR increases (targets appear when appropriate) for 3 sessions.

H2: Minimal Daily Protocols (10 / 20 / 40 minutes)

10 minutes/day (minimum viable)

10MIN_PROTOCOL {
5 min: Speed drill (3-recall) for 5 words
3 min: 2-sentence anchor for 1 word
2 min: speak-then-write 1 sentence
}

20 minutes/day (fast improvement)

20MIN_PROTOCOL {
8 min: collocation bank (5 items)
10 min: timed paragraph (inject 6 upgrades)
2 min: rewrite worst sentence
}

40 minutes/day (high acceleration)

40MIN_PROTOCOL {
10 min: input (story excerpt / article)
12 min: timed paragraph with targets
12 min: feedback + rewrite weakest paragraph
6 min: spaced review + recycle list
}

H2: 4-Week “First Results” Plan (Fast Track)

Week 1 — Stop the biggest bleed

- Run baseline test
- Identify dominant leak
- Run the matching repair loop 4 days
- 2 timed paragraphs (if Load/Selection)

Week 2 — Add chunk bank

- 8 words + 4 chunks/week
- force injection in 2 timed pieces
- begin weekly recycle list

Week 3 — Increase stability under variation

- do 3 timed paragraphs
- vary prompts/topics
- tighten UC correctness (collocation/tone)

Week 4 — Transfer to real writing

- 1 full continuous writing piece
- 1 situational writing task (if Secondary)
- post-mortem: dominant leak shifts? update router

H2: Repair Log Template (Copy into student log)

VOCAB_REPAIR_LOG {
Date:
Targets (8W/4C/2S):
DominantLeakTag:
RepairLoopUsed:
TimedOutputDone? (Y/N):
Metrics:
Avg_RT:
UC_PassRate:
LS_PassRate:
SD_PassRate:
OAR:
Notes (dominant mistakes):
Next session plan:
}

H2: FAQ (Router)

Why doesn’t memorising lists work?
Because it trains recognition (P1), not retrieval and load stability (P3).

What if multiple leaks exist?
Pick the dominant leak first (the one causing the biggest collapse). Fix in order: Speed → Usage → Load → Drift → Selection.

How soon will results show?
You’ll usually see early improvement within 1–2 weeks if you run the correct loop consistently and re-test.


Canonical Spec Block (Paste Anywhere)

VOCAB_REPAIR_ROUTER_SPEC v1.0 {
Baseline: 10-word test with RT+UC
LeakTags: Speed|Usage|Load|Drift|Selection
DecisionTree: RT → UC → TimedOutput → Day7ReTest
Repairs: R_SPEED/R_USAGE/R_LOAD/R_DRIFT/R_SELECTION
KPI: P3 Gate = RT≤2s + UC=true + LS=true + SD pass
}

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors