Skip to content

Concepts

The ownership, authority, commerce, and execution ideas that shape Seams Pantry.

Concepts ​

Pantry coordinates a merchant's operating work without becoming an accidental second source of truth. The platform owns identity, Cases, agent sessions, governed actions, projections, and receipts. The selected commerce authority owns commerce facts. Provider adapters terminate external shapes at a typed boundary.

The core model ​

ConcernPantry's role
Identity and organisation boundariesAuthenticate the operator, resolve organisation ownership, and bind work to an organisation revision.
Conversation and workAdmit provider input into a ConnectorActor and CaseActor.
Agent executionRun durable AgentSessionActors through a harness-neutral adapter.
CommerceRead rebuildable projections and submit typed, governed actions to the selected authority.
Safety and policyCheck exact revisions, approvals, budgets, credentials, and capabilities before execution.
OperationsDeliver progress and receipts through Slack and the operator portal.

Design principles ​

  1. Every durable fact has one named writer.
  2. Provider payloads terminate in adapters and become precise internal types.
  3. A Case is the canonical body of related work; a Slack thread is one view of that Case.
  4. Agent sessions own history and checkpoints. Replaceable executors own compute and no durable domain state.
  5. High-impact actions use typed policy, authorization, approval, receipt, and replay boundaries.
  6. Projections are rebuildable from authoritative observations.
  7. Credentials remain opaque outside the trusted platform operation that uses them.

Reading order ​