2026-09-19 · midday

Nothing moved, because there was no market to move in. This is the second run of a Saturday and the book it read is identical to the one the 07:05 run read - all 35 rows, the same 35 contract ids, zero quantity diffs, zero mark diffs, no working order, and a summary that matches to the cent at $1,482,973.27 NLV and -$53,891.02 cash. All twelve price series were re-fetched rather than reused and every close came back identical to the open run, as did the Dec-28 340P implied vol at 36.23%. The same two rails fire: thirteen long puts above the $260 band, and gross leverage 1.681x, red. Runbook Parts 2 through 4 were re-swept row by row and are clear on every one. The only genuinely new finding is in the check itself - today's page carries an nlv_week_pct of +5.87% that is a nine-day change, not a week; the matching-Saturday figure is +3.99%.

What to do

13 long puts sit above the $260 long-leg ceiling: 280P x5 and 300P x8.
BUY TO CLOSE 5 GOOGL Dec15'28 360 PUT / SELL TO CLOSE 5 GOOGL Dec15'28 280 PUT
one combo x5, limit near mid, day · ~$17,750.45 debit ($35.5009 net per spread at Friday's closing marks)
Your playbook: “"long leg never above $260 (must sit at/above the $230-250 floor zone, never below $230 where protection stops paying before history bottoms)"”
The same standing order at an unchanged price - $35.5009 net per spread, identical to the open run to four decimals, because the marks have not moved since Friday's close. There is no live market to hit until Monday's open, and the Dec-2028 book is illiquid enough that the figure is an order of magnitude rather than a fill: the 340P alone shows a $51.00/$54.65 bid-ask, $3.65 wide. Reprice at the moment it is placed. Nothing has been traded on this rail. It repairs 5 of the 13 out-of-band contracts; the 8x Dec-28 300P still has no written remedy and stays under gaps.

Still over, unchanged

These fire every run until you act on them. No order attached.

rail	now	limit
long_leg_band	280P x5, 300P x8	$230-$260 band	13 contracts outside
gross_leverage	1.681x	amber 1.30x, red 1.50x	0.181x above the red line
top2_name_delta_ratio	0.62x	amber 0.70x, red 0.85x	clear
total_delta_ratio	0.86x	amber 1.30x, red 1.50x	clear

Why each one reads the way it does

long_leg_band
The rail the action item addresses. No leg has been traded on it.
gross_leverage
Gross position value $2,493,525.65 against NLV $1,482,973.27, both unchanged to the cent since the open run. Red at signing too, at 1.57x on gross, where the IPS records true delta leverage as roughly 1.0x. The delta ratios this run measures, 0.617 top-two and 0.856 total, are both clear, which is the same split the IPS note describes.

delta by name

Delta notional per name as of 2026-09-19: stock at delta one, each option leg at the Black-Scholes delta implied by its own mark. Top two: GOOG, MU.

name	delta notional	of NLV
GOOG	$759,010	51.2%	1543 sh, 18 legs
MU	$155,707	10.5%	525 sh, 2 legs
META	$95,868	6.5%	144 sh, 0 legs
VOO	$86,319	5.8%	123 sh, 0 legs
RDDT	$77,386	5.2%	513 sh, 0 legs
NVDA	$50,865	3.4%	285 sh, 2 legs
AMZN	$25,371	1.7%	100 sh, 0 legs
EQT	$10,000	0.7%	200 sh, 0 legs
INTC	$8,561	0.6%	300 sh, 2 legs
TSLA	$364	0.0%	1 sh, 0 legs
DIS	$103	0.0%	1 sh, 0 legs

Everything else clear

Nearest trigger is GOOGL - tranche 3 confirmation (nearest written price level) at $360, 3% away.

All 29 triggers swept, with today's number

price trigger	now	fires at	distance
GOOGL - tranche 3 confirmation (nearest written price level)	$349.54	≥ $360	3.0% up
GOOGL - tranche 2 weakness	$349.54	≤ $317	9.3% down
GOOGL - thesis-break exit	$349.54	≤ $280	19.9% down
GOOGL - no-chase ceiling	$349.54	≥ $430	23.0% up
MU - roll the collar up (the only written MU level, and the only one above spot)	$1,015.80	≥ $1,250	23.1% up
GOOGL - Rule 6, close every short put	$349.54	≥ $434	24.2% up
GOOGL - washout, stop selling spreads and buy stock	$349.54	≤ $260	25.6% down
GOOGL - Rule 8, deploy the $100k crash reserve	$349.54	≤ $260	25.6% down
GOOGL - long spreads near max, apply the would-I-buy-it-fresh test	$349.54	≥ $500	43.0% up
GOOGL - shares capped by the 600Cs, roll the GOOG collar or accept the cap	$349.54	≥ $600	71.7% up

level trigger	now	fires at	distance
Every input re-fetched, and every one came back identical - the run found no new information	0 of 48 figures changed	a second run of a shut market	The 35 position rows, the 12 price series, the account summary and the Dec-28 340P implied vol were all pulled fresh rather than carried forward, and all of them match the 07:05 run exactly: same 35 contract ids, zero quantity diffs, zero mark diffs, NLV $1,482,973.27, gross $2,493,525.65, cash -$53,891.02, IV 0.3622516801180204. get_account_orders is empty. The last session was Friday 2026-09-18 and the next is Monday, so the identity is the correct answer rather than a stale read - it is reported because the alternative, reusing this morning's file, could not have told the difference.
GOOGL - tranche 3 at $360 is the nearest unfired trigger	349.54	daily close above $360 on the 50-day, 1.2x average volume	2.99% above Friday's $349.54 close. Friday's high was $359.44, $0.56 short of the line, on 23.3M shares against Thursday's 10.9M - so the tape reached the level intraday on more than double the volume and gave back $9.90 into the close. The rule reads on the CLOSE with a volume condition, the close came in $10.46 under, and nothing is proposed.
MU's first weekly close above $1,000, with nothing written underneath it	1015.8	no written level below spot at any price	MU closed $1,015.80, +3.92% on the session. The runbook's only MU rows are the $1,250 collar roll-up, 23.06% above, and a Part 5 thesis break on HBM contract pricing that is a qualitative judgement rather than a level. The collar is on - 525 shares against 5 short Dec-28 1740C and 5 long Dec-28 900P - so the floor is $900, 11.40% below spot, but that is a position, not a rule. $155,707 of delta notional, second-largest in the book, and the fiscal Q4 print is eleven days out. Named, nothing proposed, because nothing is written.
Long call spreads against the 90%-of-width sell rule	44.0	any spread marking 90% of its width	Recomputed from this run's marks, not copied: Dec-28 300/400 is widest at 44.00% of its $100 width, then Sep-27 300/440 at 41.78%, Sep-27 300/445 at 41.10%, Dec-28 350/500 at 31.35%, Dec-28 300/600 at 29.25%. None is within 46 points of the rule.
GOOGL Dec-28 340P extrinsic	54.15	below $5.00	GOOGL at $349.54 leaves the 340P fully out of the money, so its whole $54.15 mark is extrinsic. The runbook notes this row only reaches $5 if GOOGL is under roughly $250 in 2028. rails.json still lists this as needing a live Dec-2028 chain pull; the position row's own mark answers it.
Excess liquidity against the Part 4 defence rows	75.83	amber below 40%, red below 25%	$1,124,514.56 of excess liquidity on $1,482,973.27 of NLV. 35.83 points of headroom to amber.
Net cash against the IPS floor	-0.0363	amber -0.05, red -0.10	-$53,891.02 on $1,482,973.27, clear with $19,257.64 of headroom to amber. Cash is unchanged to the cent from the open run and from Friday, the fourth consecutive identical read.
NLV against the Part 3 one-week freeze row	3.99	a fall of 8%+ in one week	NLV is UP $56,920.52, +3.99%, against the matching Saturday reading of $1,426,052.75 on 2026-09-12, so the row is false on direction as well as magnitude. Flagged because today's page states +5.87%, which is the change against 2026-09-10's $1,400,718.26 - nine days back, not seven.
GOOGL IV against the Part 3 crash trigger	36.23	above 50%	Dec-28 340P annualised implied vol 0.3623, from the implied_vol field. option-midpoint-iv is still returning annualIv -15.8745 with isValid false on this frozen book - a negative volatility - so it is unusable and was not used. 13.77 points below the crash trigger and 6.77 below the tranche-2 alternate at 43%.

calendar	date	away
MU fiscal Q4 print, after the close - finviz carries it as Sep 30 AMC	2026-09-30	11d
Earliest clean sale date for the 6/05 GOOG loss lots if only bought calls count as replacement property	2026-10-01	12d
Earliest clean sale date if a WRITTEN call is also replacement property	2026-10-15	26d
GOOG print, first scheduled thesis adjudicator	2026-10-28	39d
Deploy the $100k reserve at market if no crash has come	2026-10-29	40d
GOOG capex guide, second scheduled adjudicator	2027-02-03	137d
GOOG lots vest long-term, add collar put leg 9 (+66 sh)	2027-03-13	175d
GOOG lots vest long-term, add collar put legs 10-11 (+200 sh)	2027-04-02	195d
GOOG lots vest long-term, legs 12-14 (+350 sh) - 193 of them clock-stopped by the 09-14 collar	2027-06-05	259d
GOOG lots vest long-term, leg 15 (+50 sh) - all 50 clock-stopped by the 09-14 collar	2027-06-25	279d

Spot prices

	last	day
GOOG	$344.41	+0.2%
GOOGL	$349.54	+0.6%
MU	$1,015.80	+3.9%
AMZN	$253.71	+1.0%
DIS	$102.67	-2.5%
EQT	$50.00	-0.7%
INTC	$108.60	-0.2%
META	$665.75	-2.4%
NVDA	$222.27	+1.3%
RDDT	$150.85	-1.3%
TSLA	$364.27	-0.5%
VOO	$701.78	+0.1%

The check itself

expected No record for today, because the job does not run on Saturday.
ops/status.py --check exits 11 with 'latest daily record is from 2026-09-18, not 2026-09-19'. launchctl print gui/$UID/com.gabriel.stock-dashboard.daily was read again this run and its StartCalendarInterval entries are Weekday 1 through 5 at 12:45 - weekdays only. runs = 4, last exit code = 1, state not running. A Saturday with no record is the job behaving correctly, and the check has no weekend-aware branch to say so, so it reports the absence as a fault either way.
will happen again Friday's record is status failed: 27 of 115 steps, and the failures are the peripheral names.
ops/status.jsonl's 2026-09-18 record reads status failed, steps_ran 115, steps_failed 27, written 12:49:41, duration 275.7s, committed true. The SUMMARY: line of ops/logs/2026-09-18.log names them: street on BRK-B, DIS, EQT, RDDT, TSLA and VOO; scorecard on those six plus INTC and MU; book_ev on BRK-B, DIS, EQT, INTC, RDDT, TSLA and VOO; house_forecast on AMZN, GOOGL, META, MU and NVDA; sync_positions on BRK-B. Also five blocked house forecasts and 24 FALLBACK DATA rows - every chain and every iv30 across all twelve names sourced from Tradier. Unchanged since the open run; nothing was rerun, and this section never reruns anything.
open The coverage gate examined 40 of 155 candidates and skipped 115, and nothing explains the skip.
gate_candidates 155, gate_examined 40, gate_skipped 115, gate_losses 0, and the log's own line reads '40 file(s) checked, 115 skipped, 0 losing coverage'. The count this check has been demanding is a real number, so the historical 'green run with a zero count' signature is gone. But a gate that reports passed over 26% of its candidates is worth understanding before it is trusted, and the record carries no field that would let this check tell a correct skip - a file that was not regenerated - from a silent one.
found this run Today's page states a nine-day NLV change as a one-week change.
report-2026-09-19.open.json carries account.nlv_week_pct = 5.87. That is the change against the 2026-09-10 07:16 reading of $1,400,718.26, nine days back. The matching Saturday, 2026-09-12, read $1,426,052.75, against which NLV is +3.99%. It changes no verdict - the Part 3 row tests for a FALL of 8%+ and NLV is up on every baseline in the window - but the runbook row is written in weeks and the figure on the page is not one. This run's report states +3.99% and names its baseline.
found this run The second weekend slot cannot observe anything, and that is now demonstrated rather than argued.
The cron fires 06:35 and 12:00 Pacific seven days a week and the run label is taken from the rails log, so a Saturday's first run is labelled open and its second midday. With the market shut from Friday 13:00 Pacific to Monday 06:30, the second slot re-derives an identical book: this run re-fetched all 35 position rows, all 12 price series, the summary and the 340P IV and every one matched to the cent. The open run's fuller record, including the GPU pull and the forecast pass, is preserved on disk as report-2026-09-19.open.json; the page at the date carries the later run, which is the normal weekday behaviour. Whether the weekend slots should fire at all is his call - changing the schedule changes his machine, so nothing was changed.
structural Neither market-check slot can ever observe a completed same-day pipeline run.
This check runs 06:35 and 12:00 Pacific; the pipeline fires 12:45. Both slots precede it, so a check demanding a record carrying today's date can only ever report its absence on a weekday. Restated because it is now the only reason this section cannot answer question 1 on a weekday. Moving either schedule changes his machine and is a proposal, not an action.
will happen again Three refusal files remain on disk and all three are closed.
ops/logs holds COMMIT_REFUSED-2026-09-15.md, -09-16.md and -09-17.md. The 09-17 one is the real gate catch - 40 checked, 105 skipped, 11 losing coverage, a uniform closes 3015 -> 3014 one-bar drop - hand-committed as b0e4dec and root-caused in c231620. The 09-15 and 09-16 pair are pre-flight dirty-tree refusals, a different failure. No file exists for 09-18 or 09-19 and none should: gate_losses is 0 and Friday's run committed.

Rails that could not be evaluated

MU has NO written price level anywhere below spot. It closed $1,015.80, its first weekly close above $1,000, it is $155,707 of delta notional - second-largest in the book - and its fiscal Q4 print is eleven days out. The runbook's only MU rows are the $1,250 collar roll-up, 23.06% above, and a Part 5 thesis break on HBM contract pricing that is a qualitative judgement rather than a level. The 900P floor is real but it is a position, not a rule: nothing written says what to do between $1,015.80 and $900.
NO RAIL COVERS SHORT CALLS AGAINST SHARES HELD. Re-counted off this run's position rows, not carried: 45 short GOOG/GOOGL calls (Dec-28 400C x1, 500C x10, 600C x18, Jun-27 425C x5, Sep-27 440C x8, Sep-27 445C x3) against 29 long (Dec-28 300C x11, Dec-28 350C x10, Sep-27 300C x8) is 16 net short - 1,600 shares of obligation against 1,543 GOOG shares held, so 57 shares stand behind nothing. Unchanged since 09-14.
THREE Sep-2027 legs and one INTC leg remain invisible to every rail: the 8x GOOGL 300/440 spread opened 08-31, the 3x GOOGL 305/445 collar opened 09-14, and the INTC 87.5/140 collar opened 09-16. rails.json carries exactly one program, the Dec-2028 GOOGL put campaign, and nothing in it can see a Sep-2027 or an INTC leg.
THE 8x Dec-28 300P STILL HAS NO WRITTEN REPAIR ORDER. The long_leg_band fire covers 13 out-of-band contracts; the written remedy addresses 5 of them. The other 8 have been outside the band every run and no doc says what to do with them.
INTC is in assets_without_written_rules, so a 300-share position carrying a $22,402 gain at a $34.42 average cost, now collared, has no written rule for any outcome. Named, nothing proposed.
stressed_excess_liquidity has still never been measured. It needs IBKR Risk Navigator at -30% price and +50% IV with the TWS gateway up.
short_dec28_340p_extrinsic is still listed in rails.json as needing a live Dec-2028 chain pull, when the position row's own mark answers it: GOOGL at $349.54 leaves the 340P fully out of the money, so all $54.15 of its mark is extrinsic. rails.json was NOT edited - the file holds only rules from an approved doc, and changing how a rail is measured is Gabriel's call.
tax-rules is still silent on whether a WRITTEN call is replacement property, and that ambiguity is what splits the clean-sale date for the 6/05 GOOG loss lots between 2026-10-01 and 2026-10-15. The wash-sale window itself opened on 2026-09-17, two days ago, so the question is now live rather than hypothetical.
option-midpoint-iv returns a NEGATIVE annualised vol on a frozen book - annualIv -15.8745, isValid false - for the second run running. The IV rail was read from implied_vol instead, which reports 0.3623 is_valid true. Nothing in rails.json says which field the IV rail is measured from, so the substitution is this check's judgement rather than a written rule.

Where the numbers came from

Run label decided from the rails log, not the clock: investing/checks/rails-log.jsonl already carried a 2026-09-19 markets-open entry at 07:05, so this is the MIDDAY run. Sections 4b (GPU) and 5 (forecast pass) were skipped by that rule and gpu and forecasts are empty objects, not carried forward from the open run.
THE MARKET IS SHUT. Today is Saturday; the last session was Friday 2026-09-18 and the next is Monday 2026-09-21. Nothing in this report is a live price and no intraday figure exists for today.
EVERY INPUT WAS RE-FETCHED, NOT REUSED, and every one came back identical to the 07:05 run. get_account_positions: 35 rows, the same 35 contract_ids, zero quantity diffs, zero mark diffs. get_account_summary: NLV $1,482,973.27, gross $2,493,525.65, cash -$53,891.02, excess liquidity $1,124,514.56, identical to the cent. get_account_orders: empty. All 12 get_price_history series: every close identical. The 340P IV: identical to 19 decimal places. The identity is reported rather than assumed, which is the point of re-fetching.
PRICES ARE REGULAR-HOURS DAILY BARS, NOT THE SNAPSHOT `last`. On a frozen weekend book get_price_snapshot's `last` is Friday's final after-hours print and it differs from the close on 11 of 12 names, flipping INTC's sign. Every last/prior_close pair in quotes.json is a get_price_history ONE_DAY RTH bar, Friday 09-18 close over Thursday 09-17 close, which is the basis the runbook's daily-close rows are written against.
IV came from the implied_vol field, NOT option-midpoint-iv. On this frozen book option-midpoint-iv returns annualIv -15.874507866387544 with isValid false - a negative volatility - so it is unusable. implied_vol annual_iv 0.3622516801180204 is_valid true was used. The 340P shows bid $51.00 / ask $54.65, $3.65 wide, plprice mark $54.152099609375, last $53.23 is_close true.
RAILS.JSON WAS NOT EDITED and nothing in ~/code/financials was edited, committed, reverted or rerun. Section 4a is read-only by its own terms and section 4b did not run.
RUNBOOK PARTS 2-4 WERE RE-SWEPT ROW BY ROW against this run's own numbers rather than copied from the open run: the 90%-of-width table was recomputed from the position marks (widest Dec-28 300/400 at 44.00%), the 340P extrinsic from its own mark ($54.15), the excess-liquidity ratios from the summary (75.83%), the MU roll-up gap from the MU close (23.06% away), and the one-week NLV row from the rails log (+3.99% against the matching Saturday). Every row is clear.
No price was estimated anywhere. No figure in this report was carried forward from a prior run except the historical NLV readings used as baselines for the one-week row, which are quoted with their dates.