Record activity is an append-only, workspace-isolated store separate from the security history

Context

Record navigation and business changes need a common activity account without crowding security decisions.

Decision

Use one shared activity table with declared event types and bounded metadata. Restrict ordinary application privileges to inserting and reading within the selected workspace.

Alternatives Considered

Combining trails would mix purposes. Separate stores would duplicate protection and history machinery.

Consequences

Database privileges protect existing rows from ordinary application changes, while retention still needs a product decision.