> ## Content Index > Fetch the complete content index at: https://llitd.com/llms.txt > Use this file to discover other available public pages before exploring further. # Last Light in the Dark Backstory - Lucas - URL: https://llitd.com/last-light-in-the-dark-backstory-lucas/ - Published: 2024-09-10T15:09:54.000Z - Updated: 2026-09-02T16:25:36.000Z - Description: Lucas Reeves is the technician everyone on the KEP-4C crew asks for first — an outer-rim childhood, a distrust of cut corners, a knack for fixing anything. - Author: Lincoln Cole - Tags: Last Light in the Dark Lucas Reeves is thirty-two when he becomes part of the crew that keeps pushing outward after the KEP-4C mission — the technician everyone on the team eventually asks for first, whether the problem is a jammed airlock or a corrupted data core. He is not, by his own account, the bravest person in any given room. He is just usually the one who can fix whatever the room needs fixed before anyone else finishes describing the problem. ## The Outer Rim, a Different Corner of It Like Marcus, Lucas grew up on an agricultural colony on the outer rim — a different settlement, a similar hardship. He was the youngest of three children in a family that measured its year by harvest cycles and equipment failures, and from an early age he was the one who could keep the failing equipment running past the point anyone else had given up on it. He built his first working radio out of a dead irrigation controller and a set of scavenged relay coils when he was eleven, mostly because he wanted to hear something other than the colony's own maintenance channel. He left at eighteen with nothing resembling a plan, which is a more honest way of putting it than any story about ambition. He talked his way onto a supply hauler bound for the core worlds, worked off his passage in the engine room, and discovered somewhere in that transit that ships were the first machines he had ever met that were actually maintained properly. He stayed close to that feeling for the next several years — spaceport repair bays, salvage-yard contract work, the occasional job nobody else wanted because the pay was bad and the wiring was worse. ## The Contracts He Wouldn't Take Lucas eventually landed steadier work with a logistics contractor doing systems support on frontier operations — the unglamorous backbone of exactly the kind of colony survey and recorder work that eventually puts him on Marcus's crew. It was not always clean work. He watched, more than once, contracts cut corners that got people hurt — a corner-cut refit that killed a junior tech on a station he'd worked two years earlier, a safety audit quietly buried because the client didn't want the delay — and it left him with a settled distrust of any organization that talks about safety margins more than it funds them. He started turning down jobs where the paperwork smelled wrong, even when the pay was good, and got a reputation among dispatchers as difficult in exactly the way that meant he was actually paying attention. That distrust is part of why, when the KEP-4C job came through — connected to people he had worked with before, doing recorder and systems support for a routine colony check — he said yes without asking too many questions about the pay grade. A recorder job is, almost by definition, the kind of contract that exists because something already went wrong and somebody wants the truth of it written down. That was a job Lucas could believe in. ## Working Next to the Theorists Lucas is not the crew's scientist, and he would tell you so himself, cheerfully, before anyone else got the chance to. That role belongs to people like Nigel, who thinks in equations and dimensional models. Lucas thinks in wiring diagrams and failure modes. The two kinds of mind turn out to need each other more than either one expects — a theory is only as good as the hardware that can test it, and hardware fails in ways no equation predicts until someone who has actually held the failing part explains why. Lucas becomes, without ever asking for the job, the person who keeps the crew's best ideas from staying purely theoretical. ## Marcus and Lucas Lucas and Marcus do not start the KEP-4C job as friends. Marcus is the mission lead; Lucas is a name on a manifest who has never taken direction well from people who outrank him on paper rather than in the room. That changes inside the first day, when Marcus asks him a technical question instead of giving him an instruction, and listens to the entire answer before deciding what to do with it. It is a small thing. Lucas has worked for a lot of people who never manage it. By the time the crew is deep enough into the mission that rank stops mattering as much as competence, Marcus and Lucas have settled into the kind of working shorthand that usually takes years to build — one that the rest of the series gives them plenty of reason to lean on. ## Who He Is Under Pressure Lucas masks a real fear of failure with a running commentary of dark humor that some of the people around him mistake for not taking things seriously. They are wrong. He takes almost everything seriously; he has just learned that saying so out loud rarely helps anyone get the job done. What he is actually good at, underneath the jokes, is improvisation — finding the unconventional fix when the by-the-book fix is not available, which on the far side of human-occupied space is most of the time. He is fiercely loyal to the people on his own crew, in a way that took most of them longer to notice than it should have, because loyalty from Lucas rarely announces itself. It shows up as the diagnostic he ran at two in the morning that nobody asked for. It shows up as him staying on comms an extra hour so someone else could sleep. He would call this ordinary competence. Everyone who has worked next to him calls it something closer to devotion, even if none of them would use that word to his face. He still has that first radio, or a version of it — he has rebuilt it twice, once after a station fire and once just because he wanted to see if he remembered how. It does not do anything a modern comm unit cannot do better. He keeps it anyway, in a case in his kit that nobody else on the crew is allowed to open, because it is the only object he owns that remembers the version of him before any of the jobs that came after it. Everyone builds a version of that object eventually. Lucas is just more honest than most about what his is and why it still matters. ## Where He's Headed Lucas does not know, when the KEP-4C recorder team boards that moon base, how far this job is about to take him. Rylee, Chelsea, Marcus, Nigel — the crew that forms around that mission keeps going long after any of them expected to stop, and Lucas's technical instincts turn out to matter more, in the books ahead, than any of them could have guessed standing in that airlock. He is, in the end, exactly the kind of person you want holding the wiring together when nothing else in the universe is behaving the way the manual — or anyone's best working theory of it — says it should. --- Check out the first chapter here: [Last Light in the Dark - Episode 1](https://llitd.com/last-light-in-the-dark/) 📖 From the world of Last Light Last Light in the Dark [Read Last Light in the Dark on Amazon →](https://www.amazon.com/dp/B0GTRRL82D?tag=darkcitadel-20&ref=llitd.com)Free with Kindle Unlimited. More from this world: - [Announcing My New Series: Last Light](https://llitd.com/announcing-my-new-series-last-light/) - [Last Light in the Dark Backstory - Marcus](https://llitd.com/last-light-in-the-dark-backstory-marcus/) - [The Last Transmission](https://llitd.com/the-last-transmission/) [Get the next story before the world does — join the Vanguard →](https://llitd.com/vanguard/)