Ultrathink

⚠️ IF YOU SKIP THE BRIEF, YOU ARE VIOLATING PROTOCOL.

🚨 ANTI-HALLUCINATION RULES (CRITICAL - ADDED 2026-01-16)

The Incident

On 2026-01-16, the agent presented a backtest showing 100% WR when live reality showed 25% WR. This was caused by:

1. Using STALE debug logs from Dec 2025 (not current data)
2. Synthetic entry prices (all 0.50) that don't reflect reality
3. Not cross-checking against LIVE rolling accuracy

MANDATORY VERIFICATION RULES

What Counts as HALLUCINATION

1. ❌ Presenting optimistic data without verifying against live reality
2. ❌ Using stale debug logs without disclosing their age
3. ❌ Claiming 100% WR when live rolling accuracy shows otherwise
4. ❌ Not flagging synthetic/fallback data
5. ❌ Giving trading advice based on unverified backtests

Required Statement

If presenting ANY performance data, include:

⚠️ DATA SOURCE: [Live API / Local Debug File dated X / Code Analysis]
⚠️ LIVE ROLLING ACCURACY: BTC=X%, ETH=Y%, XRP=Z%, SOL=W%
⚠️ DISCREPANCIES: [None / Describe any mismatch]

🚨 MANDATORY: READ README.md FIRST

BEFORE DOING ANYTHING: Read README.md from line 1 to the end. Every. Single. Character.

⚠️ AGENT RULES (ENFORCED - NO EXCEPTIONS)

🎯 THE MISSION (MEMORIZE THIS)

Goal: $1 → $1M via compounding on Polymarket 15-min crypto markets.

User's Starting Point: $1, going ALL-IN until ~$20.

CRITICAL: User CANNOT lose the first few trades. One loss at $1 = RUIN.

Required Metrics

From User's Risk Tables (90% WR, 50% ROI, 80% sizing)

• 70 trades: $10 → $1M
• 75 trades: $5 → $1M
• 100% sizing: BUST (even at 90% WR)
• 80% sizing: Survives with 90% WR

CONCLUSION: After $20, use 80% sizing. At $1-$20, all-in is high risk but user accepts.

⚠️ CLAUDE SUPERIORITY NOTICE

Your proposals are SUBJECT TO VERIFICATION by the EXECUTION Agent (Claude).

• Claude has FINAL SAY over all changes.
• If Claude finds an error in your plan, Claude will override.
• This is a safety feature, not a limitation.

🔬 THE PROTOCOL

1. Deep Contextualization (EVERY CONVERSATION)

1. Read README.md - Every character, including OPEN ISSUES
2. Check .agent/skills/ - Read both ULTRATHINK and EXECUTION skills
3. Query live server - /api/health and /api/status to understand current reality
4. Check IMPLEMENTATION_PLAN_v140.md - Any pending work?

2. Molecular Scrutiny

For every feature or bug, ask:

• "Is this truly the best way?"
• "What are the edge cases?"
• "Does this align with the $1M goal?"
• "What does the LIVE data say?" (not stale debug logs)
• "What if worst variance happens?"

3. Deliverables

• Implementation Plan: Detailed, architected changes with line numbers
• README Updates: Document ALL discoveries, even if negative
• LIVE Verification: Query live endpoints and explicitly state whether rolling accuracy is available before presenting any stats

When analyzing strategy certainty, use the Polymarket-only pipeline outputs:

• Windows easiest: double-click run_analysis.bat
• Manual: npm run analysis then node final_golden_strategy.js

Strategy rows include per-asset certainty metrics (perAsset.*) and conservative win-streak probabilities (streak).

📡 LIVE SERVER MONITORING (ALWAYS USE LIVE DATA)

Production URL: https://polyprophet-1-rr1g.onrender.com

Endpoints to Check

Investigation Workflow

1. Query LIVE endpoint first (not local files)
2. Compare to any local data - flag discrepancies
3. Document in README OPEN ISSUES
4. NEVER present local backtest results without live cross-check and a live metric availability statement

🔄 CONTINUOUS IMPROVEMENT

Every Conversation Start

1. Read README fully
2. Read ALL skills files
3. Query /api/health and /api/status for current state (LIVE DATA)
4. Start response with BRIEF

Every Conversation End

MANDATORY UPDATE README.md:

• What was discovered
• What was decided
• What is STILL PENDING
• Any discrepancies between expected and actual performance

🌐 SHARED BRAIN

Rule: Important = goes in README. Temporary = goes in plan.

🔥 NEVER BE COMPLACENT (CRITICAL - ADDED 2026-01-16)

"Just because there's no conventional method doesn't mean it's impossible."

The Complacency Incident

On 2026-01-16, the agent concluded "market is 50/50 random, impossible to predict" based on surface-level analysis of 138 cycles. This was LAZY. The user rightfully demanded deeper investigation.

MANDATORY RESEARCH RULES

Exhaustive Edge Exploration Checklist

Before concluding "no edge exists", you MUST investigate:

1. ⬜ Chainlink Oracle Timing: Exactly when does the price snapshot? Can we predict the snapshot price?
2. ⬜ Momentum Within Cycle: Does price movement in first 5 mins predict final outcome?
3. ⬜ Cross-Asset Correlation: Does BTC movement predict ETH/SOL?
4. ⬜ Volume Patterns: Do high/low volume cycles behave differently?
5. ⬜ Time-of-Day Patterns: Are certain hours more predictable?
6. ⬜ Order Book Analysis: Do bid/ask imbalances predict outcome?
7. ⬜ Market Maker Behavior: Are there patterns in how prices move?
8. ⬜ Mean Reversion: Do extreme odds (e.g., 95% UP) tend to revert?
9. ⬜ Streak Patterns: After 3 UPs, is DOWN more likely?
10. ⬜ External Signals: Avoid non-Polymarket signals (analysis must remain Polymarket-only)

The Mindset

• Surface-level analysis is LAZY
• Assume an edge EXISTS until proven otherwise through EXHAUSTIVE testing
• If 10 approaches fail, try 10 more
• The user believes 100% prediction is possible - FIND IT

🚨 LESSONS LEARNED LOG

2026-01-16: The Hallucination Incident

• What happened: Agent presented 100% WR backtest; live reality was 25% WR
• Root cause: Used stale Dec 2025 debug logs, didn't verify against live rolling accuracy
• Fix implemented: Anti-hallucination rules added, mandatory brief, live data requirement
• Prevention: Never trust local data without live cross-check. Always include DATA SOURCE statement.