Chapter 4 — “When Ethan Walks Through His Parents’ Files and Discovers the First Hidden Injury Report”
Ethan didn’t sleep that night.
Not because he was held.
Not because he was questioned.
But because for the first time in his life, there was nothing left in his mind that felt stable enough to lean on.
Even memory had started to feel like it might have been edited.
The federal liaison had given him access—limited, supervised, structured.
A digital review terminal.
A clean room system.
The kind of setup that looks sterile on purpose, because anything emotionally charged inside it becomes evidence too.
I was not supposed to be there.
But I was.
Not officially.
Just present enough to ensure the chain of custody on what he saw could not later be questioned as “influenced interpretation.”
That was the phrase used.
Influenced interpretation.
As if truth itself could be biased.
Ethan sat in front of the screen for a long time without touching anything.
The cursor blinked.
Patient.
Unbothered.
Like it had all the time in the world.
“You don’t have to do this now,” I said.
He didn’t look away from the screen.
“If I don’t do it now,” he said quietly, “I might never do it.”
That, I understood.
He moved the mouse.
Logged in using the restricted access token.
The system loaded slowly.
Too slowly.
As if it knew what was waiting inside it.
Folders appeared.
Procurement history.
Incident overlays.
Field adjustment logs.
Ethan swallowed.
“These are just numbers,” he said.
I didn’t answer.
Because I had learned a long time ago that numbers are where stories go when no one is supposed to feel them.
He clicked the first folder.
“Fort Ridgeway — Armor Panel Compliance Batch 14.”
A list opened.
Rows of entries.
Serial codes.
Certification stamps.
Digital signatures.
And there it was again.
His name.
Ethan J. Hawthorne — Fallback Approval Node.
He frowned.
“I don’t even know what that means,” he said.
I leaned slightly closer.
“It means,” I said, “you were assigned as a failsafe signature when procurement officers were unavailable.”
“Why would they need that?”
“Because speed matters more than verification in high-volume defense contracting,” I replied. “At least, that’s what they tell themselves.”
He clicked deeper.
Another file expanded.
Then another.
And then the system flagged something in red.
“ATTACHED INCIDENT REPORT — PRIORITY REVIEW REQUIRED.”
Ethan paused.
Something in his posture changed.
“Incident?” he repeated.
I didn’t answer this time.
Because I already knew which one it was.
He opened it.
The screen shifted.
And suddenly there was no longer a system.
There was a story.
INCIDENT REPORT — FORT RIDGEWAY TRAINING EXERCISE 19-B
Subject: Armored transport vehicle, Hawthorne Defense Systems Model ARX-9
Event Type: Structural failure under controlled detonation simulation
Result: Partial breach of passenger compartment shielding
Injuries Reported: 3 personnel
Classification: Initially “non-critical training anomaly”
Ethan leaned closer.
“Three people?” he whispered.
The report continued.
Attached photos loaded slowly.
Too slowly.
Like the system was reluctant to show them.
A scorched vehicle frame.
A torn panel section.
A helmet cracked along the side.
And then—
A hospital form.
Redacted names.
But not everything redacted.
Rank visible.
Unit visible.
Diagnosis partially visible.
Ethan’s breath changed.
I saw it immediately.
That moment where someone realizes the document is not describing equipment.
It is describing humans.
His voice dropped.
“This… this is real?”
“Yes,” I said.
He stared at the screen.
Then clicked “SUPPLEMENTARY NOTES.”
The text expanded.
NOTE FROM FIELD OFFICER (REDACTED):
“Armor panel variance exceeded acceptable threshold. Manufacturer batch labeled compliant despite prior rejection due to material fatigue concerns.”
Ethan’s hand froze on the mouse.
“I don’t understand,” he said. “If it was rejected… why was it used?”
I answered quietly.
“Because rejection costs money.”
He looked at me sharply.
“So they just… approved it anyway?”
I nodded.
“Under expedited override protocols.”
Ethan leaned back.
The chair creaked.
Like it was struggling under the weight of realization.
“And my signature… allowed that?”
“Yes.”
A long silence followed.
Then he whispered:
“I didn’t know anyone got hurt.”
I looked at him then.
Properly.
Carefully.
“I believe you,” I said.
That was important.
Because truth doesn’t require belief—but people do.
He swallowed.
“Why didn’t anyone tell me?”
I hesitated.
Then answered honestly.
“Because you were convenient.”
That word hit harder than accusation.
He frowned.
“Convenient?”
“Yes,” I said. “Your credential removed friction. That’s all they needed.”
He stared at the screen again.
Then scrolled further.
Another document opened.
This one different.
Not a report.
A correspondence log.
Internal messaging.
Subject line:
“Incident De-escalation Strategy — Fort Ridgeway Batch 14”
Ethan clicked.
And the room changed again.
“We cannot allow formal escalation. Contract exposure threshold exceeded.”
“Reclassify as training irregularity.”
“Medical documentation to be adjusted to non-operational cause.”
“Legal review bypass authorized under executive discretion node: E.J.H.”
Ethan stopped breathing for a second.
Then slowly turned toward me.
His voice barely worked.
“What is this?”
I didn’t answer immediately.
Because there are moments where explaining too quickly can break someone in the wrong direction.
Finally, I said:
“This is where the truth was rewritten.”
He shook his head.
“No,” he said. “I didn’t approve that.”
I nodded once.
“I know.”
He blinked.
“Then why is my name there?”
I leaned back slightly.
“Because your access was used as a blanket authorization layer,” I said. “Once your credential confirmed routing approval, downstream edits inherited legitimacy.”
Ethan looked sick.
“So… my signature didn’t just approve purchases…”
“It validated corrections after the fact,” I finished.
That was the part people struggle with most.
Not the mistake.
The echo of the mistake.
Ethan stood up suddenly.
The chair scraped.
“I didn’t hurt anyone,” he said, more firmly now. “I didn’t— I would never—”
His voice broke.
And for the first time, anger came through.
Not at me.
At the structure.
At the invisible system that had been sitting behind his life like a second spine.
I stood too.
“Ethan,” I said quietly, “intent and impact are not the same system.”
He shook his head again.
“I don’t accept that.”
“That doesn’t change it.”
He turned away from the screen.
Paced once.
Then stopped.
“I was engaged to this world and I didn’t even know it existed,” he said.
I didn’t correct him.
Because he was right.
He looked at me again.
“Did you know all of this before the gala?”
“Yes.”
A pause.
“And you still came?”
I met his gaze.
“I came because your parents were not the end of it.”
That made him stop.
“What does that mean?”
I hesitated.
Then told him the part he hadn’t reached yet.
“Your parents were one node,” I said. “Not the source.”
Ethan stared at me.
“There’s more?”
I nodded once.
The system behind me was already updating its logs.
He sat down slowly.
Like the idea of standing had become optional.
“And you’re going after it,” he said.
Not a question.
A realization.
I didn’t deny it.
“Yes.”
He looked back at the screen.
At his name.
At the signatures.
At the rewritten incident.
At the three injured soldiers reduced to files and classifications.
Then quietly said:
“What do I do with this version of me?”
That question hung in the air longer than anything else in the room.
Because it wasn’t about guilt.
It was about identity.
I answered carefully.
“You stop treating it as yours alone.”
He frowned.
“What does that mean?”
“It means,” I said, “you stop carrying what was assigned to you and start confronting what was built around you.”
He exhaled slowly.
“I don’t know how to be that person.”
I nodded.
“That’s expected.”
A pause.
Then softer:
“No one teaches you how to be outside a system you were raised inside.”
Ethan looked down again.
At his hands.
Then quietly said:
“I need to fix it.”
I didn’t immediately agree.
Because that word—fix—was too simple again.
Too clean.
Finally, I said:
“You need to understand it first.”
He nodded slowly.
And for the first time since I met him, he didn’t argue with reality.
He just stayed inside it.
The screen continued to glow between us.
And somewhere deep in the system, more files were waiting.
Not just about Hawthorne Defense Systems.
But about the network that made Hawthorne possible.
May you like
And Ethan Hawthorne, whether he wanted it or not…
Was now one of the few living keys that could open it.
