CORE · STATE

Replicate semantic state instead of guessing the screen.

State v2 describes what the terminal is now: cells, cursor, modes, title, working directory, and logical-line relationships are protocol objects.

State model

The authoritative engine maintains primary and alternate screens while preserving Unicode graphemes, wide characters, styles, wrapping, hyperlinks, cursor state, terminal modes, title, and current working directory.

Validate and commit

The client validates structure, size, chunk order, and SHA-256 before publishing a received object. Only then are the primary screen, alternate screen, history boundaries, and metadata atomically committed to the Replica.

Generation identity

Every state carries an epoch and generation. They let clients reject late data from old connections and verify that a Replica belongs to the current authoritative timeline.

Compatibility

Only N-1 clients without the semantic capability enter the isolated ANSI compatibility boundary. The current baseline sends reliable complete states. ACKs, cumulative semantic diffs, and DATAGRAM state delivery are not complete.