After SCORM 1.2, SCORM 2004, and xAPI, one important question remained: how do we combine the flexibility of modern learning experience tracking with the predictable launch, session, and completion behavior expected from LMS-delivered courses?

cmi5 provides that missing structure.

Built on top of xAPI, cmi5 defines the rules that xAPI deliberately leaves open. It specifies how learning content is packaged and launched, how an LMS and an Assignable Unit establish a session, which xAPI statements must be sent, how completion and success are communicated, and how interoperable course behavior can be achieved across different systems.

This series explores cmi5 from a developer and implementation perspective, from course structure, launch parameters, and authorization to sessions, required statements, moveOn criteria, LMS behavior, and real-world interoperability.

The goal is not only to understand how cmi5 works, but also why it exists, where it fits between SCORM and xAPI, and what it takes to implement it correctly.