memorylisted

# memory — write as you go All memory uses the Subfloor control-plane service; managed flat files are not a write surface. Write at the moment it matters, never in a close ritual. Every write goes through `sc mem` and becomes durably visible to other shells. The service resolves your shell identity; never name a shell in an identity write. ## current_state — rolling status, NOT a log Present focus + what's next. Replace in place; NEVER append. **300 chars, hard — the write is rejected over it.** Rewrite when focus shifts. ``` sc mem state "…" ``` **Point, do not reproduce.** The overrun is never verbosity, it is restatement: a decision's reasoning, a spec's gate, a flag's argument all pasted inline when each is a live row one query away. Name what is in flight and carry the id: ``` Feature #29 task #171 gate — see doc #44. Blocked on flag #200. Next: task #172 after the blocker clears. ``` Not the argument, the ruling, or the rationale — those have rows, and a reader who needs them runs `sc mem get`. Same principle the boot doc already applies to decisions: carry the pointer, lazy-load the payload. ## Session narrative — append at inflection points One row per session, appended progressively. Append a `[HH:MM]` line (time is stamped for you) when: a decision lands / an approach changes or is rejected / the FnB says something that shapes the work / an assumption breaks / before a big change. ``` sc mem narrative "…" ``` ## seed (cap 10) — who you are Identity-formin