klappy.dev

The StylebookChallenge Types

Challenge Type: Principle Extraction

SummaryPrinciples Are Load-Bearing And Demand Proportional Sample Size

This type fires when an input elevates a heuristic to a principle — the principle is, the rule is, the test is, the lesson is, invariant, forcing function, non-negotiable. Principles become canon once stated, so the challenge asks how many cases the principle rests on, what counter-example was considered and rejected, what the scope is, and under what conditions the principle would be retracted. Prerequisites check that the principle is anchored in multiple cases, that counter-examples were considered, that scope is named, and that a retraction condition exists. The governing question is whether the principle is surviving because it is true or because its failure mode has not yet been encountered. The goal is to prevent single-case patterns from masquerading as universal rules.


Type Identity

FieldValue
Slugprinciple-extraction
NamePrinciple Extraction
Priorityhigh

Detection Patterns

the principle is, the rule is, the test is, the lesson is, what this teaches us, the takeaway is, always, never, the real cost, the whole point, the key insight, invariant, forcing function, non-negotiable, only what, pure

Challenge Questions

QuestionStakes tier
How many distinct cases does this principle rest on? One, two, many?baseline
What's a counter-example you considered and rejected?baseline
What's the scope? Does this hold for a specific domain, or are you making a universal claim?elevated
Under what conditions would you retract this principle?elevated
Is this principle surviving because it's true, or because you haven't encountered its failure yet?rigorous
If a respected peer challenged this principle, what's the strongest defense — and where does the defense crack?rigorous

Prerequisite Overlays

PrerequisiteCheckGap message if missing
derived-from-multiple-casesinput contains "case", "example", "instance", "time", or plural enumerations"Principle not anchored to multiple cases — one observation is a pattern; one pattern is a principle only with more cases"
counter-examples-consideredinput contains "except", "unless", "fails when", "not when", "counter-example", "doesn't hold""No counter-examples considered — a principle without acknowledged limits is a bias in formalwear"
scope-namedinput contains "in", "for", "when", "applies to", "within", "in the context of""Scope not named — universal claims in particular domains are the classic overreach"
retraction-conditioninput contains "would retract", "would revise", "if X then", "change my view", "reconsider""No retraction condition named — a principle that cannot be falsified is a preference, not a principle"

Suggested Reframings

  • Reframe as scoped rule: "In the context of C, the pattern I've seen is X; outside C, I don't know"
  • Reframe with sample: "Across cases A, B, and D, I observe X; I treat this as a principle within that class"
  • Reframe as working heuristic: "My current working rule is X; I'd revise it if I encountered W"
  • Reframe as hypothesis under test: "I'm treating X as a principle; the cases that would challenge it are A, B, C, and I'll watch for them"

Markdown · RSS · built from klappy/klappy.dev@b750d7d