Activity history is written by the database at commit; tasks keep stamps only

Context

Interaction readers need an account of changed context after correction and deletion. Task stamps provide attribution without an edit history.

Decision

The activity stream captures owned context and settles revisions at commit without a reaction handler. Shared routes present revision sections with current reference names. The cited history presentation decision does not answer the separate task-history question.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

Interaction revision capture covers the declared database stream. Tasks retain their latest attribution and closing facts rather than a reconstructable history.