Conformance status
Generated by bun run conformance:render — do not edit by hand.
Point-by-point implementation status for every targeted specification, against the literal published schema (conform-ed ADR-0013) with emergent’s product overlay (ADR-0028). Supersedes the prose status tags in ../architecture/standards.md.
| Spec | Profiles | Requirements done | Model coverage |
|---|---|---|---|
| CALIPER 1.2 | endpoint, entity, envelope, event, identifier, sender, serialization, vocabulary | 23/24 | 1693/2052 |
| CASE 1.1 | consumer, core, provider | 9/9 | 264/344 |
| CAT 1.0 | delivery, operations, section | 6/8 | 63/83 |
| CC 1.3 | authorization, curriculum-standards-metadata, discussion-topic, lti-link, manifest, web-link | 12/12 | 413/676 |
| CC 1.4 | assignment, authorization, curriculum-standards-metadata, discussion-topic, manifest, web-link | 13/13 | 84/143 |
| CLR 2.0 | displayer, host, issuer | 14/14 | 299/409 |
| CMI5 1.0 | course-structure | 6/6 | 30/45 |
| ELM 3.3 | 0/0 | 527/529 | |
| H5P 1 | library, package, semantics | 3/7 | 105/140 |
| LTI 1.3 | ags, core, deep-linking, nrps, platform-ags, platform-core, platform-deep-linking, platform-dynamic-registration, platform-nrps, platform-proctoring, platform-security, proctoring, security | 54/56 | 189/270 (+13 transport) |
| OB 3.0 | displayer, host, issuer | 16/16 | 241/340 |
| OR 1.2 | assessment-results, gradebook, resources, rostering, transport | 21/21 | 248/410 (+88 transport) |
| QTI 2.1 | item, outcome-declaration, response-declaration, response-processing, results, section, test | 0/11 | 186/4971 |
| QTI 2.2 | item, outcome-declaration, response-declaration, response-processing, results, section, test | 0/11 | 208/5378 |
| QTI 3.0.1 | accessibility, item, outcome-declaration, response-declaration, response-processing, section, test | 11/11 | 582/5344 |
| VC 2.0 | credential, presentation | 3/5 | 53/68 |
| XAPI 1.0.3 | attachment, context, statement | 11/11 | 84/111 |
| XAPI 2.0 | attachment, context, statement | 11/11 | 92/125 |
Outstanding work
Section titled “Outstanding work”The cross-spec planning backlog this board tracks: 3 requirement(s) not yet done (2 partial, 1 todo). partial is closest to done; deferred needs a product capability that does not exist yet. Same-profile rows from different specs sit together, so a single capability that unblocks several is easy to spot. Drill into a spec page for the full requirement and evidence.
| Status | Spec | Requirement | Blocked on / note |
|---|---|---|---|
| 🟡 partial | CAT 1.0 | operations/CAT-OP-1 | The create-section operation runs in-process — a SectionData assembled from a CAT Pool is accepted by the engine and yields the first stage — but the standardized CAT 1.0 REST binding (POST /sections, GET /sections/:id) is deferred to the future REST-adapter swap (ADR-0037 §1/§9). |
| 🟡 partial | CAT 1.0 | operations/CAT-OP-2 | The adaptive cycle (submit AssessmentResult → receive CatEngineResultReport with the next stage, then end) runs in-process and is additionally exposed over emergent’s own server-anchored routes (POST /workflow/cat-sessions + …/items/:id/responses); the standardized CAT 1.0 REST session binding (POST /sessions, POST /sessions/:id/results, the end operations) is deferred (ADR-0037 §1/§9). |
| 🔲 todo | CALIPER 1.2 | sender/CAL-SND-1 | Real TLS is a deployment property — the Sensor transmits over an https endpoint URL and the runtime negotiates the secure connection — not something the in-process interop lane exercises. The transmission TLS secures (single Envelope POST, headers, version negotiation) IS proven (CAL-SND-2..6), and the config-time guard (assertEndpointTransportSecure) already refuses a non-internal endpoint that is not https, so plaintext export can never reach the wire. Flips to done under a deployed-endpoint smoke check (pending the worker-host decision). |