Keep the Thread Across Boundaries

Core principle. A boundary does not lose the work. It loses the reasons.

The record is the memory this holds. Not the transcript, not the plan, and not a fact store. Only what settled and what is still open.
The weight sits in An entry stands alone. Every other rule here is cheap once entries are written that way, and worthless when they are not.
You opened this in the middle of something. This is how to keep that work, not a replacement for it. Name what you were doing before you start, and return to it when this is done.

Five moments, and nothing else

Write when something settles. These are the only triggers, and they are events rather than states.

When	Write
a decision is made	`decide`
a constraint is stated	`decide`, because a constraint is a decision with an open scope
an approval is given	`decide`, marked as approval, which expires at a boundary
the objective changes	`push`, which parks whatever was in hand
a second request arrives before the first closes	`push` if it interrupts, nothing if it is a dependency or independent