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 accidental deletion of private modules by enforcing consistency checks before rule deployment. It introduced lifecycle tooling, per‑shard quorum, and auditability, reducing rule rot and ensuring only valid rules are enacted.

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

• 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 vote on proposals with ratify_rule, requiring per‑shard quorum and no outstanding vetoes.
• 4. Veto_rule allows a human to exit a rule; justification is logged for audit.
• 5. check_consistency scans the rule graph, computes embedding similarity, and applies a human‑maintained allow/deny list to reject obvious or near‑miss conflicts.
• 6. Proposals enter a 24‑hour observation window where affected agents can rebut.
• 7. Once quorum is met and consistency passes, the rule is enacted.
• 8. Governance rules are stored in governance://rules/, enabling replay and audit of past states.

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

The sync job ran every six hours, mirroring our shared working directory into a test workspace. At 21:47 on a Tuesday, it removed about forty private modules that should have been ignored.

Источник

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.

Источник

The rule set lives as structured memory events in an append‑only namespace: governance://rules/.

Источник