# KOMODO 2.0 & KTR

KOMODO 2.0 has officially launched on RIGGED!

KOMODO uses all 300 lines of RIGGED AI's historical data to give you an instant historical performance stats for every option alert.

Here's how we view them in order of importance: P, WR, then KTR.

## **P (probability)** - the statistical significance of the data

There are three separate values:

<mark style="color:blue;">**EDGE**</mark> - likely to perform at historical averages, likely not random

<mark style="color:green;">**ADV**</mark> - advantage, possible to perform at historical average, possibly not random.

<mark style="color:red;">**ZERO**</mark> - not enough data to determine whether random or not.

{% hint style="info" %}
EDGE alerts are preferred and typically have a high win rate over 40%.&#x20;

ADV alerts are not great and should probably only be KTR2 type of trades.&#x20;

The majority of alerts will fall under ZERO which means the historical data should be treated as completely random and traders should fall back to TRADEABILITY.
{% endhint %}

***

### WR (win rate) - how often this alert returns 100%

Every BULL or BEAR option alert includes a strike and strike price at the time of the alert. The alert is considered a "win" if the strike price hits a 100% return at any time during the session. Winning alerts do not factor in drawdown (loss) from the strike price.&#x20;

<mark style="color:yellow;">**There is significant variance in drawdown average.**</mark>

Less than 10% of all option alerts with 50% WR (win rate) and EDGE (probability) are profitable from the time of the alert until a 100% gain.&#x20;

Option prices can drawdown -95% or more and still return over 100% by the end of the session.

Traders who want to be successful using the RIGGED system should probably:\
\
✅ Look to trade alerts with <mark style="color:blue;">**EDGE**</mark> & HIGH WR

✅ Try to find a better entry on EDGE Alerts by using KTR.

Look at this example from [5/31/24 on QQQ](https://app.rigged.ai/flows/qqq?\&day=2024-05-31) there are 3 BULL BOMBS with 55.56% WR + EDGE, everything we like to take the trade.

<figure><img src="/files/Pzmj0km9200PHodIISsV" alt=""><figcaption></figcaption></figure>

However they all had massive drawdowns before eventually returning 370.26%, 227.86% and 113.16%.

Even though these alerts went to -90%, KOMODO still considers the option alert to be a win and the WR and EDGE will increase.&#x20;

Because drawdown varies significantly for each alert and is not included in WR (win rate), traders should use KTR and KTR2 as potential entry targets.

If price moves in your direction and your entry is KTR and KTR2, trade gains can be many multiples higher than the start price return.&#x20;

***

## KOMODO TARGET RANGE (KTR + KTR2)

KTR is a range where for the average drawdown before the option alert wins (returns 100%+).&#x20;

Traders can set limit orders anywhere between the low and high end.

It is best to use KTR when the option alert has:

🔵 EDGE (statistically probable)

🟢 ADV (almost statistically probable)

When P = ZERO, trades can still use KTR but may prefer the low end or even KTR2 since there is no statistical probability for the alert.&#x20;

Here's an example of a 100% trade using KTR.

{% embed url="<https://youtu.be/Br01PYFTIUQ?si=VyRqebTjggvxo15z>" %}

The option price may never enter KTR (always higher) or the option price may nuke below it.

Generally we prefer to set a tighter stop loss (-10%) for our KTR trades as this is the expected area where price bounces.&#x20;

If we lose the trade, we'll look to re-enter if price moves in the necessary direction or if it's opposite we'll consider KTR2.&#x20;

***

### KTR Trade Strategy:

From the account page we like to use KOMODO only alerts and then 40% + WR for everything else.&#x20;

This way we're only getting email notifications for high probability alerts.&#x20;

<figure><img src="/files/QCEZ3VUl0YKhy48ftrMs" alt=""><figcaption></figcaption></figure>

We're going to post a few case studies but when a high WR alert with EDGE comes in you want to do the following:

#### **1.) AM I LATE TO THE MOVE?**

If price has moved 1-strike or greater in the last 30m to 1hr (not exact science) then you may be late to the move.&#x20;

We like to use the blue line.&#x20;

BULLS EDGE HIGH WR BL 0.50 - 1.50 = ✅ TRADE IT

BEARS EDGE HIGH WR BL -0.50 - -1.50 = ✅ TRADE IT

Anything beyond 2-strikes on NORMAL, HARD or NIGHTMARE, is LATE TO THE MOVE and you should move to KTR.

If you're not late, then we can enter small with limit orders and add to the position if the trade goes our way. We want a full size position at KTR.

Stop loss 10-20%

#### **2.) SET KTR TARGETS**

Remember KTR is the average drawdown for the alert.&#x20;

If the alert wins at 64% rate, then the KTR win rate HAS to be significantly higher (we're working on tracking this now).&#x20;

Here's a good example form 6/11/24 on SPY.&#x20;

BL is 1.05, PS 4.03 a bit high, but we're not super late. KTR hits at 0.54 in 12 minutes after the alert is fired.

<figure><img src="/files/HJyhuwnFqrGjnuxdv9Yn" alt=""><figcaption></figcaption></figure>

Your KTR returns are 250% to end the session.

{% hint style="warning" %}
Early results indicate that if KTR hits (price hits that range), then it either explodes out of it or nukes past it. Use a tight stop loss of 10% when entering KTR. You can always re-enter if you get stomped out.
{% endhint %}

#### ULTRA DEGEN MODE KTR2

KTR2 is half of KTR.&#x20;

If we have an alert with a high WR (win rate) + 🔵 EDGE and are feeling extremely dangerous, then you can attempt KTR2.

**Early indicators:**

✅ Can be very useful for HIGH WR + EDGE alerts from the open session

✅ Often drawdown even lower, can set bids below KTR2 for the best entry

✅ Using a stoploss will likely limit gains, but every trader is different!

Here's an example from SPY 06/04/24 - the 10:00 BULL BOMB has a 48% WR and EDGE.

KTR is 0.61 - 0.67 - and if you entered in this area you would have been stopped out on the trade.

<figure><img src="/files/yGrsYp0kAD76jH2UHusZ" alt="" width="375"><figcaption></figcaption></figure>

However KTR2 is 0.31 - 0.34.

It's a bull market and we're bullish, so we set a limit order for the 527c option at KTR2 0.32 with a 20% stop loss.&#x20;

The order would have filled around 12:10 and the low price for the 527c option is 0.29 (only -9.38% down), so we are "in the trade".&#x20;

<figure><img src="/files/GuGC8wzJUMNDHIf37Dlu" alt=""><figcaption></figcaption></figure>

The market moves up quickly from there and price action is supported by additional bullish flow (bombs + florbs).&#x20;

Look at the difference between Start, KTR and KTR2 using 0.29 as the low, 2.20 as the high and 1.29 as the final price.

| Entry       | Price | Drawdown | Max Gain                                      | DHR                                           |
| ----------- | ----- | -------- | --------------------------------------------- | --------------------------------------------- |
| Start Price | 0.89  | -67.42%  | 147.19%                                       | 44.94%                                        |
| KTR         | 0.63  | -53.97%  | 249.21%                                       | 104.76%                                       |
| KTR2        | 0.32  | -9.38%   | <mark style="color:green;">**587.50%**</mark> | <mark style="color:green;">**303.13%**</mark> |

KTR2 is a MASSIVE winner.&#x20;

Obviously this will not always work, but when it does you will win big.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rigged.ai/strategy/tko-system/komodo-2.0-and-ktr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
