What you could have known on October 31: Luminar's bankruptcy, six weeks early, in the 8-K tape

Can SEC filings warn you before a bankruptcy? In Luminar’s case, the warning was explicit, public, and 45 days early. On October 31, 2025, the lidar maker filed an 8-K that disclosed — in one document — a 25% workforce reduction, the CFO’s departure, a forbearance agreement attached as Exhibit 10.1, and this sentence: with roughly $72.0 million of cash and marketable securities on hand, the company “will not have sufficient cash and cash equivalents or cash flows from operations to meet its operating and liquidity needs during the first quarter of 2026 and may also breach the minimum liquidity covenant” on its notes before year-end. The Chapter 11 petition followed on December 15, 2025. Equity holders ultimately received nothing. This post reconstructs the whole trail from the public 8-K tape — and what it teaches about reading item codes instead of headlines.

Who’s talking: I build edgar.tools. This is filing archaeology, not an investment view — every claim below links to the SEC document it came from, and the timeline was reconstructed on June 9, 2026 using the same toolkit any subscriber has.

What did Luminar’s filings say before the bankruptcy?

Here is the 8-K tape, by date and item code, from the first loud signal to the end. Every row links to the source filing.

In between those rows sit a steady drumbeat of Item 1.01 agreement filings and Reg FD updates — nineteen 8-Ks in nine months. For contrast, Apple filed two in its most recent ninety days.

Which 8-K item codes signal financial distress?

The Luminar sequence is close to a textbook of the credit-stress signature, and none of it requires reading a single headline:

• Item 2.05 (exit/disposal costs) — restructurings and workforce cuts. Companies cut 25% of staff to extend runway, not from strength.
• Item 2.04 (obligation acceleration) — a lender just gained, or exercised, the right to demand money early. By the time this prints, the covenant conversation is over.
• Item 1.02 (termination of a material agreement) — contracts don’t usually die quietly at healthy companies.
• Item 5.02 clusters — one executive change is succession; three in six weeks, including the CFO during a liquidity crunch, is signal.
• Item 3.01 (delisting notice) and Item 1.03 (bankruptcy) — the lagging indicators. If these are your first alert, you were never watching.
• And the quiet tell that needs no item code at all: Item 8.01 prose that does covenant math in public. “May breach the minimum liquidity covenant before year-end” is a company reading you its runway.

Across the whole SEC corpus, the distress trio — Items 2.04, 2.05, and 2.06 — prints roughly 130 times a month. The signature isn’t rare. It’s just unread.

Could you actually have caught it in time?

Honesty first: this is reconstruction with hindsight, and Luminar was not a secret. By late October the stock had been falling for months, and nobody needed an 8-K to know the company was struggling. This post is not claiming the filings predicted what the market missed.

The claim is narrower and more useful: the filings stated, in plain language and on a precise date, what the headlines only confirmed later. The October 31 8-K didn’t say “challenging environment” — it said the cash runs out in Q1 2026 and the covenant may break by December. Anyone holding the equity after reading that sentence was holding paper the company itself had already condemned; the confirmed plan eventually fixed that recovery at exactly zero. The gap between “filed at the SEC” and “priced as a certainty” was 45 days wide, and it was visible to anyone whose process included reading Item 8.01 of an unglamorous Friday filing.

That’s the real lesson, and it’s about coverage, not clairvoyance. A credit analyst covering Luminar’s notes would have read that 8-K the hour it filed. The problem is the other hundred names in the book — and the ~130 distress-item filings a month across EDGAR that nobody assigns a junior to. The signal wasn’t hidden. It was filed, time-stamped, and ignored at scale.

How do you monitor 8-K item codes automatically?

The mechanical answer is to watch items, not news. On edgar.tools that’s a Sentinel: pick the names you cover, pick the item codes that matter — 2.04, 2.05, 2.06, 1.02, 1.03 for credit stress — and get the filing, with its items decoded and the document one click away, the day it hits EDGAR. The setup takes about five minutes. If you’d had one watching Luminar on October 31, your alert would have led with the covenant sentence, not the headline three weeks later.

The same item-coded event stream is available to AI assistants through the edgar.tools MCP server — the corpus-wide scan that found this case for me was one tool call: every Item 1.03 filed since March 15, nineteen results, Luminar among them.

This is the first edition of a series. The format is fixed: a real event everyone heard about, walked backward through the filing tape to the day the documents started talking. The filings always say something before the headline does. The question each edition asks is the same one to ask of your own process — was anyone listening?

Set up a credit-stress Sentinel →

Dwight Gunning is the creator of edgartools, the open-source Python library for SEC data, and builds edgar.tools. The timeline above was reconstructed from Luminar’s public 8-K filings on June 9, 2026; quoted passages are verbatim from the filings, and every row of the table resolves on sec.gov.