THE LOGNORMAL METHOD

Train the path, not the performance signal.

A method for making mathematical structure visible, locating its first failure, and training the learner to choose a valid next move without outsourcing that judgment.

Working build means visible in the current iOS development build. In active development means partially implemented or being integrated. Planned means direction, not a release promise.

I / EVIDENCE

What the method treats as evidence.

01 · Working build

Inspect the chain

A result is evaluated with the sequence of moves that produced it.

02 · Working build

Locate the first break

Feedback begins where reasoning first becomes invalid, not at the final consequence.

03 · Working build

Classify the failure

Sign, setup, transformation, dependency, and arithmetic failures require different repairs.

04 · In active development

Preserve valid work

Correct structure remains visible while the broken step is repaired.

05 · Working build

Require a declared move

The learner commits to the operation or relationship before computation continues.

II / TRAINING

Three demands, one mathematical standard.

06 · Working build

Audit

Read completed work as critically as one would write it.

07 · Working build

Articulate

Construct the reasoning and expose enough structure to inspect it.

08 · Working build

Apply

Use familiar mathematics while timing, context, or system state changes.

09 · In active development

Vary the surface

Change representation and context without lowering the underlying standard.

10 · In active development

Revisit at the right edge

Practice follows the learner’s current structural frontier rather than a grade label.

WORKED EXAMPLE · AUDIT

A finished answer can still expose unfinished reasoning.

Suppose a chain-rule solution reaches 4(2x + 3), but an intermediate coefficient is wrong. A final-answer checker either accepts or rejects. LogNormal keeps the chain visible.

  1. Read. Follow each dependency in order.
  2. Isolate. Select the first coefficient that cannot follow from the previous line.
  3. Declare. Replace it and state the valid transformation.
  4. Reconstruct. The engine calculates downstream consequences only after the repair holds.
  5. Transfer. A later problem changes the surface pattern to test whether the rule survives.

III / SYSTEM

How the method becomes a long-term instrument.

11 · Working build

Semantic workspaces

Exercises are structured mathematical documents rather than flat answer fields.

12 · Working build

Deterministic validation

Intentional rules evaluate mathematical structure; the product is not an AI tutor improvising feedback.

13 · In active development

Calibration

A short preview establishes a reversible starting coordinate.

14 · Planned

Recalibration

New evidence can move the starting coordinate without redefining the learner.

15 · In active development

Developmental interfaces

Guidance, density, motion, and abstraction mature with the learner.

16 · In active development

Parent diagnosis

Practice becomes a pattern of strengths, breaks, consistency, and next focus.

17 · In active development

Permissioned visibility

Parents decide which tutors, guardians, or schools may see which learner information.

18 · Planned

Continuous course path

Foundations through advanced mathematics share one conceptual road.

19 · Planned

Prerequisite repair

A learner can strengthen what sits beneath the current topic without changing platforms.

20 · Exploratory

Advanced horizon

The same process-first method extends toward university and professional mathematics.

THE BOUNDARY

Assistance may remove mastered friction. It may not remove the judgment being learned.

This is the method’s operational rule. What has been reliably demonstrated may recede into engine support. The current conceptual move stays explicit. The frontier moves; responsibility does not disappear.

Read the product philosophy →

INSPECT THE PRODUCT

See the method operating in the current build.