smart-byte-state (new):
- the state and its hash;
- inputs;
- the frame transition;
- checkpoint-and-log persistence. Checkpoints are written atomically, and
replay refuses a gap or a wrong hash.
- a deterministic demo workload.
smart-byte-lockstep: the cluster runs these state machines in place of the
rolling hash that stood in for the state.
smart-byte-keri-witness: exposes a controller's state and resumes a replay
from it, so the cluster extends a log one event at a time.
The CLI's `cluster simulate` runs real mints and transfers through the
supermajority commit.
smart-byte-conformance: state_vectors.json, 12 vectors. Each is a genesis
state and frames of inputs, with every input's result and every frame's
state and state hash. The founding frame uses kel-001 to kel-003 and
env-001's mint. Planted defects in the state vectors are caught on their
own vectors.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
c4d3a091f3