Shuttlewright M4 markShuttlewrightPrimitives
The platform vocabulary

The pieces beneath
the workflow.

Identity, policy, approvals, queues and evidence. Use the catalog to understand a worker team, then inspect the runtime for what is connected.

This is a reference catalog, not an integration status page. The workspace shows its current capabilities and limits. No outside accounts are connected by selecting a primitive.
Control

Identity

Every worker has its own identity and scoped permissions.

Control

Policy

Declare what each worker may do: allow, ask or deny, per action.

Control

Approvals

Hold any action until a named person approves it.

Control

Kill switch

Stop every worker in a vertical at once.

Runtime

Durable queues

Jobs survive restarts and retry without duplicating work.

Runtime

Completion tiers

A way to express how quickly a job should finish. Inspect the active runtime and its terms before relying on a cost or deadline.

Runtime

Schedules

A scheduling primitive in the platform design. The current orchestration workspace does not connect a recurring scheduler.

Runtime

Worker factory

Define a vertical once as a template, instantiate it per tenant.

Trust

Audit log

Append-only record: which worker, which tool, on whose authority.

Trust

Metering

Usage and cost recorded per worker and per tenant.

Trust

Monitoring

Health and drift checks as a runtime concern. Inspect the relevant product for the checks actually connected.

Trust

Nothing leaves without you

No outside accounts are connected yet, so nothing is sent or charged. Anything that would act outside is held for a person to approve.

Connect

MCP packs

Each vertical is a pack that exposes its tools over MCP.

Connect

Agent-to-agent

Workers publish a card so other agents can call them.

Connect

Channels

Channel connector concepts sit behind policy. The current workspace does not connect outside send adapters.

Connect

Documents

Evidence and knowledge stores workers read from, with citations.