Purpose

Use a small topic-keyed MEMORY.md hub with single-topic spokes in an authorized storage location. Verify how the selected host loads and retrieves them rather than assuming a universal directory, startup behavior or limit.

The kit's 24,000-byte hygiene budget is local policy, not a vendor loader specification. Hub bullet content after the marker is at most 250 Unicode code points on one physical line; move details into spokes instead of indented continuations. Keep mission, authoritative architecture pointers, scoped preferences, debt and references before brief active-work orientation.

templates/hooks/memory-budget-check.sh advises on size, long entries and continuations. Configured unreadable input is unassessed. It returns zero, and plain Stop-hook output may be debug-only. It neither blocks completion nor proves loading, retrieval, correctness or warning delivery. A topic catalogue from templates/scripts/gen-memory-index.sh aids navigation, not permissions or automatic recall.

A hub is a topic index, not an accumulating session journal. Remove resolved orientation while retaining needed evidence in its authoritative system. Keep useful lessons only when persistence and the destination audience are authorized. See Appendix D.