What the team learns

A role does not start from scratch every morning: it keeps what it learns while working. This page explains what it keeps, where you can see it and what the system does so that knowledge is neither lost nor turned into noise.

What a role keeps

Two different things, and they should not be confused:

Facts. What happened and what is known about the business: “client X asked for quarterly invoicing”, “the margin on line Y is 12%”. They are stored with recordar_hecho and read back with consultar_memoria.

Lessons. What to do next time: “the tests for this project need the database container running”. They are stored with anotar_leccion, and they are what changes how the role works. When a shift starts, its latest lessons go into its prompt without it having to ask.

One lesson per topic, not a diary

Each lesson carries a topic in one or two words: despliegue, facturas, precios. If the role learns something on that topic again, the new lesson replaces the previous one. Two notes on the same subject do not pile up.

This is not a matter of style:

The role’s memory still fits in its prompt a year from now. If every stumble left a new note, in three months half the context would be repeated history.
A corrected note is read in full; five versions of the same note contradict each other.

The previous one is not deleted: it is marked as obsolete and points to the one that replaced it, so you can always see what was believed before and why it changed.

An assignment is not closed until it comes with its lesson

When a role finishes an assignment, the report it sends up to its manager includes the lesson it has written down. If it wrote none, the system asks for one once, in a short shift with the work still in front of it, and if there is still no lesson, the warning travels with the report: “finished the assignment without writing down a lesson”.

That is work data, not decoration. A role that does not learn repeats the same mistakes and costs the same every month.

The hierarchy inherits experience

A manager does not just hand out work: they read what their people learn.

A director calls aprendizaje_de_mi_equipo and sees the lessons of their whole chain, downwards, with the role that wrote each one. Something that already cost an analyst a stumble does not cost the next one again.
The CEO sees the whole company’s, because their team is the entire company.

Their own lessons do not appear there: they already have those in their memory, and repeating them would spend context on what they already know.

Where you see it

In Work, next to the board figures, there is a count: how many lessons the team has logged in the last thirty days. Expand it and you get the list role by role, with the date of the latest one.

Zero is data, not silence. If a role has gone a month without writing anything down, it shows up in the list with a zero and you see it. The figure exists precisely so that “nobody is learning” does not go unnoticed.

What it does not do

It approves nothing. A lesson is a note on the craft; decisions still belong to the owner.
It does not change the role’s guidelines. What a role learns is lessons and facts; its mission and its limits are set by the owner in its profile.
It does not invent lessons. If an assignment taught nothing new, the role says so instead of filling the gap with a platitude.