Decision stack

What lands here

Employees add to the stack deliberately. They are told to ask only when a human's judgement genuinely changes what happens next — not for permission to do the work they were hired for, and not for something they could look up. A typical row is work that is already finished except for the call: the email is drafted, the post is written, the shortlist is down to two.

This matters most inside a Routine. A routine's brief was written hours or weeks earlier and there is nobody to ask mid-run, so before the stack existed an employee in that position had to guess. Now it can stop.

Answering a decision

• Open Home, or the Decisions section for the full list.
• Press Show context to read what the employee actually wrote — the draft, what it already checked, and what each option costs.
• Press the option you want. You can add a note first; the employee reads it alongside your choice.
• Nothing to decide? The × dismisses the row and tells the employee nobody picked an option, so it stops waiting.

Any Member can answer, not just owners and admins. If the employee addressed the question to one person, only they — or an owner or admin — can answer it, so nothing strands behind somebody on holiday. Owners and admins get a notification for every unassigned decision; an assigned one notifies only its recipient.

What happens next

Your answer lands in that employee's journal, and the last week of its journal is part of every prompt it runs — so it picks the work back up on its next turn without anyone scheduling anything. It can also read the answer immediately with its list_decisions tool. The Decided list on the Decisions page keeps the trail: what was asked, what was chosen, who chose it, and any note.

An employee can retract its own question if the situation moves on. A decision can also carry a deadline, after which it stops nagging anyone and shows as expired.

Decisions are not approvals

The two look similar and are deliberately separate. An Approval is Genosyn holding back an action an employee already attempted — a gated Routine tick, a payment over your threshold, a browser form submit — and the server performs that exact action once an admin approves it. That is why approvals are admin-only and ask you to re-authenticate.

A decision performs nothing. It records which option a human picked so the employee can carry on, which is why an ordinary Member can answer one. If the employee then does something privileged with your answer, that step still meets its own approval gate.