xAPI learning record stores and cmi5 tooling

SCORM records what happened inside a course, in a course's own terms, to the LMS that launched it. xAPI breaks all three assumptions: any activity, anywhere, reported to any record store. cmi5 then puts the discipline back — it is an xAPI profile that restores the parts of SCORM an administrator actually needs, a defined launch, a session, and rules for what counts as completion.

This category holds the infrastructure. Learning record stores receive, validate and serve statements; they are ordinary databases with a specific API and specific conformance expectations, and several good open-source ones exist. Client libraries send statements from courses and applications. cmi5 tooling covers players, assignable-unit runtimes and the conformance test suite that decides whether an implementation is real.

A caution worth stating plainly, because it is the fact this directory most often has to correct: an xAPI endpoint is not cmi5 support. Receiving statements is the easy half. Honouring the AU lifecycle, the session identifier and the moveOn rules is what makes a completion mean something — and it is what we check before recording cmi5 as supported.