events.jsonl as newline-delimited JSON. Each event represents a phase transition in the cognitive loop.
Event structure
Every event follows this base structure:Unique event identifier.
Event phase. Canonical values:
start, observe, interpret, plan, direction, governance, act, reflect, learn, terminate, insight, memory, intuition, reason, error. Extensions may emit additional phases.Identifier of the component that emitted the event.
Phase-specific payload data.
Timing metrics for the event.
ID of the event that caused this one (for lineage tracking).
Event phases
Additional phases you may see:- start: episode initialization metadata.
- intuition: advisory/intuition policy events.
- memory: reads/writes performed by the memory port.
- insight: computed insight metrics (alias of events —phase insight).
- reason: reasoning traces from the planner.
- error: fatal errors.
observe
Captures the raw task and context at episode start.The task or goal for the episode.
User-provided metadata tags.
ISO 8601 timestamp of observation.
Additional context provided with the task.
interpret
Summarizes signals extracted from the observed input.List of detected signals.
Classified intent of the task.
Policy that performed interpretation.
plan
Records the selected action steps.Ordered list of planned steps.
Confidence score for the plan (0-1).
direction
Records policy directives (meta mode only).Unique directive identifier.
Directive status:
applied, blocked, skipped.Human-readable advice from the policy.
Target of the directive:
input, plan, action.List of paths that were modified.
Policy that issued the directive.
Explanation for the directive.
governance
Records governance decisions (meta mode only).Unique governance event identifier.
Governance decision:
allow, audit, veto.Rule that determined the decision.
Confidence score for the decision (0-1).
Governance policy identifier.
Additional governance details.
act
Logs tool or adapter invocations.Tool that was invoked.
Adapter that was invoked.
Truncated input for logging.
Result of the action.
Action status:
success, error, timeout.Error message if action failed.
reflect
Evaluates outcomes against expectations.Whether the episode succeeded.
Human-readable explanation of the outcome.
List of expected outcomes.
List of actual outcomes.
List of issues encountered.
Evaluation metrics.
learn
Captures learning signals for future episodes. The minimal validator expects the following keys; runners may add extra detail.Policy that produced the learning signal.
Reasons or evidence that drove the learning update.
List of proposed updates (may be empty).
Whether the proposed updates were applied.
Update scope:
session, episode, policy, global.terminate
Marks the end of an episode.Final status:
completed, errored, vetoed, aborted.Episode identifier.
Total episode duration in milliseconds.
Phase order (partial)
Current phases:start, observe, interpret, plan, direction, governance, act, reflect, learn, terminate, insight, memory, intuition, reason, error.
- Required:
startkicks off every episode;terminatemarks completion. - Typical loop:
observe→interpret→plan→ (direction/governancein meta mode) →act→reflect→ (learnoptionally). - Optional tail:
insightandmemorymay emit afterterminatefor scoring/persistence. - Partial order: phases follow the sequence above when present, but not every phase appears in every run.

