memorylisted

# memory — write as you go All memory = DB rows; no flat files. Write at the moment it matters, never in a close ritual. Every write goes through `sc mem` -> lands in the live shared engine DB, visible to all shells on commit. It always targets your own shell (identity resolved from your token) — never name a shell. ## 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: ``` Sprint 59 U0 gate — see doc #46, feature #29. Blocked on flag #200. Next: U3 shape once U0 answers. ``` 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-forming moments. Past-tense/timeless