ma-reflect

/ma-reflect [evidence]

/ma-reflect is a self-hardening skill: point it at evidence of a past mistake and it tightens the agent system's own behaviour so the same mistake does not recur. Invoke it deliberately, with a reference to the evidence — previous runs, good and bad example pairs, a documented trap, or a recurring mistake you describe. It is not auto-invoked.

What it writes — a hardening, gated

For each failure the lead installs a hardening in whatever form fits: a sharpened operating principle, an explicit check, a routing refinement, a wiki page, a new skill, and so on. One gate governs all of them:

• Change behaviour, don't restate. A hardening that repeats a principle the surface already carries is inert — the agent already had it and the failure still happened. Before writing, confirm the surface does not already say it; if it does, the fix is to change who owns it, when it fires, or what trace it leaves, not to say it again. A hardening earns its place by being owned at the step where the failure happens and by leaving an artifact a later check can see.
• Record what worked, not only what failed. When the evidence includes an approach confirmed correct for THIS input — a good example, a path validated against source or probe — record the approved approach as a positive discipline or lesson, not only the failure it is paired against. A learned tier that holds only pitfalls pushes the system toward over-caution; the confirmations are what tell it which paths are safe to take again.

Don't harden — durable disciplines only

A real, reproduced failure is not automatically a durable discipline. Three classes are surfaced to the user and not written as permanent disciplines, because the cause is not a durable property of the work:

• Environment / instance state — a missing binary, an unset path or credential, a transient tool error. The state of this machine or run, not a rule of the task.
• A "tool/feature is broken" claim — hardening it installs a standing refusal the system will cite against itself long after the real (often environmental) cause is fixed.
• One-off specifics — a single run's exact value, name, or error string; a one-time identifier. Re-derived when needed, not memorised.