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.

Summary OS (Standalone Canonical Page) — Almost-Code + V1.1 (Paste-Ready)

Three students study around open books and worksheets in a shared classroom.

Slug: /summary-os/
Role: The compression engine that converts dense text into short, accurate, word-limited output without losing meaning.
Used in: Secondary English, O-Levels, many “real life” tasks (reports, notes, briefings).


H1: Summary OS — What It Is and How It Works

Canonical Definition (LOCK)

Summary_OS := a compression-and-paraphrase system that produces
word-limited output while preserving:
required points + meaning integrity + logical relations,
under strict constraints (word limit + time).

Mastery (P3)

P3(Summary) = student can consistently:
- capture required points
- paraphrase (not copy)
- obey word limit
- avoid meaning leakage
across varied passages.

H2: Summary Is Not Shortening (It’s Controlled Compression)

LOCK

A summary is not “short writing”.
It is information selection + compression + paraphrase control.

H2: Summary OS Architecture (Pipeline)

Summary_OS {
Input:
- passage segment(s)
- question/task requirements (what counts as a point)
Process:
1) Point Extraction (no paraphrase yet)
2) Point Compression (merge/reduce)
3) Paraphrase (synonym families + structure change)
4) Integrity Check (meaning preserved)
5) Word Limit Trim (remove redundancy safely)
ControlLayer:
- anti-copy rule
- evidence discipline
- time boxing
Output:
- concise accurate summary within word limit
}

H2: Phases (P0–P3) for Summary

P0: cannot identify points; copies randomly
P1: identifies some points but misses many; heavy copying
P2: can summarise but often exceeds word limit or leaks meaning
P3: consistent point capture + clean paraphrase + within word limit

H2: Top 6 Failure Modes (Summary)

FM1: Missed points (selection failure)
FM2: Meaning leakage (distortion)
FM3: Copying chunks from passage (paraphrase failure)
FM4: Word limit breach (control failure)
FM5: Repetition / redundancy (compression failure)
FM6: Wrong linking logic (cause/effect, contrast lost)

H2: Sensors Pack (Summary Instrument Panel)

Core Sensors (most important)

SUM_Sensors {
PointsCaptured / PointsRequired
MeaningLeakEvents (count)
CopyRate (how much is lifted directly)
WordLimitCompliance (Y/N)
RepetitionRate
LogicPreservationScore (relations kept)
}

Fast proxies (for quick marking)

Proxies {
- count required points present (tick checklist)
- underline copied phrases (copy rate proxy)
- circle distortions/overclaims (leak proxy)
- count redundant phrases (repetition proxy)
}

H2: The Summary Control Layer (Constraints Engine)

Time Boxing (LOCK)

TIME_BOX_SUMMARY {
Extract points: 30–40%
Write summary: 40–50%
Trim/check: 10–20%
}

Anti-Copy Rule (LOCK)

No sentence should be copied verbatim.
Change at least one of:
- word choice
- sentence structure
- point order
while preserving meaning.

Integrity Rule (LOCK)

Do not add new ideas.
Do not exaggerate.
Do not remove required points.

H2: The Core Algorithm (Step-by-Step)

Step 1 — Point Extraction (no paraphrase)

POINT_LIST := list required points as short bullet fragments.
No full sentences.
No “nice writing”.
Just content.

Step 2 — Compression (merge points)

Merge related points:
two bullets → one clause
Remove examples/details unless required.
Keep relations: because/however/therefore.

Step 3 — Paraphrase (controlled)

Use:
- synonym families
- collocation swaps
- structure swaps (active↔passive, clause merge)
Avoid:
- “synonym substitution” that changes meaning

Step 4 — Integrity Check

Check:
- all required points present?
- any distortion?
- any over-claims?

Step 5 — Word Limit Trim

Trim redundancy first.
Replace long phrases with compact equivalents.
Remove repeated framing.

H2: Repair Loops (Smallest Reliable Fixes)

Loop 1 — Point Capture Drill (Selection)

LOOP_POINTS {
read passage
list 6–10 points as fragments
compare to answer key checklist
fix missed point pattern
}

Loop 2 — Compression Drill (Merge)

LOOP_COMPRESSION {
take 8 points
compress to 5 sentences max
preserve relations (cause/contrast)
}

Loop 3 — Paraphrase Families (Vocabulary crossover)

LOOP_PARAPHRASE {
for each key phrase:
create 2 alternatives with same meaning
test:
can you paraphrase without meaning drift?
}

Loop 4 — Word Limit Trimming (Control)

LOOP_TRIM {
write summary
cut 10–15% words without losing points
remove redundancy
tighten connectors
}

H2: The “Meaning Leakage” Prevention System

What leakage looks like

  • adding a new claim not in text
  • exaggerating intensity (“always”, “never”)
  • wrong cause/effect
  • wrong scope (“all students” vs “some”)

Leak Tagging (for post-mortem)

LeakTag := AddedIdea | Exaggeration | WrongRelation | WrongScope | OmittedPoint

Repair rule: fix the dominant leak tag first.


H2: Integration (Summary OS ↔ Vocabulary OS)

LOCK

Summary requires paraphrase families.
Paraphrase families require P3 vocabulary + chunk control.

Practical link:

  • If student copies → vocabulary depth missing OR paraphrase practice missing
  • Fix by: synonym families + structure swap drills

H2: Negative Inversion — Why Students Stay Bad at Summary

Failure Mode Trace (required)

Student writes “nice sentences”
→ forgets to extract points
→ exceeds word limit
→ copies phrases to save time
→ misses required points
→ summary score stays low

Correct fix (LOCK)

Summary improves by:
point extraction first → controlled compression → paraphrase → trim.
Not by writing “better English”.

Canonical Spec Block (Summary)

SUMMARY_OS_SPEC v1.0 {
Definition: compression + paraphrase + integrity under word limit
Steps: extract points → compress → paraphrase → integrity check → trim
Sensors: points captured, meaning leakage, copy rate, word limit, repetition
Repairs: point drill, compression drill, paraphrase families, trim drill
P3 Gate: required points present + no leakage + within word limit
}

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors