Canonical Source Standards Register

1. Purpose & Authority

The Canonical Source Standards Register is the authoritative scope of normative reference for the CIAO Standard. It defines which source standards CIAO documents may engage. Amendments to CIAO content may engage only standards in this Register; proposals engaging unregistered standards are escalated as Register Addition Requests under the Change Management & Versioning Process.

The Register is an instrument of foundational governance — Class B in the Constitutional hierarchy declared in Constitution Section 7. Its authority arises from the role it plays: every entry in the Register represents the application of the patented multi-framework mapping methodology to that source standard, producing a normalized cross-mapping against the entire CIAO Standard content. A standard not yet in the Register has not yet been compiled into the CIAO mapping fabric; it cannot serve as a normative reference until that compilation is performed.

Each entry below names a source standard the CIAO Standard cites in its mappings. Each entry carries a short code used in inline references; a family classification used to group standards by tradition; the issuing authority; and the primary CAO content domain into which the standard most closely maps. Where a standard genuinely spans two CAO domains, both are listed.

Members configure their applicable source-standards portfolio at the My Source Standards page (login required). Once configured, the Dynamic Selection Engine filters the Standard’s inline references to the member’s selected portfolio. The Register’s authority over what may be referenced is independent of any individual member’s portfolio configuration; portfolio configuration is presentational, the Register’s authority is normative.

2. The Register

Twenty-six source standards are currently in the Register, organised across seven families. Additions follow the source-standard re-issue trigger pathway in the Change Management & Versioning Process.

3. Family Coverage

4. Maintenance and Expansion

The Register is maintained by the Secretariat under two pathways set out in the Change Management Process.

Re-issue of an existing entry. When a referenced source standard is itself revised by its issuing body, a Secretariat-initiated proposal is automatically created to assess the impact on every CIAO mapping that references the affected standard. Re-issues are handled at the next minor release with full notification to affected members.

Addition of a new entry — Register Addition Request. Proposals to amend CIAO content with reference to a source standard not yet in the Register are reclassified as Register Addition Requests. Addition follows three sequential steps: (a) the patented multi-framework mapping methodology is applied to the candidate standard to produce its normalized cross-mapping with the entire existing CIAO content; (b) the new entry is added to the Register at the next scheduled release event; (c) existing CIAO documents are progressively re-rendered to incorporate the new mappings across one or more subsequent minor releases. The expansion is eventually-consistent: the new standard enters the Register and operational use upon completion of step (b), with content re-rendering proceeding under the established release cadence rather than triggering an immediate major release. No individual submitter has standing to compel an immediate major release through a Register Addition Request.

Both pathways — re-issue and addition — produce entries in the Release Calendar change pipeline as Material changes. Additions are also recorded in the version history of this Register itself, and the affected-document re-rendering work is tracked across minor release events until the new entry’s mapping coverage is complete across the corpus.

Part of the CIAO Standard architecture — see Standard Architecture & Tier Content Depth for the canonical domain spine and tier-by-tier content ladder.