Traces

Traces presents recorded runs and their outcomes. It contains what the integration actually reported, with the content allowed by its capture mode.

Find a run or situation

The Traces list is the default. Use filters to inspect human interventions, matching Rules, or a particular action. Situations groups related recorded cases to help identify repeated work that could benefit from a Rule. Counts in a loaded list describe the loaded traces; older traces may be available. Human interventions include recorded reviews and approvals. Rippletide activations include matching Rules in Observe or Enforce. The same trace can appear in both categories.

Inspect the details

Open a trace in the detail panel:

Flow presents recorded business steps and their outcomes.
Full trace presents the technical span structure: runs, agents, model calls, tools, policy checks and response delivery when reported.
Correlation links connect a protected invocation to its decision and actual reported outcome.

Full trace is a view, not a guarantee that raw content was captured. A metadata/redacted trace cannot recover values that were withheld. A missing span or receipt is unavailable evidence, not a successful action.

Read outcomes precisely

Evidence	Meaning
Heartbeat	A connected process reported being alive
Inventory/manifest	The integration declared configuration
Run/turn	A request or conversation turn was recorded
Tool call	A tool attempt and any captured result/error
Policy decision	The Rules’ decision at the protected boundary
Executed / Prevented	The handler was invoked / was not invoked
Delivered / Suppressed	The candidate response was delivered / withheld
Result delivered / Result filtered	The caller reports applying the collection plan
Unconfirmed / unknown	The actual outcome has not been proven by a report

An executed handler can still fail. A model candidate is not a delivered response. Authorization without a completion event is not proof of execution.

Connection evidence differs by integration

Integration	Runtime proof
TypeScript or Python SDK agent	Current inventory, heartbeat, expected tool call, turn and before-response evidence
JavaScript/TypeScript MCP server	Inventory, heartbeat and tool call; no turn or response boundary
Codex hooks	Inventory, heartbeat, covered tool call and turn when activity is enabled; no before-response gate

Codex with activity disabled can still produce policy decisions while its activity-based status remains declared. Imported Codex history is backdated evidence, not proof that those turns were governed.

Inspect from the CLI

rippletide events --agent <agentId> --limit 20
rippletide events <traceId> --agent <agentId> --json
rippletide events --agent <agentId> --cursor <nextCursor> --json

events --wait checks live readiness and cannot be combined with a trace ID or cursor. Use Rule testing and Business context to turn inspected evidence into a reviewed policy change.

Getting started

Connect

Rules and sources

Inspect evidence

Workspace

Find a run or situation

Inspect the details

Read outcomes precisely

Connection evidence differs by integration

Inspect from the CLI

​Find a run or situation

​Inspect the details

​Read outcomes precisely

​Connection evidence differs by integration

​Inspect from the CLI

Find a run or situation

Inspect the details

Read outcomes precisely

Connection evidence differs by integration

Inspect from the CLI