The Investigator's Case

Jinx removed the best-looking card from the Threadboard first.

It had everything a dramatic card should have: the Ledgerjack mark, the Far Relay rumor, a sharp red border, and Pixel’s tiny drawing of a shadowy hat that nobody had approved.

She moved it away from the center and onto the side rail.

Pixel made a wounded sound. “That was our most interesting card.”

“That was our loudest card,” Jinx said.

Grimalkin nodded from the map table. “Loud cards are expensive.”

Whiskers looked over the report packet. “We present in an hour.”

Byte dimmed the Threadboard until only verified paths remained bright. The wall looked plainer now. Ledger Lab. Library terminal. Research relay. Project Orchard labels. Public summary mismatches. Caretaker confirmations. Far Relay mark, off to the side with careful wording.

It was less thrilling and much harder to knock down.

The Case Folder Thickens

The Glass Bureau review table was round, transparent, and far too clean.

Ms. Vale sat with the library caretaker, the relay archivist, and two Bureau reviewers. The Script Kitties stood beside a portable version of the Threadboard, which Byte had built with folding panels and enough labeled lights to make Pixel jealous.

Whiskers opened. “This is a record-based case summary. We are not naming a person. We are asking for coordinated preservation, affected-project support, and review of old trust paths.”

Jinx took the next part. She expected her voice to shake. It did not.

“This is what we knew first,” she said, lighting the first card. “A -0.75 mismatch appeared in the Hushline model and then in the Ledger Lab resource board.”

She lit the second card. “This is what changed. The same value repeated under Project Orchard labels. One terminal was warm after hours. Blank print slips appeared. A library endpoint later showed a related public summary.”

She lit the third card. “This is what we ruled out or weakened. Museum kiosk reset: moved to gray. Bad clock: checked and not supported. Project Orchard owner action: not supported by schedule or caretaker notes.”

She lit the fourth card. “This is what remains unknown. Who held the borrowed door. Whether the Ledgerjack mark points to one broker, a copied mark, or a rumor someone wanted us to see. How many old trust paths are still active.”

The room stayed still.

Then one Bureau reviewer leaned forward. “And what does the evidence support?”

Jinx lit the final row.

“Repeated unexplained resource mismatches tied to a project label across connected Grid endpoints, with signs of unauthorized use and a possible brokered relay layer.”

No one spoke for five seconds.

Pixel, who was not supposed to talk, did not talk with visible effort.

Evidence With A Spine

Grimalkin presented the alternate theories. He did not hide them in the back. He made them part of the case.

Late charges explained one event but not the repeated route. Clock error did not survive comparison. Museum reset stayed gray. Project owner action lacked support and risked blaming the wrong students.

The relay archivist tapped the old trust path map. “This gray line should have been removed from active summaries years ago.”

“Was it removed from the system?” Whiskers asked.

The archivist looked tired. “That is what we are going to find out.”

Byte demonstrated the Threadboard’s record order. It did not reveal private student details. It showed who confirmed each public summary, when a card was added, and which claim the card supported.

“The board does not decide,” Byte said. “It keeps us from forgetting what the records actually said.”

One of the reviewers looked at Jinx. “You kept uncertainty in the presentation.”

Jinx braced for criticism.

The reviewer continued. “That made it more useful.”

Jinx almost smiled. Almost.

What The Case Can Say

The action list that came out of the review was not cinematic: preserve related summaries, notify affected project owners, review old trust paths, create a shared evidence channel, check relay records for repeated marks, and assign one Bureau coordinator so the case did not bounce between desks.

Jinx read the list and felt a strange relief. The case had not exploded open. It had become work.

Outside the review room, Pixel finally exhaled. “You removed the cool hat drawing.”

“Yes.”

“The case survived anyway.”

“Somehow.”

Whiskers handed Jinx a copy of the action list. “You made the mystery useful.”

Jinx looked at the paper. “I made it smaller.”

Grimalkin folded the old map. “You made it accurate.”

That was better: less shiny, maybe, but more durable.

The Folder Closes Carefully

Back at the Hideout, Jinx returned the loud Ledgerjack card to the board, but she left it on the side rail.

Pixel added the tiny hat back in pencil, very small and in the corner. Jinx pretended not to see.

The Threadboard glowed with a new label at the top:

CASE ACCEPTED FOR COORDINATED ACTION

For the first time since the -0.75 appeared, Jinx felt the thread loosen in her chest. She had not solved every unknown. She had done something harder: she had shown the city what it could know.

Teaching Tie-In

• Concept: case building.
• Story idea: the strongest case separates known facts, changes, ruled-out theories, and unknowns.
• Key distinction: uncertainty can make a report more trustworthy when it is stated clearly.
• Defensive habit: Jinx presents evidence without overstating it.
• Season thread: the Glass Bureau accepts coordinated action.
• Field Guide habit: Keep evidence before story.

Behind the Signal

Stoll’s public accounts made the defender’s case-building work dramatic. The investigation did not succeed because every unknown vanished at once. It succeeded because records, logs, traces, and careful claims accumulated until other people could see what the evidence showed.

Jinx’s case presentation follows that model. She does not win by sounding certain. She wins by separating known facts, ruled-out theories, open questions, and requested action. The historical lesson is generous to uncertainty: when uncertainty is named honestly, it can make an investigation stronger.