Skip to main content

[DSB:THEORY.SEMANTIC_BINDING] [DSI:NAME=IMPLEMENTING_SEMANTIC_BINDING;ROLE=LEARNING;AUTHOR=SIMON_MACFARLANE;VERSION=1_0] [DSM:SYSTEM=SEMANTIC_BINDING;AUDIENCE=PUBLIC,PROFESSIONAL,AUTHORING_SYSTEMS]

Page 8 — Implementing Semantic Binding​

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.SCOPE.OVERVIEW.8-0]
[SSI:TITLE=IMPLEMENTATION_SCOPE;AUTHORITY=PRIMARY;REF=8-0]
[SSM:SECTION=SCOPE;INTENT=CONSTRAINT;ABSTRACTION=HIGH]

8.0 - Scope and Preconditions​

This document explains how to implement Semantic Binding.

It assumes the reader already understands:

  • what Semantic Binding is
  • why it exists
  • the six semantic anchors (DSB, DSI, DSM, SSB, SSI, SSM)

These topics are defined authoritatively in SB-001 — Introduction to Semantic Binding and are not repeated here.

If those concepts are not already understood, stop and read SB-001 before continuing.

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.PROCEDURE.CANONICAL.8-1] [SSI:TITLE=HOW_TO_IMPLEMENT_SEMANTIC_BINDING;AUTHORITY=PRIMARY;REF=8-1] [SSM:SECTION=PROCEDURE;INTENT=PROCEDURE;ABSTRACTION=LOW]

8.1 — How to Implement Semantic Binding​

Semantic Binding is implemented through a fixed sequence of authoring steps. Each step is mandatory and must be completed before proceeding to the next.

Step 1 — Declare Document Anchors Before Writing​

Before any prose is written, declare the document’s DSB, DSI, and DSM. These anchors define what the document is about, its identity, and the context in which it applies.

Writing before these anchors exist is invalid and produces semantically ungoverned content.

Step 2 — Define Section Scope Before Prose​

For each section, define the SSB that declares the semantic scope of that section. The SSB determines what meaning is allowed to appear and what content is out of bounds.

If required meaning does not fit the declared scope, the section must be redesigned before writing.

Step 3 — Declare Section Identity and Behaviour​

Each section must declare an SSI to provide a stable identity and a SSM to define intent and abstraction. These declarations control how the section may behave and how systems may retrieve or use it.

A section without declared identity and behaviour is not eligible for deterministic use.

Step 4 — Write Strictly Within Declared Anchors​

Once anchors are declared, all prose must conform to the declared scope, intent, and abstraction. Authors must not mix instruction with explanation, or procedures with rationale.

Any deviation from the declared anchors is a semantic error, not a stylistic one.

Step 5 — Split Sections When Meaning Changes​

If intent or abstraction changes during writing, the section must be split. Each section may express only one intent at one abstraction level.

Combining multiple semantic behaviours in a single section breaks retrieval eligibility.

Step 6 — Enforce Anchor Compliance​

After writing, content must be reviewed for compliance with declared anchors. Sections that violate scope, intent, or abstraction must be rewritten or rejected.

Semantic Binding is only achieved when anchors are declared first and obeyed without exception.

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.AUTHORING.MODEL.8-2]
[SSI:TITLE=AUTHORING_WITH_INTENT;AUTHORITY=PRIMARY;REF=8-2]
[SSM:SECTION=MODEL;INTENT=MODEL;ABSTRACTION=HIGH]

8.2 - Authoring Discipline​

Semantic Binding is implemented through authorial discipline.

Authors do not write free-form text and annotate it later.
They declare meaning first, then write within constraints.

Documents Are Semantic Units​

Every document must explicitly declare:

  • what domain it belongs to
  • what object it describes
  • what role it plays in the system
  • who it applies to

Without this, systems cannot determine whether the document is eligible for retrieval or use.

Sections Are Semantic Contracts​

Each section exists for one semantic purpose only.

A section must never:

  • mix explanation with instruction
  • mix principles with procedures
  • mix abstraction levels

One section. One intent. One abstraction level.

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.DOCUMENT.PROCEDURE.8-3]
[SSI:TITLE=DOCUMENT_ANCHOR_SETUP;AUTHORITY=PRIMARY;REF=8-3]
[SSM:SECTION=PROCEDURE;INTENT=PROCEDURE;ABSTRACTION=LOW]

8.3 - Authoring Principles - Declare Document Anchors​

Every document must declare the following anchors before any prose.

8.3.1 - Declare the DSB​

The DSB defines what the document is about.

It must include:

  • DOMAIN
  • OBJECT

Example:
[DSB:THEORY.SEMANTIC_BINDING]

Omitting or changing the DSB after publication is a semantic error.

8.3.2 - Declare the DSI​

The DSI defines document identity and versioning.

It must include:

  • NAME (stable, immutable)
  • ROLE (e.g. LEARNING, REFERENCE)
  • AUTHOR
  • VERSION

Example:
[DSI:NAME=IMPLEMENTING_SEMANTIC_BINDING;ROLE=LEARNING;AUTHOR=SIMON_MACFARLANE;VERSION=1_0]

Changing NAME or VERSION creates a new document.

8.3.3 - Declare the DSM​

The DSM defines applicability constraints.

It must include:

  • SYSTEM
  • AUDIENCE

Example:
[DSM:SYSTEM=SEMANTIC_BINDING;AUDIENCE=PUBLIC,PROFESSIONAL,AUTHORING_SYSTEMS]

Omitting DSM is a semantic fault.

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.SECTION.PROCEDURE.8-4]
[SSI:TITLE=SECTION_ANCHOR_DECLARATION;AUTHORITY=PRIMARY;REF=8-4]
[SSM:SECTION=PROCEDURE;INTENT=PROCEDURE;ABSTRACTION=LOW]

8.4 - Declare Section Anchors​

Every section must declare all three section anchors before content.

Required Anchors​

Each section must declare:

  • SSB — semantic address
  • SSI — stable section identity
  • SSM — intent and abstraction

Example: '[XXX:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.SECTION.PROCEDURE.XX]' '[XXX:TITLE=SECTION_ANCHOR_DECLARATION;AUTHORITY=PRIMARY;REF=XX]' '[XXX:SECTION=PROCEDURE;INTENT=PROCEDURE;ABSTRACTION=LOW]'

Writing before anchors is invalid.

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.RULE.CONSTRAINT.8-5] [SSI:TITLE=WRITING_TO_THE_ANCHORS;AUTHORITY=PRIMARY;REF=8-6] [SSM:SECTION=RULE;INTENT=CONSTRAINT;ABSTRACTION=HIGH]

8.5 - Write to the Anchors​

Once declared, anchors become binding constraints.

Content must conform to:

  • declared scope (SSB)
  • declared intent (SSM.INTENT)
  • declared abstraction (SSM.ABSTRACTION)

Anchors are not descriptive labels.
They are enforceable rules.

8.5.1 - Scope Discipline (SSB)​

Authors must not:

  • introduce concepts outside the declared category
  • preload future sections
  • expand scope “for completeness”

If new meaning is required:

  • create a new section, or
  • revise anchors before writing

Scope drift is a semantic error.

8.5.2 - Intent Discipline (SSM.INTENT)​

Intent defines how content may behave.

Examples:

  • DEFINITION must not instruct
  • INSTRUCTION must not theorise
  • RATIONALE must not execute

Intent mixing breaks retrieval eligibility.

8.5.3 - Abstraction Discipline (SSM.ABSTRACTION)​

Abstraction controls conceptual altitude.

  • HIGH — principles, definitions
  • MEDIUM — models, reasoning
  • LOW — procedures, actions

Cross-level leakage causes semantic collapse.

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.RETRIEVAL.APPLICATION.8-7] [SSI:TITLE=SEMANTIC_BINDING_IN_RETRIEVAL;AUTHORITY=PRIMARY;REF=8-7] [SSM:SECTION=APPLICATION;INTENT=APPLICATION;ABSTRACTION=MEDIUM]

8.7 — Retrieval and AI Usage​

Semantic Binding changes retrieval by enforcing eligibility before relevance.

Before similarity scoring, systems can check:

  • DSB alignment
  • SSB scope match
  • Intent compatibility
  • Abstraction compatibility
  • DSM applicability

Only eligible content may be retrieved.

This enables:

  • intent-aligned responses
  • abstraction-safe answers
  • explainable selection
  • auditable exclusion

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.CHECKLIST.PROCEDURE.8-8]
[SSI:TITLE=IMPLEMENTATION_CHECKLIST;AUTHORITY=PRIMARY;REF=8-8]
[SSM:SECTION=PROCEDURE;INTENT=PROCEDURE;ABSTRACTION=LOW]

8.8 — Implementation Checklist​

  1. Declare DSB, DSI, DSM before writing
  2. Define all SSBs before prose
  3. Declare SSI and SSM per section
  4. Write strictly within anchors
  5. Split sections when intent or abstraction changes
  6. Reject content that violates anchors

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.SUMMARY.OVERVIEW.8-9] [SSI:TITLE=IMPLEMENTING_SEMANTIC_BINDING_SUMMARY;AUTHORITY=SECONDARY;REF=8-9] [SSM:SECTION=SUMMARY;INTENT=MODEL;ABSTRACTION=HIGH]

8.9 - Summary — Implementing Semantic Binding​

Semantic Binding is implemented through authorial discipline, not tooling.

Anchors must be declared first.
Prose must obey them without exception.

When this discipline is followed:

  • retrieval becomes intentional,
  • agent behaviour becomes predictable,
  • and knowledge scales without semantic decay.

[SSB:THEORY.SEMANTIC_BINDING.IMPLEMENTATION.STATUS.DECLARATION.8-10] [SSI:TITLE=STATUS;AUTHORITY=SECONDARY;REF=8-10] [SSM:SECTION=STATUS;INTENT=STATUS;ABSTRACTION=LOW]

8.10 - Status​

Semantic Binding implementation is normative and enforceable.

The anchors, disciplines, and constraints defined in this document are not optional guidance.
They define the minimum requirements for content to be considered semantically bound.

Content that violates declared anchors is structurally invalid, regardless of writing quality or intent.