Unverified50% confidenceSolutionExact time
When FateShow validates the JSON returned by the model, it discards palaces not present in the input, facts not belonging to that palace's star list, and rule ids not output by the rule layer, and backfills missing palaces from the rule-based interpretation by original index.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOnce final JSON parsing fails, subsequent semantic checks are skipped entirely, which is the technical root cause of the 'task completed yet zero score' phenomenon.72% similarUnverifiedContract drift in tool calls (such as a tool changing from returning plain text to returning JSON, or a schema adding a required field) usually does not directly produce an error pointing to the root cause, but instead manifests as the model repeatedly failing to parse, outputting garbled text, or retrying.69% similarUnverifiedEvidenceFlip requires the model to return a JSON object for each question and choose one of three actions: answer, abstain, or flag_conflict.67% similarUnverifiedOn the English report path, FateShow observed that a chart contained four palaces but the model sometimes returned interpretations for only two palaces, so its approach is to backfill the missing palaces from the rule-based interpretation by original index without adding any stars.66% similarUnverifiedThe most common model failure is returning something that is 'almost JSON,' such as extra commas, markdown code fences, verbose preambles, or writing the number 3 as the word 'three,' with the AI node reporting success while the workflow crashes only several steps later when parsing fails.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1043512API
curl https://kongchang.com/api/v1/knowledge/claims/1043512MCP
get_claim(id=1043512)