Can Voss
Overview
Can Voss serves as Cryptologic Technician and Data Recovery Specialist aboard the ICS Valkyrie, where he is the sole qualified operator of the ship’s custom-built quantum memory core diagnostic suite. He is responsible for maintaining the vessel’s communication arrays, decrypting encoded transmissions, and recovering usable data from damaged, corrupted, or intentionally fragmented storage systems. On a ship that depends on intercepted signals and salvaged intelligence, Voss’s ability to extract meaning from noise makes him indispensable.
His expertise is narrow but profound: he hears data degradation before sensors register it, recognizes encryption patterns by their rhythm, and treats even the most hopelessly scrambled file as a puzzle with a solution waiting to be found. That obsessive drive exacts a personal toll, and Voss often loses himself so completely in technical problems that he forgets the human stakes surrounding them, but the crew of the Valkyrie has learned that when the core lights fail and the logs go dark, Voss is the one they need in the seat.
Background
Born on Tycho Station during its peak as a lunar shipbuilding hub, Voss grew up in a world of torque specs and pressure-hull integrity reports. His parents, both engineers, recognized his pathological gift for pattern recognition early — by seven he could diagnose faulty life-support cycles by ear, and at twelve he cracked the station’s inventory encryption because the data patterns “smelled wrong.” An apprenticeship with the Tycho Data Guild, a semi-official collective of cryptographers and forensic archivists, honed that raw talent into a discipline. Under the tutelage of veteran archivist Dima Reyes, Voss mastered the art of partial decryption, learning to pull readable fragments from media that other technicians would have written off as total losses.
When the station’s economy contracted in his early twenties, Voss signed a contract with the Terran Mining Consortium and shipped out to the Belt. TMC wasted his cryptographic skills on routine equipment telemetry and manual labor, a poor fit that ended abruptly after Voss accessed a restricted data cache and uncovered evidence his superiors wanted buried. The incident earned him a quiet transfer and a succession of remote postings, his talent undervalued and his file marked as a liability. He eventually drifted onto the ICS Valkyrie roster, where Captain Cade Brennan recognized his worth and gave him the latitude to build the ship’s diagnostic suite from salvaged components. For the first time in years, Voss found himself in a place that valued what he actually was.
Physical Description
Voss looks like a man who has spent his adult life hunched over diagnostic consoles in cramped shipboard compartments. He is short by Belt standards, compact, with rounded shoulders and a forward-thrust neck shaped by years of screen glare and tight avionics bays. His build is soft at the middle but wiry in the arms — the result of alternating between marathon data-sifting sessions and the occasional frantic EVA to recalibrate a relay array by hand.
His round face is pale and perpetually flushed, with a high forehead made higher by a slowly retreating hairline cropped to a practical fuzz. Broken capillaries trace the wings of his nose, souvenirs of Tycho Station homebrew and old pressure-differential headaches. His pale blue eyes are constantly in motion, flicking across readouts even at rest, and they narrow to warning slits when he is deep in a problem and about to deliver information his crewmates will not fully understand. He wears wire-rimmed optical assist frames with a hairline crack in the left lens that he insists “aligns the focal plane better than factory spec.”
His hands tell a dual story: fingertips callused from haptic interface work, palms carrying older scars from shipyard days — a plasma-cutter burn across the right palm, a crescent divot near the left thumb from a misaligned cargo clamp. When thinking, he taps his right index finger against his thigh in irregular, staccato rhythms that sometimes resolve into recognizable codes, though he is never aware of doing it. He dresses in a faded blue multi-pocket ship-jacket (sixteen pockets, each with a designated tool, data chip, or snack bar), thermal greys, and cargo trousers held up by a belt with a buckle fashioned from a decommissioned gyroscope bearing — a gift from his long-dead mentor.
Personality
Voss is obsessively methodical. He treats every data corruption as a lock waiting to be picked, and he cannot accept the idea that any information is permanently lost — only that the correct retrieval pattern has not yet been discovered. He will work through multiple sleep cycles without noticing, sustained by shipboard coffee and the conviction that the next iteration will succeed.
He is compulsively explanatory. When he finds a pattern or a solution, he needs the listener to understand it exactly as he does, a drive that overrides social awareness. He will launch into a forty-minute lecture on hash-chain protocols while his captain is bleeding, not from callousness but from genuine belief that the information will help. The ship-wide shorthand for cutting him off — “Voss. Headline.” — has become a necessary ritual.
Voss compartmentalizes emotion with the same efficiency he applies to extraneous data. He is not cold, but he refuses to let fear or grief occupy processing cycles that could be devoted to the work. This survival mechanism makes him appear detached in moments of crisis, though those who know him recognize it as a carefully maintained defense. Beneath the technical surface, he holds a quiet, unspoken principle: information wants to be whole, and burying truth is a kind of violence. He never articulates this philosophy — it sounds too much like the Guild mysticism he outwardly mocks — but it governs his choices.
Fifteen years of being shuffled from post to post by corporate managers who saw him as a liability have left Voss with a reflexive distrust of authority. He follows Cade Brennan’s orders without question, but that loyalty is personal, not institutional. Outside the Valkyrie crew, he assumes every authority figure is hiding something, and he is usually correct.
Relationships
Cade Brennan. Voss regards Cade with a respect that borders on devotion. Cade is the first commanding officer who valued his skills instead of trying to bury them, and Voss repays that with absolute loyalty. Their conversations are brief, technical, and freighted with mutual understanding: both men spent too long serving systems that didn’t deserve them. Voss delivers bad news without sugarcoating, trusting Cade to handle reality without flinching.
Tobias Kinnas. Sharing the comms station has forged an alliance that is part collegial expertise, part sibling rivalry. Tobias is a decade younger and carries an idealism Voss finds simultaneously irritating and endearing. They bicker constantly about methodology — speed versus thoroughness — but the arguments mask genuine affection. Tobias is the only person on the ship who can make Voss laugh, usually by saying something so absurdly optimistic that Voss’s cynicism collapses.
Mira Castell. Voss and the ship’s medic share a mutual wariness that never resolves into friendship or open conflict. Mira regards his work habits as a health hazard and has sedated him twice when he refused to sleep, which Voss resents but respects in principle. They communicate in clipped, efficient exchanges and otherwise orbit separate spheres of expertise.
Seren Varga. The pilot’s economy of speech and Voss’s preference for minimal social interaction suit each other well. Their working relationship consists of terse system checks and quiet confirmations. Voss knows Seren carries a discharged past that the crew whispers about, but he never pries. Her secrets are her own, and Voss, who has secrets of his own, considers that a form of respect.
Djen Li. Before recent events, Voss and the young crewman shared a quiet, intermittent camaraderie. Djen was eager to learn, and Voss — who rarely got to teach — found unexpected satisfaction in explaining the ship’s data architecture to someone who actually listened. Their bond ran deeper than either acknowledged aloud.
Speech Pattern
Voss speaks in complete, grammatically precise sentences that often run longer than the situation warrants. His default mode is the lecture, and he struggles to condense technical information without visible effort. When interrupted, he pauses, blinks twice, and restarts from the beginning with slightly simpler vocabulary, as though downgrading a transmission protocol. His humor is dry to the point of desiccation; crewmates sometimes realize he made a joke thirty seconds after he has left the room.
His speech is marked by the starter-phrase “Right, so,” drawn out while he organizes his thoughts. When processing new information, he murmurs “mm” in a rising-falling tone that signals he is slotting the data into his mental architecture. Under stress, he retreats into technical jargon that only he understands, a verbal haven where he feels fully in control. He never swears — not from prudishness, but because profanity is imprecise, and imprecision offends him.
An exchange in the comms station might sound like this, when a crewmate interrupts him mid-explanation:
“No — no, you’re not — if you’ll let me finish the sentence, the signal degradation isn’t just random noise, it’s a patterned interference cycle with a specific phase variance that — what? Sorry. Right. Simpler. It’s like a heartbeat in the static. If we find the rhythm, we can filter it out. That’s what I was trying to tell you.”