From SCORM Runtime to xAPI Statements: The Mental Model Shift
xAPI is not SCORM with JSON. The real shift is from browser-owned runtime state to event records sent to an LRS, which changes launch, identity, debugging, and reporting.
Discover more
Responses API, Agents SDK, and the Modern Agent Stack
Most teams think they are choosing a framework. In practice, they are choosing what they will be able to see, control, and recover when an agent fails. This article explains the execution layer, orchestration layer, state tradeoffs, and the real architectural decisions behind a modern agent stack.
Breaking Temporal Coupling: Design Beyond Sequence
Systems become fragile when correctness depends on invisible timing assumptions.
Is SCORM 2004 Still Relevant in 2026?
SCORM 2004 is not the future of e-learning standards, but it is still part of the present. If you work with enterprise LMS platforms, legacy content, or structured learning paths, SCORM 2004 remains highly relevant. Not because it is modern, but because it is still deeply embedded in the ecosystem.
How to Build a Useful Eval Set for a Tool-Using Agent
Learn how to design an eval set for a tool-using agent using trace-level evaluation, dataset splits, layered scoring, and realistic failure cases that catch regressions before production.
Configuration: Separate Policy from Mechanism
If changing a setting requires changing code, your system is tighter than it needs to be.
Debugging SCORM 2004 Like a Developer
SCORM 2004 does not fail silently. It tells you exactly what went wrong. If you are not reading error codes, validating API calls, and tracing lifecycle state, you are not debugging. You are guessing.
Agent Evaluation and Tracing: Why Prompting Is Not Enough
Prompting can improve a single run, but it cannot prove that an agent workflow is reliable. This article explains how traces, scorecards, offline evals, and online monitoring turn agent quality into an engineering discipline.
Inheritance Tax: The Cost of Rigid Hierarchies
Inheritance feels elegant at first, but deep hierarchies often charge interest later.
Migrating from SCORM 1.2 to SCORM 2004
Migrating from SCORM 1.2 to SCORM 2004 is not a version upgrade. It is a behavioral redesign. If your migration strategy only updates API calls and manifest versioning, you are not migrating. You are creating hidden inconsistencies.