Signal Delivery Shift — Monthly to Weekly (+ Work Milestones)
Update (February 2, 2026 — 2:00 PM PT): There is a known issue in the latest SEC filing
delivery. Theexcerptsfield is returning raw XBRL tag identifiers instead of human-readable text from the filings. This has been confirmed in 10-K signals and likely extends to 10-Q, 20-F, 8-K, and 6-K as well. We are currently investigating the full scope — if there is a major quality issue across the batch, we will reprocess and re-upload the affected signals. This will be resolved no later than February 3, 2026.
Signal delivery has been upgraded from a monthly to a weekly cadence across nine existing signals, providing more timely data to downstream consumers. We've also launched a new Work Milestones signal covering job changes, promotions, and work anniversaries.
For full delivery schedules and next delivery dates, see the Delivery docs.
Delivery Cadence: Monthly → Weekly
The following signals have shifted from monthly to weekly delivery. The January 31 delivery was a one-time push to get data in by end of month for partners who required it. Starting February 3, 2026, these signals will begin their regular weekly cadence.
| Signal | Bucket |
|---|---|
| SEC 10-K Annual Filings | gs://autobound-10k-v1/ |
| SEC 10-Q Quarterly Filings | gs://autobound-10q-v1/ |
| SEC 8-K Current Reports | gs://autobound-8k/ |
| SEC 20-F Foreign Company Filings | gs://autobound-20f-v1/ |
| SEC 6-K Foreign Company Reports | gs://autobound-6k-v1/ |
| Earnings Transcripts | gs://autobound-earnings-transcripts/ |
| News | gs://autobound-news-v2/ |
| Hiring Velocity | gs://autobound-hiring-velocity-v1/ |
| Hiring Trends | gs://autobound-hiring-trends/ |
The output format, schema, and bucket structure remain unchanged - only the frequency has increased.
New Signal: Work Milestones
We launched a brand new signal: Work Milestones (gs://autobound-work-milestones/). This signal consolidates three career event subtypes under a single workMilestone signal type:
- jobChange — Contact moved to a different company
- promotion — Contact changed roles within the same company
- workAnniversary — Contact hit a tenure milestone at their current company
This signal is also on a weekly delivery cadence, starting February 3, 2026.
Access details:
- Bucket:
gs://autobound-work-milestones/ - First run:
gs://autobound-work-milestones/2026-01-30-16-07-00/ - Files:
output.jsonl(54.4 GB)output.parquet(7.8 GB)
- Auth: Authenticate via
gcloud auth loginwith access to theautobound-signal-deliveryproject
Why the first delivery is unusually large (~54 GB)
The first run produced a significantly larger file than future deliveries will. This is expected behavior.
The delivery window is based on detected_at (when our system identified the event), not event_date (when the career event actually occurred). Since this is the first run under a new process, every historically detected signal was included in a single backlog delivery — even if the underlying career events happened months or years ago.
Going forward, each weekly delivery will only include signals where detected_at falls within the past week, resulting in much smaller files.