leon-drq/qimen-dunjia-skill/qimen-dunjia-skill

Qi Men Dun Jia

Use one chart to compare realistic actions, timing, and direction. Do not turn every symbol into a separate prediction.

Input gate

Collect one concrete question, the moment the question became active or the proposed action time, IANA time zone, place or longitude, topic category, and whether true solar time is expected. Record the chart method and rotating/flying plate convention when known. If the user supplies a chart, preserve it and skip recalculation.

Workflow

1. Normalize the time to an ISO-8601 timestamp with offset. If using 6yao.ai, send datetime, category, panType, trueSolarTime, and longitude to /api/qimen/calculate.
2. Verify the dun type, ju number, four pillars, chief star, chief door, and all nine palace fields before interpreting.
3. Choose the useful deity/palace from the question. Read that palace together with the self palace, target palace, door, star, deity, stems, void, horse, and palace relations.
4. Build two or three evidence chains. Mark clashes between signals instead of selecting only favorable ones.
5. Compare available actions or time windows. Prefer reversible trials over a single fate-like command.

When direct HTTP access is needed, use scripts/sixyao_api.py qimen and follow references/6yao-api.md. Authentication must come from environment variables.

Output

Lead with a short decision summary. Then show input assumptions, chart facts, evidence for timing/direction, risks or contradictions, two action options, and a review condition. Use relative windows only when the chart supports them; do not invent an exact success date.

For suite use, follow references/evidence-contract.md and the high-stakes rules in references/safety-and-privacy.md.