A square-centric scan can classify more than:
- attacked;
- defended;
- contested.
It can also tell us when:
- neither side affects a square;
- only one side affects it;
- a line relationship exists but is blocked;
- a move changes a whole map of relationships.
This section turns individual attack relations into a board-wide spatial model.
Control-state vocabulary
For pedagogical overlays, a square can be classified according to which side affects it under the stated attack/control model.
Uncontrolled
Neither side currently exerts the relevant direct attack/control influence on the square.
Symbolically:
- White: 0
- Black: 0
Exclusively White-controlled
White affects the square.
Black does not.
Symbolically:
- White: 1+
- Black: 0
Exclusively Black-controlled
Black affects the square.
White does not.
Contested
Both sides affect the square.
- White: 1+
- Black: 1+
| White influence | Black influence | Descriptive state |
|---|---|---|
| 0 | 0 | Uncontrolled |
| 1+ | 0 | Exclusively White-controlled |
| 0 | 1+ | Exclusively Black-controlled |
| 1+ | 1+ | Contested |
Control-state labels describe spatial influence, not strategic ownership.
"Controlled" is not "owned"
Avoid phrases such as:
"White owns e5."
unless the later strategic context defines what is meant.
A square controlled only by White can still be:
- irrelevant;
- impossible to occupy usefully;
- tactically dangerous;
- strategically weak;
- temporarily affected.
At this stage, keep the classification descriptive.
An uncontrolled square can still matter
A square with:
- no current attackers/controllers
can still be:
- a future route square;
- a promotion square;
- an intersection;
- a tactical target after one move;
- important because a line may open.
So uncontrolled means only:
no relevant current direct influence under the map being used.
It does not mean:
- unimportant;
- permanently free.
Exclusive control can change instantly
Suppose e4 is controlled only by White.
Black moves a knight.
Now that knight attacks e4.
The square changes:
- before → exclusively White-controlled;
- after → contested.
Nothing had to move onto e4 itself.
A move can change a square's relationships without changing the square itself.
Direct and latent spatial relationships
Two chessmen can be:
- aligned;
- but not directly connected because a blocker stands between them.
This is a latent spatial relationship.
Direct relationship
A compatible piece has clear line of sight to the target.
Example:
- White rook a1;
- Black queen a7;
- a2-a6 empty.
Direct line relationship exists.
Latent relationship
Now insert:
- White bishop a4.
The rook and queen remain:
- aligned.
But:
- bishop blocks direct line of sight.
The relationship can become direct if the blocker leaves.
Latent geometry can become active when occupancy changes.
One blocker vs several blockers
A line can contain:
- one blocker;
- several blockers.
Example:
rook a1;
- pawn a3;
- bishop a5;
- queen a8.
The queen is aligned with the rook.
But opening only a3 does not necessarily create direct line of sight because:
- a5 remains another blocker.
"One blocker moved" does not imply "the line is now open."
Scan the entire segment.
Avoid premature tactical labels
A blocker leaving can create:
- attack;
- check;
- tactical opportunity.
Start by describing the spatial transformation itself:
- line opened;
- line closed;
- direct relationship appeared;
- direct relationship disappeared.
Do not automatically label:
- discovered attack;
- x-ray;
- pin;
- skewer.
Those terms carry tactical meaning owned elsewhere.
Latent defense
Latent relationships can also concern friendly support.
Example:
- White rook a1;
- White bishop a4;
- White queen a7.
Rook and queen:
- aligned.
But bishop blocks direct support.
If bishop leaves:
- rook may directly defend queen along the file.
Again:
- geometry first;
- tactical evaluation later.
Attack maps
An attack map is a conceptual representation of squares attacked by:
- one chessman;
- one side;
- or selected chessmen.
It is a board-vision tool.
It is not a separate rule of chess.
Piece-centric attack map
Origin: one piece.
Output: all squares attacked from its current position.
Examples:
- knight footprint overlay;
- rook ray overlay;
- pawn attack arrows.
This answers:
What does this piece attack?
Square-centric attacker map
Origin: one square.
Output: all pieces that attack/defend/control it under the chosen model.
This answers:
What affects this square?
Side-wide attack map
Take the union of attack sets from every chessman of one side.
The result can show:
- areas with many overlapping attacks;
- squares attacked once;
- squares not attacked by that side.
Union does not preserve counts by itself
A simple union map answers:
Is this square attacked at least once?
It does not tell us:
How many attackers?
Example:
Square d5:
- attacked by three White pieces.
Binary union map:
- White attack = yes.
Count map:
- White attackers = 3.
These are different visualizations.
Presence map and count map answer different questions.
Attack-count map
A count map stores:
- 0;
- 1;
- 2;
- 3+ attackers/controllers
for each square.
This can be useful for:
- board-vision exercises;
- comparing overlap;
- identifying heavily contested squares.
But counts remain descriptive.
High attack count ≠ safe occupation ≠ strategic superiority.
Do not turn the heatmap into an automatic evaluation function.
Defense map
A defense/protection overlay focuses on:
- friendly-occupied targets;
- friendly support relationships.
This is useful because a legal-move overlay alone can hide protection.
Example:
- White knight defends a White pawn.
The knight cannot legally move onto the pawn's occupied square.
But the protection relationship is still important.
Control map
A control map can combine:
- attacks on empty/opposing squares;
- protection relationships;
- side-wide spatial influence.
Because chess literature uses control variably, every production feature should define the exact layer it displays.
Recommended UI labels:
Attacks
Squares attacked under the selected attack model.
Defends
Friendly support/protection relations.
Control
Broad pedagogical influence overlay; explain its construction.
Legal moves
Actual legal destinations for selected side/piece.
Never imply those four are interchangeable.
Attack maps and king safety
Attack maps are essential for:
- king destinations;
- check;
- castling transit/destination safety.
But a simplistic legal-move map cannot replace the attack map because of the FIDE pinned-piece nuance.
The legal-move layer adds an important constraint:
- a pinned piece may still attack squares for rule purposes even if it cannot legally move there.
King safety consumes attack information, not merely opponent legal-move destinations.
Attack maps are conceptual tools
A player does not need to imagine:
- 64 squares glowing with overlays
during every move.
The map is a teaching representation.
Real board vision may operate through:
- focused square scans;
- piece footprints;
- line recognition;
- habitual pattern recognition.
Build a side-wide map
Position with modest material.
Step 1
Map White pawn attacks.
Step 2
Add White knight attacks.
Step 3
Add White slider rays.
Step 4
Add king neighbourhood.
Step 5
Mark squares with:
- 0 White attacks;
- 1;
- 2+.
Step 6
Repeat for Black.
Step 7
Classify:
- White-only;
- Black-only;
- contested;
- uncontrolled.
Learning goal: construct a board-wide attack/control picture from piece-level geometry.
What changed after a move?
A basic piece-safety question is:
What changed?
The same question can be made more precise with a geometric checklist.
After every move, compare the before/after spatial state.
1. Which footprint moved?
The moved chessman now attacks/controls a new set of squares.
Old origin footprint:
- partly disappears.
New destination footprint:
- appears.
Example: knight g1 → f3.
The knight attack set changes completely.
2. What did the vacated square reveal?
A moving chessman may have been a blocker.
When it leaves:
- rook line may open;
- bishop diagonal may open;
- queen line may extend.
3. What did the destination square block?
A moved chessman can also close a line.
Example: knight moves onto a bishop diagonal.
Before: bishop had clear line.
After: knight becomes first blocker.
4. Which squares became newly attacked?
The moved piece may attack:
- completely new targets.
An opened slider behind it may also gain:
- new attacked squares.
So spatial change can come from:
- moved piece;
- pieces whose lines changed.
5. Which squares stopped being attacked?
The origin footprint may disappear.
A line may close.
A defender may leave.
A pawn may advance and therefore change its attack diagonals.
6. What became newly defended or undefended?
A move can:
- add a friendly defender;
- remove a friendly defender;
- create indirect/latent alignment;
- break direct support.
This is purely relational before asking whether the consequence is tactically important.
7. Did a control state change?
For any important target square:
before:
- uncontrolled;
- exclusive;
- contested.
after:
- another state.
Example:
e5:
- White-only before;
- contested after Black knight move.
8. Did a blocker move or appear?
For every changed slider line:
ask:
- nearest blocker before?
- nearest blocker after?
This quickly explains why:
- long-range relationships changed.
Geometry-focused after-move scan
- [ ] Moved piece footprint changed
- [ ] Origin square vacated
- [ ] Destination square occupied
- [ ] Line opened?
- [ ] Line closed?
- [ ] New attacker?
- [ ] Attack removed?
- [ ] New defender?
- [ ] Defender removed?
- [ ] Control-state change?
- [ ] Nearest blocker changed?
One move changes more than one piece's map.
This is the bridge from static geometry to dynamic position awareness.
Before/after example
Construct:
Before:
- White rook d1;
- White bishop d3;
- Black queen d7.
Bishop blocks rook's file.
White bishop moves:
- d3 → e4.
After:
- rook's d-file line extends toward d7;
- bishop has a new diagonal footprint;
- d3 becomes empty;
- e4 becomes occupied;
- any lines through e4 may be newly blocked;
- queen d7 may become directly related to rook depending on remaining blockers.
Ask:
- What line opened?
- What line/relationships did bishop gain?
- What square stopped being occupied?
- What square became occupied?
- What attacked/defended states changed?
Spatial delta, not full calculation
This after-move scan is not yet calculation.
It answers:
What geometric relations changed after a known move?
Calculation asks:
If I consider future move A, what replies and future positions follow?
That becomes calculation once future moves and replies are introduced.
Attack-map mistakes
"Legal moves are the attack map."
Wrong.
Pinned-piece rules alone disprove this equivalence.
"Every aligned slider attacks through every blocker."
Wrong.
Direct slider relation stops at the first blocker.
"A defended piece is safe."
Wrong.
Defense is one spatial fact.
Safety requires tactical evaluation.
"2 attackers vs 1 defender means I own the square."
Wrong.
Count is not a tactical or strategic verdict.
"Control means I can legally move there."
Wrong.
Control, attack, defense, and legal movement are distinct layers.
"If my piece moved, only its own attack map changed."
Wrong.
Its departure/arrival can:
- open lines;
- close lines;
- remove defense;
- add defense;
- change several other pieces' footprints.
Putting square-control states together
A whole-board spatial model can classify:
By side influence
- uncontrolled;
- White-only;
- Black-only;
- contested.
By relation
- direct;
- blocked/latent.
By representation
- piece-centric attack map;
- square-centric attacker map;
- side-wide union map;
- count map;
- defense map;
- broader control overlay;
- legal-move map.
These representations answer different questions.
Use the map that matches the question.
After a move
Update:
- moved piece footprint;
- vacated square;
- occupied destination;
- opened/closed rays;
- attackers;
- defenders;
- contested states;
- nearest blockers.
This creates a disciplined spatial update without yet becoming tactical calculation.
Square-control mastery check
- [ ] I distinguish attack, control, defense, and legal movement.
- [ ] I build attack maps piece-centrically.
- [ ] I find attackers square-centrically.
- [ ] I preserve pinned-piece attack nuance.
- [ ] I identify friendly defenders.
- [ ] I classify contested squares.
- [ ] I identify uncontrolled and exclusive-control states.
- [ ] I distinguish direct from latent line relationships.
- [ ] I understand side-wide union vs count maps.
- [ ] I know attack maps are tools, not automatic evaluations.
- [ ] I can explain what changed spatially after a move.
The next area asks a different geometric question:
How much access does a piece actually have once blockers and occupancy restrict its raw footprint?
That is mobility.