Strength Analysis vs Structure Analysis in Bazi
Compare what strength and structure analysis measure, keep their outputs separate, and integrate them through an explicit policy rather than a hidden score.
Overview
Strength analysis and structure analysis answer related but different questions in Bazi. Strength analysis (旺衰, wàng shuāi) estimates relative support, pressure, and effective capacity around the Day Master or another declared reference. Structure analysis (格局, gé jú) asks what principal organization is formed through Month Command, Ten-God relations, required members, damage, rescue, purity, mixture, or special conditions. A strong Day Master is not itself a structure, and a named structure does not remove the need to test capacity and operability. A reliable workflow calculates each conclusion from its own evidence, then states whether strength constrains structure, structure sets priority, or the methods remain parallel. Disagreement must remain visible rather than being averaged into an opaque score.
At a glance
- Strength question
- Relative support, pressure, and effective capacity
- Structure question
- Formation, organization, function, damage, and rescue
- Shared evidence
- Season, roots, revelation, Ten Gods, and relations
- Distinct outputs
- Strength state versus named organizational form
- Integration need
- Declared priority, constraint, and conflict policy
- Cannot imply
- One universal score, personality, or guaranteed outcome
Begin with two distinct questions
Strength asks how much effective support and pressure a reference receives under season, roots, revelation, and relations. Structure asks whether a defined organization is formed and can perform its function.
Write the question and output type before calculation. Shared inputs do not make the conclusions interchangeable.
- Do not use strength as a structure name.
- Do not treat structure as proof of capacity.
Maintain separate evidence ledgers
For strength, record season, roots, support, output, wealth, control, transformation, and effective action. For structure, record candidate, required members, formation, damage, rescue, change, and mixture.
Mark evidence used by both methods so it is not counted twice as independent confirmation. Preserve disputed thresholds and formation rules.
- Publish two traceable evidence paths.
- Avoid double-counting shared symbols.
Declare how the methods interact
One school may use strength as a prerequisite for structure, another may let structure set the useful function, and another may keep both outputs parallel. Name the adopted policy and source.
When conclusions conflict, show the exact decision point and offer separate scenarios. Do not average incompatible categories into a percentage.
- State priority and revision rules.
- Keep unresolved conflicts visible.
Keep both labels technical and provisional
Strong, weak, successful, damaged, pure, or mixed are chart-model terms. They do not describe human worth, health, leadership, morality, wealth, relationship quality, or destiny certainty.
Use direct evidence for real decisions and revise the reading when inputs or method definitions change. Neither framework validates deterministic prediction.
- Technical labels are not identity judgments.
- No life guarantee from method agreement.
Sources and editorial basis
- 《子平真詮》 (True Explanations of Ziping)《子平真詮》的月令、格局、成敗、喜忌與救應材料支持格局分析回答結構如何成立，而旺衰只是其中一組力量證據A major reference for month-command, structure, and contextual Bazi interpretation.
- 《滴天髓》 (Dripping Heavenly Marrow)《滴天髓》及註本的月令、根氣、氣勢、體用與流通材料支持旺衰分析回答力量如何分布，但仍須回到全局功能A core later text on Bazi balance, seasonal strength, and relational reading.
- OpenFate Editorial Methodology旺衰與格局比較頁使用同一命盤、同一層級與可追溯證據分別作答，禁止互相替代、混成單一分數或直接輸出人生吉凶OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.