Observability explains what happened without changing what may happen next. It joins current and retained facts through exact chart, instance, sequence, causation, and correlation coordinates.
Evidence has an owner
A typed client can report one instance's current Snapshot. A retained timeline records selected committed macrosteps. Storage inspection exposes checkpoints, steps, outbox rows, Park journals, and chart versions without entering the mailbox. Runtime tracing projects those durable facts into Effect spans.
These views are related, but none may impersonate another. A span is rebuildable telemetry, not a commit. A timestamp is not causation. An application correlation id may travel with a stimulus, but it does not enter chart meaning. An incident is immutable evidence of an unexpected operational Cause, not an instruction to retry it.
Choose the evidence you need
Keep reading separate from acting
Observation may reveal a parked root, pending outbound delivery, or a version that needs migration. The decision to redrive, interrupt, or migrate belongs to a different authority. Carry the exact incident, Park, or version coordinate into Operations or Versioning & Migrations; do not turn a read into an implicit command.
Begin with Committed Inspection & Provenance to establish the immutable evidence boundary.