Delivery order

Part of team configuration — The legs a send to a seat walks — native, mcp-inbox, typed — and how each level of the chain may drop or reorder them, never add one.

The order a send to this team's seats walks. It is not an owner section: writing or changing it is an ordinary change, and a record that writes none reads as the default order. Omitted, the general order is mcp-inbox, then typed, then drop; neither native nor headless-resume is ever in that default. A Codex receiver with no declared order has an implicit runtime queue first while its signed codex-daemon setting is on, then the typed wake, then the inbox and remaining default legs. If that setting is off or unavailable, the typed wake leads so an idle Codex inbox is not left unread. A declared delivery_order is followed as written. Only a declared word can add native or headless-resume to the general order. A typed leg that finds no live agent types nothing and hands the send to the leg behind it, recording typed: <reason>; a walk reaches drop when the legs before it did not take the send, or when the order puts drop before typed.

team config edit
delivery_order: [typed]
  • The word is one or more of socket, native, mcp-inbox, typed, drop and headless-resume, each at most once, in the order a send tries them. A written key with no legs is delivery_order needs at least one leg: socket, native, mcp-inbox, typed, drop, headless-resume — the default order is the absence of the key. A word outside the six is delivery_order "<word>" must be one of: socket, native, mcp-inbox, typed, drop, headless-resume; a repeated one is delivery_order names "<word>" twice.
  • The receiving seat's chain is read outermost first: the entity, the project's registry record, this file's key, then the seat's own key. No entity record carries an order in this build, so that level is always silent; the project's word is delivery_order beside teams in projects.yaml, written [typed] the same way. Each level may drop legs from the order in force or put the legs it keeps in a different order, and may add native or headless-resume, or place socket where the order in force lacks it: a word naming any other leg the order in force does not have is set aside, and the order in force stands. A word equal to the order in force is no word at all.
  • What a walk does with each leg — a leg takes the send or is recorded as a failure and the next one is tried — is team send's. A --wait send walks the same order and then awaits a reply record on the thread.