CORE · STATE
Replicate semantic state instead of guessing the screen.
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. State ACKs and cumulative semantic diffs are implemented. Version 1.2 uses Quinn and enables bounded DATAGRAM v3 fragments with current rootless/managed servers after full negotiation; older servers retain DATAGRAM v2. Baselines, repairs, and oversized states still use reliable channels. An older server missing dependencies permits only a pre-authentication reliable re-offer, never a bypass of certificate or authentication failures.