Challenge 1 — Solution

Task: Explain, using P1 and P5, why the banner comment at the top of
this chapter's own file and the prompt "rules1-3" contain overlapping
but not identical information (both reference the course and chapter,
but only one contains a date).

P1 and P5 solve two genuinely different problems, which is exactly why
their information overlaps but isn't identical.

P5 is a REQUEST format - a short, terse shorthand a human types to ask
for a specific chapter to be generated. "rules1-3" only needs to
identify WHICH chapter is being asked for (course "rules1", chapter 3)
- nothing else. It doesn't need a date, because a prompt is typed once,
in the moment, and isn't meant to be a permanent record of anything.

P1 is a RECORD format - a permanent, self-documenting comment that
lives inside the generated file itself, forever, long after the
original prompt that created it is gone from anyone's memory. Its job
is different: not just "which chapter is this," but "what course, what
snappy chapter title, what topic, and when was this file created versus
last actually edited." The Date Created / Date Updated fields exist
specifically because a file can be edited long after it was first
generated, and P1 wants both facts preserved - something a one-off
prompt like "rules1-3" was never designed to capture at all.

Notes:
- Both do share the identical course/chapter identity (rules1, chapter
  3) since the banner is directly derived from the prompt that
  requested it - but the banner also has to add a genuine, human-
  readable Chapter title ("The Permanent Rules File: P1-P13") that the
  terse prompt never contained in the first place.
- This is a good example of the more general pattern in this whole
  rules system: a short, ephemeral trigger (a prompt) versus a durable,
  self-contained artifact (a file) - the same distinction Chapter 1
  drew between memory and rules files, just applied one level down to
  a single generated chapter instead of the whole rules system.