Flows and governed actions

Blocchi uses one workflow runtime for visual authoring, Flow-as-code and agent-authored flows. The goal is not a parallel campaign engine or a separate agent execution framework.

Flow Spec v1

{
  "specVersion": "1",
  "name": "Follow up on engaged accounts",
  "nodes": [
    { "id": "audience", "type": "action", "config": { "action": "audience.resolve" } },
    { "id": "loop", "type": "loop", "config": { "collectionPath": "records" } },
    { "id": "agent", "type": "agent" },
    { "id": "authorize", "type": "action", "config": { "action": "communication.authorize" } },
    { "id": "send", "type": "action", "config": { "action": "email.send" } }
  ],
  "edges": []
}

The portable spec excludes tenant identity, revision and lifecycle state. Those belong to Blocchi's platform boundary.

Durable journeys

The workflow runtime supports durable enrollment, per-member child runs, event waits and provider evidence. Time-based waits and journey goals are being completed on the same runtime, not through a second campaign system.

Governance

An agent can reason, draft and propose. External side effects still pass through registered actions, permissions, source policy, confirmation or approval, idempotency and durable evidence.

See Governed actions for the live action catalog.