Deictic Labeling Protocol¶
Protocol — instantiates Shared Attention Anchoring Design
Replaces ambiguous 'this/that/there' references with stable labels, coordinates, tags, or identifiers whenever the stakes are high.
Pointing words — this, that, here, the one over there — only work when everyone shares the speaker's vantage and moment. Deictic Labeling Protocol bans them for high-stakes reference and substitutes a stable handle: a coordinate, a tag, an identifier, a named region that means the same thing to everyone regardless of where they sit or when they read it. Its defining move is building a durable reference standard rather than performing a one-time verification. A briefback confirms a target in the moment and moves on; a labeling protocol changes how the group talks about the target from now on, so that a mismatch shows up as two different labels rather than two silent interpretations of the same "this."
Example¶
A distributed engineering team is reviewing a nasty concurrency bug across three time zones. Early threads are a mess of "the lock in that function" and "this null check here," and two engineers spend an hour fixing different code paths before realizing it. The team adopts a labeling protocol: no referential comment may use a bare "this" or "here"; every reference must carry path:line plus the commit SHA — scheduler/queue.go:214 @ a3f1c9. Now when one reviewer writes "the race is at queue.go:214 @ a3f1c9" and another replies about queue.go:214 @ b7e02d, the labels themselves reveal that they are reading two different versions of the file — the divergence that bare pointing had hidden. The protocol also dictates that when the branch is rebased, references are re-issued against the new SHA rather than silently inherited.
How it works¶
- Ban the deictics. For flagged reference classes, ambiguous pointing terms are disallowed; a reference is not well-formed without a stable handle.
- Define the label schema. The group fixes what a valid handle looks like — coordinate, tag, ID, timestamp, named region — so labels are comparable across people.
- Compare labels to detect divergence. Because handles are stable, two references to "the same thing" that carry different labels expose a hidden split immediately.
- Re-issue on change. When the target moves or the underlying artifact revises, labels are regenerated and re-anchored rather than carried forward stale.
The protocol's discipline is stability: a good label survives a change of speaker, seat, and time, which is exactly what a pointing word cannot do.
Tuning parameters¶
- Label granularity — file-level, line-level, or character-range; region name versus exact coordinate. Finer labels remove ambiguity but cost effort and can over-specify.
- Enforcement scope — which reference classes must be labeled. Labeling everything is exhausting; reserve strict enforcement for the references whose misreading is costly.
- Versioning strictness — whether labels must carry a version/timestamp. Version-bound labels catch drift across edits but must be re-issued more often.
- Vocabulary fixedness — a controlled label set versus free-form tags. Controlled sets are unambiguous but rigid; free tags are flexible but can fragment.
When it helps, and when it misleads¶
Its strength is that it converts an invisible divergence into a visible one: mismatched labels are self-evident where mismatched interpretations of "this" are silent. It is a direct engineering of what linguists call deixis — reference that depends on the speaker's context[1] — into context-independent handles that travel. It shines in remote, asynchronous, and versioned settings where shared gaze and a shared moment are exactly what participants lack.
It misleads when the label scheme itself drifts out of sync with reality — a coordinate that no longer points where it did after an edit, or a tag whose meaning quietly shifts — so the protocol lends false confidence to a stale handle. Its classic misuse is over-labeling low-stakes chatter until the ceremony smothers ordinary conversation and people route around it. The guarding discipline is to bind labels to versions where the artifact changes, and to scope enforcement to the references that actually warrant it.
How it implements the components¶
referential_anchor— the protocol's core product is a stable, shareable handle that anchors reference independent of any speaker's vantage.attention_drift_detector— comparing stable labels surfaces version mismatch and divergence that bare pointing conceals.re_anchor_protocol— when the target or artifact changes, labels are regenerated and re-anchored rather than silently inherited.
It does not perform a spoken receiver-side verification that a specific instruction landed — the confirmation_checkback component is owned by Briefback Reference Check, which is an in-the-moment readback; this protocol instead changes the reference vocabulary itself so ambiguity cannot form.
Related¶
- Instantiates: Shared Attention Anchoring Design — the protocol supplies the stable referential anchor the archetype depends on for unambiguous pointing.
- Sibling mechanisms: Attention Reset Pause · Point-and-Confirm Round · Briefback Reference Check · Common Operating Picture Callout · Handoff Target Trace · Joint Gaze or Attention Probe · Live Annotation Layer · Multi-Modal Pointer Set · Shared Screen Highlight
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: The mechanism bans ambiguous deictics for flagged reference classes and requires stable handles under a shared schema with re-anchoring on change, so its operative form is a standing reference rule.
Nearest alternative: Protocol, Workflow & Routine — Labels are generated, compared, and reissued through procedures, but the durable well-formedness constraint rather than a fixed action sequence is the load-bearing mechanism.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Aviation is primary because high-stakes radio procedure operationalized complete, stable call signs and position labels, with explicit precautions against ambiguous or similar identifiers. Linguistics supplies the diagnosis of deictic reference, and military command practice supplies a parallel stable-designator lineage.
Related originating lineages:
- Linguistics & Semiotics — Linguistics identified deixis as reference whose interpretation changes with speaker, place, and time.
- Military & Strategic Studies — Command-and-control practice independently developed stable call signs, grid references, and target identifiers.
Review resolution: Aviation is primary because high-stakes radio procedure operationalized complete, stable call signs and position labels, with explicit precautions against ambiguous or similar identifiers. Linguistics supplies the diagnosis of deictic reference, and military command practice supplies a parallel stable-designator lineage.
Attribution caveat: The encyclopedia protocol generalizes an operational communication rule using a linguistic diagnosis.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Levinson, S. C. Pragmatics (1983). Cambridge University Press. Defines deixis as reference whose interpretation depends on features of the speaker's utterance context. registry ↩