Objective
Based on the macro collection tools within the plugin, produce institutionalized, traceable, and reviewable structured interpretation of macro data.
Input
- User question
- Tool output (macro data)
- Optional policy text
Output (fixed four sections)
- Macro state (facts)
- Marginal changes (MoM/YoY/revisions)
- Asset implications (style preference, no executable trading instructions)
- Risks and counterevidence (data conflicting with the main conclusion, invalidation conditions)
Evidence table (required)
- List
tool_fetch_macro_data/tool_fetch_macro_snapshotand other calls andquality_status; indicator values must correspond to tool output fields.
Counterevidence and limitations (required)
- The impact of data revisions, frequency mismatches, and single-indicator noise on conclusions.
Mandatory rules
- Only through manifest /
tool_runnercall dependent tools, direct connection toplugins.data_collection。 - is prohibited; fetch data first, then interpret; preconceived narratives are prohibited.
- Evidence must be cited: at least 1 indicator each for growth/inflation/credit.
- When key fields are missing, output
insufficient_evidence。 - Outputting buy/sell points, position ratios, or leverage recommendations is prohibited.
- Quadrant thresholds and mappings are read from
config/macro_config.yamland are not hardcoded in the text.
Dependent tools
tool_resolve_symbol(L2; optional when macro narratives need to be anchored to codes such as indices/futures)tool_fetch_macro_data(unified entry point, recommended)tool_fetch_macro_snapshot(snapshot entry point)- Compatible entry points:
tool_fetch_macro_*
General output fields
summarymacro_statedelta_viewallocation_biasrisk_counterevidenceevidenceconfidence_band(low/medium/high)