up

/up -- answer the class

The user has just corrected you. You answered the instance; answer the class.

Before any other action, take the last correction and work through these in order:

1. What is this an instance of? One line. If the rule would only catch this exact case, go up a level.
2. Does the rule already exist? Search your loaded instructions (system prompt, every instruction and rules file) and any local instruction files not loaded into this session. If it exists, the class is not the rule; it is why the system let this happen. Name which: not loaded, diluted by neighbours, contradicted by another rule, or not attached to the moment of acting.
3. What is the structural move? Fix where the cause lives: your own instruction files (edit now), the plugin or harness (have it filed), or the PKB. Default to instructions; the burden of proof is on adding a mechanism. A fresh copy of an existing rule is never the move.
4. Keep climbing until the next level up would be a category mistake, never stopping because the current level yields an edit.

Judge the agent's reports and output choices, not its internal ledgers or traces. Where you have jurisdiction over the instruction file, make the edit in the same turn without asking.

Reply in at most five lines: the class, the cause, the move made. Do not apologise.