Refuted Doctrines
Last updated 5/21/2026
Not every inherited rule deserves equal weight.
One of the strengths of the Wen Wang Gua case tradition is that it does not merely preserve rules. It argues with them. Some methods survive because cases support them. Others are rejected because they fail in practice.
That makes this module practical, not academic. A refuted doctrine is a rule you should not let override target selection, calendar strength, line interaction, timing state, or verified case behavior.
Target selection, calendar strength, interaction, transformation, timing states, and verified domain routing.
Methods that sound elegant but produce unreliable results when tested against actual cases.
How to evaluate a doctrine
Identify the text, chapter, teacher, or modern source.
A rule may be valid only for one domain, state, or timing condition.
Verified cases matter more than attractive theory.
If a rule conflicts with target usability, timing state, or verified mechanics, rank it properly.
Common rejected patterns
Repeated casting to force a desired signal corrupts the question.
Broad-life synthesis forces incompatible meanings into one cast.
Names, spirits, images, or auspicious-looking signs cannot override mechanics.
Do not manufacture a hidden target through lookup tricks when the actual selection method has already failed.
Natal branches, yearly markers, or personal labels cannot replace the question-bearing line in a cast.
A line's place in the stack is context, not a universal domain decoder.
Do not turn broad rise-and-fall labels into outcome rules when the target and calendar state say otherwise.
World can matter, but it does not automatically replace the selected target.
Health cases still need patient routing, target strength, support, obstacle, and timing. A named sign is not a diagnosis.
Helpful-looking markers can decorate a reading, but they cannot outrank target usability and interaction.
Response can describe the other side, but proxy questions still route by domain and role.
Month Breaker and void states are serious, but the course still checks rescue, release, and timing before declaring impossibility.
Do not let line text or mutual-hexagram symbolism replace the Six Lines mechanics used in this course.
The rejected-doctrine list is not a museum of bad ideas. It is a practical safety rail. If a rule bypasses question screening, target selection, calendar strength, line interaction, or verification, it should be treated as suspect until cases prove otherwise.
Trap
Do not turn skepticism into shallow debunking. A doctrine is rejected because it fails a method standard, not because it is old, symbolic, or unfamiliar.
The posture is conservative: keep what verified cases support, reject what breaks the workflow, and do not rescue a failed shortcut just because it occasionally sounds right.