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

来源