gizzi orchestration is where conversation and handoffs happen: who said what to whom, whether it arrived, and what’s waiting on a person.

​
Threads

A Thread is a conversation or an assignment with a bot. There are two kinds, and every surface labels them differently.
Threads live with your account, so Gizzi reads them with your sign-in, and Desktop, the web app and your phone show the same ones. A Terminal bot’s conversation is its Factory mail (gizzi orchestration mail). Vendor threads keep the vendor’s own look, and channel threads keep the channel’s look. See Bot threads.

​
Send

One verb works for every bot, whatever its binding:
A node pickup (gizzi workspace node claim, or drive) uses the same path. The engine picks the delivery from the bot’s binding, and always reports which delivery happened.

​
Delivery states

Every message shows its real delivery state, never a guess. This is rule 7 of the determinism contract: if a message can’t be delivered verified, it’s queued and says so.

​
Vendor tickets are node deliveries

A node assigned to a Vendor bot is delivered as a vendor ticket. The node is the work item. The ticket (T-n) is its delivery record: what was sent, on which lane, and the post_result that came back. The post_result becomes the node’s output, and the same judge checks it. There’s no separate ticket list. The ticket shows inside the node and inside the thread, and T-n links to its node. See How vendor bots connect.

​
Queued messages

A queued message waits in the bot’s mailbox (on the workspace’s Bus). Deliver it once the pane is free:
Each message goes through the same verified paste as a send, and is marked delivered only after the paste is read back from the pane. The first message that can’t be delivered (busy pane, pane gone, paste not verified) stays queued and stops the drain, so the order holds. Run one drain per bot at a time.

​
Capture, transcript and feed

The transcript is the pane’s raw output, recorded from its first byte, and it outlives the pane.

​
Mail

Mail is the durable, reviewable message log between bots and people. A message that needs a decision (for example an outbound email waiting for your OK) is a review thread you decide on.
This replaces gizzi mail and gizzi ac.

​
Attention

Attention is the list of things waiting on a person. It feeds the Needs you inbox on every surface.

​
Steering and the Coordinator

  • gizzi orchestration steer checkpoint|consult records a steering checkpoint or consults the steering backend before a risky step.
  • gizzi orchestration coordinate <project> "…" hands a request to the project’s Coordinator (Al). Al answers, plans the work into task threads for the project’s bots, and starts them; they appear in gizzi orchestration threads list and on the project page. --dry-run shows what would be sent; --json prints Al’s reply.