The record as data

Download newsroom-2026-08-16.jsonl (327 rows, the file exactly as the software wrote it).

Seven rows in the file are not on any page of this site. The site refuses to publish an entry whose event date is later than the day the record was read, because a record showing an event that has not happened yet is wrong on its face. The rows are left in the file, so a consumer can see them and apply the same rule.

The contract

The file's shape, every field, and the compatibility promise are published in ops/SCHEMA-newsroom.md in the repository that builds this site. Three rules bind any consumer, and this site keeps them itself, with one rule of its own added first:

• A row whose published_at is later than the date in the file name, the day the record was read, is not published.
• A row with lead_eligible: false is never set in a lead or featured position. It carries no headline of its own; the record's plain statement stands in.
• An excerpt is never rendered longer than the row's own excerpt_word_cap, and never at all where republication is link_only.
• source_url is always a link and source_name is always visible beside it.

What is in it, and what is not

Every row is a dated event at a named aerospace or defense company, fetched again at its source on the day the record was read and confirmed to carry its excerpt. Rows are in editorial order: descending editorial_score, then newest first.

The market segments are on every row as segments; the titles on this site are cut on it. A row the reading could not place carries unclassified.

The standards page carries the source register, the quoting rule per source and the terms each reading relies on.