Skip to main content

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


Page 6 — How to Write Semantically Bound Content


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.PURPOSE.OVERVIEW.6-1] [SSI:TITLE=HOW_TO_AUTHOR_SEMANTICALLY_BOUND_CONTENT;AUTHORITY=SECONDARY;REF=6-1] [SSM:SECTION=CONCEPT;INTENT=DEFINITION;ABSTRACTION=HIGH]

6.1 Purpose & Positioning

This document defines how authors apply Semantic Binding in practice.

It translates the taxonomy, anchors, abstraction model, and enforcement rules into repeatable authoring patterns that produce stable, retrievable, and explainable knowledge.

This document focuses on how to write semantically bound content.
It does not define validation tooling, ingestion pipelines, or retrieval algorithms.


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.MINDSET.PRINCIPLE.6-2] [SSI:TITLE=AUTHORING_AS_DECLARATION;AUTHORITY=PRIMARY;REF=6-2] [SSM:SECTION=PRINCIPLE;INTENT=PURPOSE;ABSTRACTION=HIGH]

6.2 Authoring Mindset – Writing as Declaration, Not Description

Semantic Binding changes the role of the author.

Authors do not merely describe content.
They declare meaning, intent, and scope explicitly.

Before writing prose, the author must decide:

  • What is this about?
  • What role does this section play?
  • At what abstraction level should it be consumed?

Prose follows structure — never the reverse.


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.DOCUMENT_PATTERN.GUIDE.6-3] [SSI:TITLE=DOCUMENT_LEVEL_AUTHORING_PATTERN;AUTHORITY=PRIMARY;REF=6-3] [SSM:SECTION=PROCESS;INTENT=MODEL;ABSTRACTION=MEDIUM]

6.3 Document Authoring Pattern

Every document begins by declaring:

  • DSB — domain and primary object
  • DSI — document identity and version
  • DSM — system and audience context

These anchors must be written before any content.

If the DSB cannot be stated clearly, the document is not ready to be written.


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.SECTION_PATTERN.GUIDE.6-4] [SSI:TITLE=SECTION_LEVEL_AUTHORING_PATTERN;AUTHORITY=PRIMARY;REF=6-4] [SSM:SECTION=PROCESS;INTENT=MODEL;ABSTRACTION=MEDIUM]

6.4 Section Authoring Pattern

Each section must declare, in order:

  1. SSB — semantic address
  2. SSI — canonical title and reference
  3. SSM — role, intent, abstraction

Only after these are declared should headings and prose be written.

This ensures:

  • sections are independently retrievable
  • meaning is explicit
  • intent is machine-visible

[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.PROSE.CONSTRAINT.6-5] [SSI:TITLE=WRITING_PROSE_WITHIN_BOUNDARIES;AUTHORITY=PRIMARY;REF=6-5] [SSM:SECTION=CONSTRAINT;INTENT=CONSTRAINT;ABSTRACTION=MEDIUM]

6.5 Writing Prose Within a Section

Once anchors are declared, prose must honour them.

Authors must not:

  • introduce new concepts outside the SSB
  • mix abstraction levels
  • change intent mid-section

If content no longer fits:

  • split the section, or
  • create a new section with its own anchors

Semantic Binding favours clarity over compression.


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.ABSTRACTION.CONSTRAINT.6-6] [SSI:TITLE=HONOURING_ABSTRACTION_LEVELS;AUTHORITY=PRIMARY;REF=6-6] [SSM:SECTION=CONSTRAINT;INTENT=CONSTRAINT;ABSTRACTION=MEDIUM]

6.6 Abstraction Discipline in Authoring

Each section declares one abstraction level.

Authors must not:

  • embed step-by-step instructions in HIGH abstraction sections
  • introduce governing principles in LOW abstraction sections

If content spans levels, it must be split into separate sections.

This discipline is essential for intent-aligned retrieval.


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.REUSE.RATIONALE.6-7] [SSI:TITLE=REUSE_WITHOUT_DUPLICATION;AUTHORITY=PRIMARY;REF=6-7] [SSM:SECTION=RATIONALE;INTENT=RATIONALE;ABSTRACTION=MEDIUM]

6.7 Reuse and Cross-Referencing

Semantic Binding encourages reference over repetition.

Authors should:

  • reference existing semantic units by SSB / SSI
  • avoid copying definitions or rules verbatim
  • treat documents as composable knowledge assets

This prevents divergence and keeps meaning centralised.


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.ANTI_PATTERNS.ANALYSIS.6-8] [SSI:TITLE=WHAT_AUTHORS_MUST_AVOID;AUTHORITY=PRIMARY;REF=6-8] [SSM:SECTION=COMPARISON;INTENT=COMPARISON;ABSTRACTION=MEDIUM]

6.8 Common Authoring Anti-Patterns

Common mistakes include:

  • writing prose before declaring anchors
  • overloading a section with multiple intents
  • drifting abstraction levels
  • inventing new taxonomy values ad hoc

These failures reduce retrieval quality and undermine explainability.


[SSB:THEORY.SEMANTIC_BINDING.AUTHORING.SUMMARY.GUIDE.6-9] [SSI:TITLE=WRITING_SUMMARY_SECTIONS;AUTHORITY=PRIMARY;REF=6-9] [SSM:SECTION=PROCESS;INTENT=MODEL;ABSTRACTION=HIGH]

6.9 The Role of Summary Sections in Semantic Binding

Summary sections serve orientation and navigation, not authority.

They exist to:

  • establish shared context
  • explain document structure
  • direct readers and systems to authoritative sections

They are entry points, not sources of truth.

(Sections 6.9.1–6.9.7 intentionally inherit this SSB.)


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

Status

Semantic Binding succeeds only when authors apply it consistently.