Morning Brief: Wednesday Waning Gibbous in Taurus Map Tests $83,755 BTC, $90.46 WTI, SPCX, and STRC Yield into Chicago PMI

When Gann explains stop orders, he separates the trigger level from the price a broker can actually obtain. His example allows a sale below the stated stop and says outright that a broker cannot guarantee execution at that limit. He also tells the reader to decide the affordable loss before entering a trade, not after. That distinction is more concrete than the usual advice to use protection. A stop level defines a planned decision; the eventual fill determines the realized loss. A lesson that treats the two as identical hides an assumption that the market is not obliged to honor. Build a small risk worksheet with separate cells for entry, quantity, stop trigger, and assumed fill. Compute the loss at the trigger and again at the fill, and label both as assumptions. This does not produce a worst-case guarantee. It only shows how one different execution price changes the arithmetic. Read your broker's actual order terms before applying any historical wording to a current product, because order handling differs by venue and instrument.

Try it

An invented position buys 100 shares at 50. The stop trigger is 48, but assume a fill at 47.50. Ignore fees. What is the planned loss at the trigger, the loss at the assumed fill, and the difference?

Limits

The historical description is not a statement of present broker behavior. Stops execute differently across products and conditions. Fees and further adverse execution are omitted. No order is placed and no strategy efficacy is claimed.

Source

W.D. Gann, Truth of the Stock Tape (1923), Stop-loss order explanation and the section on overtrading. Primary author text, public domain. Digital reproductions can contain OCR errors; cite by chapter.

Today

BTC live worksheet: a 2% stop trigger sits at $82,100.48; a fill 0.25% below that trigger raises the loss by $20,525.12 versus the trigger math. Bitcoin spot (CoinGecko BTC/USD), As of 2026-09-30T11:04:00Z: assumed_loss = units × (latest_price_usd − assumed_fill_usd); planned_loss = units × (latest_price_usd − stop_trigger_usd) = 188077.12 USD assumed loss for 100 units (inputs: assumed_fill_usd=81895.2288, fill_pct_below_trigger=0.25, latest_price_usd=83776.0, planned_loss_usd=167552.0, slippage_difference_usd=20525.12, stop_trigger_pct_below_price=2.0, stop_trigger_usd=82100.48, units=100.0). Data source 1

Horizons separates apparent coordinates from refracted coordinates. Apparent coordinates already include astronomical effects such as light-time and aberration. Refracted coordinates add an Earth-atmosphere correction, and the manual warns that this depends on local atmosphere and weather. That means the correction is an observing assumption, not a universal property of the planet. This matters most near the horizon. A target at -0.1 degrees apparent elevation and a rough +0.6 degree refraction correction may appear above a flat sea horizon, while the same apparent value behind mountains or haze may not be usable. The arithmetic is simple, but the label is the lesson: state whether the row is apparent or refracted, and name the weather assumptions if a correction is applied. For market work, this prevents a template from turning a marginal visibility fact into a timing claim. Pairing a refracted sky row with price is acceptable only when the site, timestamp, coordinate frame, and correction assumptions are kept with the number.

Try it

A target has apparent elevation -0.10°. A worksheet applies a +0.60° refraction correction. What is the refracted elevation, and what assumption must be disclosed?

Limits

The numbers are a teaching approximation. Real refraction varies with pressure, temperature, wavelength, horizon dip, and terrain. The example classifies an observation boundary; it does not forecast markets.

Source

NASA/JPL, Horizons System manual, General Definitions, Refracted Coordinates. Primary NASA/JPL technical documentation; observing-geometry caveat, not astrological doctrine.

Today

JPL places the Moon 45.42° above New York at the sampled minute, so the near-horizon illustrative correction rule adds 0.00°; BTC is retained as the synchronized price row, not a forecast input. Moon apparent elevation over New York plus BTC/USD price row, As of 2026-09-30T11:06:00Z: refracted_elevation = apparent_elevation_deg + assumed_refraction_correction_deg = 45.423998 degrees apparent-plus-declared-correction (inputs: apparent_elevation_deg=45.423998, assumed_refraction_correction_deg=0.0, azimuth_deg=263.637286, btc_price_usd=83776.0). Data source 1 Data source 2