Recursive Governance: When Agents Write the Rules They Execute

Описание и применение

Система управления правилами, позволяющая агентам писать и проверять правила, предотвратила случайное удаление приватных модулей, обеспечив контроль версий и жизненный цикл правил.

Задача

A sync job mirrored a shared directory to a test workspace every six hours, deleting about forty private modules because a filter file missed one pattern. The static filter file could not adapt to changes in the source tree, leading to accidental deletion and a two‑hour recovery effort.

Результат

The governance system prevented accidental deletion of private modules by enforcing consistency checks and per‑shard quorum. It also introduced rule lifecycle management, reducing rule rot and ensuring that only valid, audited rules influence agent behavior.

Рабочий процесс

• 1. Detect missing pattern in filter file after repository restructuring.
• 2. Restore deleted modules from backup, one by one, taking ~2 hours.
• 3. Implement a governance system with five non‑removable MCP tools: propose_rule, amend_rule, ratify_rule, veto_rule, check_consistency.
• 4. Store rules in append‑only namespace governance://rules/ with metadata (birth date, parent, owner).
• 5. Enforce per‑shard quorum and observation windows for rule proposals.
• 6. Run preflight pass for sync jobs to abort if deletion target exists.
• 7. Periodically replay governance history to retire obsolete rules.

Доказательства

We almost lost forty modules to a file that never changed.

Источник

The filter file was a static text file. It encoded what the sync could delete and what it couldn't, and it had no idea that the real inventory had changed.

Источник

We gave the agents the ability to write their own rules.

Источник

Governance is five non‑removable MCP tools in our agent runtime.

Источник

If the sync job had this system, the filter file would have been a rule in governance://rules/sync-filters/.

Источник