parameters for effective evaluation of data. I am at hazard of overloading my circuitry with extraneous material.
As for the observation of two men bringing wrapped waste for disposal at point 1392-A16, I am unsure why my alert circuitry was activated. I must conduct a search of the files, and shall allocate.004 seconds to the task.
It appears that the automatic correlation analysis conducted by the Mass Archival Data Collator and Presenter has noted a series of events occurring at widely separated points as evidently interrelated and fruitful of mischief. Since the MADCAP circuitry has been organized for precisely this function, even in the absence of any direct evidence, it appears logical to.99876 degree to accept the finding as representative of an actual potential threat, to be acted upon accordingly.
Thus I compute that my first mission is now clear. I must act against these men and the wrapped waste at once.
53
(General Margrave to Bolo technical staff, November 4, 1084 NS, 0800 hours)
Proceed at once with second-stage activation.
54
(unidentified detainee, Relocation Facility, audio pick-up by electronic surveillance grid, November 4, 1084 NS, 0830 hours)
Hey, lookit that thing! Pardon me, mister, I'm in a hurry. I tell ya, it's coming this way! See that scarf draped over the fore turret? That's the twelve-foot chain-link fence! It's on the loose! Let's move!
Don't panic there. Let's not have no pile-up.
Wait a minute. It's veering off. It's missed the Admin hut, but-well, I'll be! It's taken out the guard hut. Lookit them hardshots sparking off the hull-like shooting BB's at a rhino!
She sure is big. Easy, boys. We got a clear escape route past the huts. Let's form up here and march out in good order. The Bolo released us, insteada running us down. Funny, and we're in here because we're against it, or supposed to be.
Fall in, there! You, too, Mr. Trace. What are you waiting for? You said she was your baby, didn't ya? Maybe it's you she wants ta bust out. Maybe she couldn't see no other way around the Imperial red tape. Come on!
That's it. Hup, two, column haff-right, make for Supply Street yonder. We're out! Probably just accidental, but the Bolo let us out! It's nutty but I like it! Hup, two…
55
(Bolo Systems Coordinator, to General Margrave, via computer, November 4, 0930 hours)
No, sir, I have no theory as to why the machine should have broken through the security fence at the Relocation Facility. Very probably, simply accidental-happened to be in its path. Its destination? It had none. I mean, no specific one. It simply wanted to broaden the scope of its data base. It wanted to go out and see the world, so to speak.
Yes, sir, we could have stopped it, but only by wrecking the circuitry, which hardly seemed warranted at the time.
56
(Special Programmer Th. Uling, in taped conversation with General Margrave, November 4, 1084 NS, 1000 hours)
'I certainly did. I followed the special coding to the letter, but the Bolo just kept going. You can see for yourself, sir, with respect. Look at the seals on that panel. Every 'abort' device we have was activated, and they didn't stop her. I don't know what we'll do next. I'm only a technician, sir. You'll have to ask the boss, or ex-Chief Trace, maybe, if you can find him.
'But we don't have to worry. She's bound to stop soon. She didn't do any damage except to let that bunch of radicals loose. If you'll excuse me now, sir, with respect, I've got work to do-'
57
(from a scrambled audio communication, General Margrave to First Secretary, Strategic Command, Hexagon, November 4, 1084 NS, 1200 hours)
I know the boys were a little startled when she engaged her drive without a specific order, but that's just because they were jumpy. Tense, like the rest of us.
Yes, we know that it's now bypassing downtown D.C. via Processional Way. Nothing to worry about. The actions fall well within the parameters of the program as written. This thing is designed to be self-motivated within the limits of the programming. That is, when something clearly needs to be done, she'll do it without waiting around for a specific command.
For example, let's suppose the Bolo is following a preset course and encounters a ravine that's not on the map. She'll stop, not charge ahead to destruction.
No, I don't know what danger is averted by departing the Proving Ground and trampling the fence, but you notice it avoided the vehicles in the parking area directly in its path, though it did flatten a small utility shed. Breaking down the security fence around the restraint facility next door was accidental. We don't yet know its destination, but we're satisfied everything's A-OK.
58
(media interview with eyewitness, Pfc. Mervin Clam, guard at the Relocation Facility, November 4, 1084 NS, 1300 hours)
' 'No loss of life,' the SOB's say! If I wouldn't of broke the record for the hunnert-yard dash, it've got me! I was right in the shadow of the thing the whole time. I seen it was headed for the guard shack, and I figgered it'd veer off, but it took the hut right over my head, and I hit the ground running. I thought it had me, but I beat it out. It would've got me sure, if the I-99 Interchange hadn't been there. I went under the abutment, and it hadta veer off
