SUPERVISION/OBSERVABLE EVENTS
04 / OBSERVABLE EVENTS

Follow the run
as it changes.

A process view is useful only when it explains how the run reached its current state. Events make admission, handoffs, budget decisions and worker outcomes reviewable in order.

EXAMPLE MODEL This page describes a runtime surface; values and events are illustrative.
EVENT STREAM

A reviewable
sequence.

Each transition keeps its relationship to the mission and the state that authorized it. That makes later review more useful than a detached success message.

09:41:02 · RUN

Mission admitted

A run is associated with its policy, workspace and declared execution envelope.

01
09:41:05 · WORKER

Research worker started

A configured worker begins inside the run boundary.

02
09:42:18 · BUDGET

Allocation updated

The supervisor records a budget decision with its affected worker.

03
09:44:31 · HANDOFF

Evidence review requested

A result moves to a review step with its source outputs attached.

04
WHAT THE OPERATOR CAN INSPECT

Context is part
of the control.

OrderingtimestampedSequence explains transitions
Attributionrun + workerEvents retain their source
Reviewfilterable historyInvestigate a path after it ends
“
RUNTIME PRINCIPLE
The event record describes observed runtime activity. A Eureka event requires an accepted regulation transition; normal process shutdown alone does not qualify.
← Back to supervision overview