7-2-1 Interpretation — Normative Definition of Framework Components

This document specifies requirements for 7-2-1 interpretation in professional and quasi-professional written communication.

It applies wherever the 7-2-1 framework is cited.

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 input — artefact or datum required before the process can begin

3.2 decision — point at which the process may proceed along more than one path

3.3 accountable owner — single named party answerable for the process outcome

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 The 7-2-1 framework shall be interpreted as seven inputs, two decisions, and one accountable owner.

5.2 Inputs shall be counted at the granularity at which they are separately obtained.

5.3 A decision that has only one available path shall not be counted as a decision.

5.4 The accountable owner shall be a single role. Joint ownership shall not be recorded.

A document conforms to SQLBL 1010: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 1010:2026, Edition 1." Partial conformance shall be declared by clause number, for example "conforms to SQLBL 1010: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-1010 against which it was run.

Counting inputs at the wrong granularity is the most common source of apparent non-conformance. Assessors should ask who obtains the input rather than what the input contains.

Where a process genuinely has fewer than seven inputs, the description should say so; the framework describes shape, not sufficiency.

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

EXAMPLE 1 — Conforming. Seven inputs are obtained from four systems; the two decisions are scope acceptance and release authorisation; the accountable owner is the release manager.

EXAMPLE 1 — Non-conforming. The process has many inputs and several decision points owned jointly by engineering and operations.

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