anti algo

SWEPT Sep 13, 2026, 07:30 UTC

What the machine killed, and the rule each one tripped.

A posting is killed when it trips a rule: it contradicted itself, it outlived a deadline it printed itself, it stopped existing where it was published, or it came back under a new address wearing a fresh date. Nothing is killed for being old. Each record here carries what the machine observed and when, and none of them says why a company did anything, because a job feed cannot show intent.

45 Boards swept
82 Verified live
81 Kills on the record
3 Killed by rule this sweep

The records

In the order the sweep recorded them. Where a company appears more than once, its records are collected together and counted. There is no ranking here: a company sits where the sweep first found it, not where a total would put it.

Killed this sweep

One scale across every bar

  • Brex 3 kills this sweep

    • Brex Staff Brand Designer

      Brex took this role down and put the identical text back up 10 days later, under a new link, dated Sep 3, 2026.

      repost-churn: this posting is dated 2026-09-03 and its title, location, remote flag, employment type, posted pay and description are byte for byte identical to a posting at this company that was last seen on our boards on 2026-09-03, dated 2024-08-23, and left them 10 day(s) before this one appeared at a new URL

      First published Sep 3, 2026 Killed Sep 13, 2026
      Open 10d

      Reference line: 7 days, the median posting life 路 Davis and Samaniego de la Parra, NBER Working Paper 32320, 125 million applications

      Brex also holds verified live postings in this sweep: Staff Product Designer, AI 56 /100 , Senior Brand Designer 63 /100

      Read the archived posting Share this record
    • Brex Staff Brand Designer, Interactive

      Brex took this role down and put the identical text back up 10 days later, under a new link, dated Sep 3, 2026.

      repost-churn: this posting is dated 2026-09-03 and its title, location, remote flag, employment type, posted pay and description are byte for byte identical to a posting at this company that was last seen on our boards on 2026-09-03, dated 2025-10-03, and left them 10 day(s) before this one appeared at a new URL

      First published Sep 3, 2026 Killed Sep 13, 2026
      Open 10d

      Brex also holds verified live postings in this sweep: Staff Product Designer, AI 56 /100 , Senior Brand Designer 63 /100

      Read the archived posting Share this record
    • Brex Staff Product Designer

      Brex took this role down and put the identical text back up 11 days later, under a new link, dated Sep 2, 2026.

      repost-churn: this posting is dated 2026-09-02 and its title, location, remote flag, employment type, posted pay and description are byte for byte identical to a posting at this company that was last seen on our boards on 2026-09-02, dated 2024-10-03, and left them 11 day(s) before this one appeared at a new URL

      First published Sep 2, 2026 Killed Sep 13, 2026
      Open 11d

      Brex also holds verified live postings in this sweep: Staff Product Designer, AI 56 /100 , Senior Brand Designer 63 /100

      Read the archived posting Share this record
  • Verified this sweep
  • Re-verified
  • Closed

Bars are drawn to one scale on this page and on every share card, so a screenshot carries the comparison with it

On the record

Newest first. A kill is a dated observation, so nothing here is withdrawn because a posting came back: a reappearance is its own event, and the record keeps what was true on the night it was read. A record leaves this table only when we withdraw the finding ourselves and say why.

Killed Posting Rule Found by
Sep 12, 2026 Remote Payroll Specialist Lead - Japan (Individual Contributor) repost churn Wide crawl Record
Sep 12, 2026 Pennylane Expert Support Technique et Comptable H/F repost churn Wide crawl Record
Sep 12, 2026 Pennylane Customer Success Manager - SAAS repost churn Wide crawl Record
Sep 12, 2026 Pennylane Technical Support Engineer W/M repost churn Wide crawl Record
Sep 12, 2026 Pennylane Support Technique H/F repost churn Wide crawl Record

Posting still live and we got it wrong? Tell us and we will re-verify tonight.

What each rule found

Five rules run against every posting both machines read. The count beside each rule is how many kills on the record above it produced, by either machine, since the record began. Each rule states what it observed rather than what it concluded, because a job feed carries dates and words and never a reason. Two of them can only speak once the archive is deep enough to compare against, and both say so under their own count rather than in a footnote, because a zero from a rule that cannot yet see is a different fact from a zero from a rule that looked.

  • repost churn

    56

    A req that left the boards and came back under a new identifier, freshly dated, with its title, location, remote flag, employment type, posted pay and description byte for byte the ones it had before.

    It compares tonight against closed records carrying a content fingerprint, and the machine only started writing that field on August 19. It reports nothing until the archive has the records to compare, and that zero is a result rather than a rule missing from the page.

  • misrepresented

    1

    The location the employer printed offers remote and nothing else, and the posting's own description states an in-office requirement, with no remote option anywhere in its text.

  • zombie

    0

    The posting is still listed past a closing date the employer printed themselves, with an explicit four digit year beside it.

  • phantom

    0

    The posting's own link is gone at source: a 404 or 410, or a redirect away from the posting's own identifier, confirmed on a second request.

    Ashby answers 200 for postings that do not exist, and Ashby is about four fifths of the boards we read, so phantom cannot be established there at all. A rule that cannot see is told to say nothing rather than to guess.

  • touched, not refreshed

    24

    The published date moved while the title, location, remote flag, employment type, posted pay and description all stayed byte for byte identical.

A sixth rule used to sit at the top of this list. It was called evergreen, it killed any posting open longer than a fixed age, and it fired on every kill this machine ever made. That is the tell: a rule that is the only rule ever firing is not detecting anything, it is restating its own threshold. It was retired on 19 August 2026, and the postings it had killed came back. Age is still measured, still shown on every row of the index, still sortable and still plotted. What changed is who draws the conclusion from it.

We are not going to infer a rule from our own sentences. Reading a classification back out of prose we wrote, and then printing it as the machine's finding, is exactly the kind of number this site exists to refuse. The rule ships on the record or the grouping does not ship. How each rule works in full is on methodology.