Polpo Runtime

Keep execution lifetime, canonical conversation state, and the client transport distinct. A Session stores conversation history; a Run records one execution; a Project Loop is one possible execution mode; SSE is only a delivery transport.

Workflow

1. Identify the surface and invocation source: direct chat, Channel, task, schedule, or Loop.
2. Preserve x-session-id when continuity is required. Do not rebuild canonical history from client guesses when a continuation API is available.
3. Use durable delivery for work that must survive disconnects. Reconnect to the Run event log; never repeat the creation request.
4. Use direct chat for conversational turns and Project Loops for deterministic multi-step work.
5. Validate response schemas, tool calls, tool results, and Loop bindings before they reach a provider or persisted history.
6. Use idempotency keys for continuation, schedule triggers, and externally visible actions.
7. Inspect terminal events and persisted state, not only the last SSE chunk, before declaring a run successful.