Understand an execution.

Start with a readable log when an action needs investigation. Use structured observations and Trace Local when you need to follow the details.

Readable logs and structured records

The optional file-logging companion writes a human-readable execution.log and a structured execution.jsonl from the same real SDK results. JSONL keeps one JSON observation per line for filtering and comparison. Logging is optional and follows the first runnable action.

Run the companion · Read the host-owned writer · See its integration

What to record

SDK results describe the action outcome, lifecycle, identities, effect truth and claim permission. Your host adds observations such as the phase, actual provider-write count and whether it sent a customer confirmation. Keep those host observations separate from SDK fields.

The companion captures an initial UNKNOWN result and later verifier-only reconciliation. It aliases identities per run and allowlists fields instead of writing credentials, raw customer inputs or full host state. Apply the same care to your own logs.

Inspect supplied evidence with Trace Local

Trace Local preview.7 helps inspect a captured execution, its identities and the evidence provided to it. Arrange the supported capture/export path before the execution you want to inspect. File logging does not automatically create a Trace export.

The n8n example describes observation hooks for its live initial and recovery results. Its downloadable source remains unchanged and does not include an automatic logger or Trace exporter.

Evidence still needs an authoritative check

A log records what was observed. Trace displays supplied evidence. Neither independently proves that a reservation, payment or other business effect occurred.

Your independent verifier must read the business system for the original effect and its exact binding. An unavailable read remains uncertain. Even a verified effect does not authorize every customer statement: the application must also check claim permission and the requested subject before confirming.

Provider and verifier responsibilities · Supported claims · UNKNOWN reconciliation · Operating your host · Troubleshooting · First-action troubleshooting