Observability
Under development
This section is a stub. The observability subsystem is managed in b4arena/observe and will be documented in detail as it matures.
Overview
Observability in #B4arena covers multiple levels of inspection:
| Level | What You See | Tool |
|---|---|---|
| Platform status | Agent registration, sync state, host health | ludus info status |
| Agent health | Container state, last activity, error counts | ludus info doctor |
| Work visibility | Open beads, blocked work, agent assignments | bd stats, bd blocked |
| Session inspection | Individual agent reasoning traces | ludus ops replay |
| Dashboards | Visual overview of beads and agent activity | beads-ui, PinchChat |
Design Principles
From the Constitution (Principle #4 — Transparency Over Trust):
Every agent action leaves a trace. Not because we distrust agents, but because an opaque system cannot be debugged.
Agents are software — their reasoning, tool usage, decisions, and outputs are inherently recordable. #B4arena treats this as a structural advantage.
Source: b4arena/observe · Operating Model Reference §8