The Lab

Trust


Everything known to make these numbers weaker than they look — which is the point of publishing it. A reader who can see the instrument's limits can decide what to do with its readings.

Window opened Aug 12, 2026 · collectors run hourly and daily · generated Sep 15, 2026, 10:29 UTC

The cheapest check

Every row on every lane links to its source — a GitHub repository, a lab’s own page, a filing on EDGAR. The fastest way to audit this section is to click one and see whether the row said the truth about it.

Known limits

  • Ranks are real; star counts are not. Every count on these pages is a sample count — distinct accounts seen in GitHub’s public event stream, which carries only a small fraction of real starring. For composition: the stream holds roughly one starring event per 89 pushes in this window. Measured against real star counts on Sep 11, 2026 (the latest settled day with a snapshot pair), the stream carried about one starring event for every 3 stars actually gained across 8,105 watched repositories. Relative ranking survives sampling; absolute counts do not, which is why every count is labeled as in-sample and compared only within its own day.
  • Fresh days are incomplete on purpose. A newly published hour holds a fraction of its final events and fills in over days. Fresh days are ranked within themselves (which holds up), then re-ingested once settled — settled through Sep 11, 2026 as of this generation.
  • The star-history series is 27 days old. GitHub withdrew the API that let anyone reconstruct star history, so it exists only going forward: 9,365 repositories snapshotted daily since Aug 20, 2026. Trend lines appear here when there is enough series to draw one honestly — about two weeks.
  • The attention floor of 5 is inherited, not measured. It comes from the monthly instrument’s published floor and will be re-settled by measuring a week of arrivals against it.
  • The money lane’s readings are interpretations. Each deal filing’s plain-English card is written by a language model from the filing text alone. The filed facts (codes, dates, the document itself) are separate on every card, and the filings the model set aside are listed with its one-line reading of each — the cut is auditable, not asserted.
  • The classifier is a model and it errs. AI-tooling calls are made by a language model on each arrival. The dimmed rows on What to try exist so its cuts stay visible; repositories with no description at all are dropped as presumed scratch work rather than guessed at.

The collectors, and how often they run

8 collectors run in five chains. Each chain writes a heartbeat as its steps complete, whatever they found, so the record shows the automation rather than asserting it — and because every lane is idempotent, a run that finds nothing is a successful run, not a silent failure. The list below is declared rather than read back from the heartbeats, so a collector that stopped writing shows up as missing instead of quietly disappearing from it.

This page is a snapshot, not a live readout. The schedule below is a standing rule and does not go stale, but the completion times were read when the page was generated, on Sep 15, 2026, and refreshing will not move them. The collectors keep running regardless; the page catches up the next time it is generated.

:00:15:30:45:00within each hourannouncementshourly:25sweep 18 sources → flag stale channelsfollow the moneyhourly, 06:00–22:00 ETEDGAR only accepts filings inside this window:40SEC panel sweep → Federal Register → read the filingsGH Archive + discoveryhourly:50ingest the hour → roll up + discover → classify arrivalsrepo snapshots → publishdaily, 06:10 ETonce a day, not on this dialcapture stars + forks for every watchlist repo → regenerate + publish this section

The minutes are staggered on purpose: all three hourly chains run on one machine, and GH Archive's ingest is heavy enough that overlapping it with the SEC sweep would put both behind the same disk. The daily capture is marked because it is the one lane whose miss cannot be undone — GitHub withdrew the endpoint that would let star history be reconstructed, so a day not snapshotted is a day gone for good. Publishing hangs off the end of that same chain rather than off a clock of its own: the day's data is complete exactly when the capture lands, and if the capture fails the section keeps yesterday rather than going out with a hole in it.

The published schedule, not a status light. Every lane is idempotent and converges to zero new rows when nothing has happened, so a quiet run is a successful one — health is whether it was checked, never whether it found something.
CollectorWhat it doesHow oftenLast completed (UTC)
announcementssweeps 18 announcement channelshourly at :252026-09-15 10:25:07
gharchiveingests the newest GH Archive hour, re-settles old dayshourly at :502026-09-15 09:50:00
discoverrolls the day up and puts new repos on the watchlisthourly at :50, after ingest2026-09-15 09:50:01
classifylabels new arrivals as AI tooling or nothourly at :50, after discovery2026-09-15 09:52:35
moneysweeps a 531-company panel at the SEC, then the Federal Registerhourly at :40, 06:00–22:00 ET2026-09-15 02:42:18
money-readreads new deal filings into plain Englishhourly at :40, after the sweep2026-09-15 02:42:22
snapshotscaptures stars and forks for every watchlist repodaily at 06:10 ET2026-09-15 10:29:24
publishregenerates this section from the store and ships itdaily, after the snapshot lands2026-09-14 10:33:10

Generated Sep 15, 2026 from the Ouroboros store · regenerated and republished daily, after the morning snapshot lands