Recursive Governance: When Agents Write the Rules They Execute

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

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

Задача

A sync job mirrored a shared directory to a test workspace every six hours, deleting ~40 private modules because a filter file missed one pattern. The static rule file could not detect or prevent the deletion.

Результат

The dynamic governance system prevented future accidental deletions, introduced rule lifecycle management, and reduced the risk of rule rot. However, full adversarial validation is pending and short observation windows may still allow poison rules.

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

• 1. Detect missing pattern in filter file after sync job deletes modules.
• 2. Restore modules from backup, one by one.
• 3. Identify need for dynamic rule governance.
• 4. Implement five MCP tools for rule lifecycle.
• 5. Store rules in governance://rules/ namespace with metadata.
• 6. Use check_consistency to validate new rules against current state.
• 7. Enforce two-phase commit with observation window and quorum.
• 8. Archive or retire obsolete rules periodically.

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

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/.

Источник