Change log
What changed, when, and why. A framework that quietly rewrites itself is not citable.
Scope of this log and how to cite the document#
A document meant to be cited has to be stable enough to cite and honest about when it is not. Substantive changes to the definition, the six stages or the maturity levels are recorded here. Typographic and wording fixes are not.
Clause numbers are generated from document order. A clause number SHALL NOT be treated as a stable reference across versions; a citation SHOULD give the heading text and the version.
Revisions#
- 1.0 · 2026-09-05First publication. Definition, six-stage framework, six-level maturity model, attack-surface enumeration and four boundary documents. Published as a draft for comment: no part of it has been validated against a body of real implementations, and the maturity model's level spacing in particular is asserted rather than measured.
Anticipated revisions#
Stated in advance, so that a revision reads as intended rather than as a quiet correction.
- The maturity model's evidence tests. These are written to be answerable in practice. A test that turns out to be unanswerable, or answerable only by organisations holding a specific tool, is defective and will be replaced.
- The discovery source list. The discover stage ranks VMS exports and switch data above active scanning. That ordering reflects how video estates are usually built. Evidence that it does not hold for a class of deployment not represented here is treated as a defect against the clause.
- Scope of access control and intercoms. Currently in scope, on the argument that they share an owner and a contract with video. This is the boundary decision held with the least confidence.
Correction policy: disagreement is treated as more useful than agreement, and a reported defect is answered in a numbered revision recorded above. [email protected].