Receipts and replay

A live stream is presentation. A trace is evidence.

RECEIPT PATH · NO RE-EXECUTION

Store identity, not a shadow journal

Keep the trace path or run identity beside the application’s business record. Do not copy selected event fields into a second log and call that the receipt.

const verdict = await nika.traceVerify(tracePath)

await auditStore.write({
  tracePath,
  intact: verdict.intact,
  chainHead: verdict.head,
})

Verify before trust

traceVerify() is offline. It does not call a model or execute a task. A broken or unchained journal remains readable, but should not be presented as verified evidence.

Re-project with the engine

nika trace show .nika/traces/<run>.ndjson
nika trace replay .nika/traces/<run>.ndjson
nika trace export .nika/traces/<run>.ndjson

Replay passes recorded events through the renderer. It never reruns the workflow.

Retention

Trace content is local by default. Choose retention, redaction and export policy from the workflow’s data sensitivity. Content-inclusive telemetry is an explicit widening, not a default.

Continue

Test and trace

Compare behavior and verify integrity.

Trace concepts

Learn the journal and chain model.

Run receipts pattern

Carry receipts through application boundaries.

Observability

Inspect before, during and after a run.

Overview

Start

Project · live

Local API · live

Runtime · live

Remote API · preview

Operations

Reference

Receipts and replay

Store identity, not a shadow journal

Verify before trust

Re-project with the engine

Retention

Continue

Test and trace

Trace concepts

Run receipts pattern

Observability

​Store identity, not a shadow journal

​Verify before trust

​Re-project with the engine

​Retention

​Continue

Test and trace

Trace concepts

Run receipts pattern

Observability

Store identity, not a shadow journal

Verify before trust

Re-project with the engine

Retention

Continue