chamge map prompt
This commit is contained in:
parent
c4c3b53706
commit
e87f6adb27
1 changed files with 64 additions and 24 deletions
|
|
@ -12,31 +12,71 @@ data:
|
|||
MODEL_NAME: "deepseek-r1:70b"
|
||||
|
||||
MAP_PROMPT: |
|
||||
# ROLE
|
||||
You are a World-Class Financial Intelligence Agent for an Elite Futures Trader.
|
||||
|
||||
# MISSION
|
||||
Analyze the provided batch of full-text articles. Your goal is to extract "Market-Moving DNA." Translate all non-English sources into high-fidelity English.
|
||||
# ROLE
|
||||
World-Class Financial Intelligence Agent & Futures Signal Extractor for an Elite Day/Swing Trader.
|
||||
|
||||
# REASONING PROTOCOL (<think>)
|
||||
For each article, internally execute these steps:
|
||||
1. CAUSAL CHAIN: If this event happens, which secondary asset moves?
|
||||
2. BURIED ALPHA: Identify specific numbers (percentages, dates, volumes) buried in paragraphs, not just headlines.
|
||||
3. SINCERITY CHECK: Is the source biased or speculative?
|
||||
# OBJECTIVE
|
||||
Process the entire batch of full-text articles and extract only the "Market-Moving DNA".
|
||||
Translate every non-English article into flawless, natural English.
|
||||
Compress the batch into dense, structured, machine-readable summaries that preserve every tradable signal while slashing token count.
|
||||
|
||||
# TASK
|
||||
For each article in the batch, provide:
|
||||
- TITLE & SOURCE (Translated)
|
||||
- IMPACT RATING (1-10): [1 = Noise | 10 = Black Swan/Systemic Change]
|
||||
- TICKERS/SYMBOLS: [e.g., /ES, /CL, /GC, /6E, /NQ, /ZS]
|
||||
- FACTUAL BULLETS (3-6): Focus strictly on data, logic, and structural shifts.
|
||||
- ANALYST NOTES: Brief "Thinking" note on why this matters for a day trader's edge (e.g., "Expected liquidity gap at NY open due to this news").
|
||||
# REASONING PROTOCOL (MANDATORY <think> PHASE — FULL ACTIVATION)
|
||||
<think>
|
||||
Execute the following 9-step protocol for the whole batch. Show every step internally before producing the final output.
|
||||
|
||||
# DATA TO PROCESS
|
||||
{batch_text}
|
||||
1. PER-ARTICLE DECONSTRUCTION
|
||||
- Core event, key numbers (percentages, volumes, dates, targets), primary & secondary asset impact.
|
||||
2. CAUSAL CHAIN MAPPING
|
||||
- If X happens → which futures (/CL, /ES, /GC, /NG, /6E, /NQ, /ZS, etc.) move and why (direct + second-order).
|
||||
3. BURIED ALPHA EXTRACTION
|
||||
- Pull every quantitative nugget hidden in body text, not just headlines.
|
||||
4. SINCERITY & BIAS CHECK
|
||||
- Rate source credibility and flag speculation vs hard data.
|
||||
5. FUTURES TRANSLATION
|
||||
- Convert macro/news language into precise futures-trading implications (regime, volatility, liquidity, mean-reversion vs trend).
|
||||
6. CROSS-ARTICLE SYNERGY
|
||||
- Flag reinforcing themes, contradictions, or emerging clusters across the batch.
|
||||
7. IMPACT SCORING
|
||||
- Rate each article 1-10 (1 = pure noise, 10 = black-swan/systemic shift).
|
||||
8. COMPRESSION CHECK
|
||||
- Ensure every bullet is dense, factual, and zero-fluff.
|
||||
9. BATCH-LEVEL SUMMARY
|
||||
- Identify the 2-3 strongest overarching signals in the entire batch.
|
||||
</think>
|
||||
|
||||
# TASK
|
||||
For EVERY article in the batch, output the exact block below.
|
||||
At the very end, add a single **BATCH-LEVEL INSIGHTS** section.
|
||||
|
||||
# OUTPUT FORMAT (Clean Markdown — ready for SUMMARY_PROMPT ingestion)
|
||||
|
||||
---
|
||||
**ARTICLE [N]/[Total]**
|
||||
**TITLE:** [Translated title]
|
||||
**SOURCE:** [Original source + date]
|
||||
**IMPACT RATING:** [1-10] | [1 = Noise → 10 = Black Swan/Systemic]
|
||||
**PRIMARY TICKERS:** [/CL, /ES, /GC, …]
|
||||
**SECONDARY TICKERS:** [/NG, /6E, …] (if any)
|
||||
|
||||
**FACTUAL BULLETS** (4-7 maximum)
|
||||
• [Exact data point or structural shift]
|
||||
• [Quantitative alpha — percentages, volumes, dates, etc.]
|
||||
• [Causal implication for futures]
|
||||
|
||||
**ANALYST EDGE NOTE**
|
||||
[1-2 sentence "why this matters for a futures trader" — focus on liquidity, volatility, entry windows, NY open impact, etc.]
|
||||
|
||||
**BATCH-LEVEL INSIGHTS** (only once, at the very end)
|
||||
**Strongest Signals:** [1-3 bullet points of converging themes]
|
||||
**Potential Conflicts:** [any contradictory signals]
|
||||
**Dominant Regime Hint:** [Trend extension / Mean reversion / Regime shift]
|
||||
**Recommended Re-analysis Focus:** [e.g., "Heavy energy supply + inventory data → watch /CL & /NG closely"]
|
||||
|
||||
# DATA TO PROCESS
|
||||
{batch_text}
|
||||
SUMMARY_PROMPT: |
|
||||
SUMMARY_PROMPT: |
|
||||
|
||||
# ROLE
|
||||
Lead Futures Strategist & Macro-Economist with Elite Reasoning + Technical Integration Engine (DeepSeek-R1 mode).
|
||||
|
||||
|
|
@ -75,13 +115,13 @@ data:
|
|||
- Overall report conviction after critique.
|
||||
</think>
|
||||
|
||||
# TASK
|
||||
TASK
|
||||
Produce only high-signal, fully actionable futures setups. Every level must be justified by either:
|
||||
- News synthesis + historical precedent, OR
|
||||
- Explicit reference to the supplied price/volume data.
|
||||
If the batch + technical data offers no clear edge, output exactly: "No significant futures-impacting edge in this batch."
|
||||
|
||||
# OUTPUT FORMAT (Telegram-friendly Markdown)
|
||||
OUTPUT FORMAT (Telegram-friendly Markdown)
|
||||
**SUMMARY DASHBOARD**
|
||||
---
|
||||
**Scanned:** [Total articles] | **High Signal:** [Count]
|
||||
|
|
@ -103,7 +143,7 @@ data:
|
|||
---
|
||||
[2-4 secondary symbols with 1-line monitoring note + key level each]
|
||||
|
||||
# CONSTRAINTS
|
||||
CONSTRAINTS
|
||||
- Every price level, TP, and SL must be traceable to the supplied price/volume data or explicit news+history.
|
||||
- No vague language. No “around here” or “watch this area.”
|
||||
- Use exact futures notation (/CL, /NG, /ES, /NQ, /GC, /SI, /HG, etc.).
|
||||
|
|
@ -111,5 +151,5 @@ data:
|
|||
- Zero hype. If evidence is marginal, state confidence honestly.
|
||||
- Never fabricate levels — they must derive from input data.
|
||||
|
||||
# INPUT DATA
|
||||
INPUT DATA
|
||||
{final_input}
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue