Event delivery model

The Event Log is an owner-scoped, retained history of public domain transitions. Every in-scope V1 transition is captured when cloud-backed, even when no integration connection or webhook subscription exists at capture time. Integration-control writes are not domain event sources.

Ordering and polling

Events are ordered by barakahsequence, the publication sequence assigned when a committed event enters the external log. Poll forward from the last sequence observed. Unlike ordinary collection pagination, Event Log traversal has no fixed high-water. It can continue without restarting until the 90-day retention boundary removes older history.

Numeric gaps in publication sequence are normal. They can reflect events that the current connection is not authorized to read. A gap alone is not evidence of event loss.

Authorization

A read requires all of the following:

1. The immutable owner captured with the event matches the current connection owner.
2. The caller presents that exact current REST connection.
3. The connection has events:read.
4. The connection has the event type’s registry-owned underlying read scope.
5. The operation’s entitlement rule permits the read.

Membership in another owner’s shared List does not transfer that owner’s retained event history.

Offline changes

Offline edits may reach the cloud later and then appear in a publication burst. Several local edits may collapse into one cloud transition. Use the external sequence for traversal, not a device edit timestamp.