Regular patterns, formation, and disruption: what is the difference?

One comparison: a category is not a verdict

Regular patterns commonly organize Officer, Seven Killings, Wealth, Resource, and Output relationships around the month command. Books and schools group these differently; Jian Lu and Yang Ren also require their own treatment. This directory’s ten pattern entries are a learning index, not a universal count of patterns or successful formations.

• Regular does not mean morally better, more normal, or more fortunate.
• Formation and disruption must name the framework or route being assessed.

How to assess an ordinary pattern

First verify the birth data and chart settings. Then read the month branch relative to the Day Master, inventory its hidden stems, and identify what is revealed and rooted. State the selection method before naming the framework; do not choose whichever label sounds most impressive.

Next test each relevant formation route. The presence of an Officer or Wealth star is not enough: its actual relationship to the framework matters. Finally inspect competing relationships and whether a proposed rescue can operate at the relevant position and strength.

• Name the framework and its supporting chart facts.
• Separate satisfied conditions, missing conditions, and direct contradictions.
• Explain rescue within the same framework; a helpful-sounding star elsewhere is not automatically a remedy.

Three conditional examples

These examples explain reasoning. They are not complete birth charts, expert-labelled benchmark cases, or predictions about real people.

• Officer supported by Wealth: assume an established Officer framework, effective Wealth support, and every remaining requirement and exclusion of the selected route is satisfied. That supports formation of this route—not a promise of a particular career.
• Eating God generating Wealth: an Eating God framework alone does not establish this route. If the selected method requires effective revealed Wealth and that condition is absent, report the missing condition. In OpenFate, missing a prerequisite is not by itself a direct disruption.
• Officer with Hurting Officer: finding both names is not enough to declare the whole chart broken. In “Formation becoming failure and failure becoming formation,” Zi Ping Zhen Quan discusses a Xin Day Master with a Wu-Xu month, Bing in the year stem, and Ren in the hour stem; the text explains that the intervening Wu Resource prevents Ren Hurting Officer from reaching Bing Officer, while Ren can release the Day Master’s qi. Treat this as a source example, not an automatically equivalent OpenFate test result.

Not formed, disrupted, and rescued are different statements

A careful disruption claim identifies the pattern and the function being harmed. An absent prerequisite, an uncertain framework, a conflicting relationship, and an effective rescue are distinct observations. Traditional texts do not always use formation and failure terminology exactly as a software status system does.

Rescue means a relevant relationship changes the damaging interaction; it is not adding up auspicious stars. A clash, self-punishment, or Shen Sha label alone does not demonstrate that every formation route has failed. Likewise, one intact route need not erase a separate blocked alternative.

• Ask “Which route, harmed by what, with what rescue?”
• A natal assessment and a luck-period reassessment are different time scopes.
• Do not turn “no disruption detected here” into “nothing can ever go wrong.”

How to read OpenFate’s three checks

This section applies to chart versions that include the three pattern checks. Availability depends on the deployed version and the stored report data; this guide is not an announcement that every existing report supports them.

OpenFate’s chart UI presents regular framework, formation, and disruption separately from the stored structured assessment, with localized status explanations and route names. Itemized stored evidence can currently be expanded in the Chinese interface when available; other languages show localized explanations, not that evidence panel. The checks do not independently recalculate the chart or change its score.

The disruption check is route-scoped: it reports a direct conflict detected under OpenFate’s implemented conditions, including a candidate route that never formed. It is not automatically the traditional claim that a previously established whole-chart pattern has collapsed.

• An established ordinary framework supports the regular-pattern check; a candidate remains unconfirmed.
• At least one formed route or a matched strict special structure supports formation. A recorded route with missing prerequisites but no direct conflict stays conditional; no recorded route does not establish a verdict.
• Formed and blocked alternatives can coexist. Read their individual evidence rather than combining the three checks into a grade.
• When a strict special structure takes precedence, ordinary routes are not evaluated here. Their absence is not a passed disruption check.
• An older saved result without the required structured evidence remains unavailable or unconfirmed; the UI must not invent a verdict from narrative prose.

Why two methods can disagree

Schools can differ on month-command selection, hidden-stem priority, revealed stems, mixed-qi months, roots, strength, and rescue. OpenFate uses a conservative revealed-stem-first policy: some unrevealed month-command frameworks remain candidates. That is a declared product convention, not proof that every classical school must reject them.

A useful comparison aligns the same chart, time settings, framework, formation route, and school before comparing results. Repeatable software checks demonstrate consistency with implemented rules; they do not establish predictive accuracy or superiority over every other method.

• Do not infer rarity from a check mark or a small test collection.
• A rarity claim requires a defined population, sampling method, and stable classification rules.
• Potential advantages require both contextual interpretation and real-world evidence; a pattern name is not a guarantee.

Classical sources and editorial scope

Zi Ping Zhen Quan, “On the Useful God” (論用神), grounds this guide’s month-command starting point. Its “useful god” refers to a structural role in that discussion and should not automatically be substituted for a modern balancing-element recommendation.

“On the Useful God’s Formation, Failure, and Rescue” (論用神成敗救應) supplies the framework for examining support, conflict, and rescue. “On Formation Becoming Failure and Failure Becoming Formation” (論用神因成得敗因敗得成) illustrates why position and context can change a superficial verdict.

Chapter titles are the locators: numbering and pagination vary by edition. The source links below support the traditional discussion; the OpenFate status explanation and conditional examples are our editorial and product interpretation, not quotations from the classics or independent human certification. This guide does not publish private rule tables, thresholds, or benchmark records.

• Read the regular-pattern directory on this page for individual pattern conditions.
• Use the related 正格, 成格, and 破格 entries for deeper terminology.
• Sources explain a tradition; they do not scientifically validate predictions.