What it is
The Adoption Register is where formal ALiF adoption events are logged. The core team maintains it, and it is cross-referenced in the Architecture Document. It is defined in the Versioning and Review Policy and the Architecture Document.
What each entry records
- the adopting organization or jurisdiction;
- the date of formal adoption;
- the version of the ALiF Standard adopted against;
- the scope of adoption: which layers, components and stakeholder roles;
- any conditions or adaptations;
- the designated liaison for the organization, or the ALiF Hub that supports it;
- from ALiF 2.0, for organizational implementations, the date of the current Learning Conditions Statement.
Why it matters
The register provides a way to check whether an organization’s claim about ALiF has been recorded, and against which version. It also gives later adopters evidence of who has gone before them.
It has a governance role too. The number of jurisdictions in the register decides when governance of ALiF moves beyond the core team: when two or more jurisdictions have formally adopted the Standard, a Governance Advisory Council must be set up. Requests from two or more adopting organizations or jurisdictions can also trigger a major review of the Standard.
Current state
No conformance claim has been registered. Organizations that adopt ALiF record their commitment in an Adoption Charter; a conformance claim comes later, after the program has delivered and the evidence required by the conformance requirements exists.
Transition to ALiF 2.0
Entries record the Standard version they refer to, so claims made against version 1 remain readable after ALiF 2.0 is released. The proposed transition period and the timing of the new requirements are described on the conformance and ALiF 2.0 pages.