Actor

Definition & Purpose

An Actor represents a participant capable of triggering actions or receiving notifications in the experience graph. Declaring actors makes security permissions and role boundaries explicit.

Actor Classifications

Actors are categorized using the 'type' attribute:

• human — End user, workspace admin, support agent, or buyer.
• system — Automated backend service, webhook listener, cron worker, or payment gateway.

Address Syntax & Examples

Actor addresses use the actors top-level dictionary:

1Address format:
2actors.actor_id
3
4Real-world domain address examples:
5- actors.customer
6- actors.workspace_admin
7- actors.stripe_billing_system
8- actors.auth_service

Complete Valid Example

Here is a document declaring human and system actors:

1actors:
2  customer:
3    name: Workspace Owner
4    type: human
5    metadata:
6      role: owner
7  stripe_gateway:
8    name: Stripe Payment Webhook
9    type: system
10    metadata:
11      protocol: HTTPS Webhook

What an Actor Does NOT Mean

An Actor is NOT a database user ID, NOT an OAuth access token, and NOT a user profile object. It describes participant roles across the experience graph.