Use Chinese for analyst reports
Request: - Make analyst reports Chinese by default and record the rule in the analyst skill. Changes: - Add a Simplified Chinese default-language rule to the analyst skill. - Update the single-IPO report generator to emit Chinese Markdown sections, labels, actions, risks, triggers, and exit plans. - Preserve ticker symbols, stage codes, rule ids, score buckets, and source paths as machine-readable identifiers. - Regenerate the 06106 T0 report in Chinese. - Document the Chinese report default in README and the rule change log. Verification: - Ran py_compile for scripts/generate_ipo_report.py. - Generated a 06106 dry-run report and checked Chinese section headings. - Regenerated reports/2026-06-15_06106_T0_prospectus_analysis.md. - Ran git diff --check. Next useful context: - Future analyst prediction and review reports should be written in Simplified Chinese unless the user explicitly requests another language.
This commit is contained in:
@@ -85,6 +85,7 @@ If the ticker is absent from `data/snapshots/analysis_model_v0_dataset.csv`, use
|
||||
|
||||
Generated prediction reports must remain stage-safe:
|
||||
|
||||
- Analyst Markdown reports should be written in Simplified Chinese by default, while preserving ticker symbols, stage codes, rule ids, source paths, and stable error tags in their original machine-readable form.
|
||||
- T0 reports use only prospectus-stage fields and T0 calibration.
|
||||
- T1 reports may add allotment demand fields and T1 calibration.
|
||||
- T2/D1 is the intended sell window; D5/D20/D60 returns are never shown as prediction inputs and are reserved for later review cards.
|
||||
@@ -111,6 +112,11 @@ Every prediction card should include:
|
||||
- explicit T2/D1 sell discipline
|
||||
- source paths
|
||||
|
||||
Language standard:
|
||||
|
||||
- Write analyst reports, prediction cards, and review cards in Simplified Chinese by default.
|
||||
- Keep field identifiers, model versions, score buckets, ticker symbols, and source paths as code-formatted English identifiers when they are part of the project data contract.
|
||||
|
||||
Every review card should include:
|
||||
|
||||
- linked prediction card
|
||||
|
||||
Reference in New Issue
Block a user