Listen to Your Lizard Brain: Trust Your Instincts, Verify with Evidence
Your intuition is years of experience speaking quietly, but it still needs evidence before it becomes knowledge.
Discover more
Verbs, Activities, and IDs: The Naming Decisions That Break Analytics
Most xAPI analytics failures begin before the LRS, when teams choose verbs and activity IDs without a reporting plan. This article explains why IDs, not labels, drive aggregation and how to prevent silent reporting drift.
AI Agent Memory: Why State and Memory Are Not the Same Thing
State keeps an agent moving through the current thread. Memory persists selective information for future runs. External knowledge stays in source systems and should be retrieved on demand. This distinction matters because AI agent memory is a systems design problem, not a prompt trick.
Blackboards: Collaborate Through Shared Knowledge
The most adaptable systems are often built through collaboration, not strict sequencing.
Anatomy of an xAPI Statement with Developer Examples
An LMS manages assignment, launch, and completion rules. An LRS manages the learning record contract. Here is why that split matters in real xAPI systems.
From Prompting to Agent Engineering
Prompting matters, but it is only one control layer. Reliable agents come from designing the loop, validating tool use, tracing decisions, and treating runtime behavior as the real unit of quality.
Actors and Processes: Build with Independent Components
The easiest systems to scale are often the ones whose components know the least about each other.
What an LRS Does and Why an LMS Is Not Enough
An LMS manages assignment, launch, and completion rules. An LRS manages the learning record contract. Here is why that split matters in real xAPI systems.
Production Failure Modes in AI Agents and How to Anticipate Them
AI agents usually do not fail with a dramatic crash. They fail quietly through wrong tool calls, invalid arguments, retry storms, looping behavior, and weak recovery. This article explains where the agent loop breaks and how to design traces, guardrails, limits, checkpointing, idempotency, and evals that catch incidents before users do.
Shared State Is Incorrect State: Reduce Hidden Dependencies
The most difficult bugs often come from code that changes data you did not realize it could touch.