# "Recharge" names the reset; "commune across" is accepted, not taught

Status: accepted (2026-09-09) — supersedes the **naming half** of ADR-0009. The wake/machinery
split that ADR established (`!!wake!!`, `wake_arm`/`wake_fire`, `arm_wake` for markers, envelopes
and code identifiers) is untouched and still governs.

The agent- and operator-facing name for the self-initiated context reset becomes **recharge**
(`--recharge`, "recharge"). `--across`, "commune across" and "across-commune" remain **silently
accepted** — understood wherever they are written, refused nowhere.

The rename is worth doing because ADR-0009's `--across` names the *file mechanism* ("a commune,
carried across") rather than the outcome, and it reads as a departure. Agents repeatedly treated
it as a signoff and avoided it out of fear of losing their perch — the exact opposite of what it
does, since the perch and the Psyche stay up throughout and the agent comes back lean. "Recharge"
names what happens to the agent, and nothing about it suggests going offline.

**The retirement is staged, and the staging is the decision.** ADR-0009 chose a hard cutover for
"checkpoint" and was right to: that word collided with Claude Code's own `/checkpoint` skill, so
every surviving occurrence was a live mis-trigger. This rename has no collision — the old spelling
is merely older — and the population that still writes it is unreachable by any release, because
peers carry it in durable context (roles, communes, briefs already ingested into their minds). A
hard cutover here would refuse the request of an agent doing exactly what its own memory taught it
last week. The knock rename is the cautionary case in the other direction: spt-core 0.54.0 renamed
the directionality flags with no aliases, and text teaching the old spelling stopped being stale
and became a hard parse error.

So both halves are guarded rather than one (`tests/recharge-vocabulary.sh`, `REQ-RECHARGE-VOCABULARY`):
every taught surface must name `recharge`, **and** no taught surface may present the old spelling as
current usage — naming it as the older/accepted one is correct and stays legal. Without the second
half the staging silently becomes a no-op, leaving two live spellings and no signal about which one
an agent should write.

**History is left alone, deliberately.** Shipped `CHANGELOG.md` sections, prior ADRs, `docs/plans/`
and the root JIT plans describe what shipped under the name it shipped under; rewriting them would
make the release notes lie about their own releases. **Requirement ids are not renamed** — an id is
identity, so renaming one is a delete plus an add that orphans every tag pointing at it. The
`REQ-*-COMMUNE-*` ids keep their spelling, and `REQ-RECHARGE-VOCABULARY` is the single authoritative
statement that the taught name has moved.

Completing the retirement — refusing `--across` — is a later release, once peers' durable context
has rotated. The precedent to respect is that the wake rename took three stages and shipped its
retirement forty releases late; the lesson recorded there is to grep `ci/` and `tests/` for a wire
token before retiring it, not just `src/`.