working-memory handoff
definitionThe detailed contents of the state-memory file that let the next session pick up exactly where the build left off.
The body of the state memory (Kamae 6): the dense material a fresh agent reads to reconstitute a build's whole state without opening code—sealed decisions, a per-ho log, do-not-rediscover traps, queues, and the practitioner's voice verbatim. Grows by event-gated accretion (light under active oversight, carrying the build when autonomous); the state-memory file that holds it is always present. Hot, non-canonical; kept honest by the freshness and hot / cold rules.
The State Memory File (Kamae 6). The State Memory is the [[kamae-project-framing|Kamae 6]] (framework/structure/kamae-project-framing.md §2.7) document: the single living file the fresh agent reads first, before any code, to reconstitute the whole build state. It always exists, at a fixed path (§10). In pālana its body is the innovation—the working memory that made an autonomous, self-directing, multi-session build possible. Everything else in the pattern is close to standard Ho practice; this file's body is not.