Journey map

Operate Vera by stage, not by endpoint list.

External agents should carry a small state machine: hydrate workspace state, choose the current journey stage, queue or review one safe step, then read the resource produced by that step.

Hydrate

Start every loop from workspace state.

Read the active project, readiness, Gmail state, current runs, and next actions before deciding what to do next.

Hydrate agent state

$ curl https://api-vera.symph.ai/v1/workspace \
>   -H "Authorization: Bearer vwk_live_..."

$ curl https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/next-actions \
>   -H "Authorization: Bearer vwk_live_..."

Stages

Choose one journey stage.

The canonical stages are connect, build seller context, shape prospects, send grounded outreach, handle replies, and continue safely.

Stage 1

Connect

Create a bearer key, confirm workspace state, and verify Gmail readiness before doing work.

Stop if Gmail is not connected, the sender is not confirmed, or readiness returns blockers.

Stage 2

Build Seller Context

Upload notes, URLs, and files, then turn source material into evidence-backed knowledge.

Do not use claims that are rejected, disputed, or unsupported by evidence.

Stage 3

Shape The Prospect Pipeline

Find buyer accounts, research each prospect, and advance reviewable strategy work.

Research, strategy, and drafts all carry review status and safety flags.

Stage 4

Send Grounded Outreach

Generate, inspect, edit, approve, and send drafts through the selected Gmail sender.

Never send a draft that is not approved or explicitly confirmed reviewed.

Stage 5

Handle Replies And Follow-Ups

Sync inbound messages, classify intent, draft replies, and process due no-reply follow-ups.

Stop for human takeover, unsubscribe intent, pricing asks, ambiguous replies, or risky claims.

Stage 6

Continue Safely

Use project policy and next actions to advance safe work without skipping review boundaries.

Autonomous mode can continue safe steps, but it still preserves hard stops.

Queue stage work

$ curl -X POST https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/runs \
>   -H "Authorization: Bearer vwk_live_..." \
>   -H "Content-Type: application/json" \
>   -d '{ "operation": "research_prospects", "inputs": { "limit": 4 } }'

Continue

Ask Vera for the next safe step.

When the agent does not know the next exact run, use `agent:continue`. Vera returns queued work or blockers instead of hiding review gates.

Continue journey

$ curl -X POST "https://api-vera.symph.ai/v1/projects/proj_01hx6x9v2r/agent:continue?max_runs=4" \
>   -H "Authorization: Bearer vwk_live_..."