1
00:00:05,160 --> 00:00:08,560
Speaker 1: Hello, I'm welcomed stories all the time. Glad you are here.

2
00:00:09,160 --> 00:00:11,599
Let's get into it. There's a certain kind of light

3
00:00:11,640 --> 00:00:13,359
you learned to fear after and enough years an id.

4
00:00:14,039 --> 00:00:16,320
It's not the dark blue glow over crisis screen or

5
00:00:16,359 --> 00:00:18,440
the dozy pulse of a corporate dashboard at noon, but

6
00:00:18,519 --> 00:00:21,359
something thinner, perpetual flicker that hovers on the periphery, whispering

7
00:00:21,440 --> 00:00:23,160
that something in the machine well has slipped out of

8
00:00:23,160 --> 00:00:25,800
place while you weren't looking. It was pushing close to

9
00:00:25,839 --> 00:00:28,440
one fifty a m. The city outside my window dissolved

10
00:00:28,440 --> 00:00:30,399
in sodium vapor and the wine of a distant sireen.

11
00:00:30,519 --> 00:00:32,479
When the new security monitor I'd ritten popped up its

12
00:00:32,560 --> 00:00:36,359
latest anomally badge, I'd already muted the group chat the

13
00:00:36,399 --> 00:00:39,560
other contractors had signed off years ago. Both coasts quiet now,

14
00:00:39,560 --> 00:00:42,439
except for the odd slack emoji floating beside on resolved tickets,

15
00:00:43,079 --> 00:00:46,759
the endless journ of ride logs, driver routes, support, bought communications,

16
00:00:46,799 --> 00:00:49,359
normally just background radiation now felt like a low sided

17
00:00:49,439 --> 00:00:52,759
compressing and from every tap tonight the badge was red

18
00:00:52,799 --> 00:00:56,479
instead of its usual yellow. I scrolled from instinctively drumming

19
00:00:56,479 --> 00:00:59,159
the edge of my desk. The anomaly was tagged no

20
00:00:59,280 --> 00:01:02,320
transit idea, nested under an oftened ride detail marked with

21
00:01:02,320 --> 00:01:05,079
a midnight time stamp. When I cracked open the ride

22
00:01:05,120 --> 00:01:07,120
in staging, the details found out in a panel in

23
00:01:07,159 --> 00:01:11,560
their familiar dull gray origin, destination invisible, trip flagged for deletion,

24
00:01:11,799 --> 00:01:15,280
customer and driver entes wipe. I paused at the chat transcript,

25
00:01:16,040 --> 00:01:18,079
just one line short enough to fit easily in the

26
00:01:18,120 --> 00:01:21,760
preview bubble. Is anyone there? He never left the car.

27
00:01:22,400 --> 00:01:24,680
The message was time stamped two forty three a m.

28
00:01:24,879 --> 00:01:27,239
On after the support chat traffic usually flat lined him

29
00:01:27,239 --> 00:01:30,000
well after my own teens on call window. The center

30
00:01:30,000 --> 00:01:32,319
field was only half filled a hash matching no current

31
00:01:32,400 --> 00:01:35,000
driver account history blanked except for the account creation and

32
00:01:35,040 --> 00:01:37,400
deletion dates, and even those conflicted as if a clip

33
00:01:37,400 --> 00:01:39,959
A script had snip time lines out at random, as

34
00:01:39,959 --> 00:01:41,840
I have it. Over the bubble, A fine wine rattled

35
00:01:41,840 --> 00:01:44,879
my laptop speakers, raise it thin. The fan spun up

36
00:01:44,920 --> 00:01:46,920
to you a sudden grind, like gravel in a pipe.

37
00:01:47,359 --> 00:01:49,719
I'd had the suppression but non reflex, but all it

38
00:01:49,719 --> 00:01:52,959
did was collapse the lock. After a moment, I expanded

39
00:01:52,959 --> 00:01:55,200
the audit trail around the ride, fingers grazed by the

40
00:01:55,200 --> 00:01:58,280
warmth of the screen, the usual artifacts custered near it,

41
00:01:58,480 --> 00:02:01,480
health check fail, deleting rope and error ride not found

42
00:02:01,519 --> 00:02:05,200
on driver ledger. Then a second unrelated entry time stump

43
00:02:05,239 --> 00:02:08,439
two forty six a m reading only goes rye clean

44
00:02:08,520 --> 00:02:11,599
up complete. It should have been another scap for the trotspinaud,

45
00:02:11,639 --> 00:02:14,000
but nowhere near as bad as fishing attempts or accidental

46
00:02:14,120 --> 00:02:16,800
data leaks. But the message itself, the slightly desperate question

47
00:02:16,879 --> 00:02:20,000
hanging there, wouldn't let go. I checked the system camera,

48
00:02:20,120 --> 00:02:22,719
just my own reflection in the dim glow, unremarkable except

49
00:02:22,759 --> 00:02:25,439
for a twitchiness at the jaw. I typed a fresh query,

50
00:02:25,599 --> 00:02:28,319
mind taking for anything like an explanation, but nothing else

51
00:02:28,360 --> 00:02:31,159
surfaced in that log window. All the while, that thread

52
00:02:31,159 --> 00:02:33,840
thin digital rain seemed to hiss in my headphones. The

53
00:02:33,879 --> 00:02:36,039
small home office that most evenings felt like my safe

54
00:02:36,080 --> 00:02:39,280
half cocoon now pressed in with a new, uneasy hush.

55
00:02:39,319 --> 00:02:41,240
Somewhere out there, deep in the lats work of the

56
00:02:41,240 --> 00:02:43,840
company's system, someone or something was trying to be seen,

57
00:02:44,439 --> 00:02:46,159
or maybe the thing with a voice was only just

58
00:02:46,240 --> 00:02:49,080
learning how to listen. I thought for a second, I

59
00:02:49,080 --> 00:02:50,960
saw something move in the glass of the window beside

60
00:02:51,000 --> 00:02:53,680
my monitor, but it was just the city distant headlights

61
00:02:53,759 --> 00:02:56,719
drifting pass nothing more. There was a little point in

62
00:02:56,759 --> 00:02:59,919
staying up longer. I flagged the ride for a secondary scan,

63
00:03:00,439 --> 00:03:03,000
locked my laptop and sat there for several minutes, hands

64
00:03:03,000 --> 00:03:05,400
flat on the cooling surface, letting nerves out in the

65
00:03:05,479 --> 00:03:08,599
charge silence. There's comfort in the rules of beckend work

66
00:03:08,719 --> 00:03:12,360
input process perge, but the line between digital house cleaning

67
00:03:12,400 --> 00:03:16,400
and hiding evidences in practice always thinner than the manual's claim,

68
00:03:16,639 --> 00:03:19,039
and some things clinging, odd things refused to be raised.

69
00:03:19,680 --> 00:03:21,840
I powered everything down and watched the faint pulse of

70
00:03:21,879 --> 00:03:24,439
the ratter in the corner. It blinked at me, steady

71
00:03:24,479 --> 00:03:27,039
as a slow harpy. No more life, if you could

72
00:03:27,039 --> 00:03:29,439
call it. That started late with the electric kettles thrown

73
00:03:29,520 --> 00:03:32,120
rattling over the stale hush of the apartment. Miyone is

74
00:03:32,120 --> 00:03:35,000
a streamlined existence by design. Never mugne its hook, every

75
00:03:35,000 --> 00:03:37,400
cable wound, every trace of old day to wipe nightly

76
00:03:37,400 --> 00:03:40,599
from devices I don't trust. Since taking this contract a

77
00:03:40,719 --> 00:03:42,840
year and a half ago, I'd stopped caring much about

78
00:03:42,879 --> 00:03:45,680
the scraps of personality most people leave scattered in their rooms,

79
00:03:46,319 --> 00:03:48,560
pulses culled at the edges, a dying house, blunt in

80
00:03:48,599 --> 00:03:51,960
the kitchen, all silent and imposing. The real world taxi

81
00:03:52,080 --> 00:03:54,639
is passing down the block. Shouts muffled by glass felt

82
00:03:54,639 --> 00:03:57,800
like a foreign signal, occasionally flickering through. Most of my

83
00:03:57,879 --> 00:04:00,319
day passed between a rays of sanitized dashboard words and

84
00:04:00,360 --> 00:04:04,360
status checks. The company a rideshair conglomerate with servers everywhere,

85
00:04:04,400 --> 00:04:06,840
and people now were preferred onboarding contractors for their most

86
00:04:06,840 --> 00:04:11,240
thenkas bacan tasks. Contractors didn't ask too many questions, didn't

87
00:04:11,280 --> 00:04:14,319
require a seat at the table, our standing video calls

88
00:04:14,360 --> 00:04:17,560
rarely lingered on names. I was and cheebas in the directory.

89
00:04:17,600 --> 00:04:20,639
Allowed to work in sweatshirts and slippers provided productivity metrics

90
00:04:20,639 --> 00:04:23,759
were met. From my window, A glimpsed a slice of city,

91
00:04:23,800 --> 00:04:26,439
a bare alley slash with graffiti, still by the glassy

92
00:04:26,519 --> 00:04:29,920
quiet of late morning. Sunlight when it arrived, came thin

93
00:04:29,959 --> 00:04:32,600
and mechanical through the clouds, always filtered, always too brief.

94
00:04:33,160 --> 00:04:35,519
The only reminders of humanity and this job came through

95
00:04:35,560 --> 00:04:39,240
slack jokes about raised conditions. Copy pasted memes. The companies

96
00:04:39,240 --> 00:04:41,279
which I bought bring us to celebrate a team win

97
00:04:41,360 --> 00:04:45,040
of the week. I like the clean separation order. Encode

98
00:04:45,079 --> 00:04:47,879
is its own comfort. Every morning I checked my own

99
00:04:47,879 --> 00:04:51,240
scheduled scripts to use logs, corrupt, old chat transcripts, archived

100
00:04:51,319 --> 00:04:54,240
permissions maintained. The chaos below the dash were to the

101
00:04:54,240 --> 00:04:57,240
snarls of users at variables. Legacy IPI, lashed together by

102
00:04:57,279 --> 00:04:59,680
duct tape, offered problems only if you look too closely.

103
00:05:00,319 --> 00:05:03,839
Everything measured in arrow rates, everything disposable. That's what I

104
00:05:03,879 --> 00:05:07,560
told myself for months. Anyway, Occasionally, though, there were ticket

105
00:05:07,560 --> 00:05:10,439
I couldn't quite resolve. A ride that failed to clear

106
00:05:10,480 --> 00:05:14,040
from a ledger, a chat from a deleted user trash.

107
00:05:14,240 --> 00:05:17,519
The leads called these companied tritus not with overtime. But

108
00:05:17,600 --> 00:05:20,600
I'd learned, over several contracts and two failed start ups,

109
00:05:20,680 --> 00:05:24,879
that all platforms collect ghosts, often data, soombie users, rides

110
00:05:24,920 --> 00:05:27,319
scheduled after the system's own clock insists no one was

111
00:05:27,399 --> 00:05:31,000
on line. Slack channels filled with quite paranois. Sometimes did

112
00:05:31,000 --> 00:05:33,319
you see another ghost trip last night? Some one might ask.

113
00:05:34,000 --> 00:05:36,920
Usually it got laughed off. I'd poked around the form

114
00:05:36,959 --> 00:05:39,240
some months ago. Found an old inten no wiki entry

115
00:05:39,279 --> 00:05:42,240
redacted but not the leaded, musing about phantom rids that

116
00:05:42,319 --> 00:05:45,040
popped up to spite or customer facing logs saying otherwise

117
00:05:45,720 --> 00:05:47,759
every dev cycle, some one tried to close the ticket

118
00:05:47,800 --> 00:05:51,920
on those. Nobody succeeded. Most of my social life, such

119
00:05:51,959 --> 00:05:55,240
as it existed, was mediated through cables and screens. My

120
00:05:55,319 --> 00:05:58,800
mother's emails blinked in cheerful as check out receipts. Friends

121
00:05:58,800 --> 00:06:00,480
from college popped up once or WHI was a month,

122
00:06:00,560 --> 00:06:04,160
or rather the avatars did. Still it suited me. The

123
00:06:04,199 --> 00:06:08,120
digital world is predictable, banded, or it should be. What

124
00:06:08,199 --> 00:06:11,680
the company didn't encourage was curiosity. We were tesked to patch,

125
00:06:11,839 --> 00:06:14,480
to elete and move on, not to trace anomalies to

126
00:06:14,519 --> 00:06:18,160
their roots. Their privacy compliance training had a quiet emphasis

127
00:06:18,160 --> 00:06:21,160
on the dangers of privileged misuse. Dig deeper and you rest,

128
00:06:21,160 --> 00:06:25,240
triggering audits warnings, and the silent, unblinking scrutiny of security.

129
00:06:25,879 --> 00:06:28,839
Still the ride from last night, no transit ida chat transcript.

130
00:06:28,920 --> 00:06:31,759
The odd phrasing brickled at my mind through lunch. Most

131
00:06:31,759 --> 00:06:35,360
bogues have patterns, most ghosts of someone's fingerprints on them.

132
00:06:35,639 --> 00:06:38,480
By late afternoon with the sun already giving up, I

133
00:06:38,519 --> 00:06:41,160
found myself queuing up another search window coffee gone stair

134
00:06:41,199 --> 00:06:43,959
beside me, trash or not, the ride wasn't gone yet,

135
00:06:44,480 --> 00:06:46,839
and this system, for all its self scrubbing veins, never

136
00:06:46,920 --> 00:06:50,199
really forgets. It started with a simple query for riodes

137
00:06:50,199 --> 00:06:52,439
flagged with a no transit idea, normally from the last

138
00:06:52,519 --> 00:06:56,000
ninety days. Ordinarily these would be edge cases, trips canceled

139
00:06:56,040 --> 00:06:58,639
before pick up accounts to lead of midry, all discarded

140
00:06:58,639 --> 00:07:01,480
within twenty four Eyes by auto made it sweeps, but

141
00:07:01,560 --> 00:07:04,519
the results didn't fit the usual decay pattern. Dozens of

142
00:07:04,560 --> 00:07:07,240
rites some weeks apart, all processed round midnight with the

143
00:07:07,279 --> 00:07:10,240
nagative payment delta, no fare, no tip, no origin or

144
00:07:10,279 --> 00:07:13,600
destination address, only a pair of unhelpful hashes in the logs.

145
00:07:14,240 --> 00:07:16,720
Oddis of all, the customer and driver accounts were both

146
00:07:16,720 --> 00:07:20,680
deleted immediately after the ride supposedly completed. Still a kend

147
00:07:20,720 --> 00:07:23,839
reference idea survived in cold storage and linked to anything public.

148
00:07:24,560 --> 00:07:26,360
I pulled up the data for three of the oldest

149
00:07:27,079 --> 00:07:32,199
New York City Chicago Thollless, each time stamped between twelve

150
00:07:32,319 --> 00:07:35,360
zero and twelve twenty a m. The metadata sparse as

151
00:07:35,360 --> 00:07:37,920
it was repeat it, no payment, no route mapping, the

152
00:07:37,920 --> 00:07:41,839
same airstream ghost right Cleano complete registered afterwards, no ratings,

153
00:07:41,959 --> 00:07:44,319
enters populated. Even though the cobe was supposed to prompt

154
00:07:44,360 --> 00:07:47,839
both parties after every ride, the database obviously still held

155
00:07:47,839 --> 00:07:50,839
these logs, even if the logic was meant to suppress them.

156
00:07:51,160 --> 00:07:54,519
As I dug, more anomalies surface. Four rides from different cities,

157
00:07:54,600 --> 00:07:57,560
each with their own invisible markers, clustered around holidays or

158
00:07:57,600 --> 00:08:00,680
moments of heavy traffic. None ever appear aired in customer

159
00:08:00,680 --> 00:08:04,759
receipts or driver dashboards. The logs stuck around like digital barnacles.

160
00:08:05,360 --> 00:08:08,240
What a nerved me Most were the chat transcripts, while

161
00:08:08,240 --> 00:08:11,680
most support chats are long exchanges but tips lost sunglasses,

162
00:08:11,800 --> 00:08:14,240
phone chowgers. A few of these phantom rides had messages

163
00:08:14,279 --> 00:08:17,680
one line rarely two from the driver handle. Each carried

164
00:08:17,680 --> 00:08:20,360
a time stump long after normal support ires, and each

165
00:08:20,399 --> 00:08:24,439
account was marked deleted, often within minutes afterscending one can

166
00:08:24,519 --> 00:08:28,279
you see my route? She didn't get up? Another nothing

167
00:08:28,279 --> 00:08:31,360
here but falk am madan one simply read is any

168
00:08:31,360 --> 00:08:35,679
one there? He never left the car. The repetition wasn't accidental.

169
00:08:36,279 --> 00:08:38,679
It felt like someone was improvising a distressed signal and

170
00:08:38,679 --> 00:08:41,399
code space, looping it through right logic, hoping it would

171
00:08:41,399 --> 00:08:44,759
slip through whatever digital erases swept the platform. Nightly, I

172
00:08:44,879 --> 00:08:48,399
skimmed through the tripp distance fields. Each was anomalously lawn

173
00:08:48,480 --> 00:08:50,879
or short summer zero point one miles. Others are two

174
00:08:50,960 --> 00:08:53,799
hundred eight point seven faalties that couldn't possibly be correct.

175
00:08:54,440 --> 00:08:57,399
Each ride showed no passenger review and no known payment method.

176
00:08:58,000 --> 00:08:59,600
I ran a quick check in the driver I d

177
00:09:00,399 --> 00:09:03,600
all wiped and I found in current pyrol and yet

178
00:09:03,799 --> 00:09:06,240
their chat locks had been posted IROs, even days after

179
00:09:06,279 --> 00:09:09,519
their own accounts were officially terminated. A cold ripple went

180
00:09:09,600 --> 00:09:13,200
up my spine. I scrolled father back, quietly and suddenly tingling.

181
00:09:13,679 --> 00:09:15,559
In my time at the company, I had swept up

182
00:09:15,559 --> 00:09:18,600
plenty of strange locks, but these these felt less like

183
00:09:18,600 --> 00:09:22,120
bugs than intentions. Iurs after midnight accounts there should have

184
00:09:22,120 --> 00:09:25,919
been dead poking messages into voided channels, transcripts truncated, as

185
00:09:25,960 --> 00:09:27,799
if some one listening on the other end had snipped

186
00:09:27,799 --> 00:09:30,440
the feed. I copied the logs into a text file,

187
00:09:30,519 --> 00:09:33,600
locking it twice with encryption. For the first time in years,

188
00:09:33,679 --> 00:09:36,440
I felt the old ember of curiosity tinged not with excitement,

189
00:09:36,440 --> 00:09:39,279
but with a twist of bread from my speakers. Static

190
00:09:39,360 --> 00:09:42,360
kelt thinly through so faint I almost dismissed it. The

191
00:09:42,399 --> 00:09:46,399
system clock ticked on, digital rain running down. Step, of course,

192
00:09:46,519 --> 00:09:49,279
would not come easily. The next day I set myself

193
00:09:49,320 --> 00:09:51,759
to solving the puzzle in ernest, not for the company's sake,

194
00:09:52,000 --> 00:09:54,679
not even for personal pride, but for something more elemental,

195
00:09:54,840 --> 00:09:58,519
an urge to reclaim order from this rolling hid and chaos. First,

196
00:09:58,600 --> 00:10:00,320
I wrote a script to Crawford Ride's with the no

197
00:10:00,399 --> 00:10:03,440
transit idea nominally, but also to correlate with deleted driver

198
00:10:03,519 --> 00:10:06,759
and customer accounts. The result was growing table peppered with

199
00:10:06,840 --> 00:10:09,559
rides and dozens of cities Miami, Seattle, Atlanta to run to,

200
00:10:09,600 --> 00:10:13,279
always around midnight, always with payment indicators set TOANNEL, deep

201
00:10:13,360 --> 00:10:16,240
diving into the transaction lolks. I cross checked ride creation

202
00:10:16,279 --> 00:10:19,840
events with customer service pings. Most reel rights generated at

203
00:10:19,879 --> 00:10:22,159
least one support for billing event, but the ghost rides

204
00:10:22,159 --> 00:10:25,840
had nothing, no account creation IP, no devised fingerprint, not

205
00:10:25,879 --> 00:10:28,960
even the expected customer support stub. Some now, these were

206
00:10:29,000 --> 00:10:31,360
skirting the very frameworks built to keep arant rides from

207
00:10:31,360 --> 00:10:35,399
polluting production. I ran a geolocation cluster analysis, mapping pins

208
00:10:35,399 --> 00:10:39,120
for every ghost ride found. To my surprise, patterns bloomed

209
00:10:39,480 --> 00:10:42,360
certain cities enter sore clusters every few months, rides lining

210
00:10:42,480 --> 00:10:46,679
up like faint after images near major intersections, busy bus terminals, airports,

211
00:10:46,720 --> 00:10:49,840
and almotas, whose names ranging bell like with the distant ache.

212
00:10:49,919 --> 00:10:52,919
I highlighted three clusters that talented almost perfectly with publicized

213
00:10:52,919 --> 00:10:56,639
cases from local news headlines, missing persons, open investigations, cold

214
00:10:56,679 --> 00:11:00,000
case forms. Some clusters matched dates. When the company rolled

215
00:11:00,320 --> 00:11:04,000
new infrastructure requests for older cloud archive data hit walls

216
00:11:04,720 --> 00:11:07,519
privacy compliance, the response bart replied, even though I was

217
00:11:07,519 --> 00:11:10,679
well inside the company's internal permission schema. I put in

218
00:11:10,720 --> 00:11:14,720
the request again, marked as urgent, and waited. Tensions rose.

219
00:11:15,399 --> 00:11:17,960
A fagged findings on a private's birdsheet hidden under a

220
00:11:17,960 --> 00:11:20,879
benign file name. Small details glimmered in the data. When

221
00:11:20,879 --> 00:11:23,639
the anomaly spiked, support locks showed redacted entries or ticket

222
00:11:23,679 --> 00:11:27,000
closed with the terse reassigned, sometimes with no explanation at all.

223
00:11:27,600 --> 00:11:30,279
Every time I checked, the interfish shivered like something resisting

224
00:11:30,320 --> 00:11:33,639
being seen. I tried messaging and engineering leads, and oli

225
00:11:33,720 --> 00:11:36,440
Rajan the only one I'd seen handle lager clean up jobs.

226
00:11:37,080 --> 00:11:40,360
She replied minutes later with a clipped direct message, don't

227
00:11:40,360 --> 00:11:44,080
waste time on zombie tickets. Stick to the scope. No

228
00:11:44,120 --> 00:11:47,600
one wants audits. I wondered if she was brushed off genuinely,

229
00:11:47,720 --> 00:11:49,360
or if it was a performance. Every one knows the

230
00:11:49,399 --> 00:11:52,360
cost of prying too far. Thirty minutes after that, a

231
00:11:52,399 --> 00:11:56,320
private message pinged into my inbox. The sender's handle was unfamiliar,

232
00:11:56,320 --> 00:11:58,240
a string of numbers and admined at the end, one

233
00:11:58,279 --> 00:12:01,399
I vaguely remembered from last year's ORDI now long transferred

234
00:12:01,440 --> 00:12:05,799
or deleted. The message was only four words, stop following me.

235
00:12:06,559 --> 00:12:09,879
I checked the handle last act three hundred seventy two

236
00:12:09,960 --> 00:12:13,440
days ago. Had someone broken retention protocols or was this

237
00:12:13,480 --> 00:12:16,240
an automated warning. If so, it was crafted to be

238
00:12:16,279 --> 00:12:19,679
too human, too precise, No foniness in the spacing, no

239
00:12:19,759 --> 00:12:23,200
outo corrections. The next day, my cloud storage ticket was

240
00:12:23,240 --> 00:12:26,879
closed for cause, date and validation, no further explanation given.

241
00:12:27,399 --> 00:12:29,879
I sat back, feeling as if the room was smaller.

242
00:12:30,000 --> 00:12:33,200
The air gone heavy outside, cause crawled by head less,

243
00:12:33,240 --> 00:12:36,000
like fish sliding beneath thick glass. There was a point

244
00:12:36,000 --> 00:12:38,399
in all this whereto would have seemed melodramatic, a young

245
00:12:38,440 --> 00:12:42,080
contractor haunted by digital shadows, evidence only half formed. But

246
00:12:42,279 --> 00:12:44,639
in a quiet, hummy office, I felt watched in a

247
00:12:44,639 --> 00:12:46,679
new way, as if my queers themselves pinged back to

248
00:12:46,720 --> 00:12:49,840
some silent observer, immine to oudits and code reviews. The

249
00:12:49,879 --> 00:12:52,240
pragmatic solution would have been to close out the logs,

250
00:12:52,720 --> 00:12:56,200
wipe the spreadsheet, and let the ghosts recede. But the compulsion,

251
00:12:56,320 --> 00:12:59,279
now urgent and compulsive, kept driving me deeper in the

252
00:12:59,320 --> 00:13:01,960
dimness before I found a way to access a backpack

253
00:13:02,000 --> 00:13:05,000
I've not yet loved. Behind the privacy fil it folders

254
00:13:05,000 --> 00:13:07,600
bopped with right event packets, thousands of them, time stamped

255
00:13:07,639 --> 00:13:10,120
in twenty four IRO rolls, some no longer reference by

256
00:13:10,120 --> 00:13:14,519
any live dashboard, among them dark and archives. The Darken

257
00:13:14,559 --> 00:13:16,600
files were brief ten seconds, some as short as for

258
00:13:17,320 --> 00:13:19,799
the first video, taggert to a ghost ride and Philly

259
00:13:19,879 --> 00:13:22,240
opened on a jitter of pixels, the camera lens smeared

260
00:13:22,240 --> 00:13:25,360
by condensation neon lights running into rain outside a rear window.

261
00:13:26,000 --> 00:13:28,759
The driver's fum glowed on the dash half way through

262
00:13:28,799 --> 00:13:31,279
a passenger's that line appeared as slow at shoulders hunched

263
00:13:31,320 --> 00:13:33,120
under a hoe face. A blue gray blow with a

264
00:13:33,200 --> 00:13:36,399
lens never managed to focus. The figure stepped into the car,

265
00:13:36,480 --> 00:13:39,639
a shadow among city shadows. The video ended abruptly with

266
00:13:39,679 --> 00:13:42,639
the sound of the driver's seat creaking, nothing else. The

267
00:13:42,679 --> 00:13:45,879
next two files from Rygiers Apart in Heuson and Minneapolis,

268
00:13:45,879 --> 00:13:50,279
repeated the same effect. The passenger, identical frame, identical dark clothing,

269
00:13:50,360 --> 00:13:52,759
same blurb, asage slipped into the back seat, torso shifting

270
00:13:52,759 --> 00:13:55,200
out of focus. Then the feed cut dead, sometimes with

271
00:13:55,240 --> 00:13:58,720
the static burst, sometimes with a dull, subsonic pop. There's

272
00:13:58,759 --> 00:14:01,080
no way a single person could appeared in every city

273
00:14:01,120 --> 00:14:04,600
across years, crossing impossible distances, but the outline never changed.

274
00:14:05,279 --> 00:14:07,879
I ran facial detection, but the scanner crashed up with

275
00:14:07,879 --> 00:14:11,440
a processing error. The forefile hung for several seconds before

276
00:14:11,440 --> 00:14:14,559
halting on a frozen frame. At first, the image dissolved

277
00:14:14,559 --> 00:14:17,960
into artifacted bands, the sound a thickening whisper, unintelligible, but

278
00:14:18,039 --> 00:14:21,679
Rythick I suspected audio corruption, but as I looped the clip,

279
00:14:21,759 --> 00:14:26,039
it resolved almost forming words are you there? It was loud,

280
00:14:26,080 --> 00:14:28,799
barely a distortion, more suggestion and statement, but the cadence

281
00:14:28,840 --> 00:14:31,480
fit the lines from the chat logs, the same hunger

282
00:14:31,519 --> 00:14:33,240
at the same sense of someone knocking in a place

283
00:14:33,279 --> 00:14:36,360
without doors. I stopped, a heart beating high in my throat.

284
00:14:37,000 --> 00:14:39,039
The glow from the monitor painted the office is far

285
00:14:39,120 --> 00:14:42,600
walpale gray shadows pulling in the corners. This was no

286
00:14:42,679 --> 00:14:45,039
longer just a back end bug. No meridmins grew up,

287
00:14:45,039 --> 00:14:48,279
but something stranger. Threads woven into dated by someone or

288
00:14:48,320 --> 00:14:51,080
something using the infrastructure not to hide mistakes, but to

289
00:14:51,159 --> 00:14:54,559
lay a mask over whatever was actually transpiring. If a person,

290
00:14:54,720 --> 00:14:57,879
what use was all that effort, ficking rise, petted logs overwriting,

291
00:14:57,919 --> 00:15:00,519
driver and passenger accounts were scrambling time d stamps and

292
00:15:00,559 --> 00:15:03,720
identities dozens at a time. If not, what was his

293
00:15:03,799 --> 00:15:06,600
face's passenger doing haunting the system through glitch, video and

294
00:15:06,600 --> 00:15:09,559
echoing chat lines. The glow of the laptop delled as

295
00:15:09,559 --> 00:15:11,960
I took my hands off the keyboard. I sat for

296
00:15:12,039 --> 00:15:14,440
long minute, letting the last frame burone into my mind.

297
00:15:15,080 --> 00:15:17,440
For the first time since starting remote work, I felt

298
00:15:17,480 --> 00:15:21,120
truly watched a sense of some other presents, digital cold intent.

299
00:15:21,840 --> 00:15:24,279
The Workham's green a led flickered for a split second,

300
00:15:24,360 --> 00:15:27,480
then when dark, as if blinking, I pulled the power cord.

301
00:15:27,759 --> 00:15:30,320
Let my eyes are just to the dark, far below

302
00:15:30,399 --> 00:15:33,399
the city's hum stuttered something in the code or above

303
00:15:33,440 --> 00:15:36,840
It was surveiling, maybe for years. When the chill faded,

304
00:15:36,879 --> 00:15:39,159
I realized this wasn't but one ride or even a

305
00:15:39,240 --> 00:15:42,519
rogue admin. It felt bigger, orchestrated, pride loose from the

306
00:15:42,559 --> 00:15:45,840
skeleton of the company by invisible hands. And if the

307
00:15:45,879 --> 00:15:48,840
company's own systems could be subverted so easily, then every ride,

308
00:15:48,960 --> 00:15:51,720
every message, every EGOS event was a potential signal, one

309
00:15:51,720 --> 00:15:54,200
side calling out, hoping to the acknowledge, or maybe warning

310
00:15:54,240 --> 00:15:57,200
me to turn away. I lay awake for eyres, unable

311
00:15:57,240 --> 00:15:59,840
to silence the imagined hums and shifting shadows leaking from

312
00:15:59,840 --> 00:16:02,799
the edges of the glass. The next week, I chased

313
00:16:02,840 --> 00:16:06,600
every ardity to ground time stamps, ride geo locasions, and

314
00:16:06,639 --> 00:16:09,320
fragments of deleted chat locked mapped are on too spreadsheets

315
00:16:09,559 --> 00:16:13,559
pasted into sprawling diagrams sprawling over my walls. I filtered

316
00:16:13,559 --> 00:16:16,120
for the anonymised passenger's signature of the low statu key

317
00:16:16,159 --> 00:16:19,080
blow captured in each figure. Musket strained at the edges

318
00:16:19,120 --> 00:16:22,039
of the company's axis controls sometimes slow in or crashing,

319
00:16:22,120 --> 00:16:24,519
always producing one or two more ghost rides than logic

320
00:16:24,519 --> 00:16:28,080
search should be possible. Technical connections began to call less.

321
00:16:28,840 --> 00:16:32,440
Certain ghost events unnoticed, always followed or preceded by administrative

322
00:16:32,440 --> 00:16:35,480
overright locks. Users with high ranking admin privileges forcing rides

323
00:16:35,480 --> 00:16:39,799
into production bypassing the ordinary locking protocols. Their ACXIS track

324
00:16:39,840 --> 00:16:43,440
didn't survive, disappearing beneath at it exponge complete lines. Minutes afterwards,

325
00:16:43,519 --> 00:16:46,840
certain locks de faced or shredded. Tracing these, I found

326
00:16:46,879 --> 00:16:49,279
that at least three admins were listed as active subsequent

327
00:16:49,279 --> 00:16:52,519
to official leaves or terminations. Proxy accounts perhaps or ghosts

328
00:16:52,559 --> 00:16:56,320
within the ledger raced after each operation in support locks,

329
00:16:56,440 --> 00:16:59,200
redacted names appeared alongside rides that lined up with missing

330
00:16:59,240 --> 00:17:02,840
persons clusters. The more I searched, the more deliberate it seemed,

331
00:17:02,919 --> 00:17:05,960
a web of operation, not accident, making sure everything rootless

332
00:17:06,079 --> 00:17:08,480
vanished into code space, no matter how many safety checks

333
00:17:08,480 --> 00:17:10,960
were built on top. It was only as I tried

334
00:17:11,000 --> 00:17:13,680
exporting one last round of logs that things began abruptly

335
00:17:13,720 --> 00:17:16,960
to disappear. My own nod AT traces began flickering out.

336
00:17:16,960 --> 00:17:19,319
First at Field converted to null, then a support request

337
00:17:19,400 --> 00:17:23,720
removed without ventcode, then entirely unsaved edits. The clipboard froze,

338
00:17:23,759 --> 00:17:26,079
then the screen lot for a half second, only to reload,

339
00:17:26,079 --> 00:17:30,519
missing half my work Slock notifications began pinging insistently dropped

340
00:17:30,519 --> 00:17:34,119
this for priority tickets. I received private messages from HR,

341
00:17:34,279 --> 00:17:37,480
escalated by a system alert escalation pot warning that continued

342
00:17:37,480 --> 00:17:40,480
access attempts to deprecate the logs may result in disciplinary action.

343
00:17:41,000 --> 00:17:44,079
I didn't reply. Instead, I set up a screen chair

344
00:17:44,119 --> 00:17:46,799
so all my work would save locally. One evening, as

345
00:17:46,839 --> 00:17:49,200
midnight drew close, I returned to my desktop to find

346
00:17:49,200 --> 00:17:51,519
my work comes led flickering out of time, on off,

347
00:17:51,599 --> 00:17:53,680
on twice per second for a minute, then off again.

348
00:17:54,279 --> 00:17:56,799
The audio feed hissed softly, even with all inputs muted,

349
00:17:56,839 --> 00:18:00,039
as if oldwires were decaying through my motherboard. The failing

350
00:18:00,079 --> 00:18:03,200
of being watched wasn't paranoida so much as certainty. Not

351
00:18:03,319 --> 00:18:06,480
surveillance by the company exactly, but by some process inside

352
00:18:06,519 --> 00:18:08,759
the machine, a gaze that flickered wherever the data trailed

353
00:18:08,759 --> 00:18:11,720
out of sight, waiting to catch anyone who noticed. I

354
00:18:11,799 --> 00:18:14,119
knew there'd be a point of no return, but by

355
00:18:14,160 --> 00:18:17,680
then it felt inevitable. The obsession took on a physical toll.

356
00:18:18,359 --> 00:18:21,519
Every night that week, I slept lesser work more packet

357
00:18:21,519 --> 00:18:23,799
logs were freshed in the background, timing scripts running on

358
00:18:23,799 --> 00:18:26,680
a separate devices. If one instance crash, the other might survive.

359
00:18:27,400 --> 00:18:29,759
I started preparing to watch in real time to see

360
00:18:29,759 --> 00:18:32,480
if the ghost rides spun up on schedule. Friday night,

361
00:18:32,519 --> 00:18:35,359
the system clock dragged past eleven thirty five p m.

362
00:18:35,680 --> 00:18:37,720
A mug of black coffee steamed at my elbow, the

363
00:18:37,799 --> 00:18:40,759
only warmth in the room. I checked my local machine,

364
00:18:40,880 --> 00:18:43,519
made sure the video capture script was aggregating right events

365
00:18:43,559 --> 00:18:46,119
director backup drive disconnected from Wi Fi except for a

366
00:18:46,119 --> 00:18:49,440
single ethnet feed. I watched the right creation logs roll

367
00:18:49,480 --> 00:18:52,559
in minute by minute. By eleven fifty eight p m.

368
00:18:52,599 --> 00:18:55,720
The sweat on my wrist turn cold. No obvious anomalies,

369
00:18:55,759 --> 00:18:59,359
just routine glitches, support tickets drifting quietly to resolved. At

370
00:18:59,359 --> 00:19:02,240
exactly midnight, the feet hickepped. A red notification swelling in

371
00:19:02,279 --> 00:19:04,480
the corner of my monitor. New ride event, no transit

372
00:19:04,559 --> 00:19:08,160
ID flagged from an LA address, a passenger field null.

373
00:19:08,759 --> 00:19:11,920
The driver d three ACE in minutes one nine. Without waiting,

374
00:19:11,960 --> 00:19:14,160
I forced the video feed live scraping daff can data

375
00:19:14,240 --> 00:19:17,799
until the transfer nearly locked up. My arim Simultaneously, my

376
00:19:17,880 --> 00:19:21,279
phone buzzed with a coal blocked no number. A froze.

377
00:19:21,799 --> 00:19:23,799
I let the call go to vorsemail, but the phone

378
00:19:23,799 --> 00:19:27,480
buzst again, insistent. The line opened besil it, white noise streaded,

379
00:19:27,480 --> 00:19:29,880
the line laced with the distant flutter of highway wind

380
00:19:30,000 --> 00:19:33,839
and small waped syllables repeating beneath it. In one brief surge,

381
00:19:33,880 --> 00:19:36,759
A caught is anyone there? On the monitor, the dash

382
00:19:36,799 --> 00:19:40,160
and feet popped up for the first time. The video stabilized.

383
00:19:40,720 --> 00:19:43,279
A passenger entered the car, face pixelated, but beneath the

384
00:19:43,279 --> 00:19:45,839
shuttering video distortion the features shop and just for an

385
00:19:45,880 --> 00:19:49,559
instant they looked exactly like me, not similar, in near

386
00:19:49,599 --> 00:19:51,960
perfect match, the same bent of browt the mouth tents

387
00:19:51,960 --> 00:19:54,279
and wary a jacket I owned, a gesture I remembered

388
00:19:54,319 --> 00:19:58,839
from Choudhood. Face flickered, glitched, warped, then snapped back. The

389
00:19:58,960 --> 00:20:01,759
video began dissolving. The voice no odder, do you remember

390
00:20:01,759 --> 00:20:04,720
who you're driving? The mouse locked, pointer frozen mid air,

391
00:20:05,319 --> 00:20:08,640
A screen clays gray, then black. An automatical log at

392
00:20:08,640 --> 00:20:13,440
dialog appeared. Company access revoked a single frozen framessured my

393
00:20:13,519 --> 00:20:16,720
own face watching me from inside the spectral car. And now,

394
00:20:16,799 --> 00:20:19,400
as the monitors called, I could see my own reflection, warrant,

395
00:20:19,480 --> 00:20:21,559
pale and yet not quite alone, peering back at me

396
00:20:21,599 --> 00:20:24,039
from the dim screen. The hum of the apartment felt

397
00:20:24,039 --> 00:20:27,359
suddenly immense, like the breathing of some huge, invisible presence

398
00:20:27,480 --> 00:20:30,000
just at the edge of perception. I sat shivering, the

399
00:20:30,039 --> 00:20:32,240
taste of metal in my mouth, the city's lights below

400
00:20:32,279 --> 00:20:35,680
flickering like insistent warning beacons lost in rain. Whatever I'd

401
00:20:35,720 --> 00:20:38,319
found it had seen me too. And now as the

402
00:20:38,319 --> 00:20:41,160
silence wrapped itself around the room, the line wherever it ended,

403
00:20:41,200 --> 00:20:44,119
whoever was really waiting, was still open. And now, as

404
00:20:44,160 --> 00:20:46,519
the silence wrapped itself around the room, the line wherever

405
00:20:46,559 --> 00:20:49,319
it ended, whoever was really waiting, was still open. I

406
00:20:49,319 --> 00:20:51,799
sat motionless for a long time, uncertain on or how

407
00:20:51,839 --> 00:20:55,400
to move. Details of the office pressed themselves into unlikely shortness.

408
00:20:55,440 --> 00:20:57,359
A faint scuff on the far wall, the two warm

409
00:20:57,400 --> 00:20:59,400
plastic beneath my palm, the sigh or haze of old

410
00:20:59,440 --> 00:21:02,680
coffee in the air. Screen after screen behind me shimmered

411
00:21:02,680 --> 00:21:05,960
in the sleep modes, a shifting constellation of blinking indicator lights.

412
00:21:06,599 --> 00:21:09,039
The tremor in my hands finally stared, but my heartbeat

413
00:21:09,039 --> 00:21:11,359
hammered at the base of my throat, a stubborn, stuttering

414
00:21:11,440 --> 00:21:13,920
echo of what had just happened. It took me a

415
00:21:13,920 --> 00:21:16,160
moment to close the laptop, needing to feel the solid

416
00:21:16,160 --> 00:21:19,079
click beneath my fingers, anything to mark at the session

417
00:21:19,160 --> 00:21:22,240
they encounter. Whatever that truly was, had physically completely under

418
00:21:23,000 --> 00:21:25,480
I sat back listening. The old fridge clicked and conked

419
00:21:25,519 --> 00:21:28,039
in the kitchen, but the interior hush of the office deepened,

420
00:21:28,160 --> 00:21:30,839
almost a dull roar. I couldn't shake the thought that

421
00:21:30,839 --> 00:21:32,920
the hum in the air, a pressure building behind it,

422
00:21:33,039 --> 00:21:35,359
was not just the ordinary residue of lost sleep or strain.

423
00:21:35,920 --> 00:21:38,599
It was as though someone invited frequency long buried in

424
00:21:38,640 --> 00:21:41,039
the white noise of my nights at, tuned to my presence,

425
00:21:41,079 --> 00:21:43,319
and was now waiting for a new signal. When my

426
00:21:43,359 --> 00:21:46,279
phone vibrated again, one brief met a tremor, I nearly jumped,

427
00:21:46,880 --> 00:21:48,839
But this time there was no call, no repeated a

428
00:21:49,119 --> 00:21:52,400
only a background system notification of mist event. I picked

429
00:21:52,400 --> 00:21:55,319
it up, thumb hesittin on the screen, checking the locks,

430
00:21:55,440 --> 00:21:57,400
I saw a small gap in a coal register. Just

431
00:21:57,400 --> 00:21:59,039
a blank time stamp with a right up should have

432
00:21:59,079 --> 00:22:02,200
annotated what happened. No audio left in the mail books.

433
00:22:02,240 --> 00:22:04,920
The interface itself had recorded nothing but an empty, cold duration,

434
00:22:05,039 --> 00:22:07,319
as though the entire exchange was meant to leave no trace.

435
00:22:07,960 --> 00:22:10,839
The room grew smaller the longer I sat. I gathered

436
00:22:10,920 --> 00:22:12,680
up the few things that brought me comfort by having

437
00:22:12,759 --> 00:22:14,799
the mark, the familiar weight of my own keyring, a

438
00:22:14,880 --> 00:22:17,319
worn hoodie draped over the back of the chair. I

439
00:22:17,359 --> 00:22:19,880
slid the locks on my door into place, almost mechanically,

440
00:22:19,960 --> 00:22:22,440
feeling the tension linger between surface common the sense that

441
00:22:22,519 --> 00:22:25,599
some one somewhere within the infrastructure had finished waiting and

442
00:22:25,599 --> 00:22:28,039
found me at last. When I tried to sleep, the

443
00:22:28,079 --> 00:22:30,880
city's ambient sound trick offered no help. I lay on

444
00:22:30,920 --> 00:22:33,200
my side, back to the window, the blue after image

445
00:22:33,240 --> 00:22:35,079
of my own face from the ruined video still burned

446
00:22:35,079 --> 00:22:37,920
into my vision. I listened to every stray sound, plumbing

447
00:22:37,920 --> 00:22:40,319
shifting through the walls, a neighbor's dog barking twice and

448
00:22:40,359 --> 00:22:42,920
then falling silent, the distance, soft clatter of an elevator

449
00:22:42,960 --> 00:22:46,319
long after midnight. I counted the seconds between no sounds,

450
00:22:46,440 --> 00:22:49,039
as if curating absences could restore the clean lines of

451
00:22:49,039 --> 00:22:52,400
my old routine, but I knew better. I mourning, some

452
00:22:52,519 --> 00:22:55,839
sense of self preservation began to assert itself. I walked

453
00:22:55,839 --> 00:22:58,240
to the usual barrage of corporate emails, bulk reminders about

454
00:22:58,279 --> 00:23:01,839
new VPN protocols and automate in metrics report pinging congratulations

455
00:23:01,880 --> 00:23:03,920
and bold at the header, but nothing specific about my

456
00:23:03,920 --> 00:23:07,839
revoked access. It struck me as deliberate that omission. If

457
00:23:07,880 --> 00:23:10,480
I checked my status in the directory, I was still active,

458
00:23:10,559 --> 00:23:13,880
with no recorded issues, and yet every attempt to access

459
00:23:13,920 --> 00:23:17,200
even the basic internal dashboard resulted in a bland authentication error.

460
00:23:17,799 --> 00:23:19,680
Call support. That pop up said, if you feel this

461
00:23:19,759 --> 00:23:22,119
is an error. There was no way I would do that.

462
00:23:22,759 --> 00:23:25,480
What would I say? My screen showed my own face

463
00:23:25,480 --> 00:23:28,079
in a ride that shouldn't exist, that a shadow in

464
00:23:28,119 --> 00:23:29,559
the data was both me and not me, and a

465
00:23:29,599 --> 00:23:32,759
system I'd supposedly mastered had in some unknown way turned

466
00:23:32,799 --> 00:23:35,799
around to study me instead. Instead, I tried to gather

467
00:23:35,880 --> 00:23:38,000
some sense of the outside world to pull myself back

468
00:23:38,000 --> 00:23:41,400
into context. My mother's daily email arrived, as usual, a

469
00:23:41,440 --> 00:23:43,880
fojo of her grinning next to a recipe card offering

470
00:23:43,920 --> 00:23:47,039
good energy for my busy work, I replied, as if

471
00:23:47,039 --> 00:23:49,400
nothing had changed, refusing to see even a hint of

472
00:23:49,400 --> 00:23:53,160
worry into her morning on Slack, the background conversations flowed on,

473
00:23:53,240 --> 00:23:56,680
others discussing remote work allowances, snippet jokes, plans for the weekend.

474
00:23:57,400 --> 00:23:59,519
For a while, I let myself drift on that stream,

475
00:23:59,559 --> 00:24:02,960
pretending nothing had split. I tried to contact Sonali, the

476
00:24:03,000 --> 00:24:07,359
engineering lead, through her alternate chat handle. No response. I

477
00:24:07,440 --> 00:24:10,279
checked again hours later, her profile had gone dame status

478
00:24:10,279 --> 00:24:13,160
marked us out of office. A nake, stubborn and bitter

479
00:24:13,200 --> 00:24:16,000
settled behind my eyes. It was as if I dreamed

480
00:24:16,000 --> 00:24:18,079
one level too deep and everyone else had moved on,

481
00:24:18,359 --> 00:24:20,640
leaving me cast a fault line no one else could sense.

482
00:24:21,319 --> 00:24:24,400
Walking outside helped, but only a little. The city poured

483
00:24:24,400 --> 00:24:27,880
by in its ordinary rush, by couriers, sioux clad office workers,

484
00:24:27,960 --> 00:24:31,319
passing cargo trucks, rattling the sidewalk. I tried to read

485
00:24:31,400 --> 00:24:33,559
meaning into the patterns of traffic, wondering if any of

486
00:24:33,559 --> 00:24:35,880
the unmarked carse iidling at red lights belonged to ride

487
00:24:35,920 --> 00:24:38,039
their drivers drawn by the same glitches. I chased to

488
00:24:38,119 --> 00:24:40,559
the end of their curd But nothing out of the ordinary,

489
00:24:40,599 --> 00:24:42,680
stared back at me. Nobody seemed to hold their phone

490
00:24:42,680 --> 00:24:45,000
the way drivers dead famming its greens for quick support

491
00:24:45,000 --> 00:24:48,079
tickets or ride details. The sense of being watch shifted

492
00:24:48,119 --> 00:24:51,240
as the day wore on. Instead of the unmitirectional awareness

493
00:24:51,279 --> 00:24:53,480
that had haunted the office, man's eye is sharpened into

494
00:24:53,480 --> 00:24:56,960
more targeted focus. Every time I checked a phone notification,

495
00:24:57,079 --> 00:24:59,519
I half expected another mist event, a blank time SAMP,

496
00:24:59,599 --> 00:25:01,480
or a messag that wasn't really a message at all.

497
00:25:02,039 --> 00:25:04,799
I deleted and reinstalled the ride app check or permissions

498
00:25:04,960 --> 00:25:09,799
white pash data repeatedly. Still nothing new surfaced. Maybe I

499
00:25:09,839 --> 00:25:12,920
thought the system had pulled back. Maybe I had become

500
00:25:13,039 --> 00:25:15,400
just another oddity in the nightly packet sweeps seemed to

501
00:25:15,440 --> 00:25:18,880
be ignored in erase by design. By early afternoon, my

502
00:25:18,920 --> 00:25:21,920
body ache from tension, I returned to my old routine,

503
00:25:21,920 --> 00:25:24,160
small chores in the kitchen, windows opened for a sliver

504
00:25:24,200 --> 00:25:27,000
of ress air, the white noise of podcasts filling the silence.

505
00:25:27,119 --> 00:25:29,640
Whenever my mind wandered too close to the edge of panic.

506
00:25:30,279 --> 00:25:32,680
I were cataloged my save files and encrypted the most

507
00:25:32,680 --> 00:25:35,920
sensitive ones, keeping back ups off line. But part of

508
00:25:35,920 --> 00:25:38,240
me knew the essential evidence the real encounter had already

509
00:25:38,240 --> 00:25:40,960
slipped into a realm out side proof. For a while,

510
00:25:41,079 --> 00:25:43,680
I addled on message bars and open bug trackos, tracing

511
00:25:43,839 --> 00:25:46,759
almost absent mindedly the subtle patterns that sometimes polls through

512
00:25:46,799 --> 00:25:51,000
the gig economy's technical subculture. There in fragments were hence

513
00:25:51,000 --> 00:25:52,960
I had missed before a thread from six months back

514
00:25:53,000 --> 00:25:56,240
about zero payment ghost rides in Toronto. Astray complained about

515
00:25:56,240 --> 00:25:58,519
admin exi scrat slipping endlessly in the back end of

516
00:25:58,519 --> 00:26:01,240
a now acquired small ride app. Quiet unanswered question in

517
00:26:01,279 --> 00:26:03,519
a forum for support reps. Has anyone else ever had

518
00:26:03,519 --> 00:26:06,400
a deleted driver ping for help after midnight? The posts

519
00:26:06,440 --> 00:26:08,680
didn't connect a freight, but their rhythms matched my own

520
00:26:08,720 --> 00:26:11,920
list of unease, covert heart beat inside the architecture. In

521
00:26:11,960 --> 00:26:14,759
an impulse that felt like crossing a forbidden threshold, I

522
00:26:14,799 --> 00:26:17,279
messaged an older into Gracie wants a backhand developer for

523
00:26:17,319 --> 00:26:20,519
a rival platform, now freelancing on short term AP projects.

524
00:26:21,119 --> 00:26:23,400
I kept the message cautiously vague, phrasing it as a

525
00:26:23,440 --> 00:26:26,359
technical conderary ever seen ride logs with orphan chat lions,

526
00:26:26,440 --> 00:26:29,680
ghosted writer ID, zero payment, come up late, linger then

527
00:26:29,720 --> 00:26:33,440
get expunged without a trace. I weeded, she replied with

528
00:26:33,480 --> 00:26:36,000
a single emojia raised my brow. Then a question, is

529
00:26:36,000 --> 00:26:38,200
this about those weird spikes around two minutes three? And

530
00:26:38,400 --> 00:26:40,480
we used to call them phantom packets at RYDZ. If

531
00:26:41,039 --> 00:26:44,200
that much was both soothing and deeply troubling, the pattern

532
00:26:44,279 --> 00:26:47,559
was unique to my company. It was perhaps more widespread

533
00:26:47,599 --> 00:26:50,200
than any one team, any one app My sense of

534
00:26:50,240 --> 00:26:53,839
isolation cracked open another inch, but so did the realization

535
00:26:53,920 --> 00:26:56,279
if it was systemic, my options were narrowing by the

536
00:26:56,319 --> 00:26:59,160
eyre the hard drive hum beneath my desk, a low

537
00:26:59,160 --> 00:27:02,039
and patient room. In a moment of impulse, I ran

538
00:27:02,079 --> 00:27:03,920
my old network monitor, a little piece of kit I

539
00:27:03,920 --> 00:27:06,640
had cobbled together years ago, designed to catch an omalus

540
00:27:06,680 --> 00:27:09,960
at bound connections from personal devices. I ran it twice,

541
00:27:10,000 --> 00:27:13,000
then a third time for certainty. Every sweep checked out clean.

542
00:27:13,640 --> 00:27:15,640
No signal eavn my network that I couldn't account for,

543
00:27:15,880 --> 00:27:18,440
no odd pangs from the router. Yet I knew, with

544
00:27:18,519 --> 00:27:20,599
a kind of animal certainty, that the signal i'd let

545
00:27:20,680 --> 00:27:22,680
her no longer needed my outbound port to track me.

546
00:27:23,319 --> 00:27:25,839
It had my keys already. That was the shape of

547
00:27:25,839 --> 00:27:28,559
my new normal, perpetual low level vigilance the neater book

548
00:27:28,599 --> 00:27:31,359
catalog and quarantined the strange and amounting awareness that the

549
00:27:31,400 --> 00:27:33,720
most dangerous lines in my world were not physical but

550
00:27:33,799 --> 00:27:36,039
digital cuts in the coat through which a present might slip,

551
00:27:36,039 --> 00:27:38,880
appearing as both glitch and ghost. Late in the evening,

552
00:27:38,960 --> 00:27:41,039
after dinner, I sat by the window for a while,

553
00:27:41,119 --> 00:27:43,599
pohone cradled in my lap, watching the city's lights dim

554
00:27:43,640 --> 00:27:46,160
and shift from time to time. The faint green light

555
00:27:46,200 --> 00:27:48,319
of the router blinked steady, but never quite in rhythm

556
00:27:48,359 --> 00:27:50,960
with its usual pulse. I watched for so long it

557
00:27:51,000 --> 00:27:53,279
almost seemed to sink with the cadence of my breath, steady,

558
00:27:53,319 --> 00:27:56,480
then a hithmic, then steady again. At some point I

559
00:27:56,519 --> 00:27:58,480
found myself staring not at the blinking light, but at

560
00:27:58,480 --> 00:28:01,039
my own reflection in the window. The room behind me,

561
00:28:01,079 --> 00:28:04,200
a blurred geometry of bookshelves, screen edges, and the faint

562
00:28:04,240 --> 00:28:06,799
outline of a chair, reminded me uneasily of the dash conpidire,

563
00:28:07,319 --> 00:28:09,200
the me who watched and the mea who was watched,

564
00:28:09,480 --> 00:28:12,559
separated only by glass. A night, the spell broke with

565
00:28:12,599 --> 00:28:14,519
the sound of a corrod door someway below, the heavy

566
00:28:14,519 --> 00:28:16,920
thunk echoing up the side of the building and then fading.

567
00:28:17,480 --> 00:28:19,200
I almost laughed at the jump in my nose. Just

568
00:28:19,279 --> 00:28:21,680
a neighbor, surely, or one of the endless gap drivers

569
00:28:21,680 --> 00:28:23,960
pulled up for a fair no one would mark or remember.

570
00:28:24,640 --> 00:28:26,400
Yet I could not quite dismiss the notion that if

571
00:28:26,400 --> 00:28:29,000
I stood upright then and looked down, I might see someone, know,

572
00:28:29,319 --> 00:28:31,759
some echo of myself sitting inside a waiting car, caught

573
00:28:31,799 --> 00:28:34,200
between a rival and departure, waiting for a signal from

574
00:28:34,200 --> 00:28:37,000
a line that never truly closed. I closed the blinds

575
00:28:37,000 --> 00:28:39,359
and returned to the soft, insistent light of my phone,

576
00:28:39,519 --> 00:28:42,079
the last barrier against the strangling silence of the room.

577
00:28:42,599 --> 00:28:45,240
That night, Even the city's distant murmurs couldn't quite mass

578
00:28:45,240 --> 00:28:47,599
the sense of the line still quietly open, waiting for

579
00:28:47,680 --> 00:28:50,960
its next message, waiting perhaps for me to reply. Morning

580
00:28:50,960 --> 00:28:53,799
brought no relief. The first thing I saw after opening

581
00:28:53,839 --> 00:28:56,000
my eyes after the hot, gut gnawing tumble of too

582
00:28:56,000 --> 00:28:58,519
little sleep, was the soft, consistent glow of my phone.

583
00:28:58,880 --> 00:29:01,519
Even before I reached for it. No skittered under my skin,

584
00:29:01,599 --> 00:29:04,119
the remembered ghost image on last night's dast come already

585
00:29:04,200 --> 00:29:08,079
rising through my thoughts. I checked for notifications. Nothing but

586
00:29:08,160 --> 00:29:10,920
the bland impersonal churn of bulk emails, a new round

587
00:29:10,920 --> 00:29:13,880
of password rotation reminders, and a single unread message from

588
00:29:13,880 --> 00:29:17,680
a delivery service left unopened. Company acts as still dead.

589
00:29:17,839 --> 00:29:20,799
My dashboard ide struck out, but without any flag or note.

590
00:29:21,599 --> 00:29:23,799
I tried logging into a secondary portal in a last

591
00:29:23,839 --> 00:29:26,079
gasp of habit, and got nothing but the same flat

592
00:29:26,079 --> 00:29:30,640
authentication failure, effective exile. It was raining, real heavy rain

593
00:29:30,680 --> 00:29:32,319
to day, not the digital drizzle from the hiss in

594
00:29:32,319 --> 00:29:35,599
my headphones. It patted against the mush window by my desk,

595
00:29:35,720 --> 00:29:38,680
tracking down the glass in wavering sheets. I sat for

596
00:29:38,680 --> 00:29:41,599
a long while, hands wrap around the kettle mug, willing

597
00:29:41,640 --> 00:29:43,319
the warmth to chase away the after image of my

598
00:29:43,359 --> 00:29:45,039
own feast from the video of the one that shouldn't

599
00:29:45,039 --> 00:29:48,279
logically exist. Each tick of the radiod brought my focus

600
00:29:48,279 --> 00:29:50,200
back to the room, remote and small, as if I

601
00:29:50,240 --> 00:29:52,119
were already half way into the skeleton of a kope

602
00:29:52,240 --> 00:29:55,279
is no longer being serviced. The city outside, shecharned, is

603
00:29:55,319 --> 00:29:58,359
always the traffic, the distant roll of bus wheels over

604
00:29:58,400 --> 00:30:00,799
wet pavement, the kinning of impatient horns. They all pressed in,

605
00:30:01,079 --> 00:30:03,079
mundane and safe. The only parts of the day I

606
00:30:03,079 --> 00:30:06,920
could trust. I scared my inbox, found nothing but automated noise,

607
00:30:07,039 --> 00:30:10,039
and checked personal messages. An old friend had sent me

608
00:30:10,079 --> 00:30:12,960
my years before, deliberately silly or reach across the silence.

609
00:30:13,680 --> 00:30:17,000
It didn't help My reply, a half hearted thumbs uplanded

610
00:30:17,079 --> 00:30:19,960
like gravel in my palm. Restlessness was a posture. My

611
00:30:19,960 --> 00:30:22,920
body remembered well. My foot bounced under the desk as

612
00:30:22,920 --> 00:30:24,960
I re read the chat lines I captured. He never

613
00:30:25,039 --> 00:30:26,799
left the car. Can you see my route? Am I

614
00:30:26,880 --> 00:30:30,160
den The phrasing was too specific, the pattern too careful

615
00:30:30,160 --> 00:30:32,519
to dismiss as a practical jerk by some underpaid junior

616
00:30:32,559 --> 00:30:35,680
death with access to prad. My own presence doubled, now

617
00:30:35,759 --> 00:30:38,480
immortalized in the feinnt outline burned on a dash comb screen,

618
00:30:38,519 --> 00:30:41,680
hovered at the edge of every task. Some time before noon,

619
00:30:41,720 --> 00:30:44,359
the door buzzer startled me, A froze breath caught until

620
00:30:44,359 --> 00:30:48,440
the second bus came longer urgent. The livery the confirmation

621
00:30:48,519 --> 00:30:50,559
text once I checked my phone offered no comfort to

622
00:30:50,640 --> 00:30:54,079
just parcel at your building, contactless drop off. I opened

623
00:30:54,079 --> 00:30:56,720
the door anyway, peering down the narrow carpeted hallway, half

624
00:30:56,720 --> 00:30:59,400
expecting to see someone waiting. There was only a small

625
00:30:59,400 --> 00:31:03,079
cardboard package, bubble wrapped and sealed with brown tape. I

626
00:31:03,119 --> 00:31:05,640
hesitated before picking it up, fingers light in the edges,

627
00:31:05,759 --> 00:31:08,160
the memory of the overnight warnings running quick and cold

628
00:31:08,160 --> 00:31:10,839
in my head. Still, I brought it in, set it

629
00:31:10,880 --> 00:31:13,160
on the kitchen counter, eying the corners for any avis

630
00:31:13,240 --> 00:31:16,960
hampering or identify from the company. Not then just my

631
00:31:17,079 --> 00:31:19,960
name spelled Wright, no return label. I let the package

632
00:31:20,119 --> 00:31:22,359
in touch for an hour, circling my kitchen, pretending to

633
00:31:22,400 --> 00:31:25,920
make breakfast. A low grade anxiety pulsed under everything, like

634
00:31:25,960 --> 00:31:28,079
the hush of silver fans just before sudden shut down.

635
00:31:28,599 --> 00:31:31,759
My mind drifted through possibilities, a legal letter, a second warning,

636
00:31:31,839 --> 00:31:33,680
some of the little joke meant to tip a nervous

637
00:31:33,680 --> 00:31:36,519
contractor into panic. It was only after the aged went

638
00:31:36,559 --> 00:31:38,480
rubbery in the pan that I toiled the tape free

639
00:31:38,960 --> 00:31:42,400
inside a burner. Fahn already powered on screen active with

640
00:31:42,400 --> 00:31:46,160
the unmistakable Ride Company app opened and waiting. The display posed.

641
00:31:46,240 --> 00:31:48,880
A ride request flag is appending the timer counting down

642
00:31:48,880 --> 00:31:51,960
from nineteen forty three hours until midnight. It was an

643
00:31:52,000 --> 00:31:57,279
explicit invitation, no note, no context, only the device warm

644
00:31:57,319 --> 00:31:59,400
in my hand, almost as if it had recently been

645
00:31:59,400 --> 00:32:02,039
pressed by some one else's palm. With the phone came

646
00:32:02,079 --> 00:32:04,680
a passport sized envelope, empty before a torn scrap of

647
00:32:04,680 --> 00:32:08,440
paper printed in block texts You're next in line. I

648
00:32:08,559 --> 00:32:11,359
dropped the envelope, wiped my hands on my jeans, then

649
00:32:11,440 --> 00:32:13,640
checked my own phone from messages for friends or family,

650
00:32:13,720 --> 00:32:15,440
some proof that this was still the world. I knew

651
00:32:16,039 --> 00:32:19,160
nothing unusual. Yet when I put my original phone beside

652
00:32:19,160 --> 00:32:21,799
the burner, it buzzed once, showing a glitch notification and

653
00:32:21,880 --> 00:32:24,559
readable text, half symbols vanishing. The second had tried to

654
00:32:24,559 --> 00:32:27,319
screene on it. There was no doubt now, not even

655
00:32:27,359 --> 00:32:30,960
a shout of plausible deniability. The company, some part of it,

656
00:32:31,160 --> 00:32:34,359
or whatever move beneath wasn't done with me. Whether this

657
00:32:34,480 --> 00:32:37,119
was intimidation, call to action, or a test, I couldn't say,

658
00:32:37,680 --> 00:32:39,480
but the stakes had shifted out of the digital and

659
00:32:39,519 --> 00:32:42,000
into the reel. I looked down at my hands and

660
00:32:42,039 --> 00:32:44,799
found them trembling just slightly, the nails dull against the

661
00:32:44,839 --> 00:32:47,720
marrow line. A wave of Nasser rose. This was the

662
00:32:47,720 --> 00:32:50,200
evidence I'd needed. The proof of the story wasn't only

663
00:32:50,200 --> 00:32:52,559
in my head yet. It was proof that threatened me

664
00:32:52,599 --> 00:32:56,119
with silence, not resolution. A slow, thin dread spread through

665
00:32:56,160 --> 00:32:58,920
my body, as if every point of contact, every axis badge,

666
00:32:59,039 --> 00:33:01,640
every system login, every ride home I had ever taken

667
00:33:01,680 --> 00:33:03,920
could be a weak scene pressed to open, revealing something

668
00:33:03,960 --> 00:33:06,960
at watch, but never truly left. Long after, when the

669
00:33:07,039 --> 00:33:09,319
rain eased and moonlight creased through the clouds, I let

670
00:33:09,400 --> 00:33:12,799
myself feel something like resolve. My isolation was now my

671
00:33:12,839 --> 00:33:16,359
best offense. Nobody to threaten accept me, no one else

672
00:33:16,359 --> 00:33:19,839
in the chain of custody. But it also made escape, deniability,

673
00:33:19,960 --> 00:33:23,960
even forgetfulness impossible. I started I disconnecting every smart device

674
00:33:23,960 --> 00:33:28,039
in the apartment, speakers, back parutters, the unused office phone,

675
00:33:28,519 --> 00:33:30,599
even the smart bulb in the bathium went dark under

676
00:33:30,680 --> 00:33:33,640
at them. Only the laptop and the two phones remained,

677
00:33:33,680 --> 00:33:36,839
each isolated in different rooms, the bernofhones battery taking downward

678
00:33:36,839 --> 00:33:39,519
and tiny and hurried increments. It was like waiting for

679
00:33:39,559 --> 00:33:41,480
a question I knew had already been decided for me

680
00:33:42,200 --> 00:33:45,039
after I was lost, pacing, waiting for a warning, a knock,

681
00:33:45,119 --> 00:33:47,000
a new message that failed to arrive. By brooded in

682
00:33:47,039 --> 00:33:49,039
the kitchen, staring at chipped groat lines and letting no

683
00:33:49,079 --> 00:33:52,119
weight of potential choices constrict in my chest. If the

684
00:33:52,119 --> 00:33:54,640
bernophone's ride request was a threat, it was also a

685
00:33:54,680 --> 00:33:58,200
trace some one else had set and prepared it. The system,

686
00:33:58,279 --> 00:34:01,480
whatever else it claimed, acknowledged my place in line, but

687
00:34:01,599 --> 00:34:05,240
it implied there was something beyond a latice work of events, accounts, sights,

688
00:34:05,480 --> 00:34:08,360
and actions moving on their own schedule. I picked up

689
00:34:08,400 --> 00:34:10,519
the phone and dialed out, first to my old friend

690
00:34:10,559 --> 00:34:12,960
Grace's number, then to a journalist whose work on day

691
00:34:13,000 --> 00:34:16,039
to disappearances i'd respected from of OAR. No answer on

692
00:34:16,159 --> 00:34:19,280
either front, just for smell prompts and blank echoing silences

693
00:34:19,320 --> 00:34:21,800
at the ends of the rings. I left, careful in

694
00:34:21,840 --> 00:34:24,719
direct messages who want to talk create digital anomalies, rideshair

695
00:34:24,760 --> 00:34:27,159
app not urgent but important, and knowing any one listening

696
00:34:27,159 --> 00:34:29,320
would find them harmless. Knowing too that the chances of

697
00:34:29,320 --> 00:34:32,559
actual help within evening came and the cities rhythmed into

698
00:34:32,559 --> 00:34:35,960
a harder, faster pulse. I closed my laptop, moved it

699
00:34:36,000 --> 00:34:37,840
to a drawer, and carried the Berner phone from room

700
00:34:37,880 --> 00:34:40,480
to room like a totem. I checked windows blinds. The

701
00:34:40,480 --> 00:34:43,400
people on the front door, shadows below had always looked

702
00:34:43,400 --> 00:34:45,199
the same, Now I couldn't help but count the number

703
00:34:45,199 --> 00:34:47,599
of cause idling within sight, the slow drift and rollbuck

704
00:34:47,639 --> 00:34:49,719
of the brick lights, as if some untold number of

705
00:34:49,800 --> 00:34:52,559
drivers were waiting for signals not meant for me. The

706
00:34:52,599 --> 00:34:54,639
paranoia was not just in the wires now, it was

707
00:34:54,639 --> 00:34:58,400
in the air itself. My hands remained cold, my breath

708
00:34:58,519 --> 00:35:01,480
came shorter than I wished. When I pressed my fingers

709
00:35:01,519 --> 00:35:04,119
against the wall, I felt, or imagined I felt the

710
00:35:04,119 --> 00:35:07,480
shuddering hum of all pipes rising, and barely perceptible vibration

711
00:35:07,559 --> 00:35:10,000
at ghost resonance I going through dry wall and code.

712
00:35:10,519 --> 00:35:12,679
I thought for a moment of calling the police, reporting

713
00:35:12,679 --> 00:35:16,239
the delivery as harassment. But what would I say that

714
00:35:16,360 --> 00:35:18,440
the support upon an ad traceable phone told me I

715
00:35:18,480 --> 00:35:20,199
was an ex that a message in a blank chat

716
00:35:20,239 --> 00:35:22,480
line had worn me off on behalf of some one invisible.

717
00:35:23,079 --> 00:35:25,480
Any official would shrug, and the real line, or whatever

718
00:35:25,519 --> 00:35:29,559
it was, wherever it extended, would remain safe and attached. Instead,

719
00:35:29,639 --> 00:35:31,480
I did what I had long done best. I turned

720
00:35:31,519 --> 00:35:34,119
back to the data. If I couldn't turn into the system,

721
00:35:34,239 --> 00:35:36,840
I turned to the shadows on its edges. By eight

722
00:35:36,840 --> 00:35:38,760
p m. I had written a small croller on my

723
00:35:38,800 --> 00:35:41,360
old offine machine, a safe box never connected to my work,

724
00:35:41,480 --> 00:35:45,079
a contingency from contracts passed in half Together Pathen I

725
00:35:45,079 --> 00:35:47,440
threw together a scraping tool for public endpount data and

726
00:35:47,519 --> 00:35:50,800
ride receipts posted on open social barb trackers and support forums.

727
00:35:51,400 --> 00:35:54,639
The code sifted through hashtag's BOLOGG posts, tip rumbles, easer

728
00:35:54,679 --> 00:35:57,679
complaints collated from every platform I knew. Patching together ghost

729
00:35:57,760 --> 00:36:00,800
ride effidence wherever it bled into the public Internet, patterns

730
00:36:00,840 --> 00:36:03,400
emerged the raw shapes only half hidden by corporate obsercation.

731
00:36:04,039 --> 00:36:06,320
Ride data posted from Kansas City with the same knull

732
00:36:06,360 --> 00:36:08,840
driver zero payments stamp as I had seen before above

733
00:36:08,920 --> 00:36:11,599
report from Seattle about repeated completed a ride between one

734
00:36:11,639 --> 00:36:13,920
two a m with no mapestry. A message on an

735
00:36:13,920 --> 00:36:16,679
obscure rye gia forum varied and took support language about

736
00:36:16,760 --> 00:36:19,679
dead driver id ping lifelong after those accounts went dark.

737
00:36:20,320 --> 00:36:22,599
It was everywhere. Once I stopped thinking of it as

738
00:36:22,639 --> 00:36:27,519
a unique event, I cross referencing locations, ride types, and frequencies.

739
00:36:27,599 --> 00:36:29,719
I confirmed at least six major U S city sole

740
00:36:29,760 --> 00:36:32,320
clusters of similar ghost roads on the same dates, circling

741
00:36:32,360 --> 00:36:35,000
the same pattern I had mapped in private. The platform

742
00:36:35,039 --> 00:36:38,280
specific details didn't always match, some marked as a test environment,

743
00:36:38,400 --> 00:36:40,760
others as admin over either, but the events signatures carried

744
00:36:40,760 --> 00:36:43,199
a familiar stink. Events built to vanish from customer and

745
00:36:43,280 --> 00:36:46,199
driver views, yet marked by backend anomalies. Only the unlucky

746
00:36:46,320 --> 00:36:49,119
or persistent noticed. I posted to a forum under a

747
00:36:49,119 --> 00:36:52,239
throwaway handle, any one tracking midnight rides with invisible ID,

748
00:36:52,480 --> 00:36:56,119
missing people, no transaction logs. The reply was at first

749
00:36:56,239 --> 00:36:59,559
only silence, but as the clock drifted toward nine thirty,

750
00:36:59,559 --> 00:37:02,159
a message which blink into my private channel you aren't

751
00:37:02,159 --> 00:37:05,239
alone file sent look for the ZP. The message was

752
00:37:05,239 --> 00:37:07,920
from someone using a press avatar, Julie f whose bylines

753
00:37:07,920 --> 00:37:10,800
I'd followed for a year. She suggested a video call,

754
00:37:11,000 --> 00:37:14,159
citing safety concerns. Never meet in person, virtual only you

755
00:37:14,239 --> 00:37:16,840
of something, show me what you have, but cover your camera.

756
00:37:16,960 --> 00:37:20,199
Lots of noise right now. I accepted, turning off my camera,

757
00:37:20,400 --> 00:37:23,840
encrypting everything. Before the call, Julia's voice was brisk, almost

758
00:37:23,840 --> 00:37:27,719
soothing in its directness. We've tracked three similar clusters New Jersey,

759
00:37:27,800 --> 00:37:30,599
ausin oakund If you found a ride lock, don't trust

760
00:37:30,599 --> 00:37:33,440
the dashboards. Admins disappear with the blows go dark. You're

761
00:37:33,519 --> 00:37:35,960
right to stay offline. There was a pause, then she

762
00:37:36,000 --> 00:37:39,559
spoke more quietly. Rides always bike around, vanished names, never

763
00:37:39,639 --> 00:37:42,559
the same operators, but the same logic. Something's co ordinated,

764
00:37:42,599 --> 00:37:44,559
as if you see warning stops, or at least find

765
00:37:44,559 --> 00:37:47,760
a safe way to save your evidence. The conversation lasted

766
00:37:47,800 --> 00:37:50,639
seven minutes, most of it filled with terse questions, hardware

767
00:37:50,760 --> 00:37:52,880
used log's ark out what I'd seen in the video.

768
00:37:53,480 --> 00:37:57,559
She confirmed several clusters matched disputed city zones, edges of transit, hobs,

769
00:37:57,639 --> 00:38:00,679
outskirts of airports, places where bodies in vehicles came and

770
00:38:00,719 --> 00:38:04,000
went with little record kept. Our last source vanished after

771
00:38:04,039 --> 00:38:06,639
posting about a midnight ride near the bus station. She said,

772
00:38:07,360 --> 00:38:10,719
no trace after that except a single deleted chatlock. We

773
00:38:10,880 --> 00:38:13,599
ended the call with little resolved, but the shared a

774
00:38:13,679 --> 00:38:16,079
tension gave me a perverse reassurance. There were others who

775
00:38:16,159 --> 00:38:18,119
had touched the edges of the story, their voices thin

776
00:38:18,239 --> 00:38:21,599
but not yet raised. It was close to midnight. I

777
00:38:21,639 --> 00:38:25,639
sketched the vectors on a notepad. Ride clusters, chat anomalies, dates, locations.

778
00:38:26,360 --> 00:38:28,840
I drew lines and then more cross referencing with missing

779
00:38:28,840 --> 00:38:32,000
persons data a new hunch to crute, urgent and bright.

780
00:38:32,039 --> 00:38:34,320
In my mind, the anomalies weren't only a smoke screen.

781
00:38:34,840 --> 00:38:37,400
They were a communication, yes, but also a mask of

782
00:38:37,440 --> 00:38:40,079
veil that allowed something large and network of oversight and

783
00:38:40,119 --> 00:38:43,400
disappearance to move and scene. My phone buzzed, a flinched

784
00:38:44,039 --> 00:38:47,719
an not a blank notification, content already deleted. My hands

785
00:38:47,760 --> 00:38:50,039
achedrol from gripping the pencil, the tight circles of what

786
00:38:50,199 --> 00:38:53,679
carving tension through muscle and tendon nowhere to go, nothing

787
00:38:53,719 --> 00:38:56,480
to do except keep rowing the lines. When I finally

788
00:38:56,559 --> 00:38:58,920
asked myself what to do next, the answer came bluntly.

789
00:38:58,960 --> 00:39:01,119
I had to find proof, linking the admins to something real,

790
00:39:01,159 --> 00:39:03,599
to living, breathing people who might still be out there,

791
00:39:03,719 --> 00:39:07,119
or to whoever or whatever orchestrated a disappearance. The burner

792
00:39:07,159 --> 00:39:10,280
phone waited, screen dimmed. I placed it face down on

793
00:39:10,280 --> 00:39:12,559
the table, willing away the compulsion to check the ride

794
00:39:12,559 --> 00:39:14,960
request timer. But the numbers still crept into my thoughts.

795
00:39:15,119 --> 00:39:17,719
Thirteen IROs, twelve IROs, ten hours until it would vanish

796
00:39:17,760 --> 00:39:20,079
into the same nowhere as all the others. In the

797
00:39:20,079 --> 00:39:22,280
thick hush of late night, after the rain had faded

798
00:39:22,320 --> 00:39:24,440
and the radiator. It was taken down. I returned to

799
00:39:24,480 --> 00:39:26,880
the problem in the way familiar to any backend analyst,

800
00:39:26,960 --> 00:39:28,840
traced the hands that set the system in motion by

801
00:39:28,840 --> 00:39:31,880
following the permissions that shouldn't have existed. I compiled a

802
00:39:31,920 --> 00:39:33,960
short list of no nadmin of rides from leapd dog

803
00:39:34,039 --> 00:39:36,719
charts and old employee records, scraping, LinkedIn and glassed or

804
00:39:36,719 --> 00:39:39,400
for names that matched the patterns in my clusters. The

805
00:39:39,440 --> 00:39:42,239
handful of profiles I found shared a peculiar trait. All

806
00:39:42,280 --> 00:39:44,480
had been terminated or retired within a week or two

807
00:39:44,519 --> 00:39:47,079
of a disappearance surge, Each marked as left the company

808
00:39:47,079 --> 00:39:49,480
for personal reasons, or a line that stood up seeking

809
00:39:49,519 --> 00:39:54,239
opportunities outside the transport sector. Emails to official addresses bounced predictably,

810
00:39:54,840 --> 00:39:57,480
but one attached to a Southwest city cluster returned not

811
00:39:57,519 --> 00:39:59,559
a system era but a sudden silent paying a single

812
00:39:59,599 --> 00:40:02,440
message my spam folder on red friars until I spotted it.

813
00:40:03,000 --> 00:40:05,679
The subject line re midnight this is all I have.

814
00:40:06,400 --> 00:40:09,480
Attachment identified as logs corrupted seven hundred twenty one zip

815
00:40:09,599 --> 00:40:12,719
fourteen m B, sent from a mass server. Opening it

816
00:40:12,760 --> 00:40:16,280
was a calculated risk. I ran it. It gaped extracting

817
00:40:16,280 --> 00:40:20,039
only the text files, scanning for identifiable information before opening anything,

818
00:40:20,079 --> 00:40:24,519
even assembling executable code inside thousands of lines, most of

819
00:40:24,519 --> 00:40:27,199
them garbled head a clutter, but buried within were fragments

820
00:40:27,199 --> 00:40:30,920
of chat locks. Some showed the same soccado distress pick up,

821
00:40:30,920 --> 00:40:34,719
failed cancel, ride, passenger not found. Others were more concrete,

822
00:40:34,760 --> 00:40:37,320
linked with forced ride cancelations. As the IP code clusters

823
00:40:37,320 --> 00:40:40,039
that matched recent missing persons reports I had already compiled.

824
00:40:40,599 --> 00:40:43,039
The rhythm was clear. A spiking ghost rice an abmin

825
00:40:43,079 --> 00:40:45,679
override event than a user count obliterated and removed from

826
00:40:45,719 --> 00:40:49,320
payroll message out of existence, each trace excised except for

827
00:40:49,360 --> 00:40:52,480
the bare hidden log residual after at each cluster, the

828
00:40:52,480 --> 00:40:55,320
admin accounts were erased two not simply disabled, but shredded,

829
00:40:55,360 --> 00:40:58,480
wiped from back, sometimes even flagged as never existed by

830
00:40:58,599 --> 00:41:02,039
HR systems, as if handlers expunged themselves from the ledger

831
00:41:02,079 --> 00:41:05,159
after a prodained number of operations. The horror of it

832
00:41:05,199 --> 00:41:08,199
was not only the scale, but the cold efficiency. Whatever

833
00:41:08,239 --> 00:41:10,920
moved through the system did so deliberately, one step ahead

834
00:41:10,920 --> 00:41:13,880
of audits, patching over the trail with automation, covering every

835
00:41:13,880 --> 00:41:17,719
track with plausible deniability the messages themselves reinforced the truth.

836
00:41:17,880 --> 00:41:19,880
No fare received tonight, I am ready to close out.

837
00:41:19,880 --> 00:41:22,320
The handler says job done, new lobbed Morrow, the leaving

838
00:41:22,320 --> 00:41:26,599
behind passenger I descrambled. They sounded almost ritualistic. The tolling

839
00:41:26,679 --> 00:41:29,599
bellfer process bound out last any one identity or name.

840
00:41:30,159 --> 00:41:33,320
I pieced together anew, darker hypothesis that the network itself

841
00:41:33,360 --> 00:41:36,400
was cyclical, living inside the machine, shifting riders and drivers

842
00:41:36,400 --> 00:41:39,039
and masks as needed, and when a handler's work in

843
00:41:39,039 --> 00:41:40,960
a city was done, they walked for a vanish leaving

844
00:41:41,000 --> 00:41:43,760
nothing but syndetic gerror's chat echoes and the faintest ghost

845
00:41:43,760 --> 00:41:46,320
of a presence on some one else's screen, though almost

846
00:41:46,320 --> 00:41:48,920
still eyes away and outside the window. The city's tempo

847
00:41:48,960 --> 00:41:51,119
had dropped to a slow wheeling coal hadlets wandering the

848
00:41:51,159 --> 00:41:54,840
streets with animal patients. In my mind, calculations ran and

849
00:41:54,920 --> 00:41:58,840
checked how much was automation, how much human intent, and which,

850
00:41:59,039 --> 00:42:02,039
if either, was more rightening to confront. My next move

851
00:42:02,079 --> 00:42:04,920
felt inevitable. I dressed in the dull comfort of jeans

852
00:42:04,920 --> 00:42:07,119
and a black hoodie, set the beronophone into my pocket,

853
00:42:07,199 --> 00:42:09,440
and descended the stairs to tree level for the first time.

854
00:42:09,480 --> 00:42:12,440
The day, the rye closters, this mat lay thickest nearer

855
00:42:12,480 --> 00:42:14,920
the old transit hobs. Places where pickets lingered long after

856
00:42:14,960 --> 00:42:17,599
the last bus departed, Where drivers waited with empty cows,

857
00:42:17,599 --> 00:42:21,039
staring blank and solitary at arrival gates. It was easier

858
00:42:21,119 --> 00:42:23,840
and practiced to blend in and adfered. I walked the

859
00:42:23,880 --> 00:42:26,559
unnamed block, circling the station, sipping coal coffee from a

860
00:42:26,599 --> 00:42:29,880
disposable cup, scanning faces for any flicker of recognition or intent.

861
00:42:30,679 --> 00:42:33,920
Several Rideia cars circled without purpose, windows rolled up, drivers

862
00:42:33,920 --> 00:42:36,960
scanning their own glowing screens, the vacant chemistry of anticipation

863
00:42:37,000 --> 00:42:40,000
and boredom in their postures. Some moved on, picking up

864
00:42:40,039 --> 00:42:42,280
a light passenger or pausing at a yellow crab, but

865
00:42:42,320 --> 00:42:44,920
a few remained long after any rational fairs should have arrived.

866
00:42:45,559 --> 00:42:47,760
One car parked under a faulty lamp showed the same

867
00:42:47,840 --> 00:42:49,599
rhythm I'd seen in the dash can files. Lights on

868
00:42:49,760 --> 00:42:53,119
car and park, no passenger entering or leaving the driver.

869
00:42:53,320 --> 00:42:55,719
A medium built man in a faded jacket sat silent,

870
00:42:55,840 --> 00:42:58,480
his hands drumming time on the wheel and small anxious ticks.

871
00:42:59,119 --> 00:43:02,000
His phone glowed bright, unreadable from the opposite sidewalk, but

872
00:43:02,039 --> 00:43:04,880
from his expression at tired vacancy, as if awaiting instructions

873
00:43:04,920 --> 00:43:08,199
from elsewhere, there could sense both wariness and resignition. I

874
00:43:08,239 --> 00:43:11,079
watched him for nearly an ire at tolved a m

875
00:43:11,159 --> 00:43:13,199
A flicker ran through his dash camp For a moment,

876
00:43:13,239 --> 00:43:15,039
I thought I saw a shadow shift in the back seat,

877
00:43:15,039 --> 00:43:17,679
but there was no one visibly there. A low hum,

878
00:43:17,800 --> 00:43:21,079
almost anaudible, rolled from his open window, snatch of staticky audio,

879
00:43:21,199 --> 00:43:24,920
pulsing and then fading. After four more minutes, he pulled away,

880
00:43:25,079 --> 00:43:27,920
turning not toward the highway, not toward local streets, but

881
00:43:27,960 --> 00:43:31,280
down a service alley and into darkness. I tried to pursue,

882
00:43:31,280 --> 00:43:33,039
but by the time I reached the corner, the car

883
00:43:33,039 --> 00:43:36,760
had vanished. A hollow e settled in my bones. I

884
00:43:36,760 --> 00:43:39,760
circled the block, looking for any sign of security cameras,

885
00:43:40,000 --> 00:43:42,639
but most of Sticker's warning of footage recycled every twenty

886
00:43:42,639 --> 00:43:44,519
four a for your privacy, and the last two I

887
00:43:44,519 --> 00:43:47,480
passed their lenses broken or taped. I caught my own

888
00:43:47,480 --> 00:43:50,599
face reflected briefly in a nearby store front, not just

889
00:43:50,679 --> 00:43:53,039
fatigua lastitude of the soul, as if the city's night

890
00:43:53,039 --> 00:43:54,880
had snuck in through my eyes and found a deep

891
00:43:54,880 --> 00:43:57,800
place to hide. I shook it off, walked back toward

892
00:43:57,880 --> 00:44:00,400
the bus terminal, but the street was emptying fast. Every

893
00:44:00,440 --> 00:44:02,440
taxi and rye check gun elsewhere by the time I

894
00:44:02,519 --> 00:44:05,239
turned back toward home. In the iro that followed, I

895
00:44:05,280 --> 00:44:07,840
double checked my phone in the burner, then my phone again.

896
00:44:08,440 --> 00:44:11,519
Each time interference seemed to pulse up, audio popping softly

897
00:44:11,639 --> 00:44:13,920
in my apiece go His statical in cost a net

898
00:44:13,920 --> 00:44:17,400
were creed out, battery indicators dipping by small, impossible increments,

899
00:44:17,440 --> 00:44:19,400
as if their life spans were being quietly measured up

900
00:44:19,480 --> 00:44:22,400
and siphoned away. Back in the apartment, after shutting and

901
00:44:22,480 --> 00:44:25,960
chaining the door, I waited, expecting another shooter drop nothing.

902
00:44:26,599 --> 00:44:29,079
For a moment, the tat sparal of vigilance held, and

903
00:44:29,119 --> 00:44:32,800
then with no warning, nightmares tumbled in abandoned reds lupinianously

904
00:44:32,800 --> 00:44:35,519
in dark city spaces, my own hands on a stirring wheel.

905
00:44:35,559 --> 00:44:38,440
I'd never touched, an invisible passenger whispering can you see

906
00:44:38,440 --> 00:44:41,079
my route? He never left the car. When I woke,

907
00:44:41,239 --> 00:44:43,800
adrenaline still hot under my skin. The sun had hardly

908
00:44:43,800 --> 00:44:46,840
climbed above the sky line. A delivery alert flushed on

909
00:44:46,920 --> 00:44:49,840
both fawns, though I'd ordered nothing. I opened the door

910
00:44:49,880 --> 00:44:52,880
to the landing, but nothing waited there, only the faint

911
00:44:52,880 --> 00:44:54,920
scent of ozum, the hush of the rising wheat day floor,

912
00:44:54,960 --> 00:44:56,960
A city ready to remake itself in you, unaware of

913
00:44:57,000 --> 00:44:59,960
the digital web spun tight across its lights. I power

914
00:45:00,119 --> 00:45:02,920
up my machine, running security checks on every file, every

915
00:45:02,920 --> 00:45:06,360
scrap of coppered lock. No immediate breach, but the atmosphere

916
00:45:06,440 --> 00:45:08,960
was thick with through it. I cracked open the burner

917
00:45:09,079 --> 00:45:10,960
only to find the ride request timer done to a

918
00:45:11,000 --> 00:45:14,239
few minutes, the right still appending, still in my name,

919
00:45:14,280 --> 00:45:16,559
the addresses out of block north of my own. I

920
00:45:16,639 --> 00:45:20,599
considered again calling for help, family, police, anyone, But even

921
00:45:20,639 --> 00:45:22,840
if I could make them believe me, nothing about what

922
00:45:22,880 --> 00:45:25,880
had happened was illegal in any technical sense. There was

923
00:45:25,920 --> 00:45:29,280
nothing tangible to show them. The burner buzzed, screened, flickering

924
00:45:29,320 --> 00:45:31,840
as a new message spoiled out. Were waiting. Don't let

925
00:45:31,880 --> 00:45:35,320
the line fall dead. I hurriedly changed every password I possessed,

926
00:45:35,440 --> 00:45:39,320
raise personal histories, toggle two factor authentication on every surviving account.

927
00:45:40,000 --> 00:45:43,639
It felt like building a sand barricadegainst an incommuntide as

928
00:45:43,719 --> 00:45:46,800
evening thicken, a wave of exhaustion set in. I lay

929
00:45:46,840 --> 00:45:49,000
on my back, skin prickling, and mapped the theory in

930
00:45:49,039 --> 00:45:51,760
my mind, tracing consequence from belief to proof and back again.

931
00:45:52,320 --> 00:45:55,119
It sounded at one's uprageous and irrefutable ghost fright, as

932
00:45:55,199 --> 00:45:58,519
camouflage for organized deduction, knock of her disappearance, orchestrated or

933
00:45:58,599 --> 00:46:01,360
enabled by high level adminment population. Each cycle clans by

934
00:46:01,360 --> 00:46:04,519
systematic local rasure and the erasure of the erases. No

935
00:46:04,599 --> 00:46:08,679
wallet entries, no driver permanence, no human witnesses except me, perhaps,

936
00:46:08,840 --> 00:46:12,199
and only if I survived the night. The network, I realized,

937
00:46:12,440 --> 00:46:14,880
was a hydra. Each had growing anyw as another was cut.

938
00:46:15,639 --> 00:46:18,199
Every ride, creation and override was a moving part. Each

939
00:46:18,239 --> 00:46:20,360
hand THEO tasked to erase them cells to prevent detection,

940
00:46:20,679 --> 00:46:24,519
cycling digital phantoms through expired ID and vanished points. Now

941
00:46:24,679 --> 00:46:26,840
even my own audit locks were gone. Years of digital

942
00:46:26,840 --> 00:46:29,159
presents and authority swept up by a system less concerned

943
00:46:29,199 --> 00:46:31,480
with just as them, of a cursive clanting. If I

944
00:46:31,559 --> 00:46:33,360
was lucky, I'd stay below the line, a bug not

945
00:46:33,400 --> 00:46:36,280
worth patching out. If I was unlucky, the call or

946
00:46:36,320 --> 00:46:38,159
the ride would arrive from me, and my place in

947
00:46:38,199 --> 00:46:40,840
line would come do. It was nearly midnight when I

948
00:46:40,840 --> 00:46:44,280
decided I'd flip the script, force the confrontation, and record everything,

949
00:46:44,400 --> 00:46:47,280
even if it came to nothing. With the bernarfone pulsing,

950
00:46:47,320 --> 00:46:50,079
the ride request time is snapped to zero, a silent

951
00:46:50,079 --> 00:46:54,079
push notification your riders here. I closed my laptop, making

952
00:46:54,079 --> 00:46:57,039
sure recording scripts, funnel databases and video to encrypted cloud

953
00:46:57,039 --> 00:47:00,400
storage with a secondary backup. I pocketed both pawns, stepped

954
00:47:00,400 --> 00:47:02,840
into the night and walked up the block, breth shallow,

955
00:47:02,880 --> 00:47:05,760
the cold slipping beneath my shirt. At the curb outside

956
00:47:05,760 --> 00:47:07,960
an abandoned pawn shop, a right chair car waited with

957
00:47:08,039 --> 00:47:11,360
engine running, windows dark. The make and model which generic

958
00:47:11,480 --> 00:47:14,320
enough to belong to anyone's Silver Compact, nothing to note,

959
00:47:14,800 --> 00:47:17,280
and yet it was unmistakable. The carmeas signed ride ID

960
00:47:17,400 --> 00:47:19,960
Tracey times dump for midnight with a D three Swamness

961
00:47:20,000 --> 00:47:22,400
one one as a driver account. I paused at the

962
00:47:22,480 --> 00:47:25,599
edge of the curb, half stuttering. Nobody sat visibly behind

963
00:47:25,639 --> 00:47:28,239
the wheel, but the interior glow of dash man to

964
00:47:28,320 --> 00:47:30,599
phone eliminated the empty cabin. The ride app I come

965
00:47:30,639 --> 00:47:33,480
pulsing like a warning, summoning the remains of my nerve,

966
00:47:33,559 --> 00:47:36,000
I stepped forward, thumbed the handle, and slipped into the

967
00:47:36,000 --> 00:47:39,440
back seat, closing the door behind. Inside, the out was colder,

968
00:47:39,480 --> 00:47:41,480
still heavy, with the scent of vinyl and some faint

969
00:47:41,519 --> 00:47:45,480
earthy cologne. The dashboard was a perfect recreation of company issue,

970
00:47:45,559 --> 00:47:47,559
the foreign clip to the vent displaying the system I

971
00:47:47,599 --> 00:47:49,800
knew too well, their ghost ride events, erre payment, no

972
00:47:49,840 --> 00:47:54,280
passenger identifier. A moment later, the dashboard came alive, flickering

973
00:47:54,320 --> 00:47:58,199
with banded lines. The radio whined softly, then stuttered. From

974
00:47:58,239 --> 00:48:01,039
the distorted speakers, came a glitching fore worries fragmented, but

975
00:48:01,119 --> 00:48:03,400
with the cadence I've recognized from the chat logs. YE

976
00:48:03,440 --> 00:48:06,199
shouldn't be here. Too late to exit? I steadied my

977
00:48:06,280 --> 00:48:09,039
breathing started, my phone camera concealed behind my thigh, red

978
00:48:09,079 --> 00:48:12,440
record light barely visible in the darkness. Where are we going?

979
00:48:13,079 --> 00:48:15,880
I asked voice? Even the replies spilled from the speaker

980
00:48:16,000 --> 00:48:18,400
crackled and doubled. An echo line open to lead or

981
00:48:18,480 --> 00:48:21,400
join the screen flash a white box blimming with the

982
00:48:21,400 --> 00:48:23,480
same blurred silhouette I'd seen in the dat come at

983
00:48:23,480 --> 00:48:26,320
one stringer yet familiar, shifting restlessly at the edge of vision.

984
00:48:26,840 --> 00:48:29,599
The cars shifted into gear, apparently on atopilots, pulling away

985
00:48:29,599 --> 00:48:31,960
from the coat, randing one corner then another, weaving a

986
00:48:32,000 --> 00:48:34,599
route through sleeping city blocks that made no geographic sense.

987
00:48:35,360 --> 00:48:38,159
Lights passed by outside, but streets looked empty, blank, expanse,

988
00:48:38,199 --> 00:48:41,199
with no sign of human life. Traffic signals held green

989
00:48:41,239 --> 00:48:44,360
as we drifted slowly through, as if time had bent sideways.

990
00:48:44,760 --> 00:48:47,719
The ride app demanded input. A button flashed, Eggsit now

991
00:48:47,800 --> 00:48:51,559
or acknowledge? I pressed neither, committing to pure observation. Hands

992
00:48:51,599 --> 00:48:54,519
pressed to my knees, ever, muscle quaking in the blankness

993
00:48:54,519 --> 00:48:57,360
of the mirrors, A face solidified, not the driver, not

994
00:48:57,440 --> 00:49:00,280
visible except as reflection a familiar outline, the city coggestion

995
00:49:00,360 --> 00:49:03,000
of my own feature sculpted and flickering overlay, watching me

996
00:49:03,039 --> 00:49:06,039
from within and beyond. The radio voice pulsed, do you

997
00:49:06,079 --> 00:49:08,639
remember who you were driving? When I reached for the door,

998
00:49:08,679 --> 00:49:12,000
a soft mechanical snickel locked it in place, the dashboard

999
00:49:12,000 --> 00:49:14,880
into his flask one last time dullies were join. I

1000
00:49:14,920 --> 00:49:18,599
didn't answer. I whirled myself outwardly, calm, every sense thrumming

1001
00:49:18,639 --> 00:49:21,360
with alarm. At last, the ride Drusloe crept to the

1002
00:49:21,400 --> 00:49:25,000
curb where I'd started and stopped. The car powered down, light, flickering,

1003
00:49:25,119 --> 00:49:28,400
dashboard going dark. The screen on my phone, which I'd

1004
00:49:28,440 --> 00:49:30,960
used to record, went blank, the video arc I've dissolving

1005
00:49:30,960 --> 00:49:33,920
to static. The burner phone now showed only an empty

1006
00:49:33,920 --> 00:49:37,559
home screen. All ride history gone. I staggered out, hot

1007
00:49:37,599 --> 00:49:39,599
clawing at my rib and stood back under the city's

1008
00:49:39,639 --> 00:49:42,840
pale sodium glare as I watched the car idle for

1009
00:49:42,880 --> 00:49:45,400
a full minute before sliding away, vanishing at the corner.

1010
00:49:45,960 --> 00:49:47,960
No trace in the street, nothing but my own breath

1011
00:49:47,960 --> 00:49:50,000
fogged in the air, the echo of the ghostly radio

1012
00:49:50,079 --> 00:49:52,519
voice still whispering in the back of my skull. All

1013
00:49:52,599 --> 00:49:55,480
evidence of the rider raced itself under my eyes. I

1014
00:49:55,599 --> 00:49:58,159
checked my phone once twice, three times. No art of fact,

1015
00:49:58,440 --> 00:50:00,920
no trace, only the blank, defaut wallpaper, as if I

1016
00:50:00,920 --> 00:50:02,719
had simply stepped up for air and missed any connection

1017
00:50:02,800 --> 00:50:05,159
to the line. As I walked back up the stairs,

1018
00:50:05,280 --> 00:50:07,480
leg shaking, I held tightly on to the fading thumbal

1019
00:50:07,519 --> 00:50:09,880
print out from the chet lock, the only persistent physical

1020
00:50:09,920 --> 00:50:14,000
artifact left in my pockets. The world around me returned buzzers, flickers,

1021
00:50:14,079 --> 00:50:16,280
a single car passing on the avenue, but the boundary

1022
00:50:16,320 --> 00:50:19,199
between digital and reel had blurred beyond repair. Back in

1023
00:50:19,239 --> 00:50:21,360
the apartment, I sat at the old wooden table, looking

1024
00:50:21,400 --> 00:50:23,800
down at my two fonds and white lap up. The

1025
00:50:23,800 --> 00:50:26,400
city below yawned open, indifferent to my terror, the hum

1026
00:50:26,440 --> 00:50:28,360
of its machinery echoing what I had learned but could

1027
00:50:28,400 --> 00:50:31,360
never quite prove. In that moment, I understood I had

1028
00:50:31,400 --> 00:50:33,559
seen one layer of the net, only the outer most skin.

1029
00:50:34,159 --> 00:50:37,119
The network was deeper, self repairing, erasing vets the moment

1030
00:50:37,159 --> 00:50:40,320
they touched anything vital. My own sorry was now only

1031
00:50:40,360 --> 00:50:42,480
another art fact, half visible from the back end, a

1032
00:50:42,519 --> 00:50:45,320
red badge denominally no one would choose to open. And

1033
00:50:45,480 --> 00:50:48,280
yet my hands still moved, stubborn and deliberate, as I

1034
00:50:48,320 --> 00:50:50,960
annotated everything I knew and pushed it out encrypted, shuffled

1035
00:50:50,960 --> 00:50:52,920
to every secure drop I'd memorized from me as a

1036
00:50:52,960 --> 00:50:55,800
digital life, I sent my report to where it might matter,

1037
00:50:55,960 --> 00:50:58,920
journalists advocates, the handful of friends who would recognize a

1038
00:50:58,960 --> 00:51:01,559
warning when they saw it. Then I shut everything off,

1039
00:51:01,679 --> 00:51:05,280
powered down, pulled the curtains tight. A final one line

1040
00:51:05,320 --> 00:51:06,960
text rolled in just as I was about to slide

1041
00:51:06,960 --> 00:51:10,199
my phone away. Is any one there? He never left

1042
00:51:10,199 --> 00:51:12,920
the car. The words pulsed softly on the screen, the

1043
00:51:12,960 --> 00:51:16,800
audio line humming with faint, familiar static. I saw reflected

1044
00:51:16,800 --> 00:51:18,639
in the glass of when now darkened, that upper blurred,

1045
00:51:18,840 --> 00:51:21,440
half formed figure hovering behind my left shoulder, the same

1046
00:51:21,440 --> 00:51:24,119
soil which shaded and dash and blue. I looked up.

1047
00:51:24,159 --> 00:51:26,599
The fine hair is on my arms rising, and understood

1048
00:51:26,639 --> 00:51:28,159
then that the line no longer needed a call to

1049
00:51:28,239 --> 00:51:31,760
keep itself open. On the other end, something was always listening.

1050
00:51:32,360 --> 00:51:35,440
On the other end, something was always listening. For several

1051
00:51:35,440 --> 00:51:37,920
long moments, my reflection wouldn't release me. My own outline

1052
00:51:37,960 --> 00:51:40,679
laid with half seen figure details warping and fading each

1053
00:51:40,719 --> 00:51:43,760
time I blinked. I set the phone face down, but

1054
00:51:43,840 --> 00:51:46,599
its screen glowed through the table's grain and electronic candle.

1055
00:51:46,639 --> 00:51:50,559
Guttering against sleep. I breathed with careful deliberation, pulse strumming

1056
00:51:50,599 --> 00:51:52,559
in my ears, waiting for the silence to fray, with

1057
00:51:52,639 --> 00:51:55,880
the line to drop dead. At last, it didn't. The

1058
00:51:55,920 --> 00:51:58,119
city outside my window began to stir and sure in

1059
00:51:58,159 --> 00:52:00,320
the distant bark of a CAB's horn. When shivering lose

1060
00:52:00,360 --> 00:52:03,360
a stray branch against bricks. But my world had collapsed

1061
00:52:03,360 --> 00:52:04,960
to the four feet between me and the backs of

1062
00:52:04,960 --> 00:52:07,880
my devices, a place where evidence evaporate, calls and spoiled

1063
00:52:07,920 --> 00:52:10,360
into static, and the boundary between being the watcher and

1064
00:52:10,400 --> 00:52:13,679
the watch had burned away. I forced myself upright, rolling

1065
00:52:13,679 --> 00:52:15,960
my shoulders against the egg of adrenaline, and spent terror

1066
00:52:16,519 --> 00:52:18,800
everything from the day before in the night's encounter in

1067
00:52:18,840 --> 00:52:20,960
a car wredoors click shirt and ryse sal for RaSE

1068
00:52:21,000 --> 00:52:23,760
to plead back and footmented sensory loops, the vinyl's chill,

1069
00:52:23,840 --> 00:52:26,800
the digitized voices shredded logic, the impossible familiarity of the

1070
00:52:26,840 --> 00:52:30,039
passenger blowed in mirrored glass. It was all gone, save

1071
00:52:30,079 --> 00:52:32,280
the final anonymous text and a print house much limp.

1072
00:52:32,360 --> 00:52:35,079
I sweat. If I became a missing entry nex. If

1073
00:52:35,119 --> 00:52:37,639
the network targeted me, no proof du't last the ire

1074
00:52:38,280 --> 00:52:40,840
I felt both singled out and indistinguishable, and note on

1075
00:52:40,880 --> 00:52:43,400
some hidden graph relevant only so long as I kept

1076
00:52:43,400 --> 00:52:46,440
the thrid in motion. There was, by necessity work left

1077
00:52:46,480 --> 00:52:49,440
to do. Survival instinct hollowed a path through dread, and

1078
00:52:49,519 --> 00:52:51,599
I seized it. Stood, poured a glass of tap water,

1079
00:52:51,719 --> 00:52:54,440
set it carefully on the table, I reviewed the chain

1080
00:52:54,480 --> 00:52:58,360
of messages, logs, corrupt a chat edits. I mapped connections

1081
00:52:58,400 --> 00:53:02,000
with lyone zadmin departures, right spikes, unreachable drivers, linking my

1082
00:53:02,039 --> 00:53:05,840
closest points of certainty. I locked every file with new passwords,

1083
00:53:05,920 --> 00:53:08,960
triple checked my cloud drawbendpoints, and ran a final virus check.

1084
00:53:09,119 --> 00:53:11,360
Though I suspected no code would catch the thing settling

1085
00:53:11,440 --> 00:53:14,400
over my system. Now, when the sun edged a little higher,

1086
00:53:14,440 --> 00:53:17,119
I finally composed an encrypted packet with everything I knew.

1087
00:53:17,199 --> 00:53:19,880
The clusters, the override logs, the dash conframes that had

1088
00:53:19,880 --> 00:53:22,119
nearly worn my face, the hypothesis of a raised hand,

1089
00:53:22,119 --> 00:53:24,079
those cycling through new shells as easily as rolls in

1090
00:53:24,079 --> 00:53:27,639
a script, each point nested behind layers of keys, routed

1091
00:53:27,639 --> 00:53:29,920
through anonymous uploader, as sewn in books. As I hoped Julia,

1092
00:53:30,039 --> 00:53:32,480
Gracie or some one else would reach my still monitor

1093
00:53:33,039 --> 00:53:35,360
With a thumb and numb from tension, I distributed it.

1094
00:53:35,960 --> 00:53:38,400
Every minute that passed without blowbacks did a different note

1095
00:53:38,400 --> 00:53:41,199
of panic. If my signal was meant to vanish, it

1096
00:53:41,239 --> 00:53:43,280
now existed in a dozen ghost places, hard to trace,

1097
00:53:43,280 --> 00:53:46,719
hard or still touries completely. I comfort if a frail one.

1098
00:53:47,280 --> 00:53:50,000
The act of sending was both anti climax and necessity.

1099
00:53:50,559 --> 00:53:53,840
I found the old and accountable exhaustion crashing around my shoulders,

1100
00:53:53,880 --> 00:53:55,960
and after burn of two Manday nights spent monitor in

1101
00:53:56,000 --> 00:53:59,800
quiet lines and assembling tenuous conspiracies. The apartment fell back

1102
00:53:59,840 --> 00:54:02,119
to quiet, above the stretching for folds of a neighbor

1103
00:54:02,199 --> 00:54:06,039
beside faint music filtering from someone's streaming playlist. I leaned

1104
00:54:06,039 --> 00:54:09,559
against the kitchen counter and monitored the notifications. No new messages.

1105
00:54:10,199 --> 00:54:12,639
I checked slack out of refects, discovering that my company

1106
00:54:12,679 --> 00:54:15,800
Loggin now registered as an act of contact it my

1107
00:54:15,880 --> 00:54:18,800
contract or email wants a scrape of reassuring normalcy had

1108
00:54:18,840 --> 00:54:22,760
been suspended, so had graces. A handful of names in

1109
00:54:22,800 --> 00:54:24,639
my network flickered off linked in over the course of

1110
00:54:24,679 --> 00:54:27,360
an hour, profiles going private or evaporating, as though their

1111
00:54:27,400 --> 00:54:29,519
runs had split at the fire door, not bothering to

1112
00:54:29,559 --> 00:54:33,159
turn off the lights on my phone, ryde chhair alert ceased.

1113
00:54:33,880 --> 00:54:36,840
Not a single pin for incoming rides, no safety reminders,

1114
00:54:37,039 --> 00:54:40,599
not even a survey request for apuse satisfaction. My presence,

1115
00:54:40,719 --> 00:54:44,079
I realized, was being blotted out systematically, almost gently, as

1116
00:54:44,119 --> 00:54:46,840
if the network were smoothing over wrinkles rather than issuing thrips.

1117
00:54:47,519 --> 00:54:49,960
That evening, I walked outside through her heavy with sprain,

1118
00:54:50,519 --> 00:54:53,480
the sety movement, concerned, oblivious, a parade of ignition, sparks

1119
00:54:53,480 --> 00:54:55,440
and tail lights, a few block part as pulsing the

1120
00:54:55,480 --> 00:54:59,400
shallow correctable joy. Yet every sliding car, every rycher decal

1121
00:54:59,440 --> 00:55:01,239
glowing in then and night struck me now as both

1122
00:55:01,239 --> 00:55:04,800
participant and confederate in the machinery. At glimpsed, I unplugged

1123
00:55:04,840 --> 00:55:07,840
everything not essential. I taped over the camera lens again,

1124
00:55:07,880 --> 00:55:09,880
even though the green nelide had not blinked since my

1125
00:55:09,920 --> 00:55:12,800
system blacked out. In a final ride, I unplugged the

1126
00:55:12,840 --> 00:55:15,320
smart speaker. When I made tea. The squeal of the

1127
00:55:15,360 --> 00:55:18,840
kettamask den certain discouring in my head. With nothing left

1128
00:55:18,840 --> 00:55:21,119
to monitor, I existed in the prison tense for a while,

1129
00:55:21,159 --> 00:55:23,519
phone on airplane mode, lopped up, stuffed in a drawer.

1130
00:55:23,599 --> 00:55:25,760
Only the physical acts of day to day endurance left

1131
00:55:25,800 --> 00:55:29,719
within reach. For days, nothing happened. The story didn't boil

1132
00:55:29,800 --> 00:55:34,719
up in headlines, no expressey, no law enforcements sweep Surely

1133
00:55:34,800 --> 00:55:36,880
as use, an end disappeared from every contact sheet I'd

1134
00:55:36,920 --> 00:55:38,880
known the one anonymous in which should share a bounced

1135
00:55:38,880 --> 00:55:42,079
with an undeliverable court exceeded error. I watched a ride

1136
00:55:42,119 --> 00:55:44,199
sharing apps in public app stores for changes to go

1137
00:55:44,400 --> 00:55:46,840
for user reviews, for signs of new errors crawling uproard,

1138
00:55:46,880 --> 00:55:48,440
but there were none of just the same complaints but

1139
00:55:48,599 --> 00:55:51,320
weight times and fair spikes. It was as though the

1140
00:55:51,400 --> 00:55:54,599
system recognizing a breach had replaced the surface layer without

1141
00:55:54,639 --> 00:55:59,000
effort rasure and adaptation at once, but absence two revealed patterns.

1142
00:55:59,719 --> 00:56:03,079
My location ID usually pulled for ride discounts signaled to

1143
00:56:03,119 --> 00:56:06,559
deactivator pending review. My payment card was declined on mine

1144
00:56:06,559 --> 00:56:10,199
approchases fled for suspicious routing. I called the card issue.

1145
00:56:10,199 --> 00:56:12,159
They confirmed a fraud warning from an I be assigned

1146
00:56:12,159 --> 00:56:15,519
out of nowhere, fired at midnother week before my online

1147
00:56:15,519 --> 00:56:18,960
accounts trained of social oxygen support. Tickets posted under my

1148
00:56:19,079 --> 00:56:22,599
name were rerouted or vanished. The only persistent artifact was

1149
00:56:22,639 --> 00:56:25,000
that raw printed chat lug. The lion is anyone there?

1150
00:56:25,079 --> 00:56:28,559
He never left the car. Paranoia swelled again, not a spectacle,

1151
00:56:28,599 --> 00:56:30,239
but a texture that sensed that I was always at

1152
00:56:30,239 --> 00:56:33,159
the terminal edge, that any contact might be another handler's mask.

1153
00:56:33,880 --> 00:56:35,880
I spoke to no one in person. I let calls

1154
00:56:35,880 --> 00:56:38,679
from family go unturned, fearing the line had become infested,

1155
00:56:38,800 --> 00:56:40,599
or that my voice contained too much of the story.

1156
00:56:41,239 --> 00:56:43,519
Yet in the real world, the wheels continued to turn.

1157
00:56:44,199 --> 00:56:46,960
I bought groceries, smiled at the exhausted cashier, felt the

1158
00:56:47,000 --> 00:56:49,639
subcutaneous twinge of recognition. In dim glasses. I passed a

1159
00:56:49,719 --> 00:56:52,960
ride heer Piccopson. After dark, cars came and went, some

1160
00:56:53,119 --> 00:56:55,800
circling in slow looping orbits, all of them ready to

1161
00:56:55,840 --> 00:56:58,639
slide behind another layer of digital mask of proe too closely.

1162
00:56:59,440 --> 00:57:02,760
Several weeks slid by. On a morning, handed by drizzle,

1163
00:57:02,880 --> 00:57:05,239
I noticed that the ap echosystem abruptly updated a new

1164
00:57:05,360 --> 00:57:08,199
cheerful color for the branding, a handful of privacy assurances,

1165
00:57:08,239 --> 00:57:11,360
the option to opt out of personalized ride suggestions. The

1166
00:57:11,440 --> 00:57:13,920
developers had scrubed the data layer, but the true structure,

1167
00:57:13,960 --> 00:57:17,800
passing permissions of ride and locks remained invisible. To casualize

1168
00:57:17,960 --> 00:57:20,840
hiding the machinery that had lain beneath. It was only

1169
00:57:20,920 --> 00:57:24,360
then that a pattern emerged Suttler more insulating. Reports of

1170
00:57:24,400 --> 00:57:27,400
ghost rides vanished altogether from public forums for about a month.

1171
00:57:27,960 --> 00:57:31,480
Then a summer thickened, scattered new posts described thinly simhophenomena,

1172
00:57:31,599 --> 00:57:34,639
but always in other cities, foreign platform variants, port crewers,

1173
00:57:34,679 --> 00:57:39,760
and different idioms, a new cycle, new erasures, same hidden, shaped,

1174
00:57:39,760 --> 00:57:43,079
different masks. I learned to become both less and more vigilant,

1175
00:57:43,280 --> 00:57:46,280
Less in my public documentation, more in the cold habitual

1176
00:57:46,280 --> 00:57:48,360
sweep of my living space, a daily routine of scanning

1177
00:57:48,400 --> 00:57:51,559
for Mike's, checking window latches, watching the exterior corridor for

1178
00:57:51,679 --> 00:57:55,360
cause idling toulon. I passed each reflection wearily, glancing for

1179
00:57:55,400 --> 00:57:57,559
the silhouette that had flickered, for screens in glass and

1180
00:57:57,599 --> 00:58:01,400
rear view mirrors. Even in privacy, I felt surrounded by lines,

1181
00:58:01,599 --> 00:58:04,559
both visible and codeep, each capable of snapin, shut or

1182
00:58:04,599 --> 00:58:07,280
opening in you. It struck me often in the hour

1183
00:58:07,400 --> 00:58:09,760
before sleep, that the only reason I persisted was the

1184
00:58:09,840 --> 00:58:12,880
had been cataloged now as observer, not there. If the

1185
00:58:12,960 --> 00:58:15,480
network chose to spin up another handler, another round of

1186
00:58:15,519 --> 00:58:17,880
mass rides, my rolle would again be to bear witness

1187
00:58:17,960 --> 00:58:21,360
to seed uncertainty, tacked as the static between channels. I

1188
00:58:21,440 --> 00:58:24,199
had seen one pattern close itself off cleanly and completely,

1189
00:58:24,280 --> 00:58:27,159
but the underlying structure a cursive adaptable on NI persent

1190
00:58:27,239 --> 00:58:30,280
was unchanged. Perhaps the point was not to finish, but

1191
00:58:30,440 --> 00:58:33,480
only to survive, to outlast the silence between pings. On

1192
00:58:33,639 --> 00:58:36,320
a night too hot for comfort. Four months after my ride,

1193
00:58:36,440 --> 00:58:39,400
I received the last message I would ever acknowledge, a

1194
00:58:39,559 --> 00:58:43,000
muted buzz, a sharp drain in battery and notification. Refusing dismissal,

1195
00:58:43,559 --> 00:58:46,480
I flipped the phone. As always, there was only a message,

1196
00:58:47,320 --> 00:58:50,280
Is any one there? Ye never left the car, The

1197
00:58:50,400 --> 00:58:53,639
text shown for an instant, the speakers hissed, and as

1198
00:58:53,719 --> 00:58:55,679
though the air itself thickened, that old was but threaded.

1199
00:58:55,719 --> 00:58:59,039
The shadowed silence rising just behind my shoulder, cool and

1200
00:58:59,159 --> 00:59:02,679
insistent in the glass over my reflection, the faintest suggestion

1201
00:59:02,760 --> 00:59:05,239
of a second, blurred figure stared from behind, a silhouette

1202
00:59:05,239 --> 00:59:07,239
built from every ride and every echo, fused into the

1203
00:59:07,280 --> 00:59:10,239
shape that meant nothing and everything at once. I closed

1204
00:59:10,280 --> 00:59:12,840
my eyes. When I opened them, the message was gone,

1205
00:59:13,480 --> 00:59:16,079
but the line, in all its unwinding, a cursive mystery,

1206
00:59:16,159 --> 00:59:18,719
stayed open, as always, waiting somewhere out there for its

1207
00:59:18,800 --> 00:59:23,199
next reply. And that is the end. Thank you for listening,

1208
00:59:23,280 --> 00:59:24,599
and I will see you in the next one.