yongshen-chengbai-jiuying

name	yongshen-chengbai-jiuying
description	子平真诠派用神成败救应判断。Use when an initial bazi pattern/useful-god candidate exists and Codex must evaluate 成格、败格、带忌、救应, explain risk and remediation structure, and avoid simplistic good/bad fortune claims.

用神成败救应判断

Source

• Book: 《子平真诠评注》
• Core chapter: 九、论用神成败救应
• Source URL: https://ctext.org/wiki.pl?if=gb&chapter=974137&remap=gb
• Anchor phrase: 全凭救应

When to Use

Use after yueling-quge has produced at least one 格局候选.

Inputs

{
  "pattern_candidate": "",
  "useful_god": "",
  "supporting_gods": [],
  "harmful_factors": [],
  "stems": [],
  "branches": [],
  "combinations_clashes": [],
  "ten_gods": {}
}

Procedure

1. Identify 成格 evidence: what supports the candidate pattern?
2. Identify 败格 evidence: what harms the useful god, pattern, or necessary support?
3. Identify 带忌: is a harmful factor present inside an otherwise workable structure?
4. Search for 救应: 印护、合清、食制、会合解冲、制化、去忌存用.
5. If both support and harm exist, describe the structure as mixed rather than forcing a binary verdict.
6. Translate the result into product language: advantage, bottleneck, and action posture.

Output

{
  "pattern": "",
  "status": "成|败|成中有败|败中有成|待定",
  "success_evidence": [],
  "failure_evidence": [],
  "rescue_evidence": [],
  "plain_explanation": "",
  "action_posture": "主动|保守|先补条件|避开冲突|待时而动"
}

Boundaries

• Do not use 救应 as automatic plus score.
• Do not judge without an initial pattern candidate.
• Do not skip 相神; if a key support is unclear, call xiangshen-shibie.
• Do not make deterministic fate claims.