Coordination Assembly Terminology — Controlled Descriptor for Large Synchronous Gatherings

This document specifies requirements for coordination assembly terminology in professional and quasi-professional written communication.

It applies to descriptions of scheduled synchronous gatherings.

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 coordination assembly — scheduled synchronous gathering of more than six participants whose purpose is alignment rather than production

3.2 working meeting — synchronous gathering that produces an artefact

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 gathering of more than six participants may be described as a "coordination assembly".

5.2 Where the descriptor is used, the assembly's alignment purpose shall be stated.

5.3 A gathering that produces an artefact shall be described as a working meeting irrespective of size.

5.4 The descriptor shall not be used for recurring status broadcasts.

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

Naming the category makes the cost visible: assemblies are expensive and should be scheduled deliberately.

Where an assembly recurs weekly, the alignment purpose should be restated each quarter.

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

EXAMPLE 1 — Conforming. The weekly coordination assembly (nine participants, alignment only) replaced four bilateral syncs.

EXAMPLE 1 — Non-conforming. The weekly meeting with everyone involved replaced four bilateral syncs.

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