In cmi5, package structure is part of the runtime contract. This article explains how cmi5.xml shapes LMS import, course graphs, AU launch behavior, and completion semantics before any content code runs.
cmi5 is not just xAPI packaging. It is an xAPI profile that adds rules for LMS launch, registration, session handling, allowed statements, and completion behavior so content and platforms can interoperate predictably.
xAPI solved learning event transport, but it did not define a shared LMS launch contract. This article explains why cmi5 exists, what constraints it adds, and why those constraints matter for real interoperability.
xAPI is powerful when you need flexible learning telemetry across systems, but it becomes a costly choice when the real requirement is only launch, completion, score, and bookmarking. This article explains the architectural boundary and why cmi5 matters when LMS-launched interoperability enters the picture.