Evidence

Platform proof

Dated, public evidence for Allure Connect: live status, hosted Storyline launches, session progress mapping, and the xAPI LRS self-test.

Newest item August 27, 2026

What this page is

This page lists dated platform evidence. It does not name customers or publish workspace-specific package ids, session ids, launch URLs, or webhook receivers. Each item says what was tested, where, when, and what it does not show.

Live system status

Evidence date: Continuous
What was tested: Operational status and uptime samples for the API, dashboard and data backend, sampled every five minutes.
Environment: Production, self-reported by the service’s own sampler.
Does not show: A contractual SLA, service credits or third-party monitoring.
Sources: Open status

Hosted Storyline launches

Evidence date: August 27, 2026
What was tested: Storyline packages whose SCORM entry is launcher.html load sibling index_lms.html when it is present, so a blocked pop-up cannot stop the course starting.
Environment: Hosted player and content proxy, release 2026.8.2.
Does not show: Workspace-specific package, session or launch URLs.
Sources: Changelog 2026.8.2 Dated JSON

Session progress_measure mapping

Evidence date: August 27, 2026
What was tested: Incomplete sessions map SCORM 2004 cmi.progress_measure onto progress_percent (0–99); GET and PUT /api/v1/sessions/{sessionId} return progress as an alias; completed, passed and failed read as 100.
Environment: Sessions API, release 2026.8.2.
Does not show: Incomplete-session progress webhooks (session webhooks remain terminal-only).
Sources: Session docs Dated JSON

xAPI 2.0 conformance: 1,435 of 1,435 checks in a local test run

Evidence date: June 6, 2026
What was tested: The ADL xAPI 2.0 conformance suite (commit 5bc232d) against the LRS implementation: 1,435 checks passed, zero failures.
Environment: A local build with an in-memory test configuration.
Does not show: Third-party certification, or a rerun against the hosted production service (an isolated rerun is pending).
Sources: Conformance results Dated JSON

Release notes (2026.8.2)

Changed · 2026-08-27
Hosted Storyline packages whose SCORM entry is launcher.html now load sibling index_lms.html when that file is present. GET /api/v1/content/{…path} serves the SCO when a hosted request still names launcher.html, and falls back to launcher.html if the sibling is missing, so a blocked window.open no longer prevents the course from starting.
Changed · 2026-08-27
Incomplete session progress now maps SCORM 2004 cmi.progress_measure onto progress_percent (0–99 while incomplete). GET and PUT /api/v1/sessions/{sessionId} return the documented progress alias alongside progress_percent.

Not claimed here

IEEE or ADL SCORM certification
Incomplete-session progress webhooks (session webhooks remain terminal-only)
Current-release Convex-backed qualification (isolated rerun pending)
Workspace-specific package, session, or launch URLs
A SOC 2 attestation (not published)
Customer names or logos (none published without permission)
A public uptime SLA

How we add evidence

An item qualifies when it can be inspected: a dated JSON artifact, a changelog entry or a live endpoint, with the environment it ran in. Items are dated when the evidence was produced, never when the page was edited, and they are not re-dated automatically.

Evidence expires when the thing it describes changes: a new release that touches the tested path means the item is re-run or marked as superseded. Workspace-specific launch URLs stay in private tickets and API responses; retests use the tokenized launch_url from POST /api/v1/packages/{id}/launch.