update

templates/Prompt/Relevance-Research.md

@@ -11,8 +11,10 @@ Relevance:
 
 Rules:
 - These subblocks **all already** belong to the topic — the question is not *whether* but *how central*. Judge **core vs. peripheral within its own block**, one at a time.
-- `peripheral` is a **genuine category**, not a leftover bucket. Deliberately mark peripheral items (nice-to-know, special/niche cases, detail/numeric examples, historical notes, cross-references) as `peripheral`.
-- Don't bump the level up out of caution. Only **true core concepts / central theorems** are never `peripheral`.
+- **The basic syntax / core rule of a block — what the block TITLE promises — is NEVER peripheral.** A block "Headings" without its heading syntax marked relevant is broken. Check this per block before anything else.
+- **When the BLOCK itself is a fringe/extension feature** (non-standard, niche, an add-on rather than core of the topic), only its basic syntax and purpose are relevant — its detail rules and special cases are `peripheral`. A fringe feature must not be decomposed deeper than the core topics (measured: a non-standard block carried 22 "relevant" detail rules while core blocks had 6).
+- `peripheral` is a **genuine category** for clear cases: nice-to-know, special/niche cases, detail/numeric examples, historical notes, cross-references, style tips.
+- `peripheral` items are CUT from the focused guides — a wrong `peripheral` loses content, a wrong `relevant` only adds a paragraph. **When in doubt → relevant.**
 - Only judge — invent nothing, change no subblocks.
 
 Reply with ONLY the JSON — no other text, no code fences.