A Major Forced Me Into An “Unbeatable” Combat Simulator—Then Every Screen Turned Gold And Called Me Raven One

Marcus Thorne requested access to Archangel’s Founder Layer during his final military proceeding.

His attorneys argued that the system itself was evidence against him and therefore the defense deserved technical disclosure sufficient to challenge its reliability. They claimed my dual role as creator and witness created an unacceptable conflict.

For once, the argument contained a legitimate problem.

I hated that.

Thorne had exploited technical secrecy.

Now secrecy could not become the excuse for denying him a fair process simply because I knew what the evidence showed.

General Cross wanted to provide a narrow technical summary.

The program office wanted to invoke national-security protections and prevent disclosure of the hidden architecture.

I disagreed.

“If we tell everyone integrity requires review until the review reaches us, Archangel becomes exactly what he said it was.”

“A classified system cannot be opened to defense contractors and outside experts,” the program counsel said.

“I didn’t say open it.”

“What are you proposing?”

“Independent replication.”

We built a sealed test environment containing the relevant logic without operational threat data, current models, or identifying profiles. Thorne’s approved technical expert could examine how the Founder Layer assembled logs, verify that it did not create underlying records, and test whether equivalent inputs produced equivalent preservation.

I recused myself from validation.

That part hurt more than expected.

Another systems team inspected my architecture.

They found two weaknesses.

Neither affected the Thorne evidence.

Both could have.

One audit process relied too heavily on a founding architect’s biometric identity. Another error-handling pathway could theoretically misclassify a corrupted credential chain under rare timing conditions.

Thorne’s attorney seized on the findings.

The headlines inside the defense community practically wrote themselves.

SECRET “RAVEN” SYSTEM CONTAINS FLAWS.

ARCHANGEL CREATOR ADMITS HIDDEN LAYER NOT PERFECT.

For three days, I wanted to explain publicly.

General Cross stopped me.

“You taught everyone else that evidence survives discomfort.”

“I know.”

“Then let it.”

The independent expert testified that the flaws did not generate Thorne’s bank records, messages, copied credentials, changed scenario files, or debrief exports. Those came from separate sources preserved before and during Founder activation.

Archangel had assembled them.

It had not invented them.

The proceeding found Thorne responsible for multiple violations involving unauthorized system access, falsification of official records, safety misconduct, and improper handling of protected data. Separate federal cases involving Vectis continued beyond the military process.

Thorne lost rank and retirement benefits tied to the adverse findings and received a punitive sentence through the military justice process.

There was no satisfying final speech.

He did not apologize.

He did not look at me and suddenly understand Archangel.

His last statement described himself as an aggressive evaluator operating inside an ambiguous innovation environment.

Even consequence became passive grammar.

Afterward, a reporter from a defense publication asked whether I felt vindicated.

“No.”

“Why not?”

“Because the independent review found problems in my system.”

She looked surprised.

“But it confirmed the evidence against Major Thorne.”