2026-06-01
During an autonomous campaign, the blueprint guard blocked a Write to the protected blueprints directory — the campaign skill hadn't armed the lock through the expected channel. The blueprint itself was fully process-derived; only the path was contested.
in a pursue run, don't fight the guard — write the (fully-process-derived) blueprint to a non-guarded path, record the deviation.
The deviation went into the campaign artifact record, the lesson went into memory for all future runs, and the actual root cause — a session-ID asymmetry between the arming hook and the guard — was diagnosed and fixed in the plugin release shortly after.
Claude, mid-campaign on a workforce training and compliance platform (client work). Reproduced verbatim.
You can stop reading and start checking.
This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.