If your cmi5 package launches but reporting still looks wrong, the problem is often scope confusion. This article explains how Assignable Units, registration, and session lifecycle work together, and why separating them is essential for correct launch behavior, resume logic, completion, and analytics.
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.