Skip to content

Source and versioning

Source of truth

The Observability Requirements Framework repository is the source of truth for:

  • operational categories;
  • system risk and telemetry priority tiers;
  • the obligation matrix;
  • risk, impact, and mitigation statements;
  • ORF IDs, names, types, tiers, and mathematical definitions; and
  • the ORF-to-ARC control crosswalk and mapping basis.

This playbook explains implementation and operation. If its summary conflicts with the framework source, use the framework source and raise an issue or correction for the playbook.

Baseline used for this playbook

This edition was reviewed against the structured framework definitions at commit 5db12b3, dated 2 July 2026. The later repository commit dated 27 August 2026 adds the updated technical manuscript without changing the structured categories, tiers, matrix, requirements, or crosswalk used by this playbook. The manuscript should still be reviewed for interpretive changes when the playbook baseline is next updated.

Version each system decision

The system profile, requirements register, telemetry design, and evidence register should state:

  • ORF source commit/tag or release;
  • playbook version/commit;
  • system and architecture version;
  • approval date; and
  • next review or update trigger.

Updating this playbook

When ORF changes:

  1. compare categories, risk tiers, matrix, IDs, priority, type, names, definitions, and crosswalk;
  2. identify systems whose obligation or applicability may change;
  3. update reference and implementation guidance without silently changing existing metric meaning;
  4. run link and strict site builds;
  5. record the new framework baseline; and
  6. notify system owners of required reassessment.

External standards evolve. Pin the convention or SDK version used by a production telemetry design and test changes before upgrading.