inbound_reject

Category: inbox
Access: write
Audience: administrative (ordinary users do not normally call this directly)

Purpose

Rejects staged inbound items with no content effects. Call it to decline proposals the conductor will not adopt.

Arguments

Required: kind, item_ids.

Optional: reason.

kind. Note: tasks or knowledge.
item_ids. Note: JSON array string of namespaced ids (t:/e:/r:) matching kind; every id must exist and be pending or the whole call fails.
reason. Note: Recorded as the decide reason on each item.

Result

Object with rejected array of id entries.

Boundaries

Conductor role required. Operates inside the selected profile boundary; rejection changes only item state, never content.

Lifecycle / side effects

Marks each item rejected with decider, timestamp, and reason plus a decision history event. Content entries are untouched.

Errors

Non-conductor callers get a requires-conductor error payload. Invalid kind, malformed ids, kind/id mismatch, or any ineligible item fails the whole call with nothing applied.

Example

{
  "item_ids": "[\"e:2\"]",
  "kind": "knowledge"
}

Result shape:

{
  "rejected": [
    {
      "id": "e:2"
    }
  ]
}