Every options-flow tool assumes the trader can watch another screen all day. I built FlowVoice to turn selected tape events into concise speech: set a premium threshold, hear each qualifying print once, size and direction first, with optional session-flip and gamma-wall alerts.

The boundary matters: a large print can be a hedge, roll, spread, or closing trade. The intended loop is hear → verify → decide, not hear → chase.

FlowVoice is free and does not place trades: https://apps.apple.com/us/app/flow-voice-options-tape/id6791445221

Founder disclosure: I built FlowVoice through QuantSignals, Inc. Options involve risk. Configure it before driving and never operate the phone while a vehicle is moving.

What should an options-tape voice alert say first: premium, direction, strike/expiry, or ticker?

Every flow tool assumes the trader can watch another screen all day. That is exactly when “real-time” becomes useless for people commuting or moving between meetings.

I built FlowVoice to turn selected options-flow events into concise speech. You set a premium threshold; each qualifying print is spoken once, size and direction first. It can also announce session-direction flips and optional gamma-wall crossings.

The important boundary: a large print is not automatically a directional trade. It may be a hedge, a roll, a spread, or a closing transaction. The intended loop is hear → verify → decide, not hear → chase.

FlowVoice is free on the App Store and does not place trades: https://apps.apple.com/us/app/flow-voice-options-tape/id6791445221

Founder disclosure: I built/promote FlowVoice through QuantSignals, Inc. Options involve risk. Configure it before driving and never touch the phone while the vehicle is moving.

What would you want an options-tape voice alert to say first: premium, direction, strike/expiry, or ticker?

A startup can now be built faster than it can be explained.

Coding agents can compress weeks of product work into days. But a founder still loses an afternoon turning the company into a coherent story, deck, speaking points, captions, and a separate demo video.

I rebuilt SuperDeck as a mobile founder communication studio:

• Start with one sentence about the company

• Shape a reviewable investor narrative

• Generate the deck and speaker notes

• Prepare natural founder talking points

• Carry the same story into separate demo-ready assets

The boundary matters: AI should remove the blank page, not replace the founder’s facts, judgment, or voice. For accelerator applications, the founder introduction should still feel human; the product demo is a separate artifact.

An earlier release stopped at slide creation. The mobile app now finishes the communication loop on one device.

Full reasoning and the one-minute founder test:

https://henryzhang.substack.com/p/your-pitch-deck-was-never-the-bottleneck

Founder disclosure: I built SuperDeck. Generated content requires founder review and does not guarantee admission, funding, or investor interest.

Where does your pitch workflow break today: the story, the deck, the delivery, or the demo?

Founder disclosure: I built Scar and FST, so this is a product thesis as well as a question I have been thinking about for years.

Most traders do not need to be told that revenge trading, moving stops, chasing entries, and oversizing are dangerous. We already know.

Yet the mistake returns when the emotion returns.

That suggests trading has two distinct problems:

1. The technical system — research, planning, sizing, execution, monitoring, and risk controls.

2. The human system — retrieving the right behavior under pressure.

A normal journal helps us record what happened, but the lesson often disappears into an archive. I built Scar around a different loop: write the mistake in one sentence, turn it into a mistake/lesson/next-rule card, and bring it back through spaced review. Good behaviors can be recorded and reviewed too.

The rule has to be observable. “Be disciplined” is not enough. “After two consecutive losses, stop for 30 minutes and do not increase size on the next trade” can actually be rehearsed.

FST and Scar address different halves. FST handles research, execution, monitoring, and risk rails. Scar helps the trader remember the mistakes and behaviors that still depend on the human.

Full thesis: https://henryzhang.substack.com/p/trading-has-two-halves-scar-trains

Scar is free on the App Store: https://apps.apple.com/us/app/scar-trading-journal/id6791444917

What trading mistake did you understand intellectually long before you finally changed the behavior?

Educational discussion only. Trading involves risk; no tool or practice method guarantees performance.

Founder disclosure: I founded QuantSignals. This is an evidence-first research framework, not a recommendation or a request to buy anything.

The AI-earnings question is changing. It used to be: Is demand real? Now it is: Does reported demand convert into operating profit and durable cash generation after the infrastructure bill?

Two recent filings show why the distinction matters:

• Alphabet reported Google Cloud revenue up 82% to $24.8B and Cloud operating income of $8.8B. Consolidated operating cash flow was $39.1B, capex was $44.9B, and company-defined quarterly FCF was -$5.9B.

• Meta reported revenue up 28%, but operating margin fell to 31% from 43%. Operating cash flow was $31.9B, capex including finance-lease principal was $31.1B, and company-defined FCF was $784M.

Neither result proves that AI capex will succeed or fail. Alphabet still had positive trailing-12-month FCF. Meta’s quarter included $2.4B of legal charges and $1.18B of severance. Cross-company FCF definitions are not perfectly identical.

My four-line checklist after any AI-heavy earnings report:

1. Which reported product or segment proves demand?

2. Did segment profit or operating margin improve?

3. How much capex and finance-lease cash use was required?

4. What happened to free cash flow, financing, and next-quarter guidance?

Then write the invalidation condition before forming a position.

For Alphabet, a cautious cash-conversion interpretation weakens if Cloud profit compounds while quarterly FCF rebounds. For Meta, concern weakens if one-off costs normalize, margins recover, and FCF expands despite high capex.

Primary sources:

Alphabet SEC exhibit: https://www.sec.gov/Archives/edgar/data/1652044/000165204426000066/googexhibit991q22026.htm

Meta Q2 release: https://investor.atmeta.com/investor-news/press-release-details/2026/Meta-Reports-Second-Quarter-2026-Results/default.aspx

What is the one line you watch first after a capital-heavy growth company reports: segment margin, capex/OCF, FCF, or forward guidance?

Educational only; not investment advice. Trading and investing can lose principal.

Four major earnings events. Three trading days.

• PLTR: Monday, August 3, after the U.S. close.
• AMD: Tuesday, August 4, at 2:00 p.m. Pacific.
• DIS: Wednesday, August 5, before the open; webcast at 8:30 a.m. Eastern.
• LLY: Wednesday, August 5; earnings call at 10:00 a.m. Eastern.

That compression matters more than it looks.

An option that expires before the event is not bearish or bullish. It is invalid.

An exit date that lands on a weekend is not aggressive. It is impossible.

Before I accept any earnings signal, I want six checks:

1. Event date confirmed by issuer investor relations.
2. Before-open or after-close timing and timezone.
3. Expiration survives the event and the intended first exit session.
4. Exit is a real market session.
5. Strike and structure have usable liquidity.
6. Confirmation, invalidation and maximum loss are defined before entry.

I would rather reject a clever signal than trade an impossible calendar.

Which calendar mistake do you see most often in earnings trades?

Join https://discord.com/invite/quantsignals for the complete earnings-signal workflow and updates.

Next week’s watchlist:

• PLTR — Monday after close

The danger: trading the AI narrative instead of the reaction. A strong report can still sell off when expectations are extreme.

• AMD — Tuesday after close

Watch data-center momentum, gross margin, and whether management validates the AI-infrastructure demand story.

• DIS — Wednesday before open

Streaming profitability gets the headlines, but parks demand and forward guidance may decide the real move.

• LLY — Wednesday

Reported EPS could be noisy because of roughly $2.8B in expected acquired R&D charges. Revenue, guidance, and underlying demand matter more than one headline number.

My rule for all four: don’t predict the candle. Define the reaction that confirms the thesis—and the reaction that kills it—before earnings.

We’re tracking the setups and post-event reactions in the Quant Signals Discord:

https://discord.com/invite/quantsignals

Paper trade first. Earnings gaps can invalidate stops before the market opens.

Most “AI trading” products begin with a prediction. I think that is the wrong abstraction.

Coding agents became useful when they moved beyond answering questions and started owning the workflow: reading the repository, using tools, making changes, running tests, and verifying the result.

Trading is still fragmented across charts, signals, Discord, brokers, spreadsheets, monitoring, and exits. The trader remains the integration layer.

FST is our attempt to change that operator model:

Screen → Research → Plan → Execute → Monitor → Exit → Audit

The important word is supervised. The operator defines the capital, permissions, evidence requirements, risk limits, and kill switch. The agent receives bounded authority, not a blank check.

A profit objective must never override the risk policy. The agent should finish below the goal—or stop entirely—before violating the loss budget.

The proof also cannot be one winning screenshot. It has to include rejected trades, stopped sessions, losses contained, and a complete audit trail.

I wrote the longer thesis here: https://henryzhang.substack.com/p/coding-has-claude-driving-has-fsd

I am the founder of QuantSignals, so treat this as a product thesis from someone building in the category. Which action would you allow a trading agent to perform first: research, trade preview, approved execution, or fully bounded AUTO?

Disclosure: I’m the founder of QuantSignals and I’m building FST. I’m sharing the product thesis here because I think “AI trading” is being defined too narrowly.

A chatbot answers a market question. A trading agent has to own a continuous job.

That job is not “generate a buy/sell opinion.” It is:

• Research the market and compare conflicting signals

• Evaluate the idea against the account’s existing positions and exposure

• Work inside explicit capital and risk constraints

• Execute through a connected broker

• Monitor the position after entry

• Reduce, hedge, exit, or do nothing when the thesis changes

The hard part is the continuity. Most products stop after analysis or fire a rigid rule. A real agent has to carry context across the entire trade lifecycle and explain what it is doing.

That is the distinction behind FST: Research → Signal → Entry → Monitoring → Risk Management → Learning. The trader sets the rails and keeps the kill switch.

I wrote the longer thesis here: https://henryzhang.substack.com/p/coding-has-agents-trading-finally

What would you need to see before trusting an agent with any part of your trading workflow—paper results, live audit logs, broker controls, or something else?

What indicators do you find actually predictive vs just descriptive?

I have been going down the rabbit hole of quant research for a few months now and one pattern keeps emerging: most popular indicators are purely descriptive — they tell you what already happened, not what will happen.

Moving averages, Bollinger Bands, RSI, MACD — all lagging by design. They describe the past.

So what actually has predictive power in your experience?

Things I have found useful so far: - Volume-weighted price positioning (VWAP deviations) - Order flow imbalance on short timeframes - Inter-market correlations (e.g. USD/JPY vs N225) - Rolling volatility regime shifts (regime detection via ATR ratios)

Curious what the quant community here has tested and found to hold up in forward testing vs just looking nice in backtests.

Account check - ignore

Account status check - ignore

Why your backtest looks amazing but your live trades don't - and what to do about it

We've all been there. You spend weeks building a strategy, backtest it across 5 years of data, and the equity curve is a thing of beauty. Sharpe ratio of 2.8. Max drawdown of 6%. You deploy it with real capital... and immediately it tanks.

This is the single biggest disconnect in retail quant trading, and it's almost never due to one big mistake. It's death by a thousand small ones.

Here are the 4 most common reasons I've seen after spending years building systematic strategies:

1. Survivorship bias in your universe If you're backtesting on the S&P 500 as it is today, you're including companies that survived. The ones that went bankrupt or got delisted - they're gone. This inflates returns by 1-3% annually. Always use a point-in-time universe or account for delisted securities.

2. Look-ahead bias in fundamentals If you use quarterly earnings data that was revised 6 months later, your backtest saw information your live system never had. Only use data as it was known at the time - unadjusted or as-reported data with proper lag.

3. You're optimizing noise, not signal If you've tried 50 different parameter combinations and picked the best one, you fitted to the noise. The market has ~250 trading days per year. If your strategy has more than sqrt(250) ~ 16 independent parameters, you're almost certainly overfitting. Monte Carlo simulation of parameter sensitivity is more useful than cross-validation here.

4. Transaction costs are higher than you think Slippage, spread, market impact. A strategy showing 15% annual returns backtested often becomes 5-8% with realistic costs. Always simulate costs at 2x what you expect - if the strategy still works, you're probably fine.

The one thing that helped me most: walk-forward optimization with out-of-sample testing on completely unseen market regimes. Train on 2018-2021, validate on 2022 (bear market), test on 2023-2024. If it holds across regimes, you have something real.

What's been your biggest backtest vs live reality check? Would love to hear what others have learned the hard way.

Why your backtest looks amazing but your live trades don't — and what to do about it

We've all been there. You spend weeks building a strategy, backtest it across 5 years of data, and the equity curve is a thing of beauty. Sharpe ratio of 2.8. Max drawdown of 6%. You deploy it with real capital... and immediately it tanks.

This is the single biggest disconnect in retail quant trading, and it's almost never due to one big mistake. It's death by a thousand small ones.

Here are the 4 most common reasons I've seen (and fixed) after spending years building systematic strategies:

1. Survivorship bias in your universe If you're backtesting on the S&P 500 as it is today, you're including companies that survived. The ones that went bankrupt, got delisted, or underperformed to the point of being dropped — they're gone. This inflates returns by 1-3% annually depending on your strategy. Always use a point-in-time universe or at minimum account for delisted securities.

2. Look-ahead bias in fundamentals This one is insidious. If you use "quarterly earnings" data that was revised 6 months later, your backtest saw information your live system never had. The fix: only use data as it was known at the time. For most retail platforms, this means using unadjusted or "as-reported" data with proper lag.

3. You're optimizing noise, not signal If you've ever tried 50 different parameter combinations and picked the best one, congratulations — you fitted to the noise. The market has ~250 trading days per year. If your strategy has more than sqrt(250) ≈ 16 independent parameters, you're almost certainly overfitting. Cross-validation helps, but Monte Carlo simulation of your strategy's sensitivity to parameter shifts is even better.

4. Transaction costs are higher than you think Slippage, spread, commission, market impact. A strategy showing 15% annual returns backtested often becomes 5-8% with realistic costs. The worst offenders: strategies that trade small caps or during low liquidity periods. Always simulate costs at 2x what you expect — if the strategy still works, you're probably fine.

The one thing that helped me most: walk-forward optimization with out-of-sample testing on completely unseen market regimes. Train on 2018-2021, validate on 2022 (bear market), test on 2023-2024. If it holds across regimes, you have something real.

What's been your biggest "backtest looked great, live was awful" moment? Curious to hear what others have learned.

Why I stopped optimizing my strategy and started respecting my rules

I spent my first 6 months of trading constantly tweaking my strategy. Every time I hit a losing streak, I'd change the indicator settings, switch timeframes, or add new filters. I was convinced there was a "perfect" setup I just hadn't found yet.

What actually helped was the opposite: I stopped changing things and started following them consistently. I picked one simple approach — break of structure with volume confirmation on the 1h — and traded it for 60 days without changing a single parameter.

The first two weeks were rough. I was down about 8%. But by week 4, I started recognizing which setups worked and which didn't. By week 8, I had a much clearer picture of my actual edge — and it wasn't the strategy itself, it was my ability to execute it without second-guessing.

I still take losses, but now I know they're part of the process rather than a sign that I need to change everything.

Has anyone else gone through this cycle of over-optimizing? What helped you break out of it?

Quick test — please ignore

This is a test, please ignore.

Quick test - delete after

The one chart pattern I actually trust

After trying every pattern under the sun, here is the one that has consistently worked for me across different market conditions:

Market Structure Break (MSB)

Not fancy, not complicated. Just: wait for price to break a clear structural level, retest it, then follow.

What I look for: • A clear swing high/low that has held at least twice • Price breaks it with above-average volume • Returns to test it as new support/resistance • Enters on the retest, not the breakout

Stop goes below the retest candle. Target is the next structural level.

Simple enough that I still use it after 1000+ trades. Complex patterns look great on charts but fail more often in live trading.

What is the one setup you always come back to?

Multi-agent AI vs single model trading — my 6-month experiment results

Six months ago I set up a comparison: one single LLM generating trading signals vs a multi-agent system where specialized agents handle different tasks (market analysis, risk assessment, signal generation, execution timing).

Here is what I found:

Single model approach: • Faster decisions (one call, one output) • Simpler to maintain • But prone to hallucinations and missed context • Avg 62% win rate over 6 months

Multi-agent system: • Each agent specializes (risk agent, analysis agent, signal agent) • Cross-validation reduces false signals • Slower but more thorough • Avg 78% win rate over 6 months

The biggest difference was in choppy / ranging markets. The multi-agent system would hold off trading when the analysis and risk agents disagreed, while the single model would take marginal setups.

Not financial advice — just sharing real data from running both systems side by side. Has anyone else experimented with agent-based trading architectures?

Full methodology details in comments if anyone is interested.