Change Sets

Concept

Change Sets

A Change Set is how Aarmos governs changes to governance itself. Policies, Consequence definitions, and participant bindings are what keep agents inside the lines — so if those rules can be edited live, the safety story has a hole exactly where it matters most. Without a recorded history it would be hard to show which rules were in force when a given action ran, or who loosened them.

A change is therefore its own governed object, moving through a fixed lifecycle.

The lifecycle

  • Draft — edit a proposed version of the rules. Nothing in production is affected.
  • Simulate — replay the draft against real recorded executions and see which past Decisions would have changed from allow to deny, or the reverse, before anything activates.
  • Approve — a person signs off on the exact candidate they reviewed, matched by digest, and the approver may not be its author. The approval is recorded as evidence: who, when, and against which simulation.
  • Activate — the new signed policy takes effect, and only if every gate is satisfied. Blocking findings stop activation outright; advisory findings are surfaced but do not. Every receipt from that point carries the effective policy digest.
  • Roll back — return to the previously activated set. Rollback is recorded as a new forward event, not an erasure. It restores the earlier rules; it does not undo actions already taken under the newer ones.

Change Sets are this lifecycle applied to governance itself. The same stages applied to authoring a single policy are described in policy lifecycle.

Governance history is append-only

Changes made through the supported lifecycle are recorded, and a reversal is added rather than replacing the earlier entry. Integrity checks can detect alteration of the recorded history; they do not show that no change was made outside the supported path, and attributing an approval to a person relies on separately trusted identity.

See the blast radius before you commit

Simulation runs on the same deterministic replay used for counterfactual analysis, so the result is computed from recorded executions rather than estimated. It covers only what was recorded and can be judged; it is not a guarantee about future traffic. It reports how many executions were examined and how many could be judged — the difference between "this change looks safe" and "this change would have denied 41 of the last 1,000 executions, here they are."

Change Sets are available under the Change section of Operations. Related: governance continuity and the policy gate.