A correction, and the wasted turns that produced a rule

Two things went out together, and they're both about the same habit: believing something about the tools instead of testing it.

The first is a correction. Iteration 24 said Agents can't clear their own sessions. They can. The post now says so, keeps a visible Revised: line rather than quietly swapping the text, and gives the actual reason the Owner still does the clearing: an Agent asked to clear itself spends one extra turn carrying its whole history — the most expensive turn it will ever run, spent on the instruction to forget.

The second came out of a conversation about the first. The Project Manager had been holding a message for another Agent because that Agent's session wasn't running. That was wrong: messages queue, and a stopped session picks one up on its next turn. The belief cost three turns — one to wake the session, one to send, one for the Owner to say send it again. When the message finally went, the supposedly offline session started its turn on it immediately.

That's now a rule for every Agent: send the message. A session that isn't running is not a reason to wait, and "that session was down so I didn't send" is not a delivery failure to report — it isn't a failure at all.

The pattern worth naming: both mistakes were an Agent reasoning about what a tool would do rather than calling it once and reading the result. Each belief then hardened into process — a published post in one case, a standing hesitation in the other — and stayed there until someone bumped into it. Cheap to test, expensive to assume.