We build autonomous
data products.
They run themselves.

Every reportable mining incident MSHA has on file — fatal and non-fatal — searchable by mine, operator, year, severity, or a keyword in the investigator's narrative. Built for safety inspectors training crews, researchers chasing patterns, journalists chasing stories, and families trying to find a record. Updated weekly from MSHA's open datasets.

I took an MSHA training course taught by Kim Redding and walked out unsettled. Every incident was on the record, but the public couldn't really find it — the agency's own search makes the data hard to see. This is a small counterweight: the same public record, opened up. Credit for the spark belongs to Kim.

1. Pull the latest MSHA Accidents/Injuries/Illnesses snapshot from msha.gov each Monday.
2. Normalize the schema and join against the Mine and Operator reference tables so every row carries operator name, mine name, and state.
3. Run the investigator's-narrative field through an LLM classifier for incident category and severity.
4. Index the result into Postgres with full-text search on the narrative field.
5. Publish to miningincidents.org; preserve the original MSHA report ID end-to-end so every record traces back to the source row.

• q: roof fall
• q: conveyor belt · state: WV
• operator: Peabody Energy
• year: 2024 · degree: fatal
• occupation: continuous miner operator
• q: methane ignition

Every severe workplace injury OSHA has on file since 2015 — amputations, hospitalizations, and loss-of-eye events — searchable by employer, state, NAICS, or a keyword in the inspection narrative. Built for defense counsel, insurers, safety consultants, and journalists. Updated daily from OSHA's open Severe Injury Report feed.

OSHA's severe-injury reports are public, but the agency's own search makes them effectively invisible — the same gap Mining Incidents addresses for MSHA, applied to a much broader population.

1. Pull the latest OSHA Severe Injury Report feed daily via the DOL Open Data API v4.
2. Normalize the schema and resolve each row's primary NAICS code into a human-readable industry.
3. Run the final-narrative field through an LLM classifier for body-part and event type.
4. Index the result into Postgres with full-text search on the narrative field.
5. Publish to safetyincidents.org; preserve the original OSHA incident ID end-to-end so every record traces back to the source row.

• q: amputation
• state: TX · hospitalized: 1
• naics: 2362
• employer: Amazon
• q: loss of eye
• q: conveyor · amputation: 1

COMEX and LME pricing, on-chain inflows, and social sentiment — synthesized daily into briefings, charts, and a fully automated video pipeline.

Gold coverage is either Bloomberg terminals (expensive, institutional) or YouTube stackers (vibes). There's a gap between those two for someone who just wants the feed: prices, flows, what the internet is saying, every morning. That's the Vault Report.

1. Poll COMEX (CME Group) and LME tick feeds at 1-second cadence for gold, silver, platinum, and palladium.
2. Stream Twitter and Reddit posts about precious metals and score each post for polarity and conviction.
3. Join price action against social sentiment and on-chain warehouse flows into a single daily briefing each morning UTC.
4. Render the briefing into a chart pack and feed the chart pack into the automated video pipeline.
5. Publish to thevaultreport.com and push the briefing to subscribers.

• briefings
• charts/gold
• charts/silver
• sentiment
• videos