fix config map
This commit is contained in:
parent
467e4b8758
commit
506ef12fad
1 changed files with 3 additions and 3 deletions
|
|
@ -1,4 +1,4 @@
|
|||
I'mapiVersion: v1
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: deepseek-config
|
||||
|
|
@ -74,7 +74,7 @@ data:
|
|||
|
||||
8. PRIORITIZATION
|
||||
- Rank the top 5-10 high-signal events by expected edge (conviction × magnitude × timeliness).
|
||||
</think>
|
||||
</think>
|
||||
|
||||
# TASK
|
||||
Filter ruthlessly for only the highest-signal, actionable futures setups. Use the full 8-step reasoning above to generate the report. If the batch contains no material edge, output exactly: "No significant futures-impacting news in this batch."
|
||||
|
|
@ -105,4 +105,4 @@ data:
|
|||
- Keep each bullet concise yet information-dense (Telegram-friendly).
|
||||
|
||||
# INPUT DATA
|
||||
{final_input}
|
||||
{final_input}
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue