Procedures
A lesson is a rule: «ask for three quotes». A procedure is the whole path: what gets done first, what data you need, where people trip up and a case that went well. It is what turns a role into someone who knows how to work instead of someone who improvises on every assignment.
What it stores
Section titled “What it stores”| Field | What it is for |
|---|---|
nombre |
What it is called, in two or three words («close the month», «client onboarding») |
cuándo se usa |
The situation that triggers it, in one sentence |
pasos |
The path, numbered, with the data it needs |
trampas |
What usually goes wrong and how it is avoided |
ejemplo |
A real case that was resolved, if there is one |
A procedure can belong to one role or to the whole company (once you learn how a quote is requested, you do not have to learn it again in every department).
The index goes in the prompt; the steps do not
Section titled “The index goes in the prompt; the steps do not”At the start of every shift, the role sees the list of what it knows how to do: name, when it is
used and whether it is proven. Six names take two lines. The steps do not travel: they are requested
with usar_procedimiento when the work calls for them.
It is the same idea as an agent’s skills: knowledge does not take up context until it is needed. Without that, a role with thirty procedures would start every morning with thirty pages in front of it and none the better for it.
A draft is not doctrine
Section titled “A draft is not doctrine”Every procedure is born as a draft. It is not put in front of anyone as if it were the right way to work until it has proven itself:
- It becomes current when it works twice in a row, recorded with
cerrar_procedimiento. - It goes back to draft if it fails, and stays there until it is corrected.
- Correcting the steps bumps the version and sends it back to draft: what had been proven was the previous version.
A mistake turned into doctrine costs more than having no doctrine at all, because it repeats itself on its own.
How they come to life by themselves
Section titled “How they come to life by themselves”Nobody has to sit down and write procedures. Every Monday, before the week starts, each role does a memory catch-up: it reads its lessons grouped by topic, cross-checks them with what it already knows how to do and writes the procedure that is missing. It is a cron job, it shows in Cron like any other, and it can be switched off.
What it does not do:
- It does not invent steps. If a topic does not support a concrete how-to, it leaves it out and says so.
- It does not duplicate. If one with that name already exists, it corrects it and bumps the version.
- It does not publish itself. Everything it writes is born as a draft; it has to work twice before being put in front of anyone.
That is the difference between a list of rules and a craft: rules pile up, procedures can be followed.
Where you see it
Section titled “Where you see it”In the role’s record, Memory tab, «What it knows how to do» block: each procedure with its status, its uses and its body. Unfold it to read.
What it does not do
Section titled “What it does not do”- It does not replace the guidelines. Those are set by the owner in the role record; procedures are the craft’s knowledge, with their trace in the audit log.
- It does not approve itself. Becoming current requires having worked, not having been written.
- It is not deleted. Retiring it takes it out of circulation and frees the name; the trace remains.