Seen and Read Tracking

Resources with this capability expose engagement records for each User. A seen record indicates that a User has observed the resource; a read record is an explicit confirmation for content that requires reading confirmation.

Seen and read are separate states. A resource can expose only seen tracking, or it can additionally require an explicit read confirmation; creating a read record can also establish the seen state when the resource contract defines that behavior.

The resource's Model Definition identifies the tracking capability. Its tracking endpoints define authorization, idempotency, notification updates, and any state transition caused by creating a tracking record.