A signal is a public document in which an organization says, in its own words, that a legacy system is on its way out: a job posting that names the technology being left, an annual report that describes a multi-year replacement, a state's project list with a budget attached, a federal notice asking industry who can do the work. We do not infer from press releases or vendor announcements. The organization has to have said it.
Every week we read thousands of public documents across corporate, hiring and government sources. Each candidate is held to the same written standard: is it real, is it the organization's own system, and is it early enough to matter. Machines do the reading. A person makes the call: nothing reaches an issue without being read and approved by someone who has spent 25 years inside these projects.
Each item then says what the organization posted or filed, why the timing matters, the technology on each side of the move, the part of the organization most likely to own it, and where to find them. We name roles and teams, never individuals.
Every item cites its public source, with a link. For a corporate filing or a job posting the link opens the document itself. For a government project list, the link opens the list the project appears on. Job postings expire. Where a posting has been taken down we keep the date and the wording we cited.
The free quarterly is the one exception. Its emailed edition names ten organizations with their sources. The copy on the open web describes the same ten without names, because a public page that lists who is about to buy would be a free lead list.
If we get something wrong, tell us at corrections@sunsetsignals.com. The next issue will say so, and the archive copy is amended.
No contact lists, no personal data, nothing from behind a login. We do not sell subscriber information, and we do not take payment from the organizations we write about.