Boundaries
What peregrin owns — and the neighbors it deliberately doesn't.
Owns
- The integration side of the entity plane: sessions as
kind="sepia-session"entities, campaigns askind="campaign"entities, namespaced ops, campaign hosting (campaign serve), fleet scheduling viaruns_on. - The orchestration plane: campaigns, drivers, events, templates, loaders, stores, remote transport, the outbox for offline ordering.
- The policy decision over sessions: who may act, when, and where (locks, takeover arbitration, hub-side routing).
peregrin-http's composition of session routes with the generic substrate routes under one listener.
Doesn't own
| Neighbor | Owns instead |
|---|---|
| sepia | Session mechanism — attach, prompt, restore, per-agent stores. Peregrin spawns sepia serve and never links sepia-session into orchestration code. |
| hypha | The generic substrate — entity plane, projection, outbox, locks, sync, the /api/entities* + generic HTTP routes. Consumed as git deps. |
| tamias | Bundle distribution, provisioning, deploy, service lifecycle. Peregrin ships only the tamias-driver-peregrin provider; the peregrin command itself is a tamias bins[] shim. |
| sturn | Ephemeral coordination — claims/ops/topics. Peregrin consumes it via the sturn driver and sturn-poll ingress; it doesn't own the WAL. |
| tarsi | The release plane — libraries/release drives tarsi-serve ops; peregrin doesn't cut releases. |
The web UI (peregrin-web*) is experimental and lives on the experimental/web branch — main is headless.