How an assignment works
An assignment is not a question: it is work. This page covers what happens from the moment it is handed to a role until the role delivers it.
The assignment opens a card
Section titled “The assignment opens a card”When you delegate, the card appears in Work as in progress. It is not decoration: it opens because someone is genuinely working, and if it stays there, it means they got stuck.
It works in steps
Section titled “It works in steps”The role does not answer once and leave. It receives the assignment, acts with its tools, and if after acting it has not closed it, it is given another step so it can look at the real result of what it did before signing it off. That is where the “done” that is not done slips through.
Steps have a cap (three by default): each one is paid for, and an unbraked loop multiplies the
cost without improving the work. The cap is set with ENCARGO_PASOS.
There are two clean stops:
- Delivery. The role closes with
entregar_encargo. That is the end. - There is nothing to run. If it answers without using any tool, another shift would only make it repeat the same thing in other words.
Delivery is a gesture, not a sentence
Section titled “Delivery is a gesture, not a sentence”entregar_encargo(informe, verificado, leccion, clave) is what closes the assignment, and it
leaves three things behind:
| Field | What it means |
|---|---|
informe |
What was done and how it turned out. This is what gets read; it is not rewritten afterwards |
verificado |
Whether the role checked the result or only believes it went well |
leccion + clave |
What it takes forward to next time, stored in its craft memory |
The difference between I think it is and I have checked it is stored exactly as the role declares it. We do not verify it for them: we leave it written down so it can be held to.
It remembers what it did, not just what it said
Section titled “It remembers what it did, not just what it said”Between one step and the next, the role sees the last actions it ran and their results, not only its own prose. Without that, it repeats the same call or assumes what it did not check.
What happens when the steps run out
Section titled “What happens when the steps run out”The report that exists at that point is returned all the same, but marked: there was no formal delivery. It usually means the work was bigger than the assignment. Better to know that than to assume it.
Where you see it
Section titled “Where you see it”- In Work, the card moves to done with the report.
- In the role’s profile, its memory picks up the lesson the delivery brought.
- The board’s lesson count goes up.