# Keep the Observation when current State changes

A current pointer can advance while its earlier structured assessment remains separately inspectable under retention.

Status: Internal implementation. Prelaunch; not a live service guarantee.
A bounded owner-configured View registry and reverse-dependency memberships are implemented in source. The managed execution path currently supports one required same-scope source; multi-source joins, public current-State serving, live Turn interception, and customer realtime subscriptions remain staged.

Reviewed: 2026-10-06.
Backend source: 16f1e66d303a43e245a5cff5c392e9ebd3adf201.
Native toolkit review candidate: fe3df1c237b48d04347b6f159cc49e2f0d830a2c (unmerged).
HTML: /docs/observations

> Version the derived evidence; do not rewrite the history that explains it.

## Three records with different jobs

1. **Active State pointer** — Identifies the current assessment for the server-owned View, with lifecycle and source-version conditions.

2. **Immutable Observation** — Retains the exact structured assessment, scope, View, pointer version, and candidate hash for that successor.

3. **Change evidence and delivery receipt** — Describe a particular transition and its internal queue delivery. They do not establish that a customer agent received it.

## Selection is not the final model input

An application may filter, reorder, truncate, or reformat selected evidence before calling a model. The structured Observation alone cannot reconstruct those later transformations.

A separately qualified capture boundary must record the assembled evidence or an approved immutable content reference, ordered source revisions, and transformation versions. Submission is still not proof of internal reasoning, consumption, or decision quality.

## Immutable does not mean retained forever

Observations are derived customer data with availability and deletion responsibilities. Current source export classifies them with the State pointer, change events, delivery receipts, and cursor. Retention and live erasure have their own gates.

No public Observation read endpoint, general View registry, automatic S3 archive, or universal historical reconstruction service is introduced by these internal records.

[Retention and evidence availability](/docs/retention)

[Customer exit controls](/docs/marketplace)