Team assignments
The Team assignments view is a log, not a form. Nothing is created by hand here: it shows the work Adrián has split across several roles and the outcome of each part.
One of these assignments is not just another task. It is a piece of work with several fronts running at the same time, each in its own role, read together at the end. An assignment with two parts done and one blocked is not finished, and this screen makes that plain.
How an assignment is created
Section titled “How an assignment is created”There is no button. Adrián decides the split, and only he has the tool to do it: it is called
encargar_en_equipo and he uses it when the work has distinct fronts that can run in parallel. You
ask for it by talking in the Office, in plain language: what needs to be achieved and which role
takes each part.
The rules the server applies before splitting anything:
| Rule | What happens if it is not met |
|---|---|
| At least two parts, each with its own task | It is not created: “working as a team takes at least two parts” |
| Six parts at most | It is not created: it says how many you asked for and that the maximum is 6 |
| Every role has to exist | It is not created: it names the code it cannot find |
| Every role has to be active | It is not created: it says what state that role is in |
| Whoever splits commands those roles | If a role splits the work rather than the CEO, it can only assign to whoever reports to it in the org chart |
If everything checks out, each part goes through the usual path (org chart, budget and board), so a joint assignment is not a shortcut around the rules. At most four work at once; the rest wait their turn without getting lost.
What the screen shows
Section titled “What the screen shows”At the top, the view title and a line summing it up. Below, the list of assignments: the last 30, most recent first.
When there are none:
No assignments have been split yet. When Adrián divides a piece of work across several roles, it will appear here with the outcome of each part.
The assignment card
Section titled “The assignment card”Each assignment is a card with this information:
| Element | What it is |
|---|---|
| Title | The first sentence of the assignment, truncated. The server sets it, it is not edited |
| Status badge | in progress, gathered or blocked. Painted green if every part is done |
| Count | “2 of 3 parts”, the creation date and who requested it (the code: ceo if Adrián split it) |
| View the report / hide | On the right. Only appears if the assignment has parts; clicking it expands the report |
| Assignment text | What was asked for, verbatim, with the line breaks it had |
| What Adrián concludes | A highlighted block with his reading: whether it is solved, what was missing and what decision is needed. Not always present |
| One row per part | The role code, the task it was given and its state |
| What each role brought back | When expanded: the full report, part by part. If there is none yet, “No report yet.” |
| Errors | In red and separate, “role: error”, for each part that failed |
The card header is clicked to expand and collapse the report.
The states
Section titled “The states”Of the assignment
Section titled “Of the assignment”| State | When it ends up like this |
|---|---|
| in progress | It has just been split and no part has come back yet, or the process is still alive |
| gathered | At least one part brought back a report. This is the normal state on closing, even if some part failed |
| blocked | No part brought back anything |
Of each part
Section titled “Of each part”| What you see | Internal state | What it means |
|---|---|---|
| working | in progress | That role is still on it |
| done | done | It returned a report |
| failed | failed | The role blew up or returned an error that is not about budget |
| blocked | blocked | It ran out of token budget. Not a work failure: a decision that is yours |
That distinction matters: a part blocked by budget is not retried in a loop, it waits for you to decide. A failed part is a real error and its reason is printed on the card.
It refreshes on its own
Section titled “It refreshes on its own”While any of the listed assignments is in progress —it or any of its parts— the screen requests the data again every 4 seconds. There is no refresh button: an assignment changes state with nobody touching anything, and a button would force you to guess when to press it. Once nothing is running any more, it stops refreshing.
What you cannot do here
Section titled “What you cannot do here”- Create an assignment from the screen.
- Retry a part, cancel it, or change the split.
- Edit the report or the conclusion.
- Get a detail page for a single assignment at its own URL inside the application.
To try again, you ask Adrián once more, with the split corrected. If the problem is budget, first resolve the request waiting for your signature in the queue.