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 detect the missing pattern or test proposed deletions, leading to accidental data loss.

结果

The dynamic governance system prevented the accidental deletion of private modules, reduced manual restoration effort, and introduced auditability, consistency checks, and rule lifecycle management. It also enabled agents to self‑regulate and retire rules, mitigating rule rot.

工作流

• 1. Agents propose new rules via propose_rule, including rationale, owning agent, and affected namespaces.
• 2. Agents amend existing rules via amend_rule, submitting diffs that are diffed and never overwritten.
• 3. Agents ratify proposals via ratify_rule, requiring per‑shard quorum and no outstanding vetoes.
• 4. Agents veto proposals via veto_rule, with justification written to memory for auditability.
• 5. Agents run check_consistency to scan the rule graph, compute embedding similarity, and apply a human‑maintained allow/deny list on tool names.
• 6. Proposals enter a 24‑hour observation window where affected agents can rebut or support via shared memory.
• 7. Once quorum is met and consistency passes, the rule is activated. Rules are archived or retired through scheduled cleanup days.

证据

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 a rule can't be archived, it keeps counting toward quorum and keeps confusing the live ones.

来源