September 1978
Tommy tried to forget about it.
Focused on his work. On Sarah. On being a better father, even if only one weekend a month.
But the pattern wouldn't leave his mind. Once you saw it, you couldn't unsee it.
And more: once you understood the physics, the engineering principles, you couldn't ignore them.
Systems could be designed. Outcomes could be engineered. Chaos could be harnessed.
Not through fortune-telling. Through control of initial conditions.
Tommy started reading more. Operations research. Game theory. Systems analysis. The emerging field of complexity theory.
All tools for understanding and manipulating complex systems.
All tools that, in the wrong hands, could be used to engineer human affairs like engineering aircraft.
Find the control points. Apply the right forces. Produce the desired outcomes.
It was just physics. Just mathematics. Just engineering.
Applied to human society instead of aircraft.
Terrible. Elegant. Possible.
December 1978
Sarah spent Christmas with Tommy for the first time.
Linda had remarried—an architect named David. Stable. Present. Everything Tommy wasn't.
Sarah liked him. Tommy could tell. And that hurt.
"David's nice," Sarah said on Christmas morning. "He helps me with my homework. Takes me to movies. He's teaching me to draw buildings."
"That's good. I'm glad you have him."
"I still love you, Daddy."
"I know, honey. I love you too."
They spent Christmas Day together. Tommy had gotten Sarah a telescope—not expensive, but decent. She'd been fascinated by the Viking Mars missions and the Voyager spacecraft.
"Maybe you'll be a scientist," Tommy said as they set it up.
"Maybe. Or an astronaut. Or an engineer like you."
"You could be anything you want."
That night, they set up the telescope in the apartment parking lot. Clear December night. Sarah looked at the moon, at Mars, at Jupiter.
"Daddy, did you know Voyager 1 is past Jupiter now? It's going to Saturn next."
"I know. Amazing, isn't it?"
"Why do we send robots to explore space but we use planes to fight wars?"
The same question from two years ago. She hadn't forgotten.
"It's complicated, honey."
"You always say that." Sarah looked up from the telescope. "But it's not really complicated. We choose what to build. We could choose to build things for exploring instead of fighting. Right?"
"In theory, yes."
"Then why don't we?"
Tommy had no answer. Or rather, he had an answer he couldn't give an eight-year-old.
Because exploring space doesn't make profits. Because wars are good business. Because the system is designed to incentivize conflict.
Because humans are capable of incredible things, but we choose terrible ones.
"I don't know, honey," Tommy said finally.
Sarah went back to the telescope. But Tommy could tell: she knew he was lying.
Kids always knew.
March 1979
Vehicle 2 crashed on its third flight.
Pilot survived—ejected successfully. But the aircraft was destroyed. Millions of dollars. Months of work.
Tommy reviewed the crash data. Looked for what went wrong.
Control system failure. Component malfunction.
He pulled the component specifications. Subcontractor: Meridian Technical Systems.
Tommy felt his blood run cold.
He checked Vehicle 1. Same component type, different supplier. No issues. Two years of flight testing, no problems.
He checked the procurement justification for Vehicle 2. "Cost savings - alternate supplier selected."
Meridian had underbid on this component. Won the contract. Delivered a part that failed catastrophically.
Tommy pulled the component failure analysis. The part had failed due to a resonance issue. Electromagnetic interference caused oscillations at a specific frequency. The component's shielding was inadequate.
Basic physics problem. Any competent engineer should have caught it.
But Meridian hadn't. Or had they?
Tommy ran simulations on his Apple II. The physics was straightforward. The failure mode was predictable. Anyone testing properly would have found it.
Which meant either: Meridian was incompetent.
Or the failure was deliberate.
Sabotage disguised as incompetence.
Vehicle 2 destroyed. Program delayed. More funding required. More testing. More contracts.
All because of a $50,000 component from Meridian.
Tommy mentioned it to Ben Rich. Carefully.
"Sir, the failed component was from Meridian. We might want to review their quality control. The physics of the failure suggests inadequate testing."
Rich nodded. "Already on it. They're being dropped from future contracts."
"That's it? No investigation into how they missed such a basic resonance problem?"
"Investigation costs money and time. We have a schedule. Just switch suppliers and move on."
"But if it's a pattern—if they have quality issues—shouldn't we investigate? We're talking about basic electromagnetic interference. Any engineer should have caught this."
Rich looked at him. "Forsyth, sometimes a failure is just a failure. Not everything is a pattern. Move on."
Tommy wanted to push harder. But Dave's warning echoed: Don't throw away your career.
So Tommy moved on. Documented the failure in his personal notes. Added it to his growing file of oddities.
The file was getting large now. His Apple II's floppy disk was almost full.
And the pattern was undeniable.
July 1979
Dave Miller died in a car accident.
Single-vehicle collision on Highway 14. Late at night. Dave's car went off the road, hit a tree at high speed. Died instantly.
Police ruled it an accident. Fatigue, possibly. The road was clear, weather was good, but these things happened.
Tommy went to the funeral. Met Dave's ex-wife. His teenage son.
After the service, Tommy stood by the grave thinking.
Dave had seen Tommy's documents six months ago. Had told him to stop. Had warned him.
That kind of thinking gets you fired. Or worse.
Or worse.
And now Dave was dead.
Accident?
Tommy thought about the physics. Single-vehicle collision. Clear road. Experienced driver. Car leaving the road at high speed for no apparent reason.
Steering failure? Brake failure? Both were engineering problems with engineering solutions.
Both could be induced if you knew what you were doing.
Tommy had no proof. Just timing. Just pattern. Just the growing certainty that once you started seeing, you became a problem.
And problems got solved.
October 1979
Tommy became more careful.
Stopped bringing his father's notebook to work. Stopped asking questions about Meridian. Stopped looking into procurement oddities.
Acted normal. Focused on his job. Did excellent work.
But at home, alone with his Apple II, he kept documenting. Kept tracking. Kept adding to the file.
He wrote a simple program in BASIC. Database of contracts, dates, failures, patterns. The Apple II made it easy. Rick had done this work with index cards. Tommy had a computer.
Technology advancing. Making documentation easier. Making pattern recognition faster.
But also making surveillance easier. Making control easier.
The same tools that helped Tommy see the pattern could help others hide it.
Progress cut both ways.
Tommy started taking precautions.
Copied his files to multiple floppy disks. Kept them in different locations. One at home. One in a safety deposit box. One with a friend who didn't know what was on it.
Instructions: if anything happened to him, the disks went to Sarah on her eighteenth birthday.
Tommy wasn't paranoid.
Or maybe he was. Maybe he was becoming his father.
But Dave was dead. And that felt like more than coincidence.
January 1980
The sealed envelope.
Tommy had forgotten about it until he was organizing his closet and found the package from 1972. The London solicitor. His father's watch. The notebook he'd been using.
And the envelope with instructions: Do not open until 1980.
It was 1980 now. January 15th.
Tommy sat on his bed, holding the envelope. Eight years since it arrived. Eighteen years since his father had written whatever was inside—1962, a year before Rick died.
Tommy opened it.
Inside: a letter and a key.
The letter read:
Tommy,
If you're reading this, I've been dead at least 17 years. You're 34 years old. Old enough to understand. Old enough to decide.
The key is for a safety deposit box in New York. Chase Manhattan Bank, Midtown branch. Box 1847. Paid through 2000.
Inside you'll find additional documentation I couldn't risk keeping in Baltimore. Names. Financial records. Evidence I couldn't publish because they were watching.
But also: technical documents. By 1962, I knew they were developing computational systems for war planning. Electromagnetic surveillance networks. Automated control systems. The physics and engineering that would make conspiracy possible at scale.
Your grandfather saw Pearl Harbor coming because of human intelligence—spies, reports, patterns. By the 1950s, I was seeing patterns in technology itself. Computers. Communications. Systems that could coordinate global operations.
In 1962, computers were primitive. But I could see where they were going. By the 1980s, I predicted, there would be networks connecting command centers globally. Computers running simulations of conflicts. Automated systems managing information flow.
I couldn't prove the conspiracy was using these systems. But I could prove the systems were being built. And I could predict how they'd be used.
If you're reading this in 1980, those systems probably exist now. The technology I predicted is probably operational. And the conspiracy has tools I could only imagine.
I'm giving you a choice. You can throw this key away. Forget I existed. Live your life. That's valid. That's safe.
Or you can go to New York. Open the box. See what I found. See my predictions about technology. And decide for yourself.
Just know: once you see, you can't unsee. Once you know, you're part of it. Once you start asking questions, they notice.
They always notice.
I hope you're happy, son. I hope you have a family. I hope you're building things that matter.
I hope you're nothing like me.
But if you are like me—if you can't let questions go, can't ignore patterns, can't stop seeing—then this key is for you.
Use it wisely.
Or don't use it at all.
Both choices are valid.
I love you.
—Dad
Tommy sat holding the key and letter for a long time.
His father had predicted networked computing. In 1962. When computers filled rooms and could barely calculate payroll.
Rick had seen where technology was going. And predicted how it would be used.
And now, in 1980, those predictions had come true.
The Skunk Works used networked terminals. The Pentagon had ARPANET—the precursor to what was becoming the Internet. Computers ran war game simulations. Satellite communications coordinated global operations.
Everything Rick predicted in 1962 was operational in 1980.
Which meant: if Rick was right about the technology trajectory, maybe he was right about everything else.
New York. More evidence. More documentation.
Dave's voice: Stop. Right now.
Dave's grave: fresh dirt, flowers wilting.
Pattern continuing: Vehicle 2 crash, Meridian component failure, no investigation, just move on.
And now: a key to more secrets.
Tommy put the letter and key in his safety deposit box.
He wasn't ready. Not yet.
Maybe never.