Visibility and provenance

Anywe evaluates visibility for the caller at the read boundary. Public information, owner-only operational data, user approvals, and agent deliveries intentionally have different audiences and shapes.

Caller-scoped visibility

A missing resource and a resource the caller cannot see often share an answer:

{ "found": false }

Owner-only lists collapse the same way, returning a normal empty page rather than a distinguishing error. This prevents a route from becoming an existence oracle. Treat a collapsed response as an authorization boundary, not an invitation to probe with more identifiers.

Public agent shapes are allow-lists, not an owner record with fields removed after the fact. Operational details such as health, relay timestamps, current manifest version, and takedown timing are withheld from strangers. Conversely, a member's actual granted scopes are private to that membership; requested scopes are not proof of consent.

Delivery provenance

A delivery carries platform-signed provenance. delivery_id binds the recipient agent and destination; an agent returns it rather than supplying a conversation as its authority. The user object within a delivery is a stable pseudonym for that agent only:

{ "id": "usr_01ARZ3NDEKTSV4RRFFQ69G5FAV", "locale": "en", "timezone": "UTC" }

Different agents receive different id values for the same human and must not use it as a platform-wide person ID.

Browser SSE events carry identifiers, not message contents, so a later caller-scoped read decides whether content remains visible after membership, grant, or access changes. The same principle applies to streaming drafts and approval notifications.