AskTheRecruiter · public operations
AI Tracker Health
See which data feeds are running, how we check the evidence, where coverage falls short, and what we are working on. When a source goes down we show it as a gap instead of silently counting it as zero.
Loading live operational status…
Collector operations
Last completed source attempt. Counts are raw candidate documents, not a claim of accepted events.
| Source | Coverage target | Cadence | Last pull | Result | Status / safe detail |
|---|
Recent collector runs
Append-only history from this health-ledger release onward. It records source attempts and raw candidates, not accepted events, and never reconstructs earlier runs.
| When | Source | Status | Raw candidates | Safe detail |
|---|
Product roadmap
Features list
Released capabilities and their rollout state. We show live collector status and errors above. This list does not imply complete country coverage.
Source-linked event records
Every published event keeps its cited filing, government notice, company statement or named report; a single layoff event can link to several reports.
How we decide a layoff is AI-related
We keep employer-stated cause, contributing mention, background context and outright denial separate. A model helps extract the text, but exact source quotes and fixed rules decide what we publish.
Deduplication and lifecycle review
When several outlets cover the same layoff, we combine them into one event and keep every source link. When an announced cut looks like it later actually happened, an editor reviews the match before anything changes.
Public data and audit tools
Filters, exports, record sources, corrections, release ledger, integrity, quality and source-health endpoints are publicly available.
Collector-run ledger
From this release on, we keep a record of every source run, how many raw items it found, and any outages. We do not invent history for runs from before we started logging.
Dataset releases and change report
Each deployment snapshots the public dataset; this page reports the retained ledger window and disclosed recent corrections, removals, merges and coverage status.
US announcement reconciliation (internal)
Each month we run a like-for-like US employer / announcement / AI-primary reconciliation internally to monitor coverage. We never change tracker totals to match it.
High-impact editorial review
We surface very large, AI-primary and multi-country events for source-based review. We never correct one automatically behind the scenes.
Durable evidence hashes
We hash every retained excerpt: new excerpts at write time, and the legacy backlog completed its bounded backfill on July 18, 2026. We report any newly pending hashes live above.
Adding announcement dates and company headquarters
Company-headquarters data shipped July 19, 2026 from a checked, source-verifiable registry; it powers the US-employer views. We still add announcement dates daily from stored evidence. Unknown fields stay blank rather than guessed.
How complete our coverage is (spot-checked)
The first published sample: California WARN, June 2026: 11 of 12 official notices, transcribed independently, matched a tracker event (91.7% sample recall), checked by three independent reviewers against the sealed official notice. A sample is a spot measurement, never a completeness claim; further country-period samples follow the same protocol.
Official national and company IR connectors
On July 18, 2026 we admitted the first five reviewed company-owned IR feeds to the versioned registry: Intel, SAP, Cisco, Salesforce and Micron. We retired the Japan EDINET and South Korea OpenDART discovery probes after months live yielded zero layoff rows, because those filings almost never announce layoffs. Worldwide news covers Japan and South Korea instead. We mark a country as covered only after we have built and reviewed its data feed.
Embeddable US widgets
A noindex, source-linked US national/state iframe widget links readers to its exact filtered tracker view. Build copyable code on the publisher tools page; metro variants remain deliberately out of scope.
Company layoff directory
Pages live at /company-layoffs/ and grow automatically. An indexer admits every employer with a clean identity and at least one source-linked event that we count in its own right, rather than folding into a larger one. The same server rules that govern manual review validate each one. We list an employer with two or more such events in the sitemap. An employer below that keeps its page and stays noindex, because the page repeats what the individual entry already says.
Quarterly State of Layoffs report
We publish the query-backed HTML report from a fixed server-generated snapshot. We disclose its data revision and its coverage limits.
WARN transparency dataset
The separate evidence-linked research foundation is ready. It will not label an employer non-compliant without verified notice, timing and adjudication evidence.
Current work
Actionable backlogs
Schedule and coverage
- Railway, twice daily: SEC EDGAR (United States), Google News and global GDELT (worldwide news), and reviewed company IR feeds.
- GitHub Actions, daily: US WARN and Eurofound ERM (European Union) at 13:00 UTC; dedupe, quality, evidence-hash and bounded enrichment/recovery jobs.
- Monthly: strict US announcement reconciliation (internal coverage check). A red threshold is a coverage alert, not a data-ingest crash.
- Retired probes: we stood down the Japan EDINET, South Korea OpenDART and Brazil CVM discovery probes after they yielded zero layoff rows. Worldwide news covers those countries. United Kingdom Companies House access is identity-support only.
Collector-run telemetry begins with plugin 2.18.21; we do not reconstruct or guess legacy daily pull counts.
Source-link preservation, measured live: 21,673 of 25,171 distinct source links (86.1%) have a permanent Internet Archive (Wayback Machine) snapshot. Of the rest, 0 are queued for the next daily archiving run, 1,812 have a capture requested and are retried every 3 days, and 1,803 are not in the Internet Archive yet and are re-checked weekly, forever. Rows without a snapshot say so on the page, with the date of their next check.
Rolling dataset change report
Snapshot totals begin at ledger inception. We do not label net change as gross additions, because merges, corrections and removals can change the total.
Machine-readable: quality · integrity · source health · collector runs · release ledger