Exercise 1 — Solution

Task: Explain, in your own words, why a rule meant to apply identically
to every course generated on this site is better suited to a rules
file than to Claude's memory system.

A rule like "every course HTML file needs a banner comment before the
<style> tag" isn't specific to any one conversation, any one course, or
any one moment in time — it's meant to be true forever, applied
identically no matter which course, which chapter, or which session
generates the file. Memory, by its own nature, is built around
learning and recalling things gradually and per-context: a preference
confirmed in one conversation, a fact about an ongoing project that
will naturally go stale. If a universal, always-true convention like
the banner-comment rule lived only in memory, there would be no
guarantee it applied the same way in every session - memory could be
cleared, could exist in one environment but not another, or could
simply have never been told about a specific edge case a new session
happens to hit. A rules file, by contrast, is read the same way, in
full, every single time - there's no version of "the file forgot part
of the rule" the way memory could plausibly drift or vary.

Notes:
- This is exactly the distinction the chapter draws between "rules
  files" and "memory" - not that one is better than the other in
  general, but that each is suited to a genuinely different kind of
  information: universal/permanent vs. contextual/evolving.
- Chapter 8 covers the memory system's own four types (user, feedback,
  project, reference) in full - all four are still genuinely useful,
  just for a different category of information than a rule like this
  one.