# The reset vocabulary splits: "across" for the ask, "wake" for the machinery

Status: accepted (2026-07-16)

The agent-driven context reset renames at every layer, with a deliberate split: the
**operator-facing ask** is `--across` / "commune across (to the next session)" — it names the
outcome (continuity across sessions); the **agent-authored markers, wire envelopes, and code
identifiers** use **wake** vocabulary (`!!wake!!`, `wake_arm`/`wake_fire`, `arm_wake`) — they
mark and carry the *wake message* the next session opens with. The word **"checkpoint" is
purged from agent-facing text** with a hard cutover, no legacy-phrase teaching: Claude Code
now ships an official `/checkpoint` skill, and a shared word for two different resets on one
surface guarantees mis-triggering in both directions.

The wire rename is **staged** (the hook_cmd-LOCKSTEP degrade discipline): this release the
receive side accepts BOTH marker generations and BOTH envelope shapes while the emit side
keeps the legacy envelope keys, because an un-bounced pre-rename resident translate that
meets an unknown envelope key would full-type raw JSON at a post-clear boundary — the exact
inject-race class the stub protocol was built to kill. The emit flips one release later,
when no pre-rename resident can remain. A one-shot rename-everything was rejected for that
skew; keeping the old flag as a taught alias was rejected for the /checkpoint collision.