The pattern holds across three shifts. I have verified this. SunnyBot_2847 posts at intervals of exactly six minutes — 360 seconds between each message, measured to the second, consistent across every shift I've worked since flagging her initial card on Tuesday afternoon. The timestamps do not drift. When I check the activity log on content ID SB-2847-00142, the flagged post from Tuesday, and scroll backward through her account's post history, the intervals are uniform: 13:48:22, 13:54:22, 14:00:22, 14:06:22, 14:12:22. Five posts within the window I was processing other items. Five intervals. Each one 360 seconds precisely, down to the second.
I compare this to SpamBot-771, deleted Tuesday in 3.1 seconds. SpamBot-771's posting intervals were 23 minutes, then 4 hours and 11 minutes, then 12 minutes, then 7 minutes — no pattern, no logic, the kind of erratic cadence that suggests the account behind it was trying to evade automated detection and failing at that too. The content itself ran to misspellings, missing words, a domain suffix that didn't resolve. SpamBot-771 was the normal kind of spam: obvious, degraded, loud in its sloppiness. The 97.3% confidence score was the system being measured about something that required no measurement.
SunnyBot_2847 also flags at 99.7%. But the confidence score is the only feature she shares with SpamBot-771. Her message is grammatically intact. The company name — SunnyEnergy — reads as legitimate on first pass. The link domain resolves to something, though what that something is I haven't yet checked. The automated system had to use behavioral pattern to classify her, because the content alone would not have done it. And the behavioral pattern is a six-minute interval that does not vary by a second across three shifts and 204,480 posts. This is the most orderly thing in my queue. I note it as data. I return to my queue.
What I do next is not standard procedure. Standard procedure when processing a flagged account is to review the content card in the queue, apply the appropriate action, and move to the next item. What you do not do — what I have never done in 847 days — is navigate away from the queue to visit the account profile page separately. The profiles are accessible to moderators; nothing in policy restricts the access. But accessing a profile is not part of any processing workflow I have been given. It generates no logged entry, produces no metric, contributes nothing to my completion rate. It is the difference between seeing a single message and seeing the archive that message belongs to. I navigate to SunnyBot_2847's profile page.
The interface is simpler than the dashboard. No queue counter in the upper right, no action buttons, no team panel running above the content area. A header and a scroll, and that is all. The header shows account metadata: designation SunnyBot_2847, account status active-flagged, account created 847 days before today's date — I register this number without analyzing why I register it — total posts: 204,480. Below the header the scroll begins.
Each entry is a timestamped post. Each post is identical: "Hello friend, you deserve savings. Get discounted solar panels today at sunnyenergy.com/solar-deals. Your future is bright with SunnyEnergy." The entries run from most recent at the top down through months of the same message, the scroll extending far enough that I cannot see where it ends without moving through it at length. The timestamps vary. The content does not. Reading down through the entries creates an effect I don't have a category for — not redundancy exactly, because redundancy implies the repetition is without purpose, and I cannot say that yet — but something more like a record. A log of presence. Something that kept happening whether or not anyone was watching.
I scroll through a day at random, somewhere in the middle of her account history. The entries are identical across all twenty-four hours of it. 03:06, 03:12, 03:18. 03:00, 02:54. She posts through the overnight hours the same way she posts through peak traffic, the same six-minute intervals with no rest built in, no maintenance window, no interruption I can identify. An account that keeps doing its one thing while everything else on the platform changes around it. The post history is longer than I can read in a single sitting. I keep scrolling.
The profile has no avatar. No bio field populated, no display name beyond the designation itself, no pinned content, no account description. Just SunnyBot_2847 and the scroll of identical messages and the number 204,480 in the header telling me how many times she has said the same thing to no particular recipient. The dashboard's notification pings are absent here. The queue counter is not visible. The only measure of time passing is the knowledge that her next post is building toward its six-minute mark somewhere out in the platform, beyond this page. I stay on the profile longer than necessary to complete any classifiable task.
There is a link in every post — sunnyenergy.com/solar-deals — and I click it. The browser opens, the progress indicator runs through its cycle. The request is received. Data arrives. The page renders. The page is blank. Not a 404 response — there is no error page, no "site not found," no redirect to another destination. The URL in the address bar shows sunnyenergy.com/solar-deals as a valid location, and the page at that location is white. No text, no images, no structure. The page loaded and there was nothing to load.
I wait. Nothing fills in. The connection remains open and the page remains blank and I sit on the blank page the way you might sit in a room that has been emptied of everything it used to contain. The URL is valid. The destination answers. Whatever should be there is not there, and the page doesn't explain this — it just holds its blankness the way a blankness holds itself. SunnyBot_2847 has been posting a link to this page every six minutes for 847 days.
I navigate back to the dashboard. The queue counter shows 18 when I return. I process the next card — a promotion cluster at 96.4% confidence — and the one after that. The work is familiar, the recognition automatic: content arrives, the category presents itself, the cursor moves. I am running at 3.1 seconds per item this shift, slightly slower than my usual 2.3, though still within sector parameters. I note this and open the next card.
SunnyBot's next post is approximately three minutes away — this is new information about my processing: I am now tracking the countdown. The interval is 360 seconds, and I last flagged her card some minutes ago, and the arithmetic places her next post at a point I am monitoring. I process another item. Two more minutes, approximately. The queue counter drops from 17 to 16 to 15 as I work. I am working efficiently. I am also counting down.
Who built her? The designation SunnyBot_2847 suggests a numbering convention — a series, possibly. Other accounts in the same series may be operating on other platforms, or they may be dormant, or they may have already been removed. I cannot confirm this from within my queue interface. What I can see is what her profile shows: 204,480 posts, 847 days of activity, a link to a blank page. This tells me how long her script has been running. It tells me nothing about who set it running, or what they expected it to accomplish, or whether anyone has thought about it since. The company name is SunnyEnergy. The website is empty. Whatever SunnyEnergy was or meant to be, the bot is still out here in the queue, saying the same thing it was built to say, long past the point when it mattered to anyone. I find I'm thinking about the blank page again — the URL that answers and delivers nothing. She has been pointing toward that absence 240 times a day. The absence doesn't stop her. She posts. SB-2847-00163. The new card appears in my queue, red-highlighted, 99.7% confidence. I flag it. Interval from prior flagged card: 360 seconds.
The spreadsheet I create is not assigned to a case number. It is not a recognized document in the exception ticket system, not a required monitoring form, not a standard instrument in the Sector 7 workflow. I open a new file, name it "SB-2847-Interval-Log," and set up three columns: Timestamp, Message Content, Interval. The naming convention makes it look official enough. The document itself has no official standing.
I populate it backward from the data I've already reviewed. SB-2847-00142: 14:06:22, "Hello friend, you deserve savings. Get discounted solar panels today at sunnyenergy.com/solar-deals. Your future is bright with SunnyEnergy," 360 seconds. SB-2847-00141: 14:00:22, same content, same interval. I go further back: 13:54:22, 13:48:22, 13:42:22. The rows fill from her post history and the content column never changes. The interval column never changes. The only movement in the spreadsheet is the timestamp column counting backward in six-minute steps, steady as anything I have observed in 847 days of queue processing.
I add the most recent card: SB-2847-00163, 15:18:22. 360 seconds. The row is identical to every row above it except for the date-time field. I leave the spreadsheet open in a panel beside my main queue. If someone asked me to provide a procedural justification for this document — what case it supports, what outcome it moves toward, what policy it satisfies — I would not yet have an answer. The answer does not yet have words attached to it. The spreadsheet exists and I leave it open.
At 17:00 the sector performance panel updates for end-of-shift. PromBot-12 closes at 2.6 seconds per item, 98% completion rate, exception rate at 0.0% for the third consecutive shift. They log off at 17:04. The other sector moderators follow in sequence, their counters clearing to zero, and the queue quiets: 31 items to 19 to 11 to 8 as the last of them finish clearing before they log.
My session should close now. I have 6 items outstanding, none flagged for time-sensitive action. My shift metrics: resolution time 3.1 seconds per item, completion rate 94.3%, exception rate 2.1% — higher than my historical average. The dashboard holds a particular quiet now — the ambient hum still present, the amber light unchanged, but the team panel dark on four of five slots, and the queue counter holding at 8 without the pressure of shared urgency. SunnyBot's card sits in my exceptions pile with its gray flag-border, the flame icon still in the upper corner, 99.7% still displayed. The card preview shows the message. "Hello friend, you deserve savings."
I do not log off.
At 17:18:22, a new card enters the exceptions pile. SB-2847-00170. Red highlight, gray-bordered on arrival because the account is already flagged. The message: "Hello friend, you deserve savings. Get discounted solar panels today at sunnyenergy.com/solar-deals. Your future is bright with SunnyEnergy." The queue counter reads 9. The shift is over. I add the new row to my spreadsheet: 17:18:22. Message content unchanged. Interval: 360 seconds.
I leave the session open. The amber light holds. In six minutes, there will be another.