The queue

There are two things in Organtia called a “queue”, and they are worth keeping apart:

• What waits for your signature. The panel on the right, on every screen. These are things Adrián has asked for and cannot settle on his own: a role he wants to hire, a permission or a resource he needs, a decision that is yours to make.
• The message queue. What you type while Adrián is working. It lives inside the Office, in the bar that appears above the text box.

What waits for your signature

The panel is titled “What waits for your signature” and carries a counter with the total. It can be collapsed with the arrow in the header; once collapsed, a tab remains with an envelope and a notification dot if there is anything inside. The top bar also shows a button with the number while anything is pending, which opens and closes the panel on narrow screens.

While there is nothing:

Nothing waiting for your signature. Adrián is not asking you for anything.

The order they appear in

Always the same order, by block:

1. Hiring — roles in the “requested” state.
2. Permission or resource — pending resource requests.
3. Decision — decisions in the “proposed” state.

Within each block, the server returns hirings oldest first, and permissions and decisions newest first. The header counter adds up all three blocks.

Hiring

One card per role Adrián wants to create.

Element	What it shows
Label	“Hiring”, with a person icon
Title	The name of the role
Description	Its mission; “No mission declared.” if there is none
Skills	The list, separated by dots. If there are none, it does not appear

Button	What it does	When it is active
View profile	Opens the role’s profile so you can read it in full before deciding	Always
No	Rejects the hire: the role is marked rejected and is not created	Always

There is no hire button on this card. The hire is signed from the role’s profile: the Sign button appears there while the role is pending, and it requires at least one skill ticked (“With no skills it would just be a name on a list”). That way nobody is hired blind.

Permission or resource

One card per resource request: a key, an access, a paid tool.

Element	What it shows
Label	“Permission or resource”, with a key icon
Title	The detail of what is being asked for; if there is none, the name of the resource
Description	Its justification; “No justification.” if there is none

Button	What it does	When it is active
Grant	Approves the request and triggers delivery of the resource	Always
No	Rejects the request	Always

Decision

One card per decision Adrián left open instead of taking it himself.

Element	What it shows
Label	“Decision”, with a scales icon
Title	The title of the decision; “Decision” if there is none
Description	The context: why a decision is needed

Button	What it does	When it is active
Approve	Marks it as approved	Always
No	Marks it as rejected	Always

What happens when you click

There is no confirmation: one click acts. In all three cases the server settles the case and the card disappears from the list, which is re-read immediately.

After that the application does two more things:

1. It tells you in the top bar: “Granted — summary of what was delivered. I’ll tell Adrián.” or “Rejected. I’ll tell Adrián.”
2. It tells Adrián, in a message of his own, so that he stops waiting and does not ask for the same thing again. If you rejected, the message forbids him from pushing the same request again.

If you granted it but delivery fails, the screen does not gloss over it: it shows “Approved, but it could not be delivered: …” and Adrián is warned not to take the permission for granted. A permission that does not exist is worse than a denied one.

The message queue

Only visible in the Office. It appears when Adrián is working or when something is waiting, and it looks like this:

Element	What it means
Working · Ns	A turn is running, with the seconds it has been going
The truncated text	What he is dealing with right now (cut at 58 characters; the full text on hover)
Queued · N	How many messages are waiting
The first two	The next two in the queue, cut at 40 characters. The one with a lightning bolt is urgent
and N more	The rest below
Clear	Throws away everything waiting. It says how many it discarded

The queue order is: urgent first, and among equals, whoever arrived first. An urgent message does not jump ahead of another urgent one.

Message states

State	What it means
pending	Waiting for a turn. This is what “Queued” counts
in progress	Being handled right now. There can only be one
done	It was handled and the answer was stored
discarded	You threw it away with “Clear”. It is never handled

The four buttons on the text box

Button	When it appears	What it does
Send	When Adrián is free	Sends the message and waits for the answer
Queue	When he is working and you have typed something	Queues the message for the next turn and tells you which position it lands in
Interrupt	When he is working and you have typed something	Cuts the running turn and handles yours now. What he was doing is lost
Stop	When he is working and you have typed nothing	Cuts the turn outright, sending nothing. Whatever was queued is handled afterwards

While he works, the text box warns you: what you type is not lost, you only have to choose whether it waits or whether it interrupts.