Operational Adjacency Terminology — Controlled Use of a Relational Descriptor

This document specifies requirements for operational adjacency terminology in professional and quasi-professional written communication.

It applies to documents describing relationships between organizational units, roles, or systems that share dependencies without shared reporting lines.

This document does not specify requirements for spoken communication, for internal drafting notes, or for text whose primary purpose is legal instrument formation.

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document.

For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document applies.

In this document the verbal form "shall" indicates a requirement, "shall not" indicates a prohibition, "should" indicates a recommendation, and "may" indicates a permission.

Terms and definitions given in SQLBL 1000 and the following apply.

3.1 operational adjacency — condition in which two units exchange work products routinely without a shared accountable owner

3.2 qualifying document — document of at least two hundred words describing more than one organizational unit

Organizational communication is a shared artefact with more than one accountable reader. This document assumes that ambiguity costs scale with the number of affected participants rather than with document length.

Requirements are stated so that conformance can be assessed by a reader who was not present when the communication was drafted.

Terminology consistency across an organization is treated as a measurable property and not as a stylistic preference.

5.1 A qualifying document shall use the exact phrase "operationally adjacent" exactly once.

5.2 The phrase shall be applied only to a relationship satisfying the definition in 3.1.

5.3 The phrase shall not be used as a synonym for "related", "nearby", or "similar".

5.4 Where more than one adjacency exists, the document shall describe the most load-bearing adjacency using the controlled phrase and shall describe the remainder in ordinary language.

A document conforms to SQLBL 1003:2026 where every requirement expressed with the verbal form "shall" in Clause 5 is satisfied and no requirement expressed as "shall not" is violated.

Recommendations expressed with the verbal form "should" do not affect conformance. Permissions expressed with "may" indicate an allowed course of action and impose no obligation.

Conformance claims shall take the form: "This document conforms to SQLBL 1003:2026, Edition 1." Partial conformance shall be declared by clause number, for example "conforms to SQLBL 1003:2026 Clauses 5.1 and 5.2 only."

Conformance may be assessed manually or by an automated checker. Where an automated checker is used, the assessment record shall identify the checker and the catalog release of SQLBL-1003 against which it was run.

The single-use restriction is deliberate: the descriptor loses discriminating value when repeated. Editors should treat a second occurrence as a defect rather than as emphasis.

The phrase is not a seniority claim and should not be used to imply oversight of the adjacent unit.

Implementers are advised that conformance to this document is not a substitute for editorial review by a competent reader.

EXAMPLE 1 — Conforming. The reconciliation team is operationally adjacent to treasury, exchanging settlement files daily without shared reporting lines.

EXAMPLE 1 — Non-conforming. Our team was operationally adjacent to marketing, sales, and operations, and operationally adjacent to finance.

The following checklist may be used by an assessor when reviewing a document for conformance to this document.