Chess-thinking vocabulary often collapses several different processes into the word "calculation." Keeping the distinctions clear makes both learning and error diagnosis easier.
Calculation vs Related Processes
| Process | Main question | Typical failure |
|---|---|---|
| Board vision | What is on the board now? | misread square or line |
| Pattern recognition | What familiar geometry does this resemble? | false pattern match |
| Candidate generation | What moves deserve analysis? | best move omitted |
| Calculation | What follows after moves and replies? | branch or opponent-resource error |
| Visualization | What does the future board state contain? | ghost piece / wrong turn |
| Endpoint selection | When is the line stable enough to judge? | horizon error |
| Evaluation | How good is the endpoint? | material-only judgment |
| Planning | What long-term change should I seek? | plan disconnected from concrete tactics |
| Practical decision | What should I choose under real constraints? | clock/risk mismatch |
| Post-game analysis | What happened and why? | hindsight/tool misuse |
These processes interact, but treating them as synonyms hides useful information.
Candidate Move vs Legal Move
A legal move is permitted by the rules.
A candidate move is a serious legal move selected for calculation or comparison.
Candidate moves are therefore a subset of legal moves.
Forced vs Forcing
Forced move: alternatives are absent or unacceptable in context.
Forcing move: restricts the opponent's viable replies.
A check can be forcing without being strong. A quiet threat can be highly forcing.
Check vs Forcing Move
Check is a legal concept: the king is attacked.
Forcingness is a search concept: how much reply freedom remains.
Do not treat every check as the strongest forcing candidate.
Checks, Captures and Threats (CCT)
CCT is best understood as a search-order heuristic.
It helps surface:
- checks;
- captures;
- direct threats.
But a full candidate set may also include:
- defensive necessity;
- counterattack;
- quiet tactical move;
- prophylaxis;
- pawn break;
- simplification;
- improvement.
Use CCT to avoid missing forcing resources, not to exclude every quiet move.
Breadth vs Depth
Breadth: number of serious alternatives considered.
Depth: how far one branch is followed.
Typical failure patterns:
- depth without breadth → first-move fixation;
- breadth without depth → unresolved noise.
Root vs Endpoint
Root: the real current position.
Endpoint: a chosen position where the branch's critical consequence has stabilized enough to evaluate.
A corrupted root poisons every branch. An unstable endpoint creates horizon errors.
Refuted vs Unresolved
Refuted: concrete continuation makes the candidate unacceptable.
Unresolved: branch needs more calculation or evaluation.
Do not use "refuted" to mean "I do not like this move."
Main Line vs Best Defense
A main line should normally reflect the most critical continuation, not simply the most natural moves.
The opponent's best defense may be active, ugly or unintuitive.
Elimination vs Pruning
Human-facing elimination means stopping work on a candidate because a concrete reason makes it noncompetitive.
Computer-search pruning describes algorithmic methods for reducing a search tree.
The analogy can be useful, but human elimination should not be presented as a specific engine algorithm.
Visualization vs Calculation
Visualization maintains and updates the imagined board.
Calculation chooses moves and follows branches through that board state.
Visualization is a component of calculation, not the whole process.
Endpoint Evaluation vs Positional Theory
A compact endpoint scan can include:
- material;
- king safety;
- activity/initiative;
- structure;
- compensation.
Deep positional evaluation contains many more tradeoffs and patterns. During calculation, the compact version is a working decision tool.
Quiet Calculation vs Strategy
Strategy chooses long-term goals such as improving the worst piece or preparing a pawn break.
Quiet calculation tests the concrete move implementing that goal and the opponent's response.
Final Blunder Check vs Full Calculation
The final blunder check is a last safety scan after a move has been selected.
It does not replace:
- candidate generation;
- best-defense calculation;
- endpoint evaluation;
- comparison.
A move can pass the blunder check and still be inferior.
Kotov's Candidate/Tree Framework
The candidate/tree model associated with Alexander Kotov is useful for organizing analysis: generate candidates, calculate branches and avoid repeatedly wandering through resolved lines.
Treat it as a pedagogical framework rather than a literal universal model of expert cognition.
Which Method Should You Use?
No single named framework determines the correct thinking process for every position.
Use:
- forcing scans when tactical contact is high;
- broad candidate generation when several moves compete;
- tree discipline when branches multiply;
- endpoint discipline when you stop too early;
- prophylactic questions in quiet positions;
- final verification before committing.
The position decides which component deserves emphasis.
FAQ
Is CCT a complete chess thinking system?
No. It is a useful forcing-move search heuristic, but quiet, defensive and transformational candidates still matter.
Is Kotov's tree the only correct calculation method?
No. It is a useful organizational model, not a universal law of thought.
Is visualization more important than calculation depth?
Accurate visualization is necessary for any depth. A long line built on a false board has little value.
Methods are attention-management tools. They organize the search; they do not replace chess judgment.
Practical Term Pairs to Keep Separate
| Pair | Difference |
|---|---|
| candidate / legal move | serious option vs every rule-legal option |
| forcing / forced | restricts replies vs alternatives effectively absent |
| branch / variation | branch emphasizes tree structure; variation can mean any analyzed line |
| endpoint / final position | chosen evaluation stop vs literal end of game |
| refuted / inferior | concretely fails vs merely worse than another move |
| visualization / memory | maintaining changed board state vs recalling learned positions |
| calculation / analysis | over-the-board concrete search vs broader post-game/tool-assisted investigation |
These distinctions are not pedantry. They prevent a training instruction from asking for one skill while scoring another.