Sense Boundaries: Where one domain of meaning ends and another begins

A6Prose proofThe formal treatment of context boundaries and translation between them.

This interlude introduces the sense boundary (A6): a context-indexed equivalence that partitions uses of a term into sense classes. The pomegranate — fruit, color, motif — is the canonical worked example. A6 is a proto-operator: it names what must be represented but defers the transport machinery to A10, A16, and A28. The reader who wants the intuitive, notation-free version of this example should read Vol I, Chapter 5 (The Empire of Tables), where the pomegranate appears as visceral intuition rather than formal object.

The Word That Splits

Consider the word pomegranate.

In one sentence, it names a fruit—spherical, leathery-skinned, filled with ruby-red arils. In another sentence, it names a color—deep red, between crimson and burgundy. In a third, it names a decorative motif—the stylized image that appears in Persian textiles, Armenian manuscripts, and Art Deco wallpaper.

Whatever their historical path (metaphor, metonymy, convention), these senses now behave as distinct referents that share a spelling. A pomegranate print dress does not contain fruit. A pomegranate accent wall is not edible. The word has split, and the splits have become stable enough that each can anchor an entire design vocabulary.

Now consider what a system must do when it encounters pomegranate in a product description:

"This silk scarf features a pomegranate motif in deep burgundy."

Is pomegranate the subject or an adjective? Is the motif a representation of the fruit, or is it simply the name of a geometric pattern? Does pomegranate modify motif, or does deep burgundy modify pomegranate, creating a compound color name?

A string-matching system will retrieve documents containing the word pomegranate. Some will be about fruit. Some will be about color. Some will be about decorative patterns. The retrieval is not wrong—the word appears—but the system cannot distinguish which sense is active. It has matched tokens without drawing boundaries.

A schema-governed system might have separate predicates: fruit:pomegranate, color:pomegranate, motif:pomegranate. If the predicate exists, the query is typed. But this presupposes that the predicate inventory exists and is maintained—that someone has already done the governance work of recognizing "pomegranate motif" as a category worth certifying. If the product catalog was designed before that recognition occurred, the predicate does not exist. The system can store the description as a string, but it cannot certify the sense.

This is not a failure of intelligence. It is a failure of structure. The system lacks the object that would let it say: in this context, "pomegranate" denotes a motif, not a fruit. That object is a sense boundary.

Disambiguation Is Boundary-Drawing

Word sense disambiguation is sometimes treated as a classification problem: given a word in context, assign it to one of several pre-defined senses. The classifier learns from examples; at inference time, it outputs a label.

This framing is incomplete. A label tells you which sense was chosen; it does not tell you how that choice should behave when reused. If you classify "pomegranate" as motif in one context, and later encounter a new context where the same evidence applies, does the classification transfer? What if the new context adds constraints that make motif inconsistent?

The richer concept is boundary-drawing. To disambiguate is not merely to label; it is to draw a boundary that separates uses into equivalence classes. Within the boundary, all instances are "the same sense." Across the boundary, they are not.

Boundaries have properties that labels lack. First, stability: once drawn, a boundary should persist unless explicitly revised. If "pomegranate" means motif in one product description, it should mean motif in every product description from the same source, unless evidence indicates otherwise. Second, scope: a boundary is drawn in a context. The same word may have different boundaries in different contexts. "Pomegranate" means fruit in a grocery catalog and motif in a textile catalog. The boundaries are not in conflict; they are scoped. Third, transport: when a boundary is drawn in one context and the context changes, the boundary must be carried along in a way that respects the change. If the textile catalog merges with the grocery catalog, the system must decide: are these the same "pomegranate," or different predicates that share a spelling?

Transport is where the machinery becomes non-trivial. Labeling is a one-shot operation; transport requires tracking how boundaries evolve as contexts overlap and merge.

Categories are rarely natural kinds simply discovered by inquiry; they are governance artifacts maintained by coordination. The history of classification systems—from Linnaeus to library science to enterprise taxonomies—is a history of boundary negotiations: who decides what counts as "the same," under what authority, and with what procedures for revision. A sense boundary is the smallest unit of that negotiation.

A6: Sense Boundary (Proto-Operator)

We introduce a minimal formal object to capture the intuition.

Sense Boundary (Proto-Operator) — A6

Let $U$ be a context (a view with signature, constraints, and provenance regime).

Define a context-indexed equivalence $\sim_U$ on uses $(w, c)$ , where $w$ is a wordform and $c$ is the local constraint context:

(w, c) \sim_U (w', c') \quad \text{iff} \quad (w, c) \text{ and } (w', c') \text{ denote the same sense in context } U

The equivalence partitions uses into sense classes within $U$ . A sense boundary is the distinction induced by $\sim_U$ : what must be treated as same vs. different in context $U$ .

At this stage, we specify that sense boundaries exist, must persist, and are scoped to contexts. Transport obligations—how boundaries persist across context changes—are formalized in A10/A16/A28.

Remark(Why 'Proto-Operator'?)

A6 is not yet a fully operational definition. It says what a sense boundary is (a partition of uses) but not how to compute one or how to transport one when contexts merge. The formal machinery for transport requires the equivalence witnesses of Part II and the gluing structure of Part III. Here we only demand that the system represent the distinction and its scope; the criterion for when multiple scoped distinctions can be composed is deferred.

Remark(Connection to A5)

A6 is the smallest place where A5's coherence contract bites. The first disagreement is not a contradiction of facts, but a collision of senses. Two views that draw different boundaries for "pomegranate" are not logically inconsistent—they are locally valid but globally unreconciled. This is exactly the situation A5 clause 4 (conflict handling) is designed to address: the system must produce a witnessed reconciliation artifact, not silently collapse.

Toy Model: Three Sentences

Example(Sense Flip)

Consider three sentences:

"The pomegranate tree bore fruit in October."
"The fabric featured a pomegranate motif in gold thread."
"She chose pomegranate for the accent wall."

In sentence 1, pomegranate denotes a fruit (specifically, the tree that produces it).

In sentence 2, pomegranate denotes a decorative motif.

In sentence 3, pomegranate denotes a color.

Each sentence provides constraints that determine which sense is active:

tree, bore, fruit → biological entity
fabric, motif, thread → decorative pattern
accent wall + color-selection context → color

A system with sense boundaries would recognize these as three distinct equivalence classes. A query for "pomegranate fruit" would not retrieve the fabric or the wall. A query for "pomegranate motif" would retrieve the fabric but not the tree or the wall.

The critical observation: sense is determined by surrounding constraints, not by frequency. The most common use of "pomegranate" may be the fruit, but in a design context, the most common use is the motif or the color. A system that defaults to the majority sense will systematically misclassify minority contexts.

What a Boundary Artifact Might Look Like

To make the "witnessed object" discipline concrete, consider the shape of a boundary assertion. In the easy case, scopes are disjoint:

Boundary Assertion
  term:       "pomegranate"
  sense:      motif
  scope:      source = TextileCatalogB, field = description
  evidence:   co-occurrence constraints {motif, thread, fabric, silk}
  regime:     OWA (other senses may exist in other scopes)
  
Competing Boundary
  term:       "pomegranate"
  sense:      fruit
  scope:      source = GroceryCatalogA, field = product_name
  
Reconciliation
  status:     scoped coexistence (no collapse required)
  witness:    scopes are disjoint; no shared referents

This is not yet formalized—the witness structure, the scope algebra, the reconciliation logic are all deferred. But the shape is visible: a boundary is not a label floating in isolation; it is a claim with scope, evidence, and a declared relationship to competing claims.

The Fashion Catalog

Return to the running example.

A product description reads:

"Silk midi dress with pomegranate print. Burgundy on cream ground."

The catalog has a print_type field with values like floral, geometric, abstract, animal. Where does pomegranate belong?

If pomegranate print means a representation of the fruit, it might be floral (botanicals) or representational.
If pomegranate print means the stylized motif (as in Persian textiles), it might be geometric or traditional.
If the cataloger is unfamiliar with the pomegranate motif tradition, they might default to floral because the fruit is plant-based.

The decision is a sense boundary. Once drawn, it determines:

Which queries retrieve this dress
Which recommendations it appears alongside
Which analytics categories it contributes to

If the boundary is drawn incorrectly—or inconsistently across the catalog—downstream systems inherit the error. A shopper searching for "traditional motifs" will not find the dress. A merchandiser analyzing "geometric prints" will see distorted counts.

This is T6 (Predicate Invention) in miniature: the system needs a predicate pomegranate_motif that the schema does not yet contain. It is also T2 (Reference) in miniature: the same word refers to different things, and the system must track which thing is meant. And it is T7 (Contextual Equivalence) in miniature: whether "pomegranate" equals "pomegranate" depends on the context of comparison.

What Sense Boundaries Require

A6 is a statement of existence: sense boundaries exist and are scoped to contexts. But existence is cheap. The hard requirement is stability under transport.

Consider what happens when two catalogs merge:

Catalog A has drawn a boundary: pomegranate = fruit.
Catalog B has drawn a boundary: pomegranate = motif.

When A and B merge, the system encounters overlapping referents (products described as "pomegranate") with conflicting boundaries. The options are:

Collapse: Treat all pomegranates as the same sense (loses information).
Fork: Create two predicates, pomegranate_A and pomegranate_B (loses unification).
Reconcile: Recognize that the boundaries are contextually scoped and can coexist if the scope is made explicit and the reconciliation is witnessed.

Option 3 is the response that preserves information while respecting scope, but it requires machinery that A6 alone does not provide:

Witnessed equivalence (A10, Part II): an explicit record that two terms are "the same" in a given context, with justification.
Transport maps (A16, Part III): rules for how equivalences change when contexts change.
Reconciliation artifacts (A5, clause 4): first-class objects that record when overlap agreement fails and how the disagreement is resolved.

A6 names the object. The machinery that makes it operational is constructed in Parts II and III.

Touchstones in Miniature

This interlude touches three of the ten touchstones:

T2 (Reference): The same word—"pomegranate"—refers to different things (fruit, color, motif). A system without sense boundaries conflates referents. A system with sense boundaries distinguishes them.

T6 (Predicate Invention): The sense boundary is a nascent predicate. Drawing the boundary is the first step toward minting pomegranate_motif as a certified predicate with schema guarantees.

T7 (Contextual Equivalence): Whether two instances of "pomegranate" are equivalent depends on context. In a grocery catalog, pomegranate₁ = pomegranate₂ (both are the fruit). In a cross-domain merge, they may not be.

Each touchstone will receive its full treatment in Part VI. Here, they appear as shadows—previews of the formal machinery that resolves them.

Consequence

Disambiguation requires boundary-drawing, and boundaries create obligations: the boundary must persist, must be scoped, and must transport when contexts merge.

A6 names the object. The rest of The Proofs builds the machinery to make it operational. Sense boundaries are the smallest units of the coherence contract: when contexts overlap, they are what must agree.