Skip to main content

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

Page 3.1 — DSB — Document Semantic Binding​

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.PURPOSE.DEFINITION.3-1-1] [SSI:TITLE=WHAT_IS_DSB;AUTHORITY=PRIMARY;REF=3-1-1] [SSM:SECTION=DEFINITION;INTENT=DEFINITION;ABSTRACTION=HIGH]

3.1.1 — What DSB Is​

Document Semantic Binding (DSB) declares the semantic identity of a document as a whole.

It answers one—and only one—question:

“What is this document fundamentally about?”

DSB defines the semantic territory within which all sections of the document must operate.

It is the root anchor for meaning.
Every section-level semantic binding must align with it.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.FORM.CONSTRAINT.3-1-2] [SSI:TITLE=DSB_FORM_AND_SYNTAX;AUTHORITY=PRIMARY;REF=3-1-2] [SSM:SECTION=DEFINITION;INTENT=CONSTRAINT;ABSTRACTION=MEDIUM]

3.1.2 — DSB Form and Structure​

DSB is always expressed as:

DOMAIN.OBJECT

Where:

  • DOMAIN defines the conceptual universe of knowledge
  • OBJECT defines the single primary concept the document concerns

Example

THEORY.SEMANTIC_BINDING

DSB must not encode:

  • intent
  • abstraction
  • taxonomy depth
  • section-level meaning

Those belong elsewhere.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.DESIGN.RATIONALE.3-1-3] [SSI:TITLE=WHY_DSB_HAS_ONLY_TWO_SEGMENTS;AUTHORITY=PRIMARY;REF=3-1-3] [SSM:SECTION=CONCEPT;INTENT=RATIONALE;ABSTRACTION=HIGH]

3.1.3 — Why DSB Has Only Two Segments​

DSB is intentionally limited to two segments.

This is a hard design constraint, not a simplification.

A document is not a single semantic idea.
It is a container of many semantic units.

Within a single document, it is valid—and expected—to contain:

  • definitions
  • rationale
  • models
  • rules
  • processes
  • governance statements
  • status declarations

If DSB attempted to encode which aspect of the object the document covers, it would become false for large parts of the document it governs.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.STABILITY.MODEL.3-1-4] [SSI:TITLE=STABILITY_OVER_PRECISION;AUTHORITY=PRIMARY;REF=3-1-4] [SSM:SECTION=CONCEPT;INTENT=MODEL;ABSTRACTION=HIGH]

3.1.4 — Stability Over Precision​

DSB is optimised for stability, not precision.

It must remain true even as:

  • content evolves
  • sections are added or reordered
  • explanations expand
  • examples change

A more granular DSB would fracture under normal document evolution.

Semantic precision belongs at the section level.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.RELATIONSHIP.MODEL.3-1-5] [SSI:TITLE=DSB_AND_SECTION_BINDINGS;AUTHORITY=PRIMARY;REF=3-1-5] [SSM:SECTION=CONCEPT;INTENT=MODEL;ABSTRACTION=HIGH]

3.1.5 — Relationship Between DSB and Section-Level Anchors​

The relationship is intentional and asymmetric:

  • DSB defines the semantic territory
  • SSB defines semantic coordinates within that territory

DSB sets the boundary.
Section-level anchors do the work.

No section may violate the document’s DSB.
A section that does is semantically invalid, regardless of prose quality.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.SYSTEM_ROLE.APPLICATION.3-1-6] [SSI:TITLE=SYSTEM_ROLE_OF_DSB;AUTHORITY=PRIMARY;REF=3-1-6] [SSM:SECTION=CONCEPT;INTENT=APPLICATION;ABSTRACTION=HIGH]

3.1.6 — Structural Role of DSB in the System​

Because DSB is shallow and stable, it can be relied upon by:

  • ingestion pipelines
  • vector namespaces
  • routing and scoping logic
  • access control
  • audit and governance systems

DSB allows systems to reason about what a document is, independently of how it is structured internally.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.RULES.CONSTRAINT.3-1-7] [SSI:TITLE=CANONICAL_DSB_RULES;AUTHORITY=PRIMARY;REF=3-1-7] [SSM:SECTION=DEFINITION;INTENT=CONSTRAINT;ABSTRACTION=MEDIUM]

3.1.7 — Canonical Rules for DSB​

  • Exactly one DSB per document
  • Always expressed as DOMAIN.OBJECT
  • Must appear before any section-level anchors
  • All SSBs must align with it
  • Must never encode intent, abstraction, or taxonomy depth
  • Must remain valid for the entire lifecycle of the document

Violating these rules breaks the document’s semantic contract.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.SUMMARY.SUMMARY.3-1-8] [SSI:TITLE=DSB_SUMMARY;AUTHORITY=SECONDARY;REF=3-1-8] [SSM:SECTION=SUMMARY;INTENT=STATUS;ABSTRACTION=LOW]

3.1.8 — Summary​

DSB exists to declare what a document is about, not how meaning is structured inside it.

By keeping DSB:

  • shallow
  • stable
  • and strictly constrained

Semantic Binding allows documents to evolve internally without breaking their semantic identity.

This separation between document identity and section meaning is foundational.

[SSB:THEORY.SEMANTIC_BINDING.DOCUMENT_SECTION_BINDING.STATUS.STATUS.3-1-9] [SSI:TITLE=STATUS;AUTHORITY=SECONDARY;REF=3-1-9] [SSM:SECTION=STATUS;INTENT=STATUS;ABSTRACTION=LOW]

3.1.9 — Status​

Document Semantic Binding (DSB) is active and authoritative.

Its structure and rules are stable and form a non-negotiable foundation for all Semantic Binding documents.

No section-level semantic binding, retrieval logic, or agent behaviour is valid without a correctly declared DSB.