1. Purpose & Authority
The Standards Upkeep Process is the single authority for the lifecycle of the source standards the CIAO Standard maps to. It defines how source standards are monitored for change, how new standards are onboarded into the Canonical Source Standards Register, how registered standards are maintained, and how standards are retired when superseded or withdrawn. It is a Class B Foundational instrument: it stands alongside the Register it maintains, beneath the Constitution (Section 7).
Where another CIAO instrument touches the upkeep of source standards — the Register’s maintenance scope, the Change Management & Versioning Process triggers for a source-standard re-issue or a Register addition, the Editorial Submission Framework channel by which members report a standard’s revision — that instrument operates the lifecycle as defined here and refers to this Process as the governing authority. This Process does not restate the change workflow or the submission channels; it defines the lifecycle and references the instruments that execute each step.
2. The Standards Lifecycle
A source standard moves through four phases under this Process: Monitoring (registered standards are watched for revision by their issuing bodies); Sourcing & Onboarding (a candidate standard is acquired, analysed, mapped, and admitted to the Register); Register Management (admitted standards are maintained — admission evidence, version transitions, mapping integrity); and Retirement (a superseded or withdrawn standard is deprecated and its mappings resolved). Each phase hands to the next, engages the Change Management & Versioning Process for any change it produces, and relies on the Document Quality Control instrument for the integrity gates that protect mapping consistency.
3. Version Monitoring
Every entry in the Canonical Source Standards Register is monitored for revision on a quarterly cadence, aligned to the Standard’s three-yearly major-release rhythm. Detection operates through three stacked channels: automated watch, where a source body publishes machine-readable change notices (ISO amendment notices, NIST publication updates, government gazettes); member notification, the dominant channel — members who hold a registered standard report its revision through the Editorial Submission Framework when they encounter it in their own operation; and a Secretariat backstop of periodic manual review against issuing bodies. Confirmed revisions are recorded in a Pending Updates Queue; each queued item becomes a source-standard re-issue trigger in the Change Management & Versioning Process, which assesses the impact on every CIAO mapping that references the affected standard.
4. Sourcing & Onboarding
A standard not yet in the Register is onboarded through a defined pipeline. Acquisition — the standard’s requirements are acquired by member-declared reference: a member who holds an authorised copy supplies the objective intent of the relevant controls through the structured capture defined in the Editorial Submission Framework, without reproducing the standard’s text; where no member channel exists, the Secretariat acquires a licensed copy directly as a secondary path. Analysis & mapping — the candidate standard is decomposed to the clause level and mapped against existing CIAO content using the patented harmonisation method specified in the Mapping & Derivation Methodology; overlapping control objectives are harmonised, unique constraints recorded as their own statements. Admission — the completed cross-mapping is presented for admission to the Register under the evidence rubric in Section 5. Onboarding follows the eventually-consistent expansion model: a newly admitted standard enters the Register at the next scheduled release, and the back-rendering of existing CIAO content proceeds across subsequent minor releases rather than forcing an immediate major release.
5. Register Management
Registered standards are maintained under three disciplines. Admission evidence rubric — a standard is admitted only on evidence that its issuing authority and current edition are identified, its requirements have been mapped to CIAO content by clause reference, and its mappings have passed the Document Quality Control integrity gates; admission is recorded as a Material change in the Release Calendar pipeline. Version transitions — when a registered standard is revised, the new edition is admitted as a discrete transition that fires the cross-reference integrity gate across every mapping referencing the superseded edition; affected mappings are re-verified and, where the successor edition has materially shifted, re-harmonised. Mapping integrity — every mapping is clause-reference only; the Register records which standards CIAO maps to, never their text.
6. Retirement & Deprecation
When a registered standard is withdrawn by its issuing body or superseded without a continuing successor, it is retired through a deprecation pathway, and its existing mappings are resolved one of three ways. Reattribute — where a successor or equivalent registered standard carries the same control objective, the mapping is reattributed to it. Archive — where no successor exists, the mapping is archived with its version history preserved, and the affected CIAO statements are reviewed for any coverage gap the retirement creates. Orphan review — where a retirement leaves a control objective unsupported, the gap is routed into the change process for editorial resolution. Retirement is a Material change; affected members are notified through the Release Calendar and by direct notification where the retired standard sits in their selected portfolio.
7. Roles & Watch Portfolios
Monitoring responsibility is distributed as Standards Watch portfolios: each governance domain of the Standard carries a watch portfolio for the source standards mapped into it, held by the Panel Advisor whose declared domain covers it. The Secretariat coordinates the monitoring cadence, maintains the Pending Updates Queue, and routes confirmed revisions into the change process. Portfolio assignments activate as Panel Advisor seats are confirmed; until a domain’s seat is filled, the Secretariat holds that watch portfolio directly.
8. Relationship to Other Instruments
This Process defines the standards lifecycle and composes with the instruments that execute it; it does not duplicate them. The Canonical Source Standards Register is the population this Process maintains. The Change Management & Versioning Process executes every change this Process produces — re-issues, additions, version transitions, and retirements enter its workflow as triggers. The Editorial Submission Framework is the channel through which members report revisions and supply control intent for onboarding. The Document Quality Control instrument provides the integrity gates that protect mapping consistency at every transition. The Mapping & Derivation Methodology specifies how candidate standards are decomposed and harmonised.
Part of the CIAO Standard administrative instruments — see Standard Administration for the canonical index of operational policies and processes.
Part of the CIAO Standard architecture — see Standard Architecture & Tier Content Depth for the canonical domain spine and tier-by-tier content ladder.