Integration Mappings

Intent

Map external interoperability standards to the internal core model, lifecycle transitions, and event contracts.

Use this section with:

• Core Model
• Entity Lifecycle
• Sync Topology
• Project Standards

Critical Technology Mappings (Initial Version)

1. LTI Advantage Mapping
2. xAPI and cmi5 Event Model
3. LRS and CLR Record Mapping
4. Roster and Grade Exchange

Mapping Policy

• Internal model remains source of truth for platform semantics
• Standards mappings must preserve person-centric history continuity
• Standards mappings must preserve full attempt-level and feedback-level learner portability by default
• Mapping docs must explicitly define lossless, lossy, and deferred fields
• Any mapping change that affects learner portability requires architecture review
• xAPI and LRS-facing implementation slices must map to executable upstream conformance coverage early; do not defer the ADL suite to endgame QA.

Status Legend

• planned: target documented, implementation not started
• in-progress: partially implemented and validated
• validated: tested against conformance or contract tests

For xAPI and LRS resources, validated specifically means the relevant upstream ADL LRS Conformance Test Suite batteries are green, not just local contract coverage.

Current Status

Mapping	Status
LTI Advantage	planned
xAPI/cmi5	in-progress
LRS/CLR	in-progress
Roster and grade exchange	planned

xAPI/cmi5 and LRS/CLR moved to in-progress once concrete mapping rules and implementation scaffolding began landing in the monorepo. They should not move to validated until the public LRS surface is green against the upstream ADL suite in a disposable non-production environment.