Skip to content

Alluvial diagram

A flow visualization whose blocks represent groups at successive stages and whose width-scaled streams show how members or quantities move among those groups over time or categories.

Version
v1 · 2026-09-08 · History
Domain-specific #
3261
Origin domain
data visualization
Subdomain
flow diagrams

Core Idea

An alluvial diagram depicts changes in composition by connecting category blocks across axes with ribbons proportional to transferred quantity. Records or weights are aggregated by their sequence of category memberships, and each aggregate becomes a ribbon whose splits and merges reveal structural change. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of data visualization. It is composition-over-stage visualization emphasizing splits, merges and group persistence. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test.

Scope of Application

Alluvial diagram belongs to data visualization and is useful where the analyst can specify successive categorical partitions or stages, blocks sized by quantity, flows linking blocks, stream widths, ordering and color, conserved or changing membership and labels, then evaluate block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals. The scope is broad within that domain but bounded by the need for block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity

The abstraction clarifies a crowded vocabulary by making block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Alluvial diagram can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Alluvial diagram. Alluvial diagram compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: successive categorical partitions or stages, blocks sized by quantity, flows linking blocks, stream widths, ordering and color, conserved or changing membership and labels. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of data visualization because they reuse successive categorical partitions or stages, blocks sized by quantity, flows linking blocks, stream widths, ordering and color, conserved or changing membership and labels, Records or weights are aggregated by their sequence of category memberships, and each aggregate becomes a ribbon whose splits and merges reveal structural change., and type the carrier, state every parameter and convention in the definition, test that block and ribbon widths use a consistent quantitative scale and flows reconcile with declared gains, losses or totals, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Alluvial diagramParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Alluvial diagramDOMAINPrime abstraction: Representation — is a kind ofRepresentationPRIME

Current abstraction Alluvial diagram Domain-specific

Parents (1) — more general patterns this builds on

  • Alluvial diagram is a kind of Representation Prime

    The proposed strict upward parent is prime:representation.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Alluvial diagram sits in a moderately populated region (51st percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Data Visualization & Geometric Displays (21 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08