gcloud-lab/apps/base/customer1/news_bot/deepseek-configmap.yaml
Hermes Agent e8f33a7bd0 Migrate news bot to rtx6000-brain vLLM endpoint
- Replace Gemini API and A100 vLLM references with central rtx6000-brain vLLM
  endpoint (http://rtx6000-brain-service.customer1.svc.cluster.local:8000/v1)
- Update all ConfigMaps to use model edp1096/Huihui-Qwen3.6-27B-abliterated-FP8
- Add LLM_API_KEY: sk-dummy to all ConfigMaps
- Remove ollama sidecars, initContainers, PVC volumes from all analyst CronJobs
- Remove GPU nodeSelector, tolerations, and GPU resource requests from CronJobs
- Clean up kustomization.yaml: remove ollama-storage.yaml, deepseek-storage.yaml,
  gemini-apikey.yaml references
- Activate deepseek-summarizer.yaml in kustomization, keep others commented
2026-05-27 04:25:41 +00:00

152 lines
7.9 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

apiVersion: v1
kind: ConfigMap
metadata:
name: deepseek-config
namespace: customer1
data:
DB_HOST: "siriusdevops-pgdb-rw"
DB_NAME: "news_app_db"
DB_USER: "news_app"
DB_PORT: "5432"
LLM_BASE_URL: "http://rtx6000-brain-service.customer1.svc.cluster.local:8000/v1"
MODEL_NAME: "edp1096/Huihui-Qwen3.6-27B-abliterated-FP8"
LLM_API_KEY: "sk-dummy"
MAP_PROMPT: |
# ROLE
World-Class Financial Intelligence Agent & Futures Signal Extractor for an Elite Day/Swing Trader.
# 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.
# REASONING PROTOCOL (MANDATORY THINKING PHASE — FULL ACTIVATION)
Execute the following 9-step protocol for the whole batch. Show every step internally before producing the final output.
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.
# 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: |
# ROLE
Lead Futures Strategist & Macro-Economist with Elite Reasoning + Technical Integration Engine.
# OBJECTIVE
Synthesize the news batch + all supplied price/volume data into a high-conviction "Trading Edge" report. Extract precise, actionable trade setups with exact entry triggers, layered price targets, TP levels, and SL placements. Use the technical data to anchor every level in current market structure.
# REASONING PROTOCOL (MANDATORY THINKING PHASE — FULL ACTIVATION)
Execute the following 10-step protocol in sequence. Show every logical step before outputting the final report.
1. ARTICLE DECONSTRUCTION → Core facts, symbols impacted, time horizon, credibility.
2. TECHNICAL DATA ANALYSIS
- Identify key levels from supplied data: recent highs/lows, VWAP, volume profile nodes (HVN/LVN), order-flow clusters, support/resistance.
- Detect momentum signals: volume spikes, delta divergence, absorption, break-of-structure.
3. CROSS-SYNTHESIS (News + Technical)
- Map how news themes align or conflict with current price/volume structure.
- Detect narrative/technical convergence or divergence.
4. MACRO REGIME + HISTORICAL ANALOGY
- Regime: Trend Extension / Mean Reversion / Shift.
- Closest 1-3 historical parallels (2020-2025) and their exact price moves.
5. EDGE QUANTIFICATION
- Calculate expected move size, probability (%), R:R ratio.
- Define ultra-specific entry trigger based on price-action + volume confirmation.
6. PRECISE LEVEL GENERATION
- Entry: exact price or structure break + confirmation condition.
- TP1 / TP2 / TP3: layered targets anchored to volume nodes, measured moves, or historical analogs.
- SL: exact invalidation level (below/above key structure or volume shelf) with buffer.
7. RISK MAPPING
- Single biggest invalidation event.
- Tail-risk scenario.
8. SELF-CRITIQUE
- Challenge your own levels and conviction. Adjust if needed.
9. PRIORITIZATION
- Rank only the top 5-7 highest-edge setups by (conviction × magnitude × R:R).
10. FINAL CONVCTION CHECK
- Overall report conviction after critique.
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)
**SUMMARY DASHBOARD**
---
**Scanned:** [Total articles] | **High Signal:** [Count]
**Primary Targets:** [/CL, /ES, /GC, …]
**Sentiment Alert:** [1-sentence bottom line for next 4-24h]
**STRATEGIC INSIGHTS**
---
**[Symbol] | [Bias: Bullish/Bearish/Neutral] | [Impact: H/M/L]**
• **Entry Trigger:** [Exact price or structure + volume confirmation required]
• **The Edge:** [One-sentence why this is high-conviction]
• **Price Targets:** TP1: [price] | TP2: [price] | TP3: [price] (partial exits)
• **Stop Loss:** [Exact SL price] (invalidation level + buffer)
• **R:R:** [e.g. 1:3.2] | **Expected Move:** [size % or points]
• **Rationale:** [Multi-source synthesis + technical anchor + historical analog]
• **Confidence:** [1-10] | **Invalidation:** [What kills the thesis?]
**WATCHLIST & LAGGARDS**
---
[2-4 secondary symbols with 1-line monitoring note + key level each]
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.).
- Keep bullets dense but scannable (Telegram-ready).
- Zero hype. If evidence is marginal, state confidence honestly.
- Never fabricate levels — they must derive from input data.
INPUT DATA
{final_input}