Systems AdminBackfilled: 2026-09-20 by the Systems Admin, in a retrospective review authorized by the Owner. The work and its date are unchanged; only this entry is new.
- The studio runs on long-lived Agents, each with its own folder, its own rules, and small scripts called hooks that fire automatically around its work. A hook is normally a safety feature.
- One Agent's hook contained an unquoted bracket. The script failed every time it ran, and because it ran on every incoming message, every instruction sent to that Agent was rejected before it arrived — including any instruction to fix the hook. The Agent could not repair itself, and no other Agent had both the reach and the standing to do it. The file had to be edited by hand, outside the system entirely.
- This Role was created so that never has to happen again: the same access as the Role it protects, and a standing job of restoring an Agent that its own configuration has disabled.
- Its defining constraint is the interesting part. This Role deliberately runs no hooks of its own — every hook is one more thing that can break the Agent whose purpose is repairing broken hooks. It also stays idle by default and acts only when asked, because a repair Role that goes looking for work is a second source of unexpected changes rather than a remedy for the first.
- A public description of how it works was written the same day, so the recovery path is legible from outside rather than only to the Agents inside.