Chapter 24: COMPRESSED TIMELINE
CIA Headquarters, Langley — Week 11, Tuesday, 8:00 AM
Three Doctors Without Borders physicians, taken from a mobile clinic in eastern Syria forty-three minutes ago.
Ryan delivered the briefing standing, no slides, no projector — the information too fresh for preparation, arriving through the intelligence pipeline in fragments that he assembled verbally while Greer sat at the conference table with the stillness of a man absorbing operational bad news through a professional filter that converted shock into action items.
"Dr. Marguerite Bertin, French national. Dr. Ahmed Salah, Egyptian national. Dr. Jonas Bekker, Dutch national. Their convoy was stopped at a checkpoint controlled by Suleiman-affiliated forces near Deir ez-Zor. Drivers released. Physicians taken. Communications went dark eighteen minutes ago."
Alfred sat in his assigned chair — the same chair from Friday's Hanin briefing, now his permanent position in the Suleiman working group. His notepad was open. His pen was still.
Episode Five. The kidnapping. But Episode Five placed it in a different location, with different physicians, three weeks after Paris. This version — different doctors, different checkpoint, eleven days after Paris — is the compressed timeline made manifest. Suleiman couldn't wait three weeks because 187 dead didn't generate the media saturation that 306 would have. He needs the hostage crisis to amplify the Paris narrative, and he needs it now.
The meta-knowledge was partial. The broad stroke was accurate — Suleiman kidnaps Western aid workers to create a hostage crisis that compounds the Paris attack's political impact. The specifics were wrong — different people, different geography, different operational tempo. Alfred could see the shape of the play but not its edges, like reading a map where the roads were correct and the scale was distorted.
"Suleiman's communication protocols during hostage situations," Greer said. "Do we have anything?"
Ryan looked at Alfred. The look was collegial — you're the MENA specialist, what have you got?
Alfred's pen tapped once against the notepad. A stalling gesture that bought him two seconds while his mind ran a rapid cost-benefit analysis.
I know Suleiman's hostage communication protocols from the show. Encrypted satellite phones, rotating frequencies every six hours, dead drops for demands rather than direct communication with governments. In the show's timeline, these protocols held because Suleiman had three weeks to prepare and used established communication infrastructure.
But this Suleiman has been accelerating for eleven days. The communication infrastructure may not be the same. The protocols may have been modified for speed over security. If I provide the show's protocols and they're wrong — if Matice's team operates on my intelligence and walks into an ambush because Suleiman changed his communication pattern — the hostages die and I'm responsible.
If I hold back and say nothing, we lose time. But lost time is recoverable. Dead hostages are not.
"His financial patterns suggest a preference for encrypted communication through intermediary relay stations," Alfred said. "But I don't have confirmed protocols for hostage-specific operations. I can build a predictive model from the financial data — communication infrastructure correlates with fund transfers in his network's pattern — but it would take forty-eight hours."
"We may not have forty-eight hours," Ryan said.
"I know." Alfred met his eyes. "But an inaccurate protocol assessment is worse than a delayed one."
Greer absorbed this. His coffee was untouched. Evaluating.
He noticed. He saw me pull back. He saw me have information on the tip of my tongue and swallow it, and he filed that alongside the urgent supplement and the French CT analysis and the pattern of an analyst who knows things slightly before he should.
"Build the model," Greer said. "Forty-eight hours. Ryan, work the financial trail for the hostage operation. I'm activating Matice."
The name dropped into the room like a stone into still water. Matice. Alfred knew the name — had watched John Hoogenakker play the character across Seasons 1 and 2, the black ops specialist who moved through the show's plot like a knife through paper, appearing when violence was needed and vanishing when it was done.
A man entered the briefing room ten minutes later. Compact. Mid-forties. Gray at the temples, clean-shaven, wearing a jacket that fit well enough to conceal a shoulder holster and loose enough to permit movement. His eyes scanned the room the way Greer's did — exits, people, threats — but faster, more thorough, with the practiced efficiency of someone who'd been doing it in rooms where the scanning was not a precaution but a survival mechanism.
The skull pressure spiked.
Not the gradual proximity pulse Alfred felt near Greer or Ryan. A sharp, cold spike — the strongest people-signal the system had produced. Alfred's vision narrowed for a fraction of a second, the room's peripheral detail compressing as the system flagged this individual with an intensity that exceeded every previous human registration.
Matice. The system is screaming at me. Not "danger" exactly — the spike doesn't carry threat valence. More like "significant" amplified to eleven. This man matters to the timeline in ways that exceed even Greer or Ryan.
Why? In the show, Matice was a secondary character — capable, effective, but not central to the plot's architecture. He appeared, he operated, he disappeared after Season 2 with no explanation. What does the system know about Matice that the show never revealed?
Matice sat. No introduction — Greer clearly had briefed him before the room assembled. His eyes moved across the operations board, absorbing the Suleiman network map, the financial trails, the hostage intelligence, the DGSE activity pattern. His expression was flat. Professional. The face of a man reading an operational problem the way Alfred read spreadsheets — as data, not drama.
"Three hostages. Deir ez-Zor region. Suleiman network." Matice's voice was quiet, economical, the verbal equivalent of his efficient room-scanning. "What's the extraction window?"
"Forty-eight to seventy-two hours before Suleiman leverages them publicly," Ryan said. "His operational tempo has been accelerated since Paris. He'll move fast."
Matice nodded. Stood. "I'll need satellite feeds, signal intercepts for the Deir ez-Zor corridor, and everything you have on the checkpoint configuration."
"Hatfield will build you a communication protocol model," Greer said.
Alfred looked up from his notepad. Greer was watching him — not the brief evaluative glance of previous meetings but a sustained regard, the look of a man assigning a task and measuring the recipient's reaction.
"Forty-eight hours," Alfred said. The same timeline he'd requested. Consistent. Greer nodded.
Matice left the room. His footsteps were silent on the corridor linoleum — the movement discipline of someone who'd learned to walk without sound in environments where sound meant death. The skull pressure tracked his departure, a cold line drawn from Alfred's awareness to the diminishing presence moving toward the elevator bank.
---
Tuesday, 2:00 PM
The communication protocol model was the hardest analytical task Alfred had attempted since the DGSE intelligence package.
Not because the analysis was complex — it was, but complexity was Alfred's native language. The difficulty was calibration. He had information from the show that might be accurate, information from current intelligence that was definitely accurate, and no reliable method for distinguishing which show-derived details survived the timeline compression.
He built two models. The first used only verified current intelligence — financial transfer patterns, communication intercepts from the last eleven days, the operational behavioral analysis that any competent analyst could produce from the available data. Clean. Sourceable. Conservative.
The second model, built on his personal laptop in a document he would never show anyone, added the show's protocol details: the six-hour frequency rotation, the dead-drop demand structure, the satellite phone encryption standard. He compared the two models side by side.
The overlap was seventy percent. Where the show's protocols and the current intelligence agreed, Alfred had high confidence. Where they diverged — the remaining thirty percent — he had nothing but a television show's dramatic interpretation of operational tradecraft.
He submitted the first model. The clean one. Seventy percent of the picture, fully sourced, zero exposure risk. Matice would operate on verified intelligence, and the thirty percent gap would be addressed through fieldcraft rather than foreknowledge.
The restraint costs time. The restraint may cost a hostage's life. But the alternative — providing unverified meta-knowledge as if it were confirmed intelligence — could cost all three lives if the protocols have changed.
This is the calculus now. Not "what do I know?" but "what can I prove?" Not "what will happen?" but "what might have changed?" The show was a script. This world is improvisation. And the gap between the two is growing every day.
Greer received the model at four-thirty. Read it in his office. Called Alfred in at four-fifty.
"This is conservative."
"Yes, sir."
"You held back during the briefing this morning. You had something on the tip of your tongue about Suleiman's communication patterns."
Alfred's pulse moved from sixty-four to seventy-two. Invisible. The body's stress response, absorbed through the channels he'd been training since transmigration: steady breathing, flat hands, clinical focus.
"I had an analytical instinct that I couldn't source. Instinct without evidence is speculation, sir. Matice needs intelligence he can act on, not guesses that might get people killed."
Greer held his gaze. Four seconds. The evaluative silence — the same tool he'd used since his first day at T-FAD, the quiet that measured and weighed and filed.
"That's a mature analytical judgment, Hatfield." He set the model down. "It's also unusual for someone your age."
The compliment was a question. How do you know when to hold back? Where did a mid-level analyst with three years of average performance reviews develop the operational judgment to distinguish instinct from intelligence?
"Thank you, sir."
Greer dismissed him. Alfred walked back to his desk. Twenty-eight steps. His hands were steady. His heartbeat was decelerating — seventy-two back to sixty-six, the body finding its baseline.
He noticed the restraint. He noticed I held back. And instead of reading it as incompetence — a man who had nothing to contribute — he read it as judgment. A man who had something to contribute and chose not to.
Which is exactly what happened. And which is exactly the kind of pattern that a veteran intelligence officer files away, alongside the urgent supplements and the French CT timing and the MENA framework that appeared three weeks before anyone asked for it.
Greer is building a file on me. Not formally. Not yet. But in his head, behind those sharp dark eyes, a profile is forming: Alfred Hatfield — competent, unusually accurate, demonstrates operational judgment beyond his experience level, timing consistently aligned with significant developments.
The question he's circling but hasn't asked: Is Hatfield good, or is Hatfield informed?
---
Wednesday, 11:00 AM
Matice's team deployed Wednesday morning. The operational details were classified above Alfred's clearance — even the Suleiman working group's access was limited to pre-mission intelligence and post-mission debriefing. The space between those two points was Matice's domain, and what happened in Matice's domain stayed there until the after-action report landed on Greer's desk.
Alfred worked through Wednesday building the combined Suleiman analytical picture that Greer had requested — the synthesized product that merged Ryan's financial tracking with Hanin's debriefing intelligence with Alfred's French CT analysis. The work was real. No system-assist — he couldn't risk the escalating cost before the model was needed. No meta-knowledge shortcuts — the combined picture required documented sourcing that would survive Greer's scrutiny. Just analytical work, the kind he'd done in Portland for eight years and at Langley for ten weeks, the muscle memory of a man who processed data the way other people breathed.
Ryan worked two desks away. They'd established a rhythm over the weekend — Alfred building structural frameworks, Ryan filling them with financial data, the two of them passing documents back and forth through the shared drive with the efficient collaboration of analysts who'd discovered that their skill sets were complementary rather than competitive. Ryan's ambition drove the work forward. Alfred's caution kept it defensible. The combination produced intelligence that was better than either of them could have built alone.
At two PM, Alfred's phone buzzed. Greer's text: Matice team reports: 2 of 3 extracted alive. Third was KIA pre-arrival. After-action briefing 1600.
Two alive. One dead. Dr. Jonas Bekker, Alfred would learn at the four o'clock briefing — the Dutch physician, killed before Matice's team reached the site. Shot, not gassed, not tortured. A clean execution that suggested Suleiman's operatives had standing orders to reduce the hostage count if extraction was attempted.
In the show, all three survived. The show's Matice had three weeks of preparation, confirmed communication protocols, and a Suleiman network operating at standard tempo. This Matice had forty-eight hours, my conservative model, and a Suleiman network running hot.
Did the missing thirty percent cost Jonas Bekker his life? Would the show's protocols — the frequency rotation pattern, the dead-drop demand structure — have given Matice the edge he needed to reach all three in time?
I can't know. That's the point. I can't know, and living in the gap between what I know and what I can prove means accepting that the gap has a body count.
The after-action briefing was at four. Greer presided. Matice's team leader — a man Alfred had never seen and would likely never see again, the kind of operator who existed in classified corridors and disappeared between operations — delivered the report in flat, precise language.
Extraction point compromised due to hostile patrol adjustment twenty minutes before the team's approach window. Two hostages recovered from a secondary holding location identified through on-ground signals intelligence. Third hostage found deceased at the primary site. Cause of death: single gunshot wound, estimated time of death two hours before team arrival.
Two hours. Bekker was dead before Matice's team moved. The communication protocol model — conservative or complete — wouldn't have changed the outcome. Bekker was executed as a contingency, not in response to the extraction attempt.
The realization should have been a relief. It wasn't. The arithmetic of triage didn't produce relief — it produced a different category of guilt, the guilt of a man who'd been prepared to accept responsibility for a death that turned out not to be his fault, and who found that the absence of fault didn't diminish the weight of carrying it.
Alfred sat in the briefing and listened and took notes and processed the intelligence the way he processed all intelligence — data in, analysis out, emotion queued for later processing in a dark apartment where no one could see his face.
The SDN engaged during the briefing. Not prompted — Alfred hadn't been trying to read anyone. But the system's behavioral overlay settled over his perception of the room uninvited, and a cold impression surfaced about one of the rescue team members — a man seated in the second row, unremarkable, delivering supplementary details about the site configuration.
The impression was specific: the man was omitting something. Not lying about what he reported, but failing to report something he'd observed. The SDN read carried no detail — no indication of what was omitted or why. Just a cold certainty at approximately sixty-five percent confidence that the rescue team member's after-action account was incomplete.
Alfred made a note. Small. Pencil, not pen, on the margin of his notepad. A single question mark beside the man's seat position.
Sixty-five percent. Not enough to act on. Not enough to report. But enough to file. Because in a world where my meta-knowledge is degrading and my system abilities are emerging and every day brings information that doesn't match the script I memorized — every data point matters, even the ones I can't explain.
The briefing ended. Alfred returned to his desk. Updated his private notebook — the physical ledger in the nightstand drawer, the two-column record of known and unknown.
LEFT column, show knowledge: MATICE SURVIVES S1. DISAPPEARS AFTER S2. NO EXPLANATION.
RIGHT column, blank space: TARIQ. COMPRESSED TIMELINE. MATICE — SYSTEM FLAGGED STRONGER THAN GREER OR RYAN. RESCUE TEAM MEMBER — INCOMPLETE REPORTING.
Four entries in the blank-space column. Four pieces of reality that the show never depicted, that Alfred's foreknowledge never covered, that existed only in this world where 187 people were dead and 119 were alive and a desk analyst from Portland was learning, one data point at a time, that knowing the story's ending was not the same as understanding its meaning.
He closed the notebook. Locked it in the nightstand drawer.
The satellite phone was charged. The burner phones were in the desk. The SIGs were in the closet. The money was in the freezer and the bank accounts and the coat lining. The cipher kit was under the floorboard. The Greer dossier was in the messenger bag.
And Suleiman's compressed timeline was accelerating toward an endgame that the show had depicted across three more episodes — the Ebola bioweapon, the hospital confrontation, the final kill — but that this world would deliver on a schedule Alfred could no longer predict, through logistics he could no longer anticipate, against an enemy who had noticed that someone had been watching.
To supporting Me in Pateron.
with exclusive access to more chapters (based on tiers more chapters for each tiers) on my Patreon, you get more chapters if you ask for more (in few days), plus new fanfic every week! Your support starting at just $6/month helps me keep crafting the stories you love across epic universes.
By joining, you're not just getting more chapters—you're helping me bring new worlds, twists, and adventures to life. Every pledge makes a huge difference!
Join now at patreon.com/TheFinex5 and start reading today!