Skip to content

Receptive Field

Prime #
1116
Origin domain
Neuroscience
Subdomain
sensory neuroscience → Neuroscience

Core Idea

A receptive field is the structural pattern in which a processing unit responds only to inputs that fall inside a bounded region of some input space, producing zero or baseline response to everything outside that region. The unit is characterised not by what it computes globally but by its coverage footprint: the locus in input space where stimulation matters, the shape of that locus, and the falloff at its edges. The essential commitment is that perception, prediction, control, and accountability in a large system are routed through many such units, each with a bounded local jurisdiction, and that the system as a whole tiles or covers its input space by composing these local jurisdictions.

Three consequences follow from the bounded-jurisdiction discipline. First, each unit can be specified, tuned, and audited locally, without reference to the whole. Second, the system's global behaviour can be analysed as a map from input location to which unit(s) fire. Third, inputs that fall in the gaps or overlaps of the tiling have predictable distinctive behaviour — silence in a gap, ambiguity or double-counting in an overlap. Every receptive-field design sets four parameters: the centre (where the field sits in input space), the extent (how large the responsive region is), the selectivity (within the region, which features the unit responds to), and the edge profile (how sharply response falls off, and whether there is an inhibitory surround).

The pattern is the dual of broadcast or global computation: a broadcast unit is sensitive to everything, while a receptive-field unit is sensitive to a small, named neighbourhood. The discipline of local jurisdiction is precisely what makes the ensemble scalable — because each unit's behaviour is determined by its own bounded footprint, the system can be built, analysed, and repaired one local field at a time, and its coverage understood as the union of those fields.

How would you explain it like I'm…

My Little Patch

Imagine a guard who only watches one small doorway and ignores the whole rest of the building. If something walks through their doorway, they shout; if it's anywhere else, they stay quiet. A Receptive Field is like that little patch each watcher is in charge of, and lots of watchers together cover the whole place.

Each Sensor's Square

Think about a big wall covered with motion sensors, where each sensor only notices movement in its own little square of space. One sensor doesn't care about the whole wall — it only reacts to its own square, and stays quiet about everything else. A Receptive Field is that square: the small region where a sensor actually pays attention. By tiling many sensors next to each other, the whole wall gets covered, and you can check or fix each sensor on its own without worrying about all the others.

Bounded Local Jurisdiction

A Receptive Field is the bounded region of an input space that a single processing unit actually responds to — it fires for stimulation inside that region and stays at baseline for everything outside it. The unit isn't defined by some global computation but by its 'coverage footprint': where its region sits, how big it is, what features inside the region it cares about, and how sharply its response fades at the edges. A big system handles a large input space by tiling it with many such units, each minding its own local patch, so the whole thing can be built and audited one patch at a time. This is the opposite of a 'broadcast' unit that reacts to everything at once. A neat consequence is that inputs landing in the gaps between fields get silence, while inputs in overlaps get double-counted — both predictable from the tiling.

 

A Receptive Field is the structural pattern in which a processing unit responds only to inputs falling inside a bounded region of some input space, producing zero or baseline response everywhere else. The unit is characterized not by a global computation but by its coverage footprint: the locus in input space where stimulation matters, the shape of that locus, and the falloff at its edges. The essential commitment is that perception, prediction, control, and accountability in a large system are routed through many such units, each holding a bounded local jurisdiction, and that the whole system tiles or covers its input space by composing these local jurisdictions. Three consequences follow: each unit can be specified, tuned, and audited locally without reference to the whole; global behavior can be analyzed as a map from input location to which units fire; and inputs in the gaps or overlaps of the tiling behave distinctively — silence in a gap, ambiguity or double-counting in an overlap. Every design fixes four parameters: the center (where the field sits), the extent (how large the responsive region is), the selectivity (which features inside it the unit responds to), and the edge profile (how sharply response falls off, and whether there is an inhibitory surround). The pattern is the dual of broadcast computation, and bounded local jurisdiction is precisely what makes the ensemble scalable and repairable one field at a time.

Structural Signature

the input space to be coveredthe processing unit with a bounded local jurisdictionthe four field parameters (centre, extent, selectivity, edge profile)the tiling of the space by many unitsthe coverage map from input location to firing unitthe gaps and overlaps with predictable distinctive behaviour

A system uses receptive fields when each of the following holds:

  • An input space. Some space — retinal patch, image, customer base, key-range, case space, sky — over which inputs arrive and must be covered.
  • Bounded-jurisdiction units. Each processing unit responds only to inputs falling inside a bounded region of the input space, producing baseline response outside it; it is characterised by its coverage footprint, not its global computation.
  • Four field parameters. Each field sets a centre (where it sits), an extent (how large the responsive region is), a selectivity (which features within the region it responds to), and an edge profile (how sharply response falls off, with any inhibitory surround).
  • A tiling. The system as a whole covers the input space by composing many such local jurisdictions, with controlled redundancy.
  • A coverage map. Global behaviour is analysable as a map from input location to which unit(s) fire, so each unit is specifiable and auditable locally.
  • Predictable gaps and overlaps. Inputs in tiling gaps produce silence; inputs in overlaps produce ambiguity or double-counting.

The components compose the dual of broadcast computation: because each unit is determined by its own bounded footprint, the ensemble is built, analysed, and repaired one local field at a time, and coverage failures are tiling problems to re-draw rather than unit problems to retrain.

What It Is Not

  • Not perspective. perspective is a vantage-dependent view of a whole scene — what a single observer sees, shaped by their standpoint. A receptive field is a bounded jurisdiction: the unit responds only inside its region and is silent outside, and many such fields tile a space. Perspective is one view of everything; a receptive field is total coverage of one neighborhood.
  • Not segmentation. segmentation_and_boundary_drawing partitions an already-present signal into regions. A receptive field is a sensitivity footprint fixed on the input space prior to any signal — it determines which unit responds to an input, not how a signal is carved up after arrival.
  • Not attention. attention is selective allocation of limited capacity among competing inputs. A receptive field is a fixed structural footprint; attention can be modeled as a movable receptive field, but the bare receptive field is a static jurisdiction, not a dynamic allocation of priority.
  • Not partition. partition divides a set into disjoint exhaustive blocks. A receptive-field tiling generally has controlled overlap and possible gaps — overlap gives redundancy, gaps give silence — and is characterized by center/extent/selectivity/edge-profile, not by clean disjointness.
  • Not locality of reference. locality_of_reference is an access-pattern property (clustered accesses). A receptive field is a response-jurisdiction structure; it organizes which unit fires for which input, independent of whether accesses happen to cluster.
  • Common misclassification. Debugging the unit (retrain the rep, upgrade the sensor) when the missed input simply fell outside every field's coverage. If the event lay in a tiling gap, no unit improvement helps — the fix is to re-tile the coverage geometry, a different object from unit capability.

Broad Use

  • Sensory neuroscience: a retinal ganglion cell fires only for light in a small retinal patch (the centre-surround field); V1 simple cells respond to oriented bars in a local visual patch; somatosensory neurons map to skin patches (the cortical homunculus is the tiling).
  • Convolutional neural networks: each filter responds to a local input patch, deeper layers build larger effective receptive fields by composition, and field size is a primary design parameter computable in advance from kernel, stride, dilation, and depth.
  • Organisational role design: a customer-success manager owns a bounded book of accounts, a fire warden covers one floor, a beat officer covers a geographic patch — the set of role boundaries is meant to tile the organisation's input space with controlled overlap.
  • Sales territories and distributed systems: each rep owns a bounded region of customer space; each shard owns a bounded key-range; routing sends each request to the unit whose field contains it, and re-sharding is receptive-field redesign.
  • Jurisdiction and sensing: a court or regulator has bounded subject-matter and geographic jurisdiction; a radar, telescope, or satellite has a footprint, and coverage planning is the problem of tiling the input space with sensors.
  • Attention as a controllable field: spatial attention shrinks or shifts the effective region of high-fidelity processing, the operational receptive field of the cognitive system.

Clarity

Receptive field makes a precise distinction visible that ordinary language blurs: between what a unit can in principle do and which inputs it actually responds to. A unit whose field excludes an event will be silent on that event even if it has every capability needed to process it. This relocates many system failures — a churned account, a regulatory void, a sensor blind spot — from the units themselves to the coverage geometry of their fields, which is a different object and demands a different fix (re-tile, not retrain).

The pattern also names the four parameters every field design must set: centre, extent, selectivity, and edge profile. Making these explicit dissolves confusions that arise when they are conflated — two units can share centres yet differ entirely in selectivity, or share selectivity yet differ entirely in centres, and a design discussion that does not separate the four cannot say which is wrong. The clarifying force is to convert "this unit isn't handling that case" into a precise structural question: is the case outside the field's extent, outside its selectivity, lost at the edge profile, or falling in a tiling gap between fields?

Manages Complexity

The pattern collapses a family of cross-substrate problems — sensory coverage, sales-territory design, jurisdictional allocation, sharding, beat assignment, antenna placement — into one structural problem: tile the input space with bounded- jurisdiction units whose union covers the relevant region with acceptable redundancy and acceptable gaps. A practitioner facing any of these no longer needs a domain-specific theory of coverage; they need to specify the fields and compute their union against the input space.

It also collapses a family of failure modes — blind spots, dead zones, jurisdictional gaps, between-shard lookup failures, unowned accounts, regulatory voids, scotomas — into one structural failure: some region of input space falls outside every unit's field. The diagnostic move is identical in every case: plot the union of fields against the input space and look for holes. Because each unit is locally specifiable and the global behaviour is just the union of local fields, the complexity of a large covering system reduces to per-field specification plus a coverage computation, which is the entire economy of the pattern — the system is built and reasoned about one bounded jurisdiction at a time.

Abstract Reasoning

Receptive field licenses several characteristic moves. Coverage analysis: given the units and their fields, compute the union (covered region) and the complement (gaps), where gaps predict silence and overlaps predict contention. Tiling design: choose unit count and field size under a budget — many small fields give high resolution at high cost, few large fields are cheap but blur — a trade-off that is universal across substrates. Hierarchical composition: stacking units whose fields pool over many lower-level fields produces larger effective fields with selectivity for higher-level features, the move shared by convolutional depth, organisational hierarchy, regulatory federation, and visual cortex.

Two further moves complete the toolkit. Re-tiling under load: when input load becomes uneven, the response is to redraw fields — re-shard, redistrict, reassign beats, redeploy attention — not to change the units' internal computation. And identifying load-bearing units: a unit whose field is the only coverage of a critical region is a single point of failure whose removal creates a guaranteed blind spot, while a unit becomes biased toward the dense parts of its field, systematically neglecting under-covered subregions. The reasoner asks, at every turn: what is the input space, what are the field centres and extents, where is the union complete and where does it gap or overlap, and which unit is the sole cover of a critical region?

Knowledge Transfer

Receptive field transfers because the formal problem of tiling an input space with bounded sensitivity regions recurs with the same mathematical structure across substrates, with only mild translation from its neuroscience-origin vocabulary. The role mapping is consistent: the unit maps to a ganglion cell, a CNN filter, an account manager, a shard, a court, a sensor; the input space maps to the retina, the image, the customer base, the key-range, the case space, the sky; the field maps to the receptive patch, the territory, the jurisdiction, the footprint; and the coverage gap maps identically to a scotoma, an unowned account, a regulatory void, a sensor blind spot.

The transfers are formal, not metaphorical. The mathematics of centre-surround and orientation-tuned fields directly seeded the convolutional architecture, and effective-receptive-field calculations cross over without modification. The CNN move of stacking small local fields under broader pooled fields ports to nested account coverage and to regional-national-global organisational structure. Sales-territory algorithms (k-means over customer locations weighted by revenue density) and key-range sharding algorithms are formally the same receptive-field tiling problem with the same load-balance constraint, so a distributed-systems engineer and a sales-operations analyst are solving one problem. A regulator whose field excludes a new asset class is structurally identical to a camera whose field excludes the loading bay — both produce silent failures rather than false alarms, which is the diagnostic signature of a coverage gap. And attention as a movable field ports to UI design (the user's attention is a small movable window) and to surveillance practice (a focus shift costs coverage elsewhere). The internal structure transfers too: the centre-surround motif recurs from retina to attention to competition for adjacent territories; the effective-versus- nominal distinction ports from CNNs to federated systems; and the hand-off problem at field boundaries recurs from radar tracking to sales-lead handoff to perception across saccades. The unifying transfer move is always: name the input space, specify each unit's bounded field, compute the union to find gaps and overlaps, and treat coverage failures as tiling problems to be re-drawn rather than unit problems to be retrained.

Examples

Formal/abstract

The retinal ganglion cell with a center-surround receptive field is the canonical instance and instantiates all four field parameters as measurable physiology. The input space is the retinal surface (and, through it, the visual field). The bounded-jurisdiction unit is a single ganglion cell, which fires only for light falling within a small circular patch of retina and is silent for light anywhere else — characterized entirely by its coverage footprint, not by any global computation. The four parameters are concrete: the center is the cell's position on the retina; the extent is the diameter of its responsive circle; the selectivity is set by the antagonistic organization — an ON-center cell is excited by light in the middle of its field and inhibited by light in an annular surround, so it responds not to absolute luminance but to local contrast; and the edge profile is the falloff plus the inhibitory surround that sharpens the boundary. The prime's tiling claim is literal: the full population of ganglion cells covers the entire retina with overlapping fields, smaller and denser in the fovea (high resolution, high cost) and larger and sparser in the periphery (cheap, blurry) — exactly the prime's resolution-versus-cost trade-off realized as a coverage budget. The coverage map is the retinotopic projection: which cell fires tells the brain where the stimulus is. And the prime's gap prediction is the blind spot — the optic-disc region has no photoreceptors, so a stimulus there falls outside every field's coverage and produces literal silence (a scotoma), a coverage failure in the tiling geometry, not a defect in any unit. The intervention the prime names is structural: to improve acuity in a region, increase the density of small fields there, and to eliminate a blind spot, re-tile, not retrain individual cells.

Mapped back: The retinal ganglion array is the receptive field in its founding form — center as retinal position, extent as field diameter, center-surround antagonism as selectivity, inhibitory surround as edge profile, the retinotopic population as the tiling, and the blind spot as the predicted coverage gap — confirming the prime's claim that coverage failures are tiling problems to re-draw.

Applied/industry

Two domains far from neuroscience — sales-territory design in business operations and key-range sharding in distributed databases — run the same tile-the-input-space structure (with the prime's caveat that the neuroscience vocabulary is mildly translated). In sales-territory design, the input space is the customer base, embedded by geography and revenue density; the bounded-jurisdiction unit is a sales rep who owns a contiguous territory and is responsible only for customers inside it. The four parameters map cleanly: the center is the territory's anchor, the extent is how much customer-space it spans, the selectivity is which account types the rep handles, and the edge profile is how boundary accounts are split. The prime's coverage diagnostic is the operational reality: an unowned account — a customer falling in a gap between territories — receives no outreach and silently churns, a coverage failure that the prime correctly relocates from the reps (who may each be excellent) to the tiling geometry. The fix is the prime's: re-tile (redistrict) rather than retrain, and the territory-design algorithm (k-means over customer locations weighted by revenue) is literally a receptive-field tiling with a load-balance constraint. Key-range sharding maps onto the identical problem: the input space is the keyspace, each shard owns a bounded range of keys, a router sends each request to the shard whose field contains it, and the prime's gap-and-overlap predictions are exact — a key that falls outside every shard's range produces a lookup failure (silence), and an overlap produces double-ownership contention. The prime's re-tiling-under-load move is the standard operational response: when one shard gets hot (uneven load), you re-shard — redraw the field boundaries — rather than change any shard's internal logic. In both domains the diagnostic is identical and matches the prime's: plot the union of fields against the input space and look for holes and overlaps.

Mapped back: Sales territories and database shards both instantiate an input space tiled by bounded-jurisdiction units with center, extent, selectivity, and edge profile, and both fail by the prime's signature coverage gap (unowned account; un-routed key) rather than by unit defects, so the intervention — re-tile under load, never retrain the unit — transfers from sensory neuroscience to operations and distributed systems with only mild translation.

Structural Tensions

T1 — Capability versus Coverage (scopal). A unit's competence to process an event is distinct from whether the event falls in its field; a fully capable unit is silent on inputs outside its jurisdiction. The failure mode is debugging the unit — retraining the rep, upgrading the sensor — when the event simply fell outside its coverage footprint. Diagnostic: ask whether the missed input was inside any unit's field. If the event lay in a tiling gap, no amount of improving individual units helps; the fix is to re-tile the coverage geometry, a different object from unit capability.

T2 — Resolution versus Cost (scalar). Tiling with many small fields gives high resolution at high cost; few large fields are cheap but blur. The two trade off against each other under a fixed coverage budget. The failure mode is demanding fine resolution everywhere without paying for the unit count, or accepting coarse fields where critical regions need acuity. Diagnostic: ask whether field density matches the importance gradient of the input space. If resolution is uniform while the input space has high-stakes subregions (the fovea, the key accounts), the budget is mis-allocated; concentrate small dense fields where resolution matters and economize elsewhere.

T3 — Gaps versus Overlaps (sign/direction). A tiling can err in two opposite directions: gaps produce silence (uncovered inputs vanish) and overlaps produce contention (double-ownership, ambiguity, double-counting). Eliminating one tends to introduce the other. The failure mode is tiling tight to avoid overlap and opening gaps, or padding to avoid gaps and creating contested regions. Diagnostic: plot the union of fields against the input space and inspect both holes and double-covered zones. If the design optimizes only against gaps or only against overlaps, the opposite failure is live; coverage planning must price both, often choosing controlled overlap to guarantee no gaps.

T4 — Nominal versus Effective Field (measurement). A unit's nominal field (its specified extent) can diverge from its effective field — where it actually responds with adequate fidelity — especially under composition or load. The failure mode is reasoning from the nominal footprint while the effective one is smaller, so regions assumed covered are functionally blind. Diagnostic: ask whether the unit's real responsiveness across its field has been measured, not just specified. If coverage is assumed from nominal boundaries (a CNN's theoretical receptive field, a rep's official territory) without checking effective response, the apparent coverage overstates the real one, and edge regions silently degrade.

T5 — Static Tiling versus Uneven Load (temporal). A tiling that covers the input space well under uniform load fails when load concentrates — one shard goes hot, one territory floods — even though the geometry is unchanged. The failure mode is keeping a fixed tiling as the load distribution shifts, overwhelming some units while others idle. Diagnostic: track per-unit load against capacity over time. If a field that was balanced becomes saturated as input clusters, the response is to re-tile (re-shard, redistrict) rather than to change unit internals; static coverage assumes stationary load, which rarely holds.

T6 — Distributed Coverage versus Sole-Cover Unit (coupling). Tiling distributes coverage across many units, but a unit that is the only cover of a critical region is a single point of failure whose loss creates a guaranteed blind spot. The failure mode is treating all units as redundant when one holds a critical region alone, so its removal silently opens a gap. Diagnostic: ask which regions are covered by exactly one unit. If a critical subregion has no redundant cover, that unit is load-bearing and its failure is catastrophic; the fix is deliberate overlap on critical regions, trading some efficiency for fault tolerance where silence would be costly.

Structural–Framed Character

Receptive field sits at the structural end of the structural–framed spectrum, with a near-zero aggregate of 0.1. The bounded-coverage-footprint structure is substrate-neutral, and four of the five diagnostics read flatly structural; the single non-zero criterion is a half-point on vocabulary travel, reflecting only that the neuroscience-origin lexicon carries with mild translation.

Walking the diagnostics with this prime's substrates: vocabulary travels with light baggage, scored 0.5. The home terms — "receptive field," "center-surround," "tiling," "retinotopic" — come from sensory neuroscience and must be translated into each substrate ("territory" and "book of accounts" for sales operations, "key-range" and "shard" for distributed systems, "jurisdiction" for regulators), but the underlying input-space / bounded-jurisdiction / four-parameter / tiling / coverage-gap skeleton is told identically across ganglion arrays, CNN filters, sales territories, database shards, and sensor footprints, so the translation is mild rather than a heavy frame. Evaluative weight is absent (scored 0): a field is neither good nor bad; a coverage gap is a structural fact, not a moral one. Institutional origin is formal (scored 0): the structure is stated as a bounded region of an input space covered by tiling, with no appeal to human institutions; its canonical substrate is the retina. It is not human-practice-bound (scored 0): it runs indifferently in a retinal ganglion cell, in a convolutional filter, and in a radar footprint, none requiring a human practice (the homunculus tiles the somatosensory cortex whether or not anyone studies it). And import-versus-recognize sits at 0 (structural): naming a receptive field recognizes a real coverage footprint one can test by mapping which inputs make the unit fire, not an imported reading. Every diagnostic but the translatable vocabulary points structural, and the modest 0.1 aggregate is faithful to the structural label.

Substrate Independence

Receptive Field is about as substrate-independent as a prime can be — composite 5 / 5 on the substrate-independence scale. Its signature — a bounded local jurisdiction over a region of input space, with the regions tiling the whole so each unit answers only for its patch — is a pure relational object (a bounded region of an input space) with no commitment to any medium. Its domain breadth is maximal: the same bounded-local-jurisdiction-tiling structure recurs in sensory neuroscience (the originating case of neurons responding to a patch of retina or skin), convolutional neural networks (each unit's local receptive field), organizational role design (each role owning a defined scope), sales-territory assignment, legal and administrative jurisdiction, distributed sensing (each sensor's coverage area), and attention (the windowed region currently processed). Its structural abstraction is complete because the pattern carries no domain-specific content beyond "bounded region of an input space, tiled across the whole." And the transfer is concrete and documented: the receptive-field concept was imported directly and quantitatively from visual neuroscience into CNN architecture, recognized rather than loosely analogized. Maximal breadth, a fully relational signature, and documented transfer converge on a canonical 5.

  • Composite substrate independence — 5 / 5
  • Domain breadth — 5 / 5
  • Structural abstraction — 5 / 5
  • Transfer evidence — 5 / 5

Neighborhood in Abstraction Space

Receptive Field sits in a sparse region of abstraction space (86th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.

Family — Selectivity & Bounded Windows (18 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-06-14

Not to Be Confused With

Receptive field's nearest neighbor by embedding is perspective, and the two are easy to conflate because both concern how a unit "sees" only part of a situation — but they have opposite geometries. Perspective is a vantage-dependent view of a whole: a single observer, from a particular standpoint, perceives the entire scene but in a way shaped and limited by where they stand. A receptive field is a bounded jurisdiction over a part: the unit responds only to inputs inside its region and produces baseline silence everywhere outside, and the system covers its input space by tiling many such fields. Perspective is one biased view of everything; a receptive field is complete sensitivity to one named neighborhood, with completeness achieved at the ensemble level. The distinction is operationally decisive: a perspective problem (everyone sees the whole but differently) is addressed by aggregating or reconciling viewpoints, whereas a receptive-field problem (each unit sees only its patch, and some patches are uncovered) is addressed by re-tiling the coverage geometry. Treating a coverage gap as a perspective issue would send the analyst hunting for biased viewpoints when the real failure is a hole in the tiling — a region no unit's field contains at all.

Receptive field must also be distinguished from segmentation_and_boundary_drawing, with which it shares the language of regions and boundaries. Segmentation operates on an already-present signal: given an image, a dataset, or a continuous field, it carves the signal into meaningful regions after the fact. A receptive field is a sensitivity footprint fixed on the input space before any signal arrives — it specifies which unit will respond to an input at a given location, not how a signal is divided once it is there. The difference is between a response jurisdiction (structural, prior, about which unit fires) and a post-hoc carving (operational, about how to divide observed data). The two can interact — a receptive-field array produces responses that a later stage segments — but conflating them confuses a structural coverage question ("does any unit's field contain this input?") with an analytic partitioning question ("how should this observed signal be divided?"). A practitioner who reads a receptive-field tiling as segmentation will look for the right way to carve a signal when the actual issue is whether the input space is covered at all.

A third genuine confusion is with attention, sharpened by the fact that attention is often modeled as a movable receptive field. The distinction is fixed-structure versus dynamic-allocation. A receptive field is a static jurisdiction: a unit's center, extent, selectivity, and edge profile define a fixed region of responsiveness. Attention is the selective, moment-to-moment allocation of limited processing capacity among competing inputs — it can shrink, shift, or sharpen the effective field of high-fidelity processing, but it is the act of allocation, not the footprint itself. The receptive field is the substrate on which attention operates: attention modulates which fields get prioritized resources, but the bare receptive field exists and tiles the space whether or not attention is deployed. Collapsing them loses the layered structure — a fixed array of receptive fields provides baseline coverage, and attention is a controllable overlay that re-weights or relocates the effective field. Mistaking the static tiling for dynamic attention (or vice versa) leads to expecting a coverage gap to be fixable by "paying more attention," when no allocation of attention can cover a region outside every unit's structural field.

These distinctions matter because each isolates a different facet: perspective is a biased whole-view (where a receptive field is complete coverage of a part), segmentation is post-hoc signal-carving (where a receptive field is a prior response jurisdiction), and attention is dynamic capacity allocation (where a receptive field is the static footprint it modulates). A practitioner who conflates them hunts for biased viewpoints, mis-frames coverage as signal-partitioning, or expects attention to fill a structural gap. Holding the receptive field as the specific bounded-jurisdiction / four-parameter / tiling / coverage-map structure keeps the analyst asking its real question — what is the input space, where do the fields sit, and where does their union gap or overlap?

Solution Archetypes

No catalogued solution archetypes reference this prime yet.