Quorum on Mutation
Require multiple consecutive ticks (or runs) to agree before a mutation to durable state lands.
Intent & Description
🎯 Intent
Require multiple consecutive ticks (or runs) to agree before a mutation to durable state lands.
📋 Context
A team runs a long-running agent that is allowed to propose changes to its own durable state — its persistent rules, its memory entries, its operating preferences. Over time the agent revises these to fit how the user actually behaves. Some of those proposed changes come from a single frustrated moment in a single conversation, and the agent has no built-in way to tell a passing reaction apart from a genuine long-term preference.
💡 Solution
Mutation proposals are written to a holding area. A subsequent tick must confirm the proposal (still endorses it given fresh context). After K consecutive confirms, the mutation lands. Explicit user approval bypasses the wait.
Real-world Use Case
- Durable state changes must not capture single-tick confusion.
- Mutation proposals can be held until subsequent ticks confirm them.
- Explicit user approval is available as a bypass for urgent edits.
Source
Advantages
- Reduces transient-confusion mutations.
- Surfaces hesitation: K-1 confirms then a withdrawal is itself signal.
Disadvantages
- Latency on legitimate changes.
- Implementation complexity in the agent’s state machine.