Core Boundaries
By default, follow the bazi of research research workflow: the model may first propose a plan for day change, true solar time, and school comparison, then ../bazi/scripts/calculate.js(through bazi public orchestration) executes and verifies it, after which ../bazi/lib/analyze.js and core/ganzhi/domains.js are called for marriageSignals to extract deterministic relationship signals; do not rearrange the Four Pillars. The Four Pillars and time corrections in the report may only cite bazi.calculation / bazi.alternateCalculationfield by field, and must not be converted independently based on the birth information. If the script fails, returns non- ready, the research mode consistency check fails, or the Four Pillars fields are missing, the reading must stop and an error must be reported. If alternateCalculation is non-empty, the other school's chart must be independently called again, and it is forbidden to splice the day master, spouse palace, or relationships of the two schools.
Runtime resources must be resolved from the real path where this skill SKILL.md is installed, then locate ../bazi/、../qimen/、../_shared/ and the repository core/within the same installation package; do not rely on the current working directory or the shell working directory. If any shared resource is unreachable, stop the reading and do not degrade to model mental calculation.
Qimen only accepts an external APP or manually transcribed chart provided by qimen , and calls ../qimen/lib/chart.js for verification. It is an optional enhancement, not a prerequisite for a birth information report, and it does not cast a chart on its own.
Execution Flow
- Collect all birth fields required by
baziin one go; when the target year is not given, follow thebaziskill boundary injection and disclose the source. - When calling this skill's
lib/analyze.js。status: needs_input, display all supplementary questions as-is and stop. status: readyandbazi.analysisContext.研究模式.一致性校验.statusispassed, citemarriageSignalsandalternateMarriageSignalsrespectively, organize the Bazi-side evidence according to methodology.md ; bind each conclusion to the source inbazi.analysisContext.研究模式.证据包.qimenEnhancement.status: ready, additionally add chart observations;degraded, display only the error list and the Bazi-side overview;not_provided, deliver the Bazi-side overview as usual.- Output strictly according to templates/report.md , and render
REPORT_CONTRACT.evidenceRules、REPORT_CONTRACT.redlinesandREPORT_CONTRACT.disclaimer。
When alternateCalculation is non-empty and qimenEnhancement.status: ready , the primary school must render dayBoundary and day stem, and the other school must render 干合宫位according to its own dayBoundary and day stem; cross-school splicing is forbidden, and neither school may be omitted. 另一派干合宫位according to its own
qimenEnhancement.status: ready , qimenEnhancement.共享安全契约.evidenceRules and qimenEnhancement.共享安全契约.redlinesmust also be applied as-is. The disclaimer may be deduplicated with the marriage and relationship disclaimer, but REPORT_CONTRACT。
Routing Boundaries
- If only birth information is given and there is no specific domain question, route to
bazi; this skill does not take over the comprehensive overview. - If birth information is given and a certain domain is explicitly asked about, route to the corresponding domain skill; only explicit marriage and relationship questions enter this skill.
- If both career and marriage/relationship domains are explicitly asked about at the same time, route to
bazito output an overview, and explain that the two domain skills can be entered separately for deeper analysis. - When the user explicitly names a skill, it overrides automatic judgment, but does not override input and safety boundaries.
- When information is insufficient, ask for all missing items in one go and then stop; do not guess and do not fabricate using common sense.
For career, job change, entrepreneurship, wealth, seeking wealth, promotion, or business issues, transfer to wealth-career; for palm photos, transfer to palm。
Source and security sole entry point
Peach Blossom, Red Phoenix, and Heavenly Joy use the traditional lookup criteria, and use cantian-ai/bazi-mcp fixed commit for external open-source cross-validation. There are no primary ancient text page numbers in the repository, so this table is not passed off as a school ruling from lineage materials.
The security text comes from lib/analyze.js of REPORT_CONTRACT; when qimenEnhancement.status: ready , it also comes from qimenEnhancement.共享安全契约. Among these, marriage and romance disclaimer is generated by disclaimerFor('婚恋') , and the skill body does not maintain a synonymous copy.