What is waiting in Decisions?
When work needs human judgment, read the request and its evidence before acting. A suggestion is not permission to execute.
Where do I find pending work?
Open the decisions inbox to review pending items in context. Developers can read the pending queue through the API:
GET /api/v1/cadreen/decisionsInspect the item before resolving it. The person making the decision is responsible for its consequences; do not resolve it from an unattended agent.
How do I decide from the API?
Resolve an item with its id from the inbox (the item's id: its kind, a colon and its own id, as GET /api/v1/cadreen/decisions lists it) and the choice you were offered:
POST /api/v1/cadreen/decisions/{kind:id}/resolve
Idempotency-Key: <a new UUID>
Content-Type: application/json
{ "action": "approve", "note": "Checked the amount with finance" }- The
Idempotency-Keyheader is required, and must be a UUID. Send the same key again to get the answer you already got, never a second decision. The same key with a different choice is409 idempotency_conflict. - Only a person, signed in as a member of the workspace, can decide. An API key gets
403 person_required. - Some kinds need more than membership: an admin or the owner decides the ones that move money or change what the workspace allows, such as a held payout, an off-ramp, a withdrawal, a connection deploy or an installed template. A member who tries gets
403 admin_required. The item'srequired_rolesays who may. - If someone decided first, you get
409 decision_conflict: reload the item to see the answer. Use the same key to read your own earlier answer back.
What does saying no do?
A no never runs the work again with your answer. What it ends depends on what you were asked:
- An agent's question, or output that was not good enough: the step is skipped. The steps that need it are skipped too, and the mission finishes with what else it did, marked as done with issues.
- A step that failed and asked whether to go on, or that could not be fixed: the step stays failed and is not tried again.
- A review of what a tool found: the step is declined. What the tool found is kept and is not used. The mission finishes with what else it did, marked as done with issues.
- A request for a credential: the step is declined, and its reason says to add the credential on Connections.
- A question about where the mission is heading (it moved away from what you asked, or its own check stopped it): the mission is cancelled, and you are recorded as the person who ended it.
- A plan, a step, a check before a step, or a delivery that needed your approval: that work does not run, and the mission ends as cancelled. Its reason says what you rejected.
A question that asks for information or a choice can't be declined: answer it, or cancel the mission. Once a mission has ended, you can retry it or start it again from the beginning.
Who said no is kept in the decision record and the audit trail. The sentence the mission shows says only that a person declined.
What happened afterward?
Read the linked operation and its receipt and story. The record should distinguish the human choice from the effect it authorized.