Symbol Collision Checklist¶
Checklist — instantiates Symbol-System Coherence in Visual Art
Reviews whether two symbols look too similar, signal incompatible meanings, or compete in the same composition.
Two symbols that are each fine on their own can wreck a code by colliding — looking so alike that viewers confuse them, or carrying meanings that clash when they meet. Symbol Collision Checklist is a fixed set of pairwise checks run over the symbol set at one point in time: for every pair that could plausibly meet, does it fail any collision test — visual similarity, semantic incompatibility, or competition within a single composition? Its defining move is the pairwise scan against a fixed list of clash conditions: it does not track a symbol across pieces or over time; it takes the current inventory and asks, pair by pair, "can these two be told apart, and can they coexist?" It is the sharp instrument for the archetype's collision half of the drift-and-collision audit.
Example¶
A tabletop board game has a growing set of resource icons printed on cards and the central board: a wheat sheaf (food), a stack of coins (wealth), a hammer (production), a shield (defense), a torch (exploration). Late in development the designers add two more — a bundled-arrows icon (military) and a bundled-sticks icon (fuel). Before the print run, a playtester runs the Symbol Collision Checklist over every icon pair. The bundled-arrows and bundled-sticks icons fail the visual similarity check: at card-thumbnail size they read as the same bundle, and players mis-pay costs. The torch and the wheat sheaf fail the composition competition check: on the exploration card they sit adjacent and equally bright, so players read "food discovery" instead of "explore." The coins and shield pass everything.
The checklist output is a short list of failed pairs with the failing test named. The designers redraw the fuel icon as a flame rather than a bundle (killing the similarity collision) and re-weight the exploration card so the torch dominates. The collisions are gone — caught by a mechanical scan, not by waiting for players to complain.
How it works¶
- Enumerate the pairs. From the current symbol inventory, list the pairs that can plausibly appear together or be mistaken for each other; skip pairs that never co-occur.
- Run each pair through the fixed checks. At minimum: visual confusability (too similar to distinguish at real viewing size), semantic incompatibility (meanings that contradict or muddy when adjacent), and compositional competition (two symbols fighting for the same focal role in one image).
- Test at real conditions. Judge similarity at the size, distance, and reproduction the work actually uses, not at design-canvas zoom.
- Record failures with the test named. Each flagged pair carries which check it failed, so the fix targets the right property (redraw vs. separate vs. re-weight).
Tuning parameters¶
- Pair scope — all pairs versus only co-occurring pairs. All-pairs is exhaustive but quadratic and noisy; co-occurring-only is leaner but can miss a collision when two symbols later share a frame.
- Similarity strictness — how close is "too similar." Tightening catches subtle confusions but flags pairs real viewers would never mix up.
- Viewing conditions tested — one nominal size versus the full range of sizes, distances, and media. More conditions catch more collisions but multiply the checks.
- Check set — the fixed list of collision types applied. Adding checks (e.g., colorblind confusability) widens coverage at the cost of a longer pass.
When it helps, and when it misleads¶
Its strength is that it is fast, mechanical, and repeatable — a fixed list run over the set catches the "two symbols look too similar" and "different symbols carry the same meaning" symptoms the archetype names, without needing an expert or an audience panel. Its logic is fundamentally about difference: in structural semiotics a sign carries meaning only by contrasting with the others in its system[1], so a collision is a failure of that distinguishing contrast — two signs that no longer differ enough to mean different things.
Its failure mode is that a checklist only catches the collision types on the list: a novel clash no item anticipates passes clean, and the pass gives false comfort. It also judges pairs in isolation at a moment in time, so it misses a collision that only emerges from a specific composition or from a motif's meaning shifting over a series. The classic misuse is running it once and declaring the set "collision-free" forever, when adding a single new symbol can create fresh collisions with every existing one. The guarding discipline is to re-run the full pairwise scan whenever the inventory changes and to keep the check list itself under review as new collision types surface.
How it implements the components¶
symbol_drift_and_collision_audit— it performs the collision half of this audit: pairwise checks for confusability, incompatibility, and competition among current symbols.visual_symbol_inventory— it operates over the enumerated symbol set and, in scanning it, keeps that inventory honest by exposing near-duplicates that should be merged or separated.
It scans one moment, not a trajectory: the cross_piece_continuity_map that tracks a motif's meaning across many pieces over time belongs to Motif Continuity Matrix; this checklist takes a static snapshot of the set and tests it pair by pair.
Related¶
- Instantiates: Symbol-System Coherence in Visual Art — supplies the collision half of the archetype's drift-and-collision audit.
- Consumes: Iconographic Key Table supplies the current symbol inventory the pairwise scan runs over.
- Sibling mechanisms: Compositional Semantics Review · Cultural Iconography Review · Exhibition or Series Style Guide · Iconographic Key Table · Motif Continuity Matrix · Semiotic Audience Test · Symbol Drift Revision Log · Visual Metaphor Mapping Grid
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Symbol Collision Checklist is defined in the frozen evidence as: Reviews whether two symbols look too similar, signal incompatible meanings, or compete in the same composition. Its operative deployed or enacted form is therefore Assessment, Review & Assurance.
Nearest alternative: Interface, Display & Cue — Interface, Display & Cue can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Checking that no two marks, colors, abbreviations, or gestures can be confused in one context is interface symbol-system validation. ISO directives require unambiguous terminology and symbol definitions, and ISO 7000 governs standardized graphical symbols; HCI tests contextual discriminability.
Related originating lineages:
- Art & Aesthetics — art_aesthetics contributes visual art, composition, and design practice to this mechanism's defining operation—Reviews whether two symbols look too similar, signal incompatible meanings, or compete in the same composition—without displacing the selected primary historical lineage.
- Communication & Media Studies — communication_media_studies contributes communication and media research to this mechanism's defining operation—Reviews whether two symbols look too similar, signal incompatible meanings, or compete in the same composition—without displacing the selected primary historical lineage.
- Engineering & Design — engineering_design contributes engineering design, reliability, and systems-safety practice to this mechanism's defining operation—Reviews whether two symbols look too similar, signal incompatible meanings, or compete in the same composition—without displacing the selected primary historical lineage.
- Linguistics & Semiotics — Semiotics explains how sign systems generate ambiguity.
Review resolution: The blind reviewers disagree on primary lineage (human_computer_interaction versus art_aesthetics). Authoritative or primary research supports human_computer_interaction as the best historical origin: Checking that no two marks, colors, abbreviations, or gestures can be confused in one context is interface symbol-system validation. ISO directives require unambiguous terminology and symbol definitions, and ISO 7000 governs standardized graphical symbols; HCI tests contextual discriminability. The cited ISO/IEC Directives, Use and Definition of Symbols; ISO 7000, Graphical Symbols for Use on Equipment directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=cross_disciplinary_synthesis records lineage, while domain_reach=universal records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] de Saussure, F. Cours de linguistique générale. Eds. C. Bally & A. Sechehaye, with A. Riedlinger. Payot (1916). Treats linguistic value as differential: signs function through their relations to and distinctions from other signs in the system. registry ↩