memory-loop-setuplisted

# Memory loop bootstrap (memory-loop-setup) What you are installing is not files but a **loop**: capture (6 types) → shelf (BRIEF, caps + expiry) → recall (every surface reads it at session start) → judgment (human gate) → new captures. The plumbing lives in `templates/`; this skill is the procedure for planting it in a target repo. ## 0. Confirm the target Confirm the target repo root and **2–5 domains** (e.g. investing · career · projects) with the user — if they already came up in conversation, use those. If the target already has `BRIEF.md` · `open-loops.md` · `sessions/`, **stop and report the current state** (partial installs and upgrades are a human decision). If the target is not a git repo, propose `git init` first — git is the loop's safety net. Done when: path, domains, and file-collision status are each confirmed in one line. ## 1. Plant the files Copy the 7 templates into the target and substitute placeholders — `{DOMAIN_N}` (**duplicate the `## {DOMAIN_N}` section once per domain**) · `{TODAY}` (install date) · `{TODAY+28}` (loop-ROI falsification line = install date + 28 days). If a user domain is itself "meta/system"-like, **merge** it with the fixed `## Meta (loop health)` section (no duplicate sections): | Template | Target path | Role | |---|---|---| | `build_brief.py` | `tools/` | Warm-layer builder (§0 freshness + deadman · open decisions · catalysts · judgments · cards · habit counts) | | `session-card-check.sh` | `tools/` (+`chmod +x`) | Stop hook