Record that a person opened a record
What It Does
The console sends an attributed visit after a tracked record becomes visible. The audit writer verifies current target authority, then stores a compact occurrence for later history and recent-record queries. Other record types can have their own reporting paths; custom-record API reads report server-generated visits separately.
The Flow
When Something Fails
Delivery failure is invisible to the person. Retryable failures retain the key, avoiding another stored visit after an uncertain response. Client refusals and exhausted retries lose the report. The browser fallback identity is not a UUID and is therefore rejected. Target resolution precedes the insert transaction, so no atomic lock spans authorization and activity insertion.
Open Design Questions
Retention remains undecided, and failed delivery has no repair mechanism.