Documentation / Advanced
Inspect execution truth
Current state, retained event history, analytics and audit records have different freshness and authority.
Read an execution and its history
Use filters/pagination instead of loading unbounded histories. Archived history may need an authorized restore with retention, cost and integrity checks.
rippflow executions list --status waiting --limit 20 --json
rippflow executions inspect EXECUTION_ID --json
rippflow executions history EXECUTION_ID --jsonReplay for diagnosis, not side effects
Diagnostic replay reconstructs recorded transitions, tools, budgets, approvals, callbacks and ownership changes. It must not call providers or execute handlers. Event deduplication/order and redaction matter; an audit log is not permission to repeat a payment or tool call.
The core’s model suite exercises diagnostic replay; this is separate from local CLI report inspection.
rippflow inspect --report report.json --jsonTreat missing adapters as unavailable
Check observation timestamps, scope, watermarks and adapter availability. Missing/stale inventory is not healthy zero usage. Operators can inspect live or recorded multi-cell telemetry and 3-way reconciliation in the Ratatui dashboard with rippflow monitor (1.8.1+) or rippflow analytics endurance --tui.
rippflow distributions describe --json
rippflow analytics freshness --json
rippflow monitor --demo-60s --once --jsonVerified sources
Checked 2026-11-05.
- executions.rs f6c7970 · main
- execution_observability.rs 04cb082 · main
- installation_observer.rs f6c7970 · main