ADRs

• QTI 3 ASI as the canonical assessment model
• Headless QTI runtime core (MIT) + Mantine skin
• Hybrid scoring locus, item bank, and immutable item versions
• WYSIWYG item authoring on TipTap/ProseMirror
• Unified learning + research: one construct, three axes, one selection policy
• Delivery Profile: unified scoring/selection loci and offline regime
• Session and telemetry model
• Consent and research governance
• Imported-standard boundary: ingest QTI and Common Cartridge, keep H5P/SCORM/cmi5 opaque
• Converge native assessment authoring onto QTI
• Teacher-portal data layer: router loaders now, pgxsinkit later — never react-query or TanStack DB
• OneRoster 1.2 is an interchange projection, not the roster core
• Person-rooted identity: every external identifier is a binding
• Erasure is anonymization: the GDPR data-lifecycle model
• Per-organization issuer profiles with platform-custodial keys
• Credential proof format: VC-JOSE (JWT) with Ed25519, Data Integrity later
• Issuer key custody: Supabase Vault with a KeySigner seam, transit KMS reserved
• CASE 1.1 is a boundary adapter; competency nodes become durable referents
• Server-anchored delivery: authoritative grading on an offline-first substrate
• Rich QTI assessmentTest authoring: bring authoring up to the delivery engine
• QTI 3.0: demonstrable conformance and full platform coverage
• Common Cartridge 1.4 import: decompose into native structures + a QTI 1.2→3 bridge
• QTI authoring asset pipeline: media for the graphic/media interaction kinds
• QTI graphic-interaction authoring: the coordinate/shape editor
• QTI 3.0 residual coverage: generic PCI host, XInclude, rich results, CAT
• In-app EPUB/PDF reading: opaque External-Package delivery + a generic Reading State overlay
• Assignments are human-scored Assessments — no separate submission domain
• Conformance tracking: cited-evidence overlay, CI gate, and generated readiness render
• Discussion is a native capability on the sync rail — not a vendored forum
• Notifications and messaging system
• Unified TypeScript release, versioning, and tooling standard (emergent / conform-ed / pgxsinkit)
• The “English Planet” Captivate/OLX corpus lands as cmi5 AUs on the External Package runtime — not repackaged, not fanned-out
• emergent is a content & LTI provider, not consumer-only — and the conformance board must track the provider roles it already plays
• Offering duplication is a forking copy of the authored aggregate; provisioning is a tracking copy — one deep-copy engine, two semantics
• A canonical entity image is a resolved URL — uploaded, else external, else a generated title-card — served from one polymorphic endpoint
• The issuer Profile’s descriptive fields are authored into issuer_profile.profileMeta, derived where the data already exists, and emitted into every OB/CLR Profile node
• Basic computer-adaptive testing: in-process Rasch engine behind the CAT 1.0 seam
• Capability B: emergent as credential holder and Badge Connect host
• QTI 3.0.1 authored-content ARIA accessibility, and honest disposition of the QTI model-coverage gaps
• emergent as an LTI 1.3 Platform
• Caliper as a second analytics rail via a shared telemetry projection seam
• Pseudonymous-by-default governance for external telemetry emission
• LTI Proctoring Assessment Control Service (both roles)
• Grade-category weighting (computed final grade)
• Media playback as a Caliper-native product feature
• Surveys & questionnaires as a Caliper-native product feature
• Europass / ELM European Digital Credential consumption — verify, hold, display (issuance deferred)
• Caliper aggregate measures + membership status (closing CAL-VOCAB-2)
• Caliper emission worker host — a long-lived Bun loop, not a cron
• Surface-layout engine and Surface Experiences
• Two documentation sites: end-user docs and engineering docs
• Fine-grained knowledge items as first-class competency referents
• Offline-first boot contract and demolition of the provider snapshot layer
• Helm chart type-level defaults with per-entry overrides