DIRECTORATE-00
“Every system has an origin. The danger begins when its creators disappear.”
Previously in TheCyberThrone Universe
MSDCorp’s investigation began with unexplained authentication anomalies. Rolex and Leo followed the evidence through inherited trust, forgotten credentials, the Boardroom Protocol, and twelve years of altered corporate history.
They discovered BP-01, a hidden identity embedded in executive governance. Then they found Adrian Shaw, who had designed the protocol to preserve evidence of the organization’s decisions.
Episode 11 revealed that someone was rewriting that evidence.
Episode 12 uncovered the missing architect, Mira Voss, and a network of 32 active nodes connected to an older system: the Directorate.
BP-01 was only one part of that system.
Now a new identifier has surfaced.
DIRECTORATE-00.
And someone has sent Leo a message:
We have been waiting for you.
Scene 1 — The Thirteenth Signal
1:31 PM — MSDCorp Boardroom
Thirty-two nodes glowed across the display.
Ethan had mapped their known connections, but none revealed who controlled the network.
Then a thirty-third signal appeared.
NODE 33 — CONNECTION REQUESTED
Destination: DIRECTORATE-00
“Don’t accept it,” Rolex said.
Ethan isolated the request.
It vanished.
A message replaced it.
WE HAVE BEEN WAITING FOR YOU, LEO.
Nobody spoke.
Leo stared at the screen.
“How does it know my name?”
Rolex examined the connection logs.
“It knew where to find us. That doesn’t tell us how much it knows.”
“Can you trace it?”
“Not yet.”
The request had left almost no conventional network evidence. But one detail remained: its cryptographic signature had been created twelve years earlier.
Leo turned toward Ethan.
“Can a request signed twelve years ago be responding to something we did today?”
“Not ordinarily. The signature includes a challenge generated seconds ago. Either the system has a mechanism we don’t understand, or we’re looking at something more sophisticated than a replay.”
Rolex saved the request.
“Whatever Directorate-00 is, it knows we’re investigating.”
Scene 2 — The Missing Root
1:38 PM
Ethan traced the seven containment layers backwards through the original architecture.
Each referenced another component, until the chain ended at an empty field.
ROOT AUTHORITY: UNRESOLVED
Rolex studied the diagram.
“Someone removed the reference.”
“Or designed the system so the reference was never recorded,” Ethan replied.
Leo leaned over the console.
“Can we locate the original component?”
“There’s no server address, no registered domain, and no physical location.”
Rolex considered the possibility.
“Then stop searching for a machine. Search for the earliest record of the decision to create it.”
Ethan opened the historical finance archive.
The first result appeared almost immediately.
PROJECT DIRECTORATE — INITIAL ESTABLISHMENT
Date: Six years before the Aurora Acquisition.
Approving department: Unlisted.
Beneficiary: DIRECTORATE-00.
Victor read the entry twice.
“Someone funded this before Aurora even existed.”
“Which means Aurora didn’t create the Directorate,” Leo said.
Rolex nodded.
“It inherited something that was already there.”
Scene 3 — A Name in the Ledger
1:46 PM
Victor examined the original payment authorization.
The beneficiary field contained no company name. The approval field contained no individual’s name.
Instead, the ledger referred to a standing authorization.
Victor searched the transaction history.
A single signature appeared on the supporting document.
Daniel Mercer.
Leo recognized the name immediately.
Mercer was the retired executive who had helped design the original acquisition trust model. His archived credential had already appeared in their investigation.
“Mercer was involved before Aurora,” Leo said.
Serena examined the record.
“His signature establishes that he approved this transaction. It doesn’t tell us whether he created the system, understood its full purpose, or later opposed it.”
Rolex looked at the date.
“Then we need his original records, not another interpretation of his signature.”
A new notification appeared.
ARCHIVE-08 — DOCUMENT FOUND
Title: DIRECTORATE-00 — ORIGINAL AUTHORITY CHARTER
Author: Mira Voss.
The file had never appeared in the archive’s index.
Its first page contained a handwritten note:
The existence of a trusted system does not prove that its origin can be trusted.
The final paragraph was obscured by a physical redaction.
Only the beginning remained visible:
The original authority was established by…
Scene 4 — The Call
2:03 PM
Leo’s phone rang.
Unknown number.
“Leo.”
A woman’s voice answered.
“You’re looking for Directorate-00.”
“Who is this?”
“Someone who knows what happened on September 14.”
Leo signalled Rolex, who began tracing the call.
“Are you Mira Voss?”
“No.”
The answer came too quickly to reassure him.
“Then how do you know about Archive-08?”
“Because I helped build the part they couldn’t erase.”
“Where is Mira?”
“I don’t know.”
“Is Adrian Shaw alive?”
A pause.
“You’re still asking about people.”
Leo’s expression hardened.
“What should I be asking about?”
“The decision.”
“What decision?”
“The one that created Directorate-00.”
The line disconnected.
Rolex checked the trace.
“The call passed through two of the thirty-two known nodes. The source is concealed.”
“Can you identify the caller?”
“Not from this trace alone.”
A new file appeared on the console.
BOX_00_INVENTORY.pdf
Rolex opened it.
One item was marked as retained:
Item 007 — Original Authority Charter
Its last recorded location was not a data centre or an archive facility.
It was MSDCorp’s own Office of the Executive Secretary.
Scene 5 — The Forgotten Room
2:17 PM — Executive Records
The Executive Secretary searched the digital catalogue.
No result.
“The original records room was converted during a renovation,” she explained. “Everything was supposedly digitized.”
Rolex studied the renovation plan.
One narrow section behind a meeting-room wall was labelled:
ARCHIVE TRANSFER — TEMPORARY
The notation dated back twelve years.
Ethan examined the floor plan.
“There’s a sealed service space behind this wall.”
They opened the maintenance panel.
Inside stood a small steel cabinet.
The seal had been broken and carefully replaced.
Serena photographed the cabinet before opening it.
Inside was a folder marked:
DIRECTORATE-00 — ORIGINAL AUTHORITY CHARTER
The document contained four numbered pages.
Only three remained.
The surviving pages described the system’s original purpose: coordinating continuity across participating organizations during major operational disruptions.
There was no defined termination date.
The missing fourth page was listed in the index as:
SCHEDULE D — FOUNDING SIGNATORIES AND REVOCATION
Serena looked at the index.
“Without this page, we can’t establish who held the original authority or how it could be terminated.”
Rolex examined the document’s physical condition.
“Someone opened this folder before us.”
Leo looked at the broken seal.
“And knew exactly which page to take.”
Scene 6 — Mercer’s Signature
2:31 PM
Three signatures appeared on the surviving charter.
Two were unfamiliar.
The third belonged to Daniel Mercer.
Victor stared at it.
“He’s connected to every stage of this investigation.”
“Connected isn’t the same as responsible,” Serena replied.
Rolex inspected the handwritten notes beneath the signatures.
One line had been added in a different ink:
Revocation must remain possible, even when continuity demands otherwise.
The initials beneath it were unmistakable.
D. Mercer
Leo read the sentence again.
“Mercer may have wanted the system to be reversible.”
“Or he may have wanted a record showing that he objected,” Serena said. “We need the missing schedule before we can draw a conclusion.”
Ethan searched the archive for references to Schedule D.
A restricted record appeared.
STATUS: WITHHELD
Reason: Executive privilege.
The authorization field contained one designation:
DIRECTORATE-00
Rolex leaned back.
“The missing page was withheld by the very system it describes.”
Then another alert appeared.
SCHEDULE D ACCESS REQUEST
Requester: DANIEL MERCER
Status: APPROVED
Timestamp: Current.
Victor went pale.
“Mercer is accessing the archive?”
Rolex checked the authentication record.
“The request used a credential associated with Mercer. That doesn’t prove Mercer made it.”
Leo looked at the screen.
“Can we stop the access?”
Ethan began isolating the request.
“Not without risking the remaining archive.”
“Then preserve what we have. Don’t let this request overwrite anything.”
Scene 7 — The Termination Custodian
2:39 PM
The archive began printing a document automatically.
No title.
No sender.
Only a short message:
If you want to find the person who created Directorate-00, stop looking for its founder.
A second line appeared.
Find the person who was supposed to destroy it.
Rolex searched the original charter for references to termination.
The result was immediate.
TERMINATION CUSTODIAN: A-07
Mira Voss.
The room fell silent.
Mira had not merely designed part of the architecture. She had been assigned responsibility for ending the system if it crossed a defined boundary.
The missing Schedule D likely contained the conditions under which she could act.
Leo looked at the screen.
“Twelve years ago, Mira was erased. Now someone is using Mercer’s identity to access the one document that explains how the system could be shut down.”
Rolex nodded.
“And the person who contacted us knew where the document was.”
“Can you identify the source of the printed message?”
“No. But I can preserve the printer logs and the archive events that preceded it.”
Leo looked toward the sealed cabinet.
“Then we have three leads: Mercer, Mira, and Schedule D.”
He paused.
“We pursue the one most likely to disappear next.”
Scene 8 — The Choice
2:45 PM
Ethan’s console sounded.
The archive access request had changed status.
SCHEDULE D — ACCESS IN PROGRESS
The destination was no longer the original archive.
It was an external node.
NODE 17
Rolex began capturing the transfer metadata.
“Someone is moving the missing schedule.”
“Can you retrieve it?” Leo asked.
“I can attempt to preserve the transfer and identify its destination. But if we intervene too early, we may lose the only trail we’ve found.”
Serena looked at the charter.
“If that document contains the revocation conditions, we need it intact.”
Victor glanced at the clock.
“And if Mercer really is involved, waiting could give him time to disappear again.”
Leo turned to Rolex.
“Your call.”
Rolex had seconds to choose.
Your investigation
A — Follow Schedule D
Track the transfer to Node 17. It may reveal who currently holds the missing document.
B — Find Daniel Mercer
Determine whether he is accessing the archive himself or whether someone has stolen his identity.
C — Find Mira Voss
Locate the person named as termination custodian before the Directorate can reach her.
Each choice could uncover a different part of the truth. Each could also warn the person trying to keep it hidden.
What would you choose?
Rolex’s Notebook
Confirmed
- Directorate-00 predates the Aurora Acquisition.
- Daniel Mercer signed the surviving charter.
- Schedule D is missing.
- Mira Voss was designated termination custodian.
- A current request is using Mercer’s archived identity.
- Someone is attempting to move Schedule D to Node 17.
Unresolved
- Who originally established Directorate-00?
- What did Mercer know about its purpose?
- Is Mira still alive?
- Who is using Mercer’s identity?
- What happens if Schedule D reaches Node 17?
Next Episode — Episode 14: The Revocation Clause
The team has found the charter, but not the page that explains how the system can be terminated.
Schedule D is moving.
Mercer’s identity is active again.
And Mira Voss—the person entrusted with ending the Directorate—remains missing.
The next clue is leaving the archive.
CASE STATUS: ACTIVE — GLOBAL
