Skip to content

Start here

Review history and receipts

Trace who changed a proposal, which revision was decided, and where generation came from.

Review history records creation and later changes alongside the current review state. Use it to understand who acted, what changed, and which payload and evidence basis a decision covered.

Read events in order

Open the review history and inspect revisions. Edits can show previous values; source changes and captures explain why status returned to pending. Notes explain commentary without implying a payload change. Load additional event pages when available before treating the displayed history as complete.

A current approved status does not mean every earlier revision was approved. Match the decision to its exact revision and source basis. A later edit requires a new decision rather than extending the earlier attestation automatically.

Generation provenance

A generated proposal carries the receipt for the request that published it. That receipt remains associated with the proposal even after later generation attempts. A lookup reads existing provenance and does not start generation.

Inspect available request options, source revision, outcome, and usage information when comparing proposals. A failed or uncertain attempt can preserve diagnostic and correction information without publishing a valid proposal.

Limits of the record

The history is an application review ledger. It is not an external administrator-proof archive, a legal retention system, or independent proof that the proposed interpretation was correct. Whole-App purge also removes its reviews and associated history.

If you need a particular retention or compliance process, establish that separately rather than assuming the presence of an event list supplies it.

Recovery

When a write response is lost, inspect the persisted review and history before repeating the action. The same recorded request can recover its original event even if later events exist. Read the current revision as well as the recovered receipt so you do not mistake an earlier success for today's final state.

See uncertain requests.