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.

LanguageOS Router Card Deck (20 cards)v

  • route_id
  • EL skeleton
  • Required VL islands
  • Common failures (sensors)
  • Repair moves
  • 2-sentence example
Spec: LanguageOS.RouterCardDeck
Version: v1.0.0
RecordType: ROUTER_CARD
Global Rules:
- EL first, then VL
- max_collocations_per_paragraph = 2
- no absolutes unless proven

Start Here:

CARD 01 — Suspense Build (1 paragraph)

route_id: ROUTE.NAR.002
EL: Normal → Odd detail → Escalation → Turn → Resolution
VL islands: [VL.CI.sensory_sound, VL.CI.sensory_sight, VL.CI.suspense]
Common failures: [EL.E3 LinkFailure, VL.S5 IntensityMismatch, VL.S4 CollocationClash]
Repairs: [ER3 InsertLinks, R4 TuneIntensity, R3 FixCollocation]
Example: The corridor fell silent when a faint tapping started at the window. In the dim light, the handle looked like a sharp silhouette—until I switched on the lamp and saw the blind cord swinging.

CARD 02 — Regret + Lesson (relationship repair)

route_id: ROUTE.NAR.003
EL: Mistake → Proof of hurt → Ownership/Apology → Repair action → One rule
VL islands: [VL.CI.ownership, VL.CI.apology, VL.CI.friendship]
Common failures: [VL.S6 PolarityDrift, EL.E5 ScopeLeak, EL.E4 ReferenceLeak]
Repairs: [R6 ReducePolarity, ER4 ShrinkScope, ER1 NameActors]
Example: I made a cold comment, and her smile faded, which showed I had crossed a line. I apologised without excuses and learned one rule: check facts before reacting.

CARD 03 — Failure → Adjustment → Success

route_id: ROUTE.NAR.005
EL: Fail → Why it failed → Adjustment → Proof of improvement → Reflection
VL islands: [VL.CI.failure, VL.CI.process, VL.CI.success]
Common failures: [EL.E6 LoadCollapse, EL.E3 LinkFailure, VL.S1 SenseWrong]
Repairs: [ER5 SplitLoad, ER3 InsertLinks, R1 ReplaceByEdge]
Example: I fell short because I rushed and skipped the final check. After I used a simple checklist, my accuracy improved and the result finally paid off.

CARD 04 — Humour Light (safe, non-cruel)

route_id: ROUTE.NAR.013
EL: Setup → Mismatch → Reaction → Recovery
VL islands: [VL.CI.humour_light, VL.CI.embarrassment]
Common failures: [VL.S6 PolarityDrift, VL.S2 RegisterMismatch, EL.E4 ReferenceLeak]
Repairs: [R6 ReducePolarity, R5 TuneRegister, ER1 NameActors]
Example: I waved confidently at the “teacher” and got an awkward pause in return. Then I realised it was a parent helper, so I laughed it off and slipped out.

CARD 05 — Calm Control Under Pressure (internal monologue)

route_id: ROUTE.NAR.016
EL: Pressure → Physical signal → Breath/Plan → Action → Outcome
VL islands: [VL.CI.anxiety, VL.CI.calm_control, VL.CI.time_pressure]
Common failures: [VL.S5 IntensityMismatch, EL.E2 TimeDrift, EL.E6 LoadCollapse]
Repairs: [R4 TuneIntensity, ER2 LockTense, ER5 SplitLoad]
Example: My heart raced when I saw the time limit, but I took a breath and started with the easiest question first. The plan steadied me, and I finished on time.

CARD 06 — Show Not Tell (emotion via sensory)

route_id: ROUTE.NAR.017
EL: Situation → Sensory cue → Action → Emotion (separate sentence)
VL islands: [VL.CI.sensory, VL.CI.intensity]
Common failures: [VL.S5 IntensityMismatch, EL.E6 LoadCollapse, VL.S4 CollocationClash]
Repairs: [R4 TuneIntensity, ER5 SplitLoad, R3 FixCollocation]
Example: Cold metal pressed into my palm as I gripped the railing. Only then did I realise I was more anxious than I wanted to admit.

CARD 07 — Friendship Test (trust arc)

route_id: ROUTE.NAR.011
EL: Trust → Break → Honest talk → Repair proof → Close
VL islands: [VL.CI.trust, VL.CI.ownership, VL.CI.warmth]
Common failures: [VL.S6 PolarityDrift, EL.E3 LinkFailure, EL.E5 ScopeLeak]
Repairs: [R6 ReducePolarity, ER3 InsertLinks, ER4 ShrinkScope]
Example: My trust was shaken when she broke her promise, but we spoke honestly and clarified what happened. Over time, she earned my trust again by following through consistently.

CARD 08 — Surprise Without Fear (clean expectation break)

route_id: ROUTE.NAR.021
EL: Expectation → Break → Pause → Explanation → New meaning
VL islands: [VL.CI.surprise, VL.CI.sensory_sight]
Common failures: [VL.S6 PolarityDrift, VL.S5 IntensityMismatch, EL.E3 LinkFailure]
Repairs: [R6 ReducePolarity, R4 TuneIntensity, ER3 InsertLinks]
Example: To my surprise, the “stranger” who helped me was actually my neighbour. The familiar smile changed the whole moment from suspicious to warm.

CARD 09 — Character Portrait (description with restraint)

route_id: ROUTE.NAR.026
EL: Trait claim → One scene proof → Impact on narrator → Close
VL islands: [VL.CI.description, VL.CI.warmth]
Common failures: [EL.E6 LoadCollapse, VL.S4 CollocationClash, EL.E5 ScopeLeak]
Repairs: [ER5 SplitLoad, R3 FixCollocation, ER4 ShrinkScope]
Example: Her voice was calm, and her gentle smile made the room feel safe. When I panicked, she explained the steps again, and that patience stayed with me.

CARD 10 — One Rule Ending (tight lesson, no preaching)

route_id: ROUTE.NAR.029
EL: Event → Mistake → Repair → One rule (small scope)
VL islands: [VL.CI.mistake, VL.CI.ownership, VL.CI.clarity]
Common failures: [EL.E5 ScopeLeak, VL.S5 IntensityMismatch, EL.E3 LinkFailure]
Repairs: [ER4 ShrinkScope, R4 TuneIntensity, ER3 InsertLinks]
Example: I interrupted before listening, and the conversation turned tense. One rule is enough: pause, listen, then speak.

CARD 11 — PEEL Argument (1 paragraph)

route_id: ROUTE.ARG.101
EL: Point → Evidence → Explain mechanism → Link back
VL islands: [VL.CI.argument, VL.CI.evidence, VL.CI.logic]
Common failures: [EL.E3 LinkFailure, EL.E5 ScopeLeak, VL.S1 SenseWrong]
Repairs: [ER3 InsertLinks, ER4 ShrinkScope, R1 ReplaceByEdge]
Example: Homework should be short and targeted because it reinforces key skills without draining sleep. This improves learning by keeping practice consistent and reducing rushed mistakes.

CARD 12 — Concession + Rebuttal (balanced)

route_id: ROUTE.ARG.102
EL: Counterpoint → Concede → Rebut → Stronger claim
VL islands: [VL.CI.politeness, VL.CI.argument, VL.CI.time_pressure]
Common failures: [EL.E5 ScopeLeak, VL.S6 PolarityDrift, Z0.WEAK absolutes]
Repairs: [ER4 ShrinkScope, R6 ReducePolarity, R1 ReplaceByEdge]
Example: Phones can help with quick research; however, unrestricted use often distracts students during explanations. Therefore, phones should be allowed only for specific tasks under teacher direction.

CARD 13 — Problem–Solution (policy)

route_id: ROUTE.ARG.109
EL: Problem → Causes → Solution steps → Checkpoint → Close
VL islands: [VL.CI.causality, VL.CI.process, VL.CI.neutrality]
Common failures: [EL.E3 LinkFailure, EL.E5 ScopeLeak, VL.S5 IntensityMismatch]
Repairs: [ER3 InsertLinks, ER4 ShrinkScope, R4 TuneIntensity]
Example: Excessive homework reduces sleep and creates rushed, careless work. A better solution is shorter targeted tasks with a clear time limit and a checkpoint for completion.

CARD 14 — Evidence-Safe Hedging (broad topic)

route_id: ROUTE.ARG.118
EL: Claim → Evidence → Likely mechanism → Limitation
VL islands: [VL.CI.uncertainty_hedging, VL.CI.evidence, VL.CI.neutrality]
Common failures: [EL.E5 ScopeLeak, VL.S1 SenseWrong, Z0.WEAK absolutes]
Repairs: [ER4 ShrinkScope, R1 ReplaceByEdge, R5 TuneRegister]
Example: Some evidence suggests excessive notifications can reduce attention because they interrupt focus. However, the impact varies by usage habits, so it is safer to avoid absolute claims.

CARD 15 — Criteria Judgement (fairness)

route_id: ROUTE.ARG.115
EL: Define criteria (2) → Evaluate option → Conclude rule
VL islands: [VL.CI.fairness, VL.CI.argument, VL.CI.logic]
Common failures: [EL.E3 LinkFailure, EL.E5 ScopeLeak, VL.S1 SenseWrong]
Repairs: [ER3 InsertLinks, ER4 ShrinkScope, R1 ReplaceByEdge]
Example: A fair rule is consistent and protects students from distraction. Therefore, limited phone use with clear guidelines is fairer than a total ban or no rules at all.

CARD 16 — Compare Two Options (trade-off)

route_id: ROUTE.ARG.121
EL: Define criteria → Compare A vs B → Choose → Reason
VL islands: [VL.CI.compare, VL.CI.neutrality]
Common failures: [EL.E5 ScopeLeak, VL.S1 SenseWrong, EL.E3 LinkFailure]
Repairs: [ER4 ShrinkScope, R1 ReplaceByEdge, ER3 InsertLinks]
Example: Option A is faster, but Option B is more reliable under pressure. I would choose B because accuracy matters more than speed in this situation.

CARD 17 — Polite Disagreement (letter tone)

route_id: ROUTE.LET.401
EL: Greeting → Concede → Request → Reason → Close
VL islands: [VL.CI.politeness, VL.CI.register_formal, VL.CI.clarity]
Common failures: [VL.S2 RegisterMismatch, EL.E3 LinkFailure, EL.E4 ReferenceLeak]
Repairs: [R5 TuneRegister, ER3 InsertLinks, ER1 NameActors]
Example: I understand your point; however, I would like to request a clearer timeline because it helps students plan effectively. Thank you for your consideration.

CARD 18 — Explain a Process (how-to)

route_id: ROUTE.EXP.207
EL: Goal → Steps (3) → Common mistake → Fix
VL islands: [VL.CI.process, VL.CI.clarity, VL.CI.mistake]
Common failures: [EL.E6 LoadCollapse, EL.E3 LinkFailure, VL.S3 FrameBreak]
Repairs: [ER5 SplitLoad, ER3 InsertLinks, R2 FixFrame]
Example: First, underline the key words; next, choose the method; finally, check your answer. A common mistake is skipping the final check, so use a short checklist.

CARD 19 — Explain to Younger (definition + example)

route_id: ROUTE.EXP.213
EL: Definition → Tiny example → Why it matters
VL islands: [VL.CI.clarity, VL.CI.evidence]
Common failures: [VL.S1 SenseWrong, EL.E3 LinkFailure, Z0.WEAK vague nouns]
Repairs: [R1 ReplaceByEdge, ER3 InsertLinks, ER5 SplitLoad]
Example: A fraction shows a part of a whole. For example, one slice out of four equal slices is 1/4, which helps you compare amounts accurately.

CARD 20 — Micro Repair: Tense Stabiliser

route_id: ROUTE.MIC.304
EL: Lock tense → align time markers → recheck verbs
VL islands: [VL.CI.process]
Common failures: [EL.E2 TimeDrift, VL.S3 FrameBreak, EL.E6 LoadCollapse]
Repairs: [ER2 LockTense, R2 FixFrame, ER5 SplitLoad]
Example: I walked in and my heart raced, but I took a breath and followed my plan. Then I finished on time.

If you want the deck to be “clickable” on WordPress

Use each card as a collapsible FAQ block (accordion). Title = route_id + 3-word label, body = the card content. This makes a perfect route directory hub.


Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors