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.

Publication Pack — WordPress Layout + VL Island Starter Kit (12 New Islands)

Below are two paste-ready components:

  1. A WordPress page layout (H2/H3 structure + reusable callout blocks + internal-link hooks)
  2. A VL Island Starter Kit (12 high-utility islands in full locked record format)

Start Here:


1) WordPress-Ready Page Layout (LLM-first Almost-Code)

Page Skeleton (copy/paste headings)

H1: Vocabulary Lattice + English Lattice at Work (Almost-Code)

Hook (1–2 sentences): Vocabulary is a lattice, not a list. English structure is also a lattice. This page shows both lattices operating in real writing using routes, sensors, and repairs.


H2: What This Page Does

  • Shows EL structure (roles/time/links/scope)
  • Shows VL meaning control (sense/collocation/intensity/register/polarity)
  • Provides worked examples + daily drills that phase-lock performance under exam load

H2: Canonical System Definition

H3: English Lattice (EL)

(Paste EL.S and EL.R blocks here)

H3: Vocabulary Lattice (VL)

(Paste VL.S and VL.R blocks here)

H3: Global Rules

  • EL first, then VL
  • max_collocations_per_paragraph = 2
  • avoid absolutes
  • strong claims require mechanism or proof

Callout Block (Definition Lock):
EL controls structure. VL controls meaning quality. Under load, you don’t “add vocab”; you repair sensors.


H2: Master Router (Choose a Route)

H3: Router Inputs

task_type | target_z | tone | desired_effect

H3: Route Quick Index

Narrative / Argument / Expository / Micro Repair / Letters
(Paste your route index here)

Callout Block (How to Use):
Step 1: pick route → Step 2: write EL skeleton → Step 3: add 1–2 VL islands → Step 4: run sensors → Step 5: apply repairs.


H2: VL Concept Islands Registry

H3: Island Record Format

(Paste the island record format block)

H3: Core Islands

  • sensory (and sight/sound/touch/smell)
  • confusion, calm_control
  • politeness, questioning
  • trust, hope, humour_light
  • register_formal, register_casual
  • uncertainty_hedging

Callout Block (Common Failure Mode):
Students jump to “big words” first → triggers S5 IntensityMismatch and S4 CollocationClash. Repair is R4 then R3, not bigger vocab.


H2: Word Banks (50 each)

  • Put each 50-word bank under its island as a collapsible section (optional)

Callout Block (Rule):
Word banks are a toolbox, not a target. Use them only after EL is stable.


H2: Worked Examples — True Lattice At Work (10)

For each example use this reusable block:

Example Block:
- route_id
- EL skeleton
- VL islands
- Draft v0
- Sensors fired
- Repairs applied
- Output v1

Callout Block (Grading Lens):
Marks come from stable EL flow + correct VL choices, not from fancy adjectives.


H2: Z0–Z3 Practice Plan (Daily Drills)

  • Z0: weak-word upgrades + collocation fixes + link insertion
  • Z1: 1 paragraph route
  • Z2: 2 paragraph stability
  • Z3: argument under constraints + hedging

Callout Block (Closed Loop):
Write → Sense (Sensors) → Repair → Re-write. That is the skill.


H2: Internal Links (Hooks)

Add these at the bottom as a mini directory:

  • /vocabulary-lattice-concept-islands/ (registry hub)
  • /english-lattice-links-and-connectors/ (E3 LinkFailure fixes)
  • /psle-composition-repair-protocol/ (your canonical protocol page)
  • /z0-z3-writing-routes/ (router directory)
  • /weak-words-and-upgrades/ (Z0.WEAK list)

2) VL Island Starter Kit — 12 New Full Locked Islands

Spec: VocabularyLattice.ConceptIsland.StarterKit
Version: v0.2.0
RecordType: VL_CONCEPT_ISLAND
Global:
- keep each island portable (can plug into any route)
- include ladder/frames/collocations/anti_collocations/tripwires/repairs

A) VL.CI.confidence (calm certainty with proof)

island_id: VL.CI.confidence
type: emotion/control
core_meaning:
- IS: steady belief in ability based on preparation/proof
- IS NOT: arrogance or pretending
intensity_ladder: unsure → confident → self-assured → composed confidence
frames:
- "I felt confident because ___."
- "My confidence grew after ___."
- "Instead of panicking, I ___ (plan)."
collocations:
- regained confidence
- steady voice
- handled it calmly
- trusted my preparation
- quiet confidence
anti_collocations:
- "confidently unsure" (conflict)
- "perfectly confident" (overclaim)
register_tags: neutral
polarity_rule: confidence must be anchored to proof (routine/result)
pairings: [VL.CI.calm_control, VL.CI.success, VL.CI.time_pressure]
tripwires: [S5 IntensityMismatch, S1 SenseWrong]
repairs: [R4 TuneIntensity, R1 ReplaceByEdge]
micro_demo: "After timed practice, I spoke with quiet confidence."

B) VL.CI.suspense (tension control)

island_id: VL.CI.suspense
type: narrative_effect
core_meaning:
- IS: controlled tension via delay + sensory cues
- IS NOT: shouting “scary” or random danger
ladder: curious → uneasy → tense → peak suspense → release
frames:
- "For a moment, everything was ___."
- "I hesitated before ___."
- "The sound grew ___ as ___."
collocations:
- held my breath
- a long pause
- my heart pounded
- the corridor fell silent
anti_collocations:
- "very suspense" (wrong form)
- “suddenly” spam without build
register_tags: neutral
polarity_rule: suspense is built; release must resolve clue
pairings: [VL.CI.sensory_sound, VL.CI.sensory_sight, VL.CI.surprise]
tripwires: [S5 IntensityMismatch, E6 LoadCollapse]
repairs: [R4 TuneIntensity, ER5 SplitLoad]
micro_demo: "I held my breath as the footsteps echoed closer."

C) VL.CI.embarrassment (social pressure without melodrama)

island_id: VL.CI.embarrassment
type: emotion
core_meaning:
- IS: discomfort from social attention/mistake
- IS NOT: shame identity collapse (“I’m useless”)
ladder: awkward → embarrassed → mortified (rare)
frames:
- "My face went hot when ___."
- "I wished the floor would open when ___."
collocations:
- face went hot
- avoided eye contact
- forced a small smile
anti_collocations:
- "devastated embarrassed" (intensity clash)
register_tags: neutral→casual
polarity_rule: embarrassment often pairs with humour_light or repair
pairings: [VL.CI.humour_light, VL.CI.politeness, VL.CI.ownership]
tripwires: [S5 IntensityMismatch]
repairs: [R4 TuneIntensity]
micro_demo: "My face went hot when I realised I waved at the wrong person."

D) VL.CI.curiosity (safe inquiry energy)

island_id: VL.CI.curiosity
type: emotion/function
core_meaning:
- IS: desire to understand; drives questioning
- IS NOT: suspicious accusation
ladder: curious → interested → fascinated
frames:
- "I wondered why ___."
- "I became curious about ___."
collocations:
- asked questions
- looked closer
- explored the idea
anti_collocations:
- "curiously accused" (polarity drift)
register_tags: neutral
polarity_rule: curiosity must lead to one action (ask/try/check)
pairings: [VL.CI.questioning, VL.CI.learning, VL.CI.confusion]
tripwires: [S6 PolarityDrift]
repairs: [R6 ReducePolarity]
micro_demo: "I wondered why the result changed, so I checked my steps."

E) VL.CI.description (controlled imagery without overload)

island_id: VL.CI.description
type: narrative_tool
core_meaning:
- IS: selective concrete details that support the scene
- IS NOT: long lists of adjectives
ladder: simple → vivid → precise (max 2 details)
frames:
- "The ___ was ___, and ___." (2 details only)
- "Under the light, ___ looked ___."
collocations:
- narrow corridor
- dusty shelf
- flickering light
anti_collocations:
- adjective stacking (E6 LoadCollapse trigger)
register_tags: neutral
polarity_rule: description must serve plot/emotion, not decorate
pairings: [VL.CI.sensory_sight, VL.CI.suspense, VL.CI.warmth]
tripwires: [E6 LoadCollapse, S4 CollocationClash]
repairs: [ER5 SplitLoad, R3 FixCollocation]
micro_demo: "The corridor was narrow, and the light flickered above me."

F) VL.CI.persuasion (soft influence)

island_id: VL.CI.persuasion
type: function
core_meaning:
- IS: guiding choice with reasons + respect
- IS NOT: forcing or insulting
ladder: suggest → recommend → persuade → convince (strong)
frames:
- "May I suggest ___ because ___?"
- "It might be better to ___, as ___."
collocations:
- gently persuaded
- recommended a solution
- offered reasons
anti_collocations:
- "persuaded violently" (polarity clash)
register_tags: neutral→formal
polarity_rule: persuasion needs one reason; keep tone polite
pairings: [VL.CI.politeness, VL.CI.argument, VL.CI.fairness]
tripwires: [S2 RegisterMismatch, S6 PolarityDrift]
repairs: [R5 TuneRegister, R6 ReducePolarity]
micro_demo: "May I suggest we revise earlier, because it reduces last-minute panic?"

G) VL.CI.logic (mechanism binding words)

island_id: VL.CI.logic
type: connector_logic
core_meaning:
- IS: correct use of therefore/however/because
- IS NOT: random connectors
variants: cause, contrast, addition, conclusion
frames:
- "Because ___, ___."
- "However, ___."
- "Therefore, ___."
collocations:
- leads to
- results in
- as a result
anti_collocations:
- "therefore" with no reason line
register_tags: neutral→formal
polarity_rule: link word must match relation type
pairings: [VL.CI.causality, VL.CI.argument, VL.CI.coherence]
tripwires: [E3 LinkFailure]
repairs: [ER3 InsertLinks]
micro_demo: "Because I rushed, I made careless mistakes. Therefore, I slowed down."

H) VL.CI.coherence (paragraph glue)

island_id: VL.CI.coherence
type: structure_support
core_meaning:
- IS: one paragraph one idea; consistent references and links
- IS NOT: drifting into new points
frames:
- "This shows that ___."
- "For this reason, ___."
collocations:
- stayed on topic
- linked back to the point
anti_collocations:
- new idea in final sentence
register_tags: neutral
polarity_rule: coherence is structural; vocab should not expand scope
pairings: [VL.CI.clarity, VL.CI.logic, VL.CI.neutrality]
tripwires: [E5 ScopeLeak, E4 ReferenceLeak]
repairs: [ER4 ShrinkScope, ER1 NameActors]
micro_demo: "This supports my point because it explains the main reason clearly."

I) VL.CI.intensity (ladder tuning controller)

island_id: VL.CI.intensity
type: meta_control
core_meaning:
- IS: choose word strength that matches stage/event scale
- IS NOT: “stronger word = better”
ladder_rule:
- scene scale small → use mild
- scene scale medium → use moderate
- rare big event → strong
frames:
- "I felt ___, not ___." (calibration)
collocations:
- slightly
- somewhat
- deeply (careful)
anti_collocations:
- “devastated” for small events
register_tags: neutral
polarity_rule: intensity must be consistent across paragraph
pairings: [all emotion islands]
tripwires: [S5 IntensityMismatch]
repairs: [R4 TuneIntensity]
micro_demo: "I was uneasy, not terrified."

J) VL.CI.time_pressure (performance under clock)

island_id: VL.CI.time_pressure
type: condition
core_meaning:
- IS: limited time changes mistakes and decisions
- IS NOT: excuse for chaos
ladder: relaxed → rushed → pressured → near time-out
frames:
- "Under the time limit, I ___."
- "To save time, I ___, but I still ___."
collocations:
- ran out of time
- managed my time
- rushed and missed a detail
anti_collocations:
- "time pressure made me perfect" (sense clash)
register_tags: neutral
polarity_rule: time pressure must link to a strategy (process)
pairings: [VL.CI.calm_control, VL.CI.process, VL.CI.confidence]
tripwires: [E6 LoadCollapse, S1 SenseWrong]
repairs: [ER5 SplitLoad, R1 ReplaceByEdge]
micro_demo: "Under the time limit, I started with the easiest questions first."

K) VL.CI.gratitude (specific thanks + impact)

island_id: VL.CI.gratitude
type: emotion/relationship
core_meaning:
- IS: specific appreciation tied to action and impact
- IS NOT: vague “very thankful” inflation
ladder: thankful → appreciative → deeply grateful (rare)
frames:
- "Thank you for ___; it helped me ___."
collocations:
- I appreciate your time
- your advice made a difference
anti_collocations:
- “very thankful” without specifics
register_tags: neutral→formal
polarity_rule: gratitude needs one concrete action and one impact
pairings: [VL.CI.warmth, VL.CI.trust, VL.CI.respect]
tripwires: [S4 CollocationClash, S5 IntensityMismatch]
repairs: [R3 FixCollocation, R4 TuneIntensity]
micro_demo: "Thank you for staying back; it helped me understand the method."

L) VL.CI.fairness (criteria-based judgement)

island_id: VL.CI.fairness
type: value/criteria
core_meaning:
- IS: decisions based on consistent criteria and impact
- IS NOT: “I feel it’s unfair” without reason
variants: fair process vs fair outcome
frames:
- "This is fair because ___."
- "A fair rule should ___ and ___." (2 criteria)
collocations:
- consistent rule
- equal opportunity
- reasonable outcome
anti_collocations:
- “unfair!” with no criteria
register_tags: neutral→formal
polarity_rule: fairness must state criteria (2 max)
pairings: [VL.CI.argument, VL.CI.neutrality, VL.CI.politeness]
tripwires: [S1 SenseWrong, E5 ScopeLeak]
repairs: [R1 ReplaceByEdge, ER4 ShrinkScope]
micro_demo: "A fair rule is consistent and protects students from distraction."

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors