Foreground-Background Map¶
Specification artifact — instantiates Figure-Ground Structuring
Records, in one artifact, what should be the figure, what should recede as ground, and where the boundary between them falls — the shared spec the rest of the structuring hangs on.
Before anyone chooses a color, a font weight, or a mix level, someone has to decide what the figure is and what the ground is — and write it down. Foreground-Background Map is the declarative artifact that fixes that assignment. It names the intended figure and says why it earns foreground status for this task, inventories the ground as the support layer that must recede yet stay interpretable, and states where the boundary between them runs. Crucially it is a specification, not a rendering: it does not set how strongly the figure pops or cut any clutter — it records the decision that every downstream mechanism reads from. Its whole job is to turn an implicit, arguable "obviously the eye should go here" into an explicit, contestable statement the rest of the design can be checked against.
Example¶
A city emergency-management office is producing a wildfire evacuation map for a hillside district. Before a cartographer touches the file, the team fills out a foreground-background map as a one-page spec. Figure: the single recommended evacuation route, Elm Street to Route 9 — chosen because a resident under stress needs one unambiguous path, not the full road network. Ground: every other road, terrain shading, neighborhood labels, and the fire-hazard overlays — kept visible, because a driver must still orient and see where the hazards are, but subordinate. Boundary: the route is to be a single continuous ribbon; the ground roads a thin, low-saturation web; the hazard zones translucent fills that never occlude the route.
The output is not a finished map but a short table anyone can argue with: figure = one route; ground = orienting context, muted; boundary = continuous ribbon over a thin web. When a reviewer asks "why is the route the figure and not the shelter locations?", they are challenging an explicit line in the spec rather than reverse-engineering intent from a finished graphic. Every contributor — print, web, the accessibility reviewer — then builds from the same assignment.
How it works¶
The distinguishing move is that the map is declarative and upstream of any styling:
- Name the figure candidate. State the one element (or a short ranked set) that should become the figure, and the task reason it deserves foreground — not that it is vivid, large, or convenient.
- Model the ground as an active layer. Inventory what recedes and what work each piece does: baseline, history, orientation, provenance, surrounding hazards. The ground is support, not leftover.
- Mark the boundary. State what kind of separation divides figure from ground (spatial, visual, temporal, statistical) and roughly how hard it should be — clear enough to orient, soft enough not to fabricate independence.
It stops there. It does not decide contrast magnitude, does not remove competing detail, and does not keep the context visible at runtime — those are the salience, sweep, and baseline-band mechanisms reading from this spec.
Tuning parameters¶
- Figure granularity — a single figure versus a small ranked set. One figure is unambiguous but rigid; a ranked set serves layered tasks at the cost of a weaker primary.
- Ground inventory depth — how finely the ground is enumerated. Fine detail exposes hidden context but bloats the spec.
- Boundary hardness (declared) — how sharp the intended separation is. Harder boundaries orient faster but risk falsely severing a figure from context it needs.
- Map multiplicity — one canonical map versus one per audience or task. Multiple maps serve diverse users honestly but must be kept mutually consistent.
When it helps, and when it misleads¶
Its strength is that it makes the figure-ground assignment shared and contestable before effort is spent, which is exactly when it is cheap to change. It catches the "accidental figure" — the element that dominates because of legacy styling, not because the task wants it forward — because the spec forces someone to justify the choice in words.
Its failure mode is that a written map can look authoritative and quietly freeze one assignment as natural, hiding that the choice was contestable. It also invites being written backwards — filled in to rationalize a highlight that was already chosen. And figure and ground are not independent: fixing one silently commits the other, as Rubin's vase makes plain.[1] The guarding discipline is to keep the map provisional and pair it with a figure-ground reversal test, so the "obvious" figure is challenged rather than enshrined.
How it implements the components¶
Foreground-Background Map realizes the declarative core of the archetype — the assignment itself, not its rendering:
foreground_candidate_definition— its first slot: it names the figure and records the task justification for foregrounding it.ground_context_model— it inventories the ground as an active support layer and states what each element carries.figure_ground_boundary— it declares the boundary's kind and rough hardness, the separation the styling mechanisms will encode.
It does not implement contrast_salience_gradient (that belongs to Salience Ladder Review, which tunes how strongly the figure pops) or context_retention_channel — that is Baseline Context Band, its nearest twin, which keeps the ground the map only declares actually visible in a live runtime layer.
Related¶
- Instantiates: Figure-Ground Structuring — the map is the shared assignment every other mechanism reads from.
- Sibling mechanisms: Salience Ladder Review · Background Load Sweep · Figure-Ground Reversal Test · Baseline Context Band · Lead-Support Mix Check
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Foreground-Background Map operates as a non-executable information artifact that externalizes static or prospective structure because it records, in one artifact, what should be the figure, what should recede as ground, and where the boundary between them falls — the shared spec the rest of the structuring hangs on.
Independent corroboration: The frozen evidence defines Foreground-Background Map as 'Records, in one artifact, what should be the figure, what should recede as ground, and where the boundary between them falls — the shared spec the rest of the structuring hangs on', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Art & Aesthetics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Specifying figure, ground, and boundary arises from visual composition and design practice.
Related originating lineages:
- Communication & Media Studies — Editorial framing contributes deliberate foregrounding of information.
- Human-Computer Interaction — Interface design materially turns the distinction into a shared implementation specification.
- Psychology — Gestalt psychology supplies the figure-ground theory.
Review resolution: Both reviewers agree that art_aesthetics is primary. I retain psychology, human_computer_interaction, communication_media_studies only as formative origin lineage(s), without treating every later application as an origin. cross_disciplinary_synthesis is appropriate because the exact artifact combines contributions from multiple professional lineages. Reach is multi_domain as a separate applicability judgment: it does not widen or narrow the recorded provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. The secondary differences are reconciled with no unresolved primary-provenance ambiguity.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The map is deliberately a spec, not a rendering. Keeping it separate from the styling mechanisms is what lets a team re-argue "is this really the right figure?" without redoing the finished artifact — and lets the same assignment drive a print map, a web map, and a screen-reader description consistently.
References¶
[1] Wagemans, J., Elder, J. H., Kubovy, M., Palmer, S. E., Peterson, M. A., Singh, M., & von der Heydt, R. "A Century of Gestalt Psychology in Visual Perception: I. Perceptual Grouping and Figure–Ground Organization". Psychological Bulletin 138(6), 1172–1217 (2012). Shows figure and ground as complementary border assignments whose ownership reverses in Rubin's vase. registry ↩