Recursive Governance: When Agents Write the Rules They Execute

说明与用途

一个动态规则治理系统，允许代理提出、修改和批准规则，通过一致性检查和规则生命周期管理，防止了40个模块的意外删除。

问题

A static sync filter file caused accidental deletion of ~40 private modules because it missed a pattern after a directory restructure.

结果

The dynamic governance system prevented the accidental deletion of private modules by enforcing consistency checks on sync filter rules. It also introduced mechanisms for rule lifecycle management, reducing rule rot and ensuring clarity of active rules.

工作流

• 1. Agent proposes a rule via propose_rule with rationale, owning agent, and affected namespaces.
• 2. Agent amends existing rules via amend_rule; deltas are diffed, never overwritten.
• 3. Agents ratify proposals with ratify_rule, requiring per-shard quorum and no outstanding vetoes.
• 4. Veto_rule allows a human to exit a rule, with justification logged.
• 5. check_consistency scans rule graph, computes embedding similarity, and applies an allow/deny list to reject proposals that would let an agent touch disallowed namespaces.
• 6. Two-phase commit: observation window (24h or N messages) for rebuttals, then ratification.
• 7. Governance rules stored in append-only namespace governance://rules/, with parent references for replay.
• 8. Periodic cleanup to retire obsolete rules and archive them.

证据

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

来源

The filter file was missing one pattern. That's it. One pattern.

来源

The script didn't warn, didn't ask, didn't fail. It just mirrored the state it was told to mirror.

来源

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

来源

check_consistency scans the existing rule graph, computes an embedding similarity between the new rule surface and the rule surfaces already in effect, then applies a short, human-maintained allow/deny list on tool names.

来源

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

来源