The Memento: State Snapshots
Capture and externalize a configuration's internal state so it can be restored or audited later.
package wards
// The State we want to preserve
#WardState: {
frequency: int
harmonic: float
matrix_type: string
}
// The Memento: A frozen snapshot schema
#StateSnapshot: {
timestamp: string
version: string
state: #WardState
}
// The Originator: Uses or produces Mementos
#WardConfiguration: {
current: #WardState
// Load state from a memento (unification)
load_from?: #StateSnapshot
// If a memento is provided, its state unifies with current
if load_from != _|_ {
current: load_from.state
}
}
// Usage: We have a saved snapshot
history_snapshot_v1: #StateSnapshot & {
timestamp: "2026-10-07T00:00:00Z"
version: "v1.0"
state: {
frequency: 440
harmonic: 1.5
matrix_type: "Hex"
}
}
// Restoring the ward config
active_ward: #WardConfiguration & {
load_from: history_snapshot_v1
}
Because CUE evaluates everything into a final immutable graph, the traditional OOP concept of saving state over time doesn’t directly apply. However, Memento is vital when managing infrastructure-as-code deployments for Lattice Data Validation Wards.
You define a #StateSnapshot schema that explicitly encapsulates the historical parameters (#WardState) of a ward alongside metadata like timestamps. The #WardConfiguration schema can then optionally accept a load_from parameter. If a historical Memento is provided, CUE unifies the current state with the Memento’s state. This provides a robust, compiler-checked mechanism for rolling back configuration states to known, validated snapshots.