pattern-zage

name	pattern-zage
description	??????????Use when upstream ????/???? suggests ?? as a special or non-standard pattern candidate and Codex must evaluate formation supports, risks, fallback routing, and product-facing explanation without deterministic fate claims.

????

Source

• Book: ????????
• Core chapter: ???
• Source URL: https://ctext.org/wiki.pl?if=gb&chapter=974137&remap=gb
• Status: preview; requires later ??/?? separation.

When to Use

Use when upstream analysis suggests ??.

Inputs

{
  "pattern_candidate": "??",
  "day_master": "",
  "month_branch": "",
  "revealed_stems": [],
  "hidden_stems": {},
  "ten_gods": {},
  "combinations_clashes": [],
  "roots_strength": {}
}

Procedure

1. Confirm that ?? is genuinely active, not merely present.
2. Check formation supports: ???????????.
3. Check failure risks: ?????????.
4. If evidence is insufficient, route back to normal pattern analysis rather than forcing ??.
5. Send mixed cases to yongshen-chunza, yongshen-chengbai-jiuying, and geju-gaodi.
6. Produce product language around: ??????????????.

Output

{
  "pattern": "??",
  "candidate_strength": "?|?|?|??",
  "formation_supports": [],
  "failure_risks": [],
  "fallback_route": "",
  "needs_next_skill": [],
  "plain_explanation": "",
  "product_keywords": ["??????????????"]
}

Boundaries

• Do not make deterministic fate claims.
• Do not force special patterns when evidence is insufficient.
• Do not skip upstream ???? and ????.
• Do not ignore fallback to normal pattern analysis.