The job Qurxa is doing
Qurxa reads option shorthand, natural language, and screenshots, then pulls the scenario into the calculator fields. That includes ticker, type, strike, expiration, stock move, stock price, Greeks, and implied volatility when those values are present.
The goal is not to make input feel formal. The goal is to let a trader describe the scenario in the way they naturally think about it and still end up with a usable estimate.
Why spoken-style parsing matters
Real users do not always type in chain-style shorthand. They say things like stock at 350, stock price is 350, or implied volatility 38. Qurxa needs to understand that because voice input and casual typing are both part of how people actually use tools on mobile.
That is why the recognition map keeps expanding beyond just symbols and rigid syntax.
What screenshots should show
Future blog images here should show two things side by side: the raw screenshot or spoken-style text, and the populated OptionsPeek fields after Qurxa has interpreted them. That will make the value of the engine instantly obvious.
Those screenshots should be local assets with the OptionsPeek watermark applied consistently.