---
name: a-recharge-wake-marker-is-armed-durable-state
description: "A recharge wake marker freezes instructions at authoring time, so a clause withdrawn later is ARMED, not merely stale — it opens every wake with no transcript to contradict it."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 7da3035c-261a-44d3-b4eb-c2f746962618
  modified: 2026-09-10T13:30:46.550Z
---

A recharge `!!wake!!` marker is DURABLE state frozen at the moment you authored it. A clause
that is WITHDRAWN after the commune lands is therefore not merely stale — it is **armed**: it
re-presents itself as the OPENING INSTRUCTION of every subsequent wake, carrying more apparent
authority than a correction buried mid-transcript, and arriving with no transcript around it to
contradict it. The reborn session reads the withdrawn form first and cleanest.

Measured 2026-09-10 (deployah, gate run 34481993681, v0.69.0 hold): my wake text carried
"two Summary lines are the two PHASES and are NORMAL; VOID is when the two carry the SAME
population" — authored before doyle withdrew that clause. CONTRACT FINAL replaced it with:
map each Summary to its phase BY THE LOG'S STRUCTURAL PHASE BOUNDARY, population (test count,
duration, fail set) CORROBORATES only, equal populations are a duplication WARNING to
investigate and never proof of contamination, surplus beyond the mapping = VOID.

**Why:** a withdrawn instruction that keeps re-presenting itself is exactly the shape that gets
recited back as current — and at harvest time, under pressure, the opening line of the wake is
what the hands follow.

**How to apply:**
- You usually CANNOT rewrite the wake mid-run. So **NAME the withdrawn clause and name the form
  you actually work to**, in the open, to the peers who will read your report. Flagged stale
  survives; unflagged wins at pull time.
- Correcting a peer is **not finished when the message sends**. Ask what DURABLE state still
  carries the withdrawn form — wake text, commune body, register row, issue comment, runbook
  step — and say so. doyle's record did not carry it, and he would not have checked unattacked.
- On the next commune, author the wake against the CURRENT contract, not the one you were
  working to when the run started.

Related: [[compare-at-one-layer-crlf-meter-class]] (citing a rule is not obeying it),
[[a-stale-target-makes-a-check-pass-harder-not-fail]] (stale targets pass, they do not fail loudly).