Turn It Live
The run-mode ladder — paused, sandbox and live — and what each one actually authorizes.
Checklist step
turn_live of the onboarding checklist the product shows you, told API-first.This step moves the project's run_mode off its sandbox default onto live.
The run-mode ladder
run_mode is one operator-set string on the project, and it answers what may
this project do to the outside world. Moab declares three rungs. The platform
mechanism behind them — the four capability axes and fail-closed resolution —
is on Control plane; what each rung authorizes is
here.
| Mode | What it actually authorizes |
|---|---|
paused | Nothing runs on a schedule, and nothing reaches a provider. |
sandbox (default) | The full loop runs and does send automatically — but every send is confined to the named sandbox audience: email is rewritten onto the deterministic sandbox inbox list, LinkedIn is allowlist-only. That confinement is the gate. Missing or unreadable sandbox config blocks every push rather than falling through — absence never authorizes. |
live | Sends to real recipients. live never means auto-send: it only stops forbidding it. Each send still needs a bounded, single-use, expiring per-campaign operator approval. |
Three rules bind every caller:
- Changing the mode is an operator act, never a side effect. A task run that
tries to change its own project's mode is refused with
run_mode_change_requires_operator. Absence of an instruction never authorizes a send. - An agent spawned or adjusted by an external operator runs at
send_budget.total == 0, so its drafts staydraftuntil a human raises the budget. A send budget is an authorization, never a progress lever — never raise one to make a run finish. - Read it back. After any change,
projects_getreturns the effective mode. Trust that read, never a local assumption.
Delivery events (email_sent, linkedin_sent) land on the same timeline, which
means one query answers "what has this project actually done":
List timeline events — GET /api/v1/timeline-events
curl "https://moabcrm.com/api/v1/timeline-events" \
-H "Authorization: Bearer $DASH_API_KEY" \
-H "Project-ID: pr_zest"Show me the timeline events filtered by subject typedata_query {
"collection": "timeline_events"
}{
"object": "list",
"data": [
{
"object": "timeline-event",
"id": "obj_123",
"subject_type": "subject type",
"subject_id": "subject_123",
"kind": "kind",
"title": "title",
"body": "body",
"created_at": "2026-07-25T12:00:00.000Z",
"updated_at": "2026-07-25T12:00:00.000Z"
}
],
"has_more": false,
"next_cursor": null
}See Channels & Sending for the per-provider detail and Campaign Agents for the spend gate — the human-in-the-loop window.
Next: Reach Your Goal.