use-lorelisted

# Using Lore Yesterday you and an agent solved something hard. You argued about the edges, you threw away two approaches, and the thing finally worked. Today, new session, you are explaining it again from the beginning — and the agent is not worse. It simply never received what the two of you worked out. The facts may have survived in a file somewhere. **The reason you changed your mind did not.** Lore is a **spec-driven development kit** built for that gap: it turns scattered, tacit project knowledge into **distilled, invariant criteria** that constrain every future decision. Where other SDD kits speak in pure engineering terms, this one borrows a linguistic and epistemic vocabulary — *lore, identity, principles, transmutation, distillation* — to name the same discipline. This skill is the map. It teaches the model and points at the operating skills. Read it before invoking any other Lore skill. > **This skill governs session openings too.** A session that opens — including one resumed from a continuity summary, or handed an unfinished task — resolves what Lore governs its tree **before > continuing**, and loads it silently. In a bot, load its canon > and routing table first. **Do not preload every federated body**: load only the bodies selected by the task, > leaving the rest reachable through the routing table. A change of territory > mid-session (new task type, new tree) re-resolves the same way. *"Finishing what was started" is > not an exemption: continuing is decid