Governance rule loading
How a coding rule written once in this repository reaches a Claude Code session editing a file, and why it arrives as three tiers rather than one file
Finished when you can do all of these unaided
- Say which of the three context tiers a given fact belongs in and why
- Explain what a rule's frontmatter paths glob controls and what happens with none
- Trace a rule from its authoring root to the file a session actually reads
Lessons
Glossary 4
No term matches that.
How a rule reaches you
Authoring rootThe tracked source location a maintainer edits and reviews,
distinct from any generated copy of it. First seen in
lessons/0001-rule-arrival.html.
Consumed copyThe generated copy of an authored file that a session actually
reads, kept in sync by a regeneration step. First seen in
lessons/0001-rule-arrival.html.
Paths globA pattern in a rule's frontmatter naming which edited files trigger
that rule to load. First seen in
lessons/0001-rule-arrival.html.
TierOne of three ways a fact reaches a Claude Code session: eager,
glob-matched, or on demand. First seen in
lessons/0001-rule-arrival.html.