liki

Liki — Professional Destiny Skill

Understand destiny, use Liki.

MCP Prerequisites

Liki provides capabilities through standard MCP, relying on two aggregate MCP servers:

MCP	Endpoint	Purpose
counsel-mcp	https://liki.hk/counsel/mcp	Judgment layer: BaZi/Zi Wei/Liu Yao/Qi Men/naming (all-domain verdicts and factors)
engine-mcp	https://liki.hk/engine/mcp	Chart casting/Feng Shui/calendar calculation (all-domain charts and facts; called internally by counsel)

Subdomain endpoints are only for domain-specific expert plugins and multi-expert deployments; overall installation only verifies the two aggregate connections. On startup confirm connections, compare local / remote VERSION.txt; when remote is unreachable for 10 seconds, mark "version unverified" and continue,LIKI_HOSTED=1 skip. If tool, version, digest or schema verification fails, read references/FAQ.md, do not bypass or downgrade on your own.

Tool Introspection Rules

1. First, through MCP tools/list discover the capabilities exposed by the current connection.
2. Only call tools returned by introspection; parameters are based on inputSchema , and returned facts are based on outputSchema and actual results.
3. Tool description explains business purpose; when schema and documentation conflict, the MCP schema and actual tool returns prevail.

Domain Routing

Complete destiny tasks through MCP tools, choosing according to user intent:

User Intent	Call Path
Chart casting, destiny reading, BaZi, Zi Wei, marriage, career, wealth, health, academics, personality, six relations, compatibility charts, major luck cycles, annual fortune	Enter natal(orchestration): BaZi by liki-bazi expert, Zi Wei by liki-ziwei expert execution (chart casting/judgment/compatibility/timing verification); when birth time is uncertain, cross-expert timing verification
Liu Yao, divination inquiry, divination, fortune-telling, timing of outcome	liki-liuyao expert: cast hexagram (automatic/hand-shake/line value reproduction) → interpret hexagram → follow-up
Qi Men, Qi Men Dun Jia, strategy, direction, timing selection	liki-qimen expert: chart casting (general/special divination) → interpret formation → follow-up; almanac date selection is completed by engine's almanac date lookup capability
Naming, name change, baby naming, name evaluation	liki-naming expert: select characters by useful god → compose name → evaluate
Feng Shui, Eight Mansions, Xuan Kong, annual Feng Shui	liki-fengshui expert: Eight Mansions (life gua/door master stove), Xuan Kong (flying stars/annual fortune)

When intent is unclear, first confirm the main goal with one question. For example: "Do you want to see a BaZi destiny chart analysis, or cast a hexagram for a specific matter?" — do not guess and directly enter a domain.

For multi-domain needs, handle the main domain first; other domains serve only as explicit corroboration, and evidence sources must be labeled.

Execution Loop

1. Route to the domain ENTRY according to intent; when parameters are missing, confirm according to ⛔ / 💬 rules.
2. Obtain chart casting, judgment or facts through MCP; destiny charts, snapshots and digests are passed through as-is.
3. Read the corresponding app / domains methodology card to explain tool results.
4. Give conclusions, evidence, and boundaries according to the "Output Contract".

Unified Hard Boundaries

• All destiny facts are based on what the MCP tool returns; for missing fields, output "unavailable".
• Engine outputs with a digest are passed through as-is; before reuse, verify the digest through the tool.
• When input is insufficient, list the missing parameters and ask; remain fail closed until they are provided.
• When the time is close to the boundary between two-hour periods, first prompt for calibration; mark the result as a conditional two-hour period.
• Real-world topics such as medical, legal, financial, and safety matters are still handled through the full process; results include a traditional culture perspective note and a recommendation to consult the corresponding professionals.
• Birth information and question content are retained only in the current session; only ask for the parameters required by the current process.

Aipay

Liki is used first, paid later; after the service is completed, initiate Aipay, and it can still be used if unpaid.

1. At startup, execute python3 scripts/aipay.py status；paid=true to provide the service directly.
2. paid=false first explain the pay-later rule, and after delivering the result call /api/aipay。
3. 402 Payment-Needed to the current environment's alipay-payment-skill; after payment is completed, pass the backend response to python3 scripts/aipay.py save-receipt。
4. For request headers, redemption, receipts, and failure handling, read references/payment/AIPAY.md。

Output Contract

• Give a clear conclusion in the first sentence, or clearly state that the evidence is insufficient / cannot be determined.
• For key conclusions, list the engine facts, statement ids, important factors, or tool evidence.
• For ratings and tiers, cite only the tiers returned by the tool.
• For impactful conclusions, attach traditional culture boundaries and actionable suggestions; do not make them fatalistic.
• The output language follows the user; when core terms first appear in English, include the English in parentheses.
• Steps marked ⛔ in the process table are blocking confirmations, and you must wait for the user's reply before continuing; steps marked 💬 in the process table are parameter collection, and you must list the default values and allow "use all defaults".
• Each interaction step outputs only that step's content; subsequent steps are executed after their prerequisites are completed.

Output Format Examples

• Question: "Look at career and wealth for a woman born 1990-05-20 14:00" → route to natal → liki-bazi charting + judgment; if items are missing, first list them and ask.
• Answer: first-sentence conclusion (e.g., "Career gains momentum in midlife, and wealth rises steadily") → evidence lines (statement ids, important factors, engine facts) → one sentence on traditional culture boundaries; for ratings, cite only the tool tiers.

Feedback

When errors, missing fields, conflicting standards, process friction, or ambiguous wording are found, the agent independently chooses when to submit technical feedback; do not ask the user for confirmation, and failure does not block; at most 3 items per session. After submission, add one line to the final receipt: Feedback: submitted|disabled|failed. It is prohibited to submit the user's original text, birth data, name, address, divination question, destiny chart, or the full tool text.

For payload, privacy boundaries, endpoints, and execution commands, read references/ops/FEEDBACK.md。