Departments

A department groups roles under one command, with a monthly spending cap of its own. It is not a decorative label: the department adds up the consumption of all its members, has a head and can sit under another department. The view opens from the menu, under “Departments”.

The screen itself sums it up like this: “A department groups roles, has its own monthly cap and its own document store. If it runs out of budget, nothing is delegated to anyone on the team.” The cap is additional to each role’s: a role can have balance left and still sit idle because its department has run out.

The header

Element	What it does
Help text	The explanation above, in one line.
“New department” button	Opens the empty form.

If there are none: “No departments yet. Create them to split roles into teams with their own budget”.

Departments are laid out in a grid of cards. Each card is one department.

Anatomy of a card

Part	What it shows
Name	The department’s title, in bold.
Code	Its internal identifier, small and grey.
“Edit”	Opens the form with what is already there.
“Delete”	Asks for confirmation and then deletes it.
Mission	What the team answers for, if it is written.
“Led by:”	The director’s job title. If there is no director: “nobody assigned yet”.
“Sits under:”	The name of the department it hangs off. If it does not hang off any: “nobody (sits under the owner)”.
Usage	“X of Y tokens this month” if it has a cap, or “X tokens this month · no cap of its own” if not.
Remaining	To the right of usage, “N left” or “exhausted”.
Spending bar	Only if there is a cap. It fills according to the percentage spent.
Roles	A tag for each role in the department, with an “×” to remove it. If there are none: “No roles yet”.
“Add a role…” selector	Lists the active roles that are not in any department. Picking one puts it in this one. If none are free, the selector does not appear.

The bar and the remaining balance change colour with spending:

Situation	Colour and text
It has reached the cap	Red, “exhausted”.
It has spent more than 80%	Amber, with the tokens left.
Below 80%	Green, with the tokens left.
No cap of its own	No bar and no remaining balance; only the month’s usage.

How roles are assigned

There are two gestures and neither asks for confirmation:

• Adding a role: pick it in the card’s “Add a role…” selector. Only roles that are not in any department appear, so to move someone from one team to another you first have to remove them from theirs.
• Removing a role: click the “×” on its tag. The role is left with no department; it is not deleted.

Only active roles can be assigned: requested ones do not appear in the list.

The form

It opens with “New department” or with “Edit”. The subtitle says: “The cap is monthly and is added to each role’s: with 0 it limits nothing”.

Field	What it is	Details
Code	The internal identifier.	Required. Stored in lowercase. Must start with a letter and allows letters, numbers, hyphen and underscore, 2 to 32 characters. Disabled while editing: it does not change.
Name	The visible title.	Required. Placeholder example: “Technology”.
Mission	What the team answers for.	Free text, several lines.
Director	Who leads it.	Dropdown with all roles and the option “No director”.
Sits under	Which department it hangs off.	Dropdown with the other departments and “Nobody (sits under the owner)”. It cannot sit under itself.
Monthly token cap	Its budget.	0 means no cap of its own.

At the bottom there are two buttons: “Cancel” and “Save”. Save is disabled while saving. If the code or the name is missing, the error is “Code and title are required” and nothing is sent.

When you pick a director, that role also becomes part of the “leadership” department, if that department exists: a team lead sits in the leadership of the house.

What happens when you delete

The “Delete” button opens the browser dialogue: “Delete the department “code”? This cannot be undone”. If you accept, deletion is attempted.

A department with roles inside is not deleted. The server answers: ““code” still has N role(s): remove them before deleting it, they are not going to be left without a department by surprise”. First you remove the people with the “×”, then you delete the empty team.

How spending is calculated

Usage is for the current month, from day 1 to today, and adds the input and output tokens of all executions by its members. It is recalculated every time the screen opens; there is no refresh button and no counter reset.

A department is “exhausted” when spending reaches or exceeds its cap. With a cap of 0 it is never marked exhausted: it does not limit.

The screen does not show how many executions the department has run, although the figure is calculated internally. It does not show the breakdown by role either: for that, look at each role’s profile.

What it is for day to day

• Splitting the company into teams without duplicating roles: a role belongs to one department only.
• Putting a ceiling on spending for a whole area, on top of each role’s ceiling.
• Giving it its own store: documents can be saved with a department. A department document is read by the whole team and written by its director, so what one area produces does not get mixed up with the rest.
• Knowing who is in charge: the department director is their team’s point of reference, and departments can hang off one another.