Part 3 · Operate
Signals and collectors
Nine collectors watching public change at the companies on your list.
01What it is
Nine collectors read public sources for change at watched companies: funding, hiring, product releases, pricing, docs, leadership, tech stack, homepage diffs and public posts. Each carries a reliability weight.
02Why it exists
A signal has to be public, dated and checkable, because every sentence in a draft traces back to one. Nothing here buys browsing behaviour or infers interest from a third-party graph.
The reliability weights matter as much as the collection. A funding announcement is close to certain; a homepage diff might be a designer changing a heading. Both are stored, and the weight is what stops the second from being written about as though it were the first.
03How to use it
- 01Add companies and wait. Collection runs on a schedule.
- 02Open a company to see its observations with sources and dates.
- 03Check the admin screen if a source stops producing. Health is tracked per source.
04What good looks like
- You give it
- A watched company posts four engineering roles on one team and rewrites its pricing page.
- You get
- Two high-reliability events land, dated, with their URLs. Together they clear the synthesis threshold.
- Why
- Job postings and pricing pages both carry high reliability, and two meaningful events is the floor.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- A watched company changes a heading on its homepage.
- You get
- One low-reliability event, stored, not enough for a read on its own.
- Why
- The homepage diff collector carries the lowest reliability in the set, and a lone event carries reduced weight on top of that.
Derived from the rules in the code