Module 01 · Contract beta
Activity
Activity turns product events into ordered, rebuildable timelines with retry-safe fan-out.
Start with one complete path
The shortest Activity integration has three steps:
- Learn the resource and ownership model.
- Sign an HTTP request from your host server.
- Publish a post and read the actor’s home timeline.
Activity exposes a versioned /api/v1 HTTP contract. Requests use HMAC-SHA256 gateway signatures rather than an end-user session token. The public operation surface is listed in the Activity HTTP operation index.
Continue by task
- Understand pagination, ordering, fan-out, and rebuild behavior.
- Apply visibility while keeping business authorization in the host.
- Inspect the complete REST operation index.
- Review beta limits and known gaps.
Maturity by surface
| Surface | Current status |
|---|---|
| Core resource model | Contract beta |
| HMAC gateway authentication | Contract beta |
/api/v1 HTTP operations | Contract beta |
| Supported SDK | Not available |
| Managed service and production SLOs | Not available |
What this module owns
- Event projection and timeline ordering
- Retry-safe fan-out
- Rebuildable timeline entries
What the host owns
- Business meaning and authorization
- The source-of-truth event
- Ranking policy not explicitly delegated to Activity
Current limits
Webhook delivery, complete moderation transitions, attachment safety, a supported SDK, managed operations, and downstream production adoption are not established. Keep those capabilities outside production claims.
Start: learn the Activity concepts.