14) Z0 Mathematics: Word Problems as Load Compression (Method Selection Under Text)

What this page is

Word problems are not “hard because of English.”
They are hard because they demand compression:

  • compress text → structure,
  • structure → equations,
  • equations → solution steps,
  • solution → interpretation in context.

Most students fail word problems because their Z0 system collapses at one of four points:

  1. translation (text → math)
  2. method selection (what topic is this really?)
  3. algebra transport (symbol manipulation under load)
  4. interpretation + checking (does the answer make sense?)

This page defines Word Problems as a Z0 lattice, gives inversion tests, and a repair protocol.


Definition Lock

Word Problem Reliability (Z0) is the ability to convert a written scenario into a correct mathematical model independently, execute it cleanly, and verify the result under mild load.

Word problems are a model-building pocket, not a “practice more” pocket.


First Principles (why word problems collapse)

1) Word problems are multi-pocket stacked load

A single word problem can require:

  • comprehension extraction
  • representation (diagram/table/equation)
  • algebra reliability
  • method execution
  • checking and interpretation

If any upstream pocket is P1, the whole problem collapses.

2) The “first step” is the real gate

Students freeze because they cannot generate the first modelling step:

  • define variables
  • decide relationships
  • choose a representation

3) Familiarity is not transfer

Students can solve “same type” practice questions but fail new contexts because they learned templates, not modelling.

4) Word problems reveal method-selection weakness

This is why many students say:

“I know the topic, but I don’t know what to use.”


The Word Problem Z0 Pocket Map (the real lattice)

Pocket A: Extraction (facts vs fluff)

  • identify quantities
  • identify relationships
  • identify the target variable/output

Pocket B: Representation choice

Pick one:

  • equation system
  • ratio table
  • bar model / diagram
  • graph relation
  • algebraic expression

Pocket C: Variable definition discipline

  • define variables clearly
  • keep units consistent
  • avoid shifting variable meanings mid-problem

Pocket D: Relationship encoding

Turn text relationships into:

  • equalities/inequalities
  • proportional relations
  • rate equations
  • simultaneous equations

Pocket E: Method selection

Recognise whether it is:

  • ratio/proportion
  • linear equations
  • quadratic relationships
  • geometry relation
  • speed–distance–time
  • percentage/compound change
  • functions / graphs

Pocket F: Algebra transport

Even perfect modelling fails if algebra is weak.

Pocket G: Interpretation + check

  • sanity check magnitude
  • check units
  • verify constraints
  • answer the question asked (not the intermediate)

Students fail different pockets; repairs must be pocket-specific.


Word Problem Inversion Tests

Inversion Test 1: Template Collapse Test

If performance is high only when the “type” looks familiar, reliability is not real.

Procedure:

  • Set A: familiar skin
  • Set B: same concept but new story context
    Fail: Set B collapses.

Inversion Test 2: First-Step Test (most important)

If student cannot write variable definitions and the first relationship line, they are P1 in modelling.

Procedure:
Give problem. Ask student to write only:

  1. variable definitions
  2. first equation / relationship
    Stop there.

Fail: freezes, guesses, or waits for hint.


Inversion Test 3: Representation Switch Test

If the student can solve only with one representation, transfer is brittle.

Procedure:
Force alternative representation:

  • from equations → table
  • from text → diagram
  • from ratio → algebra
    Fail: cannot convert.

Inversion Test 4: Interpretation Test

If the student gets a numeric answer but cannot tell if it makes sense, the pocket is incomplete.

Procedure:
Ask:

  • “Is this reasonable?”
  • “What does the answer mean?”
  • “What if the quantity doubled?”
    Fail: cannot interpret.

Below-threshold signatures

  • “I don’t know what the question wants.”
  • “I don’t know which topic to use.”
  • “I can do it when you show the first step.”
  • “My equation is wrong but I don’t know why.”
  • “I got an answer but it doesn’t match the options.”

These signals point to specific pockets above.


Sensors (weekly word-problem diagnostics)

Sensor 1: Variable-definition quality

Can student define variables correctly in 30–60 seconds?

Sensor 2: First-relationship accuracy

Can student write a correct first equation (or table relationship) without prompts?

Sensor 3: Method-selection success rate

Before solving, student names:

  • what topic/structure this is
  • why

Track accuracy.

Sensor 4: Check routine completion

Did student do:

  • units check
  • magnitude sanity check
  • “answer the question asked” check

Sensor 5: 48-hour re-model test

Re-test modelling (not full solving) after 48 hours.
If it collapses, modelling pocket is still recognition-based.


Common false fixes

“Do more word problem worksheets”

If the student is not modelling correctly, repetition trains wrong modelling.

“Memorise types”

Types fail when stories change.

“Skip word problems and focus on topical”

This hides method-selection weakness until the exam.


Repair Protocol (P0/P1 → P2 modelling reliability)

Step 1: Modelling-only drills (no solving allowed)

For 10 problems:

  • define variables
  • write first relationship
    Stop. This trains the true bottleneck.

Step 2: Representation discipline

Teach one default representation per problem family, then practise converting.

Step 3: Method-selection ladder

Start with:

  • obvious structure
    Then:
  • mild disguise
    Then:
  • mixed-topic sets

Step 4: Algebra coupling repair

If modelling is right but solutions fail, run algebra micro-repairs in parallel.

Step 5: Interpretation scripts

Teach 3 checks:

  • units
  • magnitude
  • constraint check

Step 6: Mild load conditioning

Timed modelling drills (not full solutions) first, then timed full questions.


What P2 word-problem reliability looks like

  • student starts confidently (variables + first equation)
  • method selection is stable
  • execution is organised
  • checks are habitual

What P3 looks like

  • adapts to new contexts quickly
  • uses smart representation choices
  • catches modelling errors early
  • performs under time pressure with calm

FAQ

Is word problem failure an English issue?
Not usually. It’s a modelling and method-selection reliability issue.

Why does my child freeze at the start?
First-step modelling pocket is still P1.

What is the fastest fix?
Modelling-only drills: variables + first relationship, repeated weekly.



15) Z0 Additional Mathematics: Integration Reliability (Drift-Heavy Pocket + Anti-Template Training)

Suggested slug: /z0-amath-integration-reliability/

What this page is

Integration is where many students experience:

  • fast forgetting,
  • confusion between methods,
  • “I thought I knew it” collapse.

Integration is a drift-heavy pocket because:

  • rules feel similar,
  • steps are easy to copy,
  • students rely on recognition,
  • mixed questions expose weak method selection.

This page defines Integration reliability as a Z0 lattice and gives inversion tests + repair routing.


Definition Lock

Integration Reliability (Z0) is the ability to:

  1. recognise what form the integrand is in,
  2. choose the correct method,
  3. execute integration cleanly,
  4. handle algebraic rewriting,
  5. remain stable under variation and load.

If the student can integrate only when the question matches a memorised form, integration is still P1.


First Principles (why integration collapses)

1) Integration is reverse-engineering structure

Students must recognise:

  • standard forms
  • substitutions
  • identities (where relevant)
  • algebraic rewrites

2) Many integration failures are algebra failures

Simplification and rewriting are often the hidden bottleneck.

3) Integration is method-selection, not memory

Memorising a list of forms does not produce reliable selection in mixed questions.

4) Drift is normal if retrieval isn’t maintained

Integration knowledge decays quickly when learned as recognition.


Integration Z0 Pocket Map

Pocket A: Standard forms reliability

  • (\int x^n dx)
  • (\int \frac{1}{x} dx)
  • exponentials/logs (if in scope)
  • trig basic forms (if in scope)

Pocket B: Algebraic rewriting

  • expand/simplify before integrating
  • factor and cancel where valid
  • rewrite powers/fractions correctly

Pocket C: Substitution recognition (if in scope)

  • identify inner function presence
  • choose substitution cleanly
  • transform limits/variables correctly (if taught)

Pocket D: Trig identity integration (if in scope)

  • use identities to rewrite integrand
  • avoid template-only behaviour

Pocket E: Constant of integration discipline

  • add (+C) consistently
  • interpret when required

Pocket F: Mixed-question method selection

  • decide quickly which pocket is needed
  • avoid “try and see” randomness

Pocket G: Checking via differentiation

  • differentiate result to verify

Integration Inversion Tests

Inversion Test 1: Mixed-Set Selection Test (core)

If the student cannot choose methods correctly in a mixed set, integration is not P2.

Procedure:

  • 8 integrals mixed across pockets A–D
    Student must label method before solving.

Fail: wrong method choice or hesitation.


Inversion Test 2: Rewrite-First Test

If the student cannot rewrite the integrand into a standard form, reliability is P1.

Procedure:
Give integrand requiring rewrite. Ask student to rewrite only (no integration).

Fail: cannot rewrite or rewrites incorrectly.


Inversion Test 3: Blank-Page Start Test

If the student needs to see examples to start, it’s recognition.

Procedure:
No notes. Ask for method label + first step.

Fail: “I forgot” / waits / tries random steps.


Inversion Test 4: Check-by-differentiation Test

If the student never checks by differentiating, errors persist and drift increases.

Procedure:
Require check for 2 items.

Fail: cannot differentiate result back correctly or refuses to check.


Inversion Test 5: Mild Load Stability Test

If accuracy collapses under mild timing, method selection isn’t stable.


Below-threshold signatures

  • “I don’t know which formula to use.”
  • “All integrals look the same.”
  • “I forgot the steps.”
  • “I get answers but not sure they’re right.”
  • “I always miss +C.”

These are P1 signals (recognition and weak selection).


Sensors (weekly integration diagnostics)

Sensor 1: Method-label accuracy

Before solving, student labels method. Track hit rate.

Sensor 2: Rewrite success rate

Give 3 integrands; student rewrites into standard forms.

Sensor 3: +C discipline rate

Count missing constants.

Sensor 4: Check-by-differentiation completion rate

Student differentiates final answers to verify.

Sensor 5: 48-hour retention micro-set

Integration decays fast. Retest after 48 hours closed-book.


Common false fixes

“Memorise more formulas”

Doesn’t fix mixed selection failure.

“Do topical worksheets only”

Hides selection weakness; mixed sets reveal reality.

“Skip checking”

Guarantees persistent errors and drift.


Repair Protocol (P0/P1 → P2 integration)

Step 1: Method selection drills (no solving first)

For 20 questions:

  • label method
  • rewrite integrand
    Stop. This builds the true bottleneck.

Step 2: Rewrite training

Teach standard rewrite moves:

  • expand vs factor
  • power conversion
  • identity conversion (if relevant)

Step 3: Short closed-book retrieval

Small sets repeated across days to fight drift.

Step 4: Mixed ladder

Start with 2-method mixes → increase variety.

Step 5: Checking habit

Differentiate answers to verify. This tightens reliability quickly.

Step 6: Mild load conditioning

Timed micro-sets only after selection reliability stabilises.


What P2 integration looks like

  • chooses method correctly
  • rewrites competently
  • executes cleanly
  • adds +C consistently
  • checks results when unsure

What P3 looks like

  • handles mixed sets fast
  • rewrites flexibly
  • uses checking proactively
  • stays stable under exam timing

FAQ

Why does integration feel harder than differentiation?
Because it requires stronger method selection and rewriting; recognition fails fast.

My child forgets integration quickly — why?
Because it was learned as template recognition. Retrieval + mixed practice is needed.

What’s the fastest improvement lever?
Method-label drills + rewrite-first drills + check-by-differentiation.


If you want to continue the Z0 stack logically, the next pages that stitch everything into “Sec 3 survival” are:

  • Z0 Trigonometry Reliability (identity drift + template overfit)
  • Z0 Simultaneous Equations Reliability (setup + elimination stability)
  • Z1 Bridge: Why Sec 3 is the Gate Year (Z0 collapse becomes visible)

Just say which one and I’ll write it full-length V1.1.