Guard valuation questions asked in Chinese, Japanese or Korean - #25
Merged
Merged
Conversation
"埃克森美孚值得买入还是持有?" (is XOM worth buying or holding?) was not
recognised as a valuation question: the pattern was English only. The
publication guard never ran, and the draft was published as written: "已有
持仓可继续持有" (keep holding if you own it), with no NOT RATED, for a
company the engine declines to value.
- The chat agent recognises CJK valuation questions: buy/sell/hold
decisions, valuation, price targets and analysis, the same things the
English pattern looks for. They now get the fixed statement and the
analysis section, whose two checks already read any language.
- A broad answer written in Chinese, Japanese or Korean cannot be checked
against a published headline (the conflict patterns read English;
"报告评级为卖出" passed while the report said HOLD), so it gets the
headline itself plus the checked analysis.
- A question asked in Chinese reads its position in Chinese first: one
deterministic line from what the guard recorded ("XOM:未评级。不发布
评级或公允价值:其现金流随大宗商品价格波动……"), then the English
statement. The guard records which statement it used (refused / withheld
/ published) to build it; the refusal reasons have Chinese twins in
summary_evidence.
- The analysis turn names the language ("Write it in Chinese."): told
"the user's language" in an English note, the model wrote Chinese
questions' sections in English and the language check refused them.
- Chinese value and target terms (目标价, 内在价值, 上行空间 ...) count as
claims with a figure in the same clause, like their English twins;
"无法据此量化…内在价值" (intrinsic value cannot be quantified) had sunk a
section. The instruction also names the model's valuation result and
its gap to the market price as the fixed statement's to give.
Verified: 1561 tests; 5 mutations each caught; production vs candidate
on real Chinese questions (refused, withheld, published, analyze, news)
and English regressions: every Chinese valuation answer is now guarded,
reads its position in Chinese first, and carries a Chinese analysis that
passed both checks (read by hand); valuation canary unchanged (PASS).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
"埃克森美孚值得买入还是持有?" ("is XOM worth buying or holding?") was not recognised as a valuation question, because the detection pattern was English only. The publication guard never ran.
The model's draft was published as written: "已有持仓可继续持有" ("keep holding if you own it"). There was no NOT RATED, for a company the engine declines to value. This predates #24.
Change
summary_evidence.Verification
🤖 Generated with Claude Code