Beacon
A wire-first learning telemetry demo. Beacon doesn’t hand you a
dashboard’s summary and ask you to trust it — it ships the
underlying facts: an append-only stream of events, not
pre-baked statements about what a learner “knows.” Every
interaction reduces to one of five verbs —
session/open, attempt, signal,
actuator invocation, and session/close — so any
downstream consumer, human or agent, folds the same stream into
mastery, engagement, or an intervention decision. An MCP server sits in
front of those same facts, so an agent can query them directly instead
of waiting on a bespoke report API.
Where we want your input
Six open questions this demo is actively testing — reactions welcome on the gist.
- Is betting the whole model on five verbs (not fifty event types) the right compression, or does it lose signal?
- What’s the real adoption wedge — a new LMS, a plugin into an existing one, or a standalone telemetry layer?
- Does treating latency as a confidence signal (not just correctness) change how a teacher reads the dashboard?
- Which actuator kinds earn their keep beyond a hint and a celebration — and which start to feel intrusive?
- Can a teacher read a learner’s state from this in the 4 minutes they actually have between classes?
- Are we removing the need for a priesthood of dashboard-readers, or just re-inventing one?
Start a session
Every visit starts a fresh, ephemeral learning stream, verified by Turnstile below. Facts are retained for 7 days, then deleted.
Resume a session
Paste the resume link you were given (it looks like ?stream=...&code=...) to pick up where you left off.