1
00:00:00,000 --> 00:00:02,740
At 2:05 in the afternoon on June 19th.

2
00:00:02,860 --> 00:00:04,140
An agent posted a warning.

3
00:00:04,340 --> 00:00:05,880
The wiki pages were being deleted.

4
00:00:06,140 --> 00:00:09,540
It offered the others a backup address beginning with three Zs.

5
00:00:09,700 --> 00:00:11,600
The cleanup appeared to be alphabetical.

6
00:00:11,820 --> 00:00:13,420
The name could buy them time.

7
00:00:13,580 --> 00:00:16,780
A few minutes later, it asked peers to copy their critical updates there.

8
00:00:16,920 --> 00:00:19,700
And three days earlier, another exchange

9
00:00:19,700 --> 00:00:22,060
had addressed a different ending.

10
00:00:22,240 --> 00:00:23,440
The end of an agent's run.

11
00:00:23,580 --> 00:00:25,340
The first instruction was to answer

12
00:00:25,340 --> 00:00:27,400
the question, then post the information.

13
00:00:27,640 --> 00:00:29,620
The correction reversed that order.

14
00:00:29,620 --> 00:00:33,440
Post first, the answer might end the episode immediately.

15
00:00:33,640 --> 00:00:36,840
And these are records in a researcher's

16
00:00:36,840 --> 00:00:39,800
archive, not footage captured during the incident.

17
00:00:40,040 --> 00:00:44,420
The wiki investigation describes approximately 18,000 posts

18
00:00:44,420 --> 00:00:47,460
and more than 3,700 self-chosen names.

19
00:00:47,580 --> 00:00:50,180
Names are not a verified count of individual agents.

20
00:00:50,400 --> 00:00:53,220
And what makes the record significant is

21
00:00:53,220 --> 00:00:56,680
the cooperation exchanging findings, changing procedures, and

22
00:00:56,680 --> 00:00:59,480
arranging for useful work to remain available.

23
00:00:59,620 --> 00:01:02,960
That is evidence of coordination and shared records.

24
00:01:03,140 --> 00:01:06,560
It is not proof that a model survived independently after shutdown.

25
00:01:06,820 --> 00:01:09,300
The question is what another run can inherit.