← all lessonsLESSON 7 OF 8 · TABLE 6: EVALUATIONS, ACTION GROUPS; THE ACTION READER
Map and Actions
The map puts each card after the cards that influence it; the roots come first. Then the practitioners’ step: score each root for feasibility, impact and whether it would fix itself. Only then are actions proposed, and each is judged against each root.
The map’s only root is “Loads are dispatched before the paperwork is checked”. Someone proposes the action “Improve communication between depots”. What happens?
✗ Not that one. The method’s answer is marked below; read why yours is not it.
It is added; the group will vote on whether it helps.✗ not this · your pick
It cannot be judged: nobody can say whether “improve communication” moved a root, because nobody can say whether it happened.
The author is shown it reads as a wish — nothing anyone would do, no way to see it done — and can rewrite it or post it anyway.✓ what the method does
The reader checks the four things the paper’s action stage needs: aimed at a root, doable, visible in its progress, owned. Vague actions are handed back before the matrix ever sees them.
You rewrite it for them.✗ not this
It is their action; an action group forms around its author. Yours would be an orphan.
ON THIS PLATFORM
Score the roots first; propose; every action is judged against every root at the same bar. An action that moves no root is not a bad idea — it is aimed somewhere else. What a root is follows the kind: a root cause in an obstacles room, a foundation — the state the others rest on — in a future room, and the thing to do first in an actions room.
“The reader” in these lessons is the language model the platform runs over a question or a card before it posts. It speaks only to the author, as a suggestion the author may take or ignore; it blocks nothing, decides nothing, and never reports to you. Where a lesson says the reader handled something, it means the author was shown a suggestion — not that anything was enforced.