Resolution Matching¶
Core Idea¶
Resolution Matching is the relation between the smallest difference an instrument, effector, representation, or interface can reliably distinguish and the smallest difference the task requires it to preserve. When the resolver is coarser than the task, distinct targets collapse into the same reading or action and failure is structural rather than a matter of extra effort. When it is much finer than the task, the surplus precision may spend cost, bandwidth, sensitivity, or attention without changing the decision.
The abstraction is not “high resolution is good.” It asks for fit between two scales: resolving granularity and required distinction. The direction and magnitude of their mismatch predict the failure and the appropriate intervention.
Broad Use¶
- Instrumentation: sensor footprint and measurement resolution must separate the features being measured.
- Action and control: actuator or effector precision must fit the geometry of the target it must hit.
- Interfaces: target size and spacing must absorb the input precision of the operating population.
- Data representation: sampling interval, quantization step, or bin width must preserve the distinctions the downstream inference uses.
- Documentation and mapping: recording granularity must retain the distinctions a later reader or decision process needs.
Clarity¶
Resolution Matching separates an inability caused by the resolver from operator error. If the available granularity merges two task-relevant states, more care cannot recover a distinction the channel never carried. It also separates useful precision from ornamental precision: additional digits that cannot alter any protected decision do not repair a mismatch elsewhere.
Manages Complexity¶
A heterogeneous design problem reduces to two quantities expressed on a common scale: the resolver's effective resolution and the task's minimum consequential separation. Their ratio identifies under-resolution, adequate fit, or over-resolution and narrows the intervention to changing the resolver, enlarging the target distinction, aggregating the task, or accepting the loss explicitly.
Abstract Reasoning¶
Identify the distinctions whose collapse would change an action or inference. Estimate the effective resolution under real operating conditions rather than nominal laboratory conditions. Compare the two scales. If the resolver is coarser, improve it or widen the separation; if substantially finer, test whether the extra precision earns its cost. Re-run the comparison whenever the task or conditions change.
Knowledge Transfer¶
The roles transfer unchanged: a resolver, a target field, a minimum consequential distinction, operating conditions, and an outcome read from their scale relation. Pixels, millimetres, hertz, seconds, bits, and category widths are local units for the same fit test.
Example¶
A touch target smaller than the scatter of a user's finger position cannot be selected reliably. Enlarging the responsive hit area repairs the scale mismatch without retraining the user. The same structure appears when a sensor footprint is wider than the feature it must detect or a sampling interval is longer than the event it must capture.
Relationships to Other Abstractions¶
Current abstraction Resolution Matching Prime
Parents (1) — more general patterns this builds on
-
Resolution Matching is a kind of Scale Prime
Resolution Matching is scale specialized to the fit between a resolver's discrimination scale and the smallest distinction a task must preserve.
Children (3) — more specific cases that build on this
-
Rules-of-Engagement Ambiguity Domain-specific is a decomposition of Resolution Matching
Stripped of military doctrine, the failure is a resolver whose grain is coarser than the smallest consequential distinction the task presents.
-
Touch-Target Miss Domain-specific is a decomposition of Resolution Matching
Touch-Target Miss is resolution mismatch framed as an HCI fault when target geometry is finer than the operating population's effective motor precision.
-
Touch Target Size Domain-specific is a decomposition of Resolution Matching
Touch Target Size is Resolution Matching applied as a UI rule that target geometry must be no finer than the operating population can reliably acquire.
Hierarchy path (1) — routes to 1 parentless root
- Resolution Matching → Scale
Not to Be Confused With¶
- Scale: names the level of granularity; Resolution Matching compares two relevant scales and judges their fit.
- Accuracy: closeness to a target value; a measurement can be unbiased yet too coarse to distinguish task-relevant states.
- Precision: repeatability or dispersion; a highly repeatable instrument can still have the wrong resolution for the task.
- Engineering Tolerances: specify an admissible variation band; Resolution Matching asks whether the apparatus can resolve or hit distinctions at the scale the task requires.
- Requisite Variety: concerns the number of response states available to a regulator; Resolution Matching concerns the granularity at which distinctions can be sensed, represented, or acted upon.
Notes¶
Authored when the mixed-DAG pass found Touch-Target Miss and Touch Target Size independently pointing to a missing cross-domain resolution-matching parent. Queued for house-style harmonization and citation verification.