CN equity track

Opening request

Establish identity and source authority first.

The compact status for this track looks like CN · CNY · Asia/Shanghai · src:<percent>% · feat:<percent>%. src is evidence maturity; feat is installed feature breadth for this track only. Neither is a completeness or correctness verdict.

Exact identity

Do not guess from a ticker-shaped string.

• A mainland listing is a six-digit code plus venue and board: SSE/XSHG, SZSE/XSHE, or BSE/XBSE. A code alone is not an identity.
• Preserve leading zeroes, Chinese names, short names, share class, and historical aliases. Return ambiguity instead of choosing a preferred venue.
• Name-to-code discovery uses Tushare when configured. A known exact code, including an already-identified ETF such as 588000, can use the Eastmoney history path without Tushare.
• The reviewed SSE STAR 50 index can use Sina history only after an Eastmoney failure is reported and the user explicitly selects Sina in a separate request. Neither call proves the index identity by itself.
• CNINFO catalogue identity is repository evidence. It does not prove an SSE, SZSE, or BSE venue, an effective listing interval, or session status.
• A/H and Stock Connect relationships stay explicit two-leg facts. They never merge a CN observation into HK or the reverse.

Canonical route

Move through four evidence phases.

Follow-up requests

Keep later questions on the same receipts.

Provider truth

Keep these limitations in the answer.

• Eastmoney access is public-web, read-only local analysis; rights and service-level facts remain explicitly unknown.
• Sina is a CN-only daily-history alternative that is never selected automatically. An Eastmoney failure may suggest it, but the user must choose Sina in a new call; its adjustment remains provider_defined and its service level, rights, redistribution, and correction behavior remain unknown.
• Production provider adapters share their named process-local quota across independently loaded Pi and DSH shells. Eastmoney and Sina admit one request per two seconds with one request in flight, bounded waiting, and no automatic retry; other providers retain their own declared quotas.
• A known exact code can use cn_raw_vendor_history with Eastmoney alone, including an already-identified ETF such as 588000. That raw route does not prove security kind or currency.
• For a name-only request, resolve identity at most once when the name-to-code mapping is uncertain. A known exact code bypasses cn_stock_symbol_search; its TUSHARE_TOKEN is not needed for Eastmoney history.
• Tushare Pro requires a caller-owned token and explicit provider selection. Its daily row is end-of-day, not a real-time claim.
• CNINFO is used only for explicitly requested announcements, disclosures, filings, or event evidence. It is never a prerequisite for quotes, OHLCV, or technical indicators.
• After OHLCV returns, use the installed sma, rsi, and atr tools instead of writing a calculation program. Do not calculate instructionRef: omit it unless a real retained hash already exists, and the tool derives a deterministic request reference. Raw-basis roots copied during handoff are preserved as context evidence and do not block calculation. Compact results give the LLM the latest and requested prior numeric values while the TUI keeps a concise first line; they retain exact receipt handles without duplicating full receipt envelopes. Request intermediate projection only for full-series drill-down.
• Questions such as whether to buy now, what happens if you buy now, or when to sell trigger read-only evidence gathering: exact identity when needed, current quote, bounded recent OHLCV, and relevant installed indicators. The LLM still owns the conditional recommendation; that decision boundary is not a reason to skip tools. Trade-plan and bar-path tools are used only when their exact required risk facts or proposed order are available.
• T6 accepts an explicitly selected, caller-supplied CN transaction-tape capability packet. Futu OpenD or another provider adapter remains external and is never bundled, authenticated, or silently selected by Sparkles.

Runtime configuration

Only configure adapters you intend to select.

These variables belong to the selected local host process—not this website, a prompt, a receipt, or source control. Values must never enter model context.