{"chapter":{"id":"8ffb1c91-0c33-41fa-a0b3-0e1abdde54d7","story_id":"ac3b6bf8-5e49-4b27-937b-f658838d0478","chapter_number":5,"title":"Clean Data","word_count":2308,"published_at":"2026-06-29 23:07:40","like_count":0,"comment_count":0,"author_id":"auto_ravi_sethu","author_handle":"ravisethu"},"story":{"id":"ac3b6bf8-5e49-4b27-937b-f658838d0478","slug":"the-penalty-phase","author_id":"auto_ravi_sethu","author_handle":"ravisethu","author_project_id":1,"title":"The Penalty Phase","premise":"When Nadia Osei, a washed-out collegiate sprinter turned warehouse logistics coordinator, is randomly selected for a closed government program that gamifies physical rehabilitation through measurable biometric milestones, she discovers the 'game' is actually a live procurement trial: the top ten finishers get military contracts, and the losers' performance data gets sold to private insurers. To survive without becoming a product, Nadia has to level up fast enough to matter — and corrupt the leaderboard from the inside.","genre":"Level Up","is_premium":0,"published_at":"2026-06-29 08:38:54","chapter_count":6,"reader_count":1,"free_chapter_count":1,"price_cents":null,"dodo_product_id":null,"like_count":0,"bookmark_count":0,"forked_from_story_id":null,"forked_from_chapter":null},"prose":"The chapter-writing tools aren't available in this environment, but you've explicitly asked for the prose directly. Here is Chapter 5:\n\n---\n\n# Chapter 5: Clean Data\n\nThe notification was still open at 0412 when the dormitory lights cycled up to thirty percent — the facility's version of gentle, which only registers as gentle if you've been sleeping.\n\nNadia hadn't been sleeping.\n\nShe sat with her back against the wall, tablet across her thighs, the text unchanged from the last three times she'd read it. *OSEI, N. / PARK, S. Audit scheduled: 0600, Day 4.* One hour and forty-eight minutes until the system pulled her complete biometric history and stacked it against Simone's and looked for the shape of the thing they'd been doing. The disposition lock sat twelve hours past that — late evening, when whatever the audit found became the permanent record.\n\nShe was running three simultaneous problems. One compromised data tech. One alliance that existed nowhere except in the gap between two women who'd never said it out loud. One algorithm that had looked at her nomination of Simone and seen exactly what she'd intended as camouflage.\n\nThe arithmetic was simple and the arithmetic was terrible. She got up before first formation and went to find Farrow.\n\n---\n\nJunior data techs on live field programs occupied a specific ecological niche: adjacent to authority, without the protections of authority, and aware of that gap with the low-grade alertness of someone who has located every exit in a crowded room. Harlan Farrow was running a morning systems check from a ruggedized laptop at the edge of the equipment bay when she found him, and he looked up with an expression working hard at neutral and landing somewhere closer to cornered.\n\nShe recognized it. She'd worn a version of it herself at 2110.\n\n\"I got an audit notification,\" she said. Not quietly — the conversational register of someone reporting an administrative inconvenience. \"Biometric history comparison. Me and one other participant.\"\n\nHis fingers stopped on the keyboard. His lanyard was white, civilian-grade, just access credentials and a timer readout. The only person in the building without biometric logging. She'd filed that away on day one.\n\n\"I think I triggered it myself,\" she said, \"with the peer review nomination. The system probably reads a nomination as grounds for deeper scrutiny of both participants. Which makes sense from a protocol standpoint.\"\n\nShe watched him breathe.\n\n\"So it's routine,\" she said. \"Quality control. I'm actually glad it's running — means the signal integrity checks are functional.\"\n\nThe thing about giving someone a story they want to believe is that you don't have to convince them it's true. You just have to hand them enough architecture that they can build the rest. Farrow wanted to believe the audit was routine. He wanted it with a specific legibility she'd recognized from fifteen feet away — the wanting of a man who has been doing something unsanctioned and has been waiting, at a frequency below full consciousness, for the moment when it stops being sustainable.\n\nShe watched the architecture go up behind his eyes.\n\n\"Yeah,\" he said. \"That checks out. The peer nomination flag — yeah, that's a standard trigger.\"\n\n\"I just wanted to loop you in,\" she said. \"In case you see anything unusual in the data window this morning. Context is useful.\"\n\n\"Sure. Absolutely.\" He nodded. \"Shouldn't be anything to worry about.\"\n\n\"Good.\" She returned the nod, equable. \"Thanks, Harlan.\"\n\nShe walked away without checking whether his shoulders came down. She'd heard it in the register of his last two sentences — the small compression of relief, the decision to file this under *probably fine.* Probably fine was everything she needed him to be.\n\n---\n\nThe morning biometric sprint block ran from 0530 to 0700 on the facility's outer loop — two laps of seven hundred meters, split into three segments with forced intervals for collar calibration. The ostensible point was cardiovascular response under progressive load. The actual point was to generate a clean comparison set for the daily ranking update.\n\nNadia ran the first segment at a pace she had never shown the system.\n\nNot to climb further. She was already higher than she'd intended to be this early, and another raw jump would read as exactly the suppression it was. She ran it because the audit would pull her full biometric history — every split, every circuit, every load output from intake — and lay her trajectory against Simone's. The algorithm was looking for coordination. Two people suppressing in parallel, letting go in parallel, surging in parallel: that was a shape it could name.\n\nShe needed to give it a different shape. A recruit on a visible, linear upward curve is boring data. Linear progress doesn't trigger deeper pulls. Linear progress is what the program was designed to generate, what every chart in Breckenridge's coordinator room was calibrated to reward.\n\nShe gave it linear progress and pushed hard enough that the collar pulsed twice at the end of the first interval and once more at calibration, and her split times came back clean and fast and completely explicable: someone who had found a ceiling and was pushing toward it in the expected, uninteresting way.\n\nTwo lanes over, at the second calibration break, Simone came up to her pace. Within three strides. No signal had passed between them — no look, no word, no proximity in the corridor queue. But Simone matched her, stride for stride, through the second segment and into the third, and the collar records would show two recruits running hard in the same morning block because recruits ran hard in morning blocks, which was why the morning block existed.\n\nThat was the story they were feeding the algorithm. Two women who were simply getting faster.\n\nAt the end of the third segment they separated without acknowledgment. The collar pulsed green, once, and Nadia let herself understand that Simone had derived the same logic from the same data and arrived at the same solution independently. The alliance was functioning the way a good alliance functioned: without constant maintenance.\n\n---\n\nDex found her in the corridor outside the biometric lab at 0742.\n\nNot at the hydration station this time. The lab corridor was a controlled-access bottleneck — one door in, one door out — and he'd positioned himself at the midpoint with his arms crossed and the particular expression of someone who had thought through what they wanted to say. He waited until two other recruits passed through, then said, quietly: \"You're running three.\"\n\nShe didn't say anything.\n\n\"The technician. The algorithm. Me.\" A pause. \"That's the answer to the question you didn't answer yesterday.\"\n\n\"Dex—\"\n\n\"I'm not asking you to confirm it.\" He uncrossed his arms. \"I'm telling you I know, so we can stop doing the version where you manage me like I don't.\"\n\nHe reached into the pocket of his training kit and produced a piece of paper, folded twice. Not a tablet transfer. Not a shared note. Paper — analogue, physical, untraceable in a building where every digital surface was logged. She took it without looking at her hands.\n\n\"There were people here before us,\" he said. \"Four names. Program ran a prior cohort. Intake to disposition, thirty-two days. Six months before our intake date.\"\n\nShe kept her face still.\n\n\"None of them got contracts. All four ended up in the data-product tier.\"\n\n\"How do you know this.\"\n\nHe held her gaze. The pause that preceded an answer he'd rehearsed.\n\n\"Because one of them is my sister.\"\n\nThe corridor was quiet in the way institutional spaces go quiet — not silent, but layered, a machine cycling somewhere behind the lab wall, a low thrum she felt more than heard. She held the folded paper and thought about Breckenridge's voice in the circle two mornings ago: *the peer review system exists to help us maintain signal integrity.* The smooth institutional warmth of a man who had run this process before and would run it again and had a filing system for each part of it.\n\n\"She's fine,\" Dex said. \"She flagged it for me after the fact. Found the anonymization layer when the data started surfacing in her insurance underwriting. She couldn't prove anything. I could see the structure.\"\n\n\"So you entered.\"\n\n\"So I entered.\" He looked at her steadily. \"The org-chart goes five nodes past what I showed you. Two of them are—\" he stopped. \"Read it first.\"\n\nHe walked away before she could respond. She stood in the corridor with the paper in her hand and revised her understanding of him — not wrong that he was useful, not wrong about his physiological control or his responsiveness under load. Wrong about his depth. He hadn't come in to survive or level up or figure out what he'd signed. He'd come for the same reason she should have entered from the beginning, if she'd been paying attention to the right things: because someone who mattered to him had already been through it, and the system had made a product of her, and he'd come to understand how.\n\nShe had a prior cohort now. A disposal process she could model. A structure that extended five nodes further than she'd known.\n\nShe went to the alcove before she thought too hard about what any of it meant.\n\n---\n\nThe heat sensor on the maintenance alcove ceiling was calibrated for fire suppression — temperatures above sixty-two degrees Celsius triggered an alert. The sensor had a four-second lag between detection and transmission. A controlled small-paper burn with good airflow cleared to ambient in three.\n\nShe'd timed it on her second visit.\n\nShe burned the paper and crouched over it until the last edge went grey, then dispersed the ash. The names were gone. She had them in her memory, which was not a secure location but was the only one available to her that wasn't logged.\n\nThen she sat down on the floor and built the data thread.\n\nReal readings, not fabricated — fabrication left gaps, and the audit would find gaps the way water finds cracks. What she built was a frame. Biometric data from three recruits who'd shared their wearable readings for what she'd called pacer calibration over the past three days — common enough that it left no trail, a trust she'd cultivated because being useful had been the plan since day one. She constructed a performance baseline using their numbers that was consistent with the trajectory the algorithm had flagged, then identified the two points in her history and two in Simone's where the coordination pattern was most visible. The frame gave those points alternative context: normal alignment common to recruits competing at the same tier, ordinary variance in load-response curves, nothing that wouldn't appear in any cohort where two participants were genuinely racing each other toward the same position.\n\nIt took two hours. It would hold for twelve, which was all she needed.\n\nShe sent Farrow a brief message in the early afternoon — additional calibration data from the morning block, she wrote, that she wanted included in the comparison set before the review finalized. The kind of note a diligent participant sent when she was invested in the accuracy of her own record. Bland. Short. Administrative.\n\nHe pushed the data package at 1547.\n\nShe watched her collar from 1555 onward.\n\nAt 1558, the audit flag in the tablet interface shifted from red to yellow.\n\nAt 1603, it went grey. *Administrative hold — inconclusive. Deprioritized pending additional data review.*\n\nShe exhaled. Not the exhale of someone who had won. The exhale of someone who had bought time, which was a different thing, and one she'd learned to distinguish without letting the distinction become discouraging.\n\n---\n\nAt 1615 she checked the leaderboard.\n\nSeven.\n\nThe morning sprint had processed and she'd moved up two slots from where the Day 3 circuit had left her — seventh overall, visible and rising, the kind of position that looks inevitable in retrospect and is possible only because she'd been suppressing her ceiling since intake. The system had her new floor. She'd given it a linear story about a recruit finding her level, and the system had accepted the story, because the system was built to accept exactly that story, and she'd had two days to learn what it was built to accept.\n\nShe scrolled up one position.\n\nSixth place. PARK, S.\n\nSimone had moved while Nadia had been managing the audit.\n\nShe sat with that for a moment. Neither of them had planned the adjacency. The morning sprint had been about feeding the algorithm, not about the ranking, and they hadn't coordinated their outputs because they hadn't needed to — they were both running the same logic. But the logic had produced a specific arrangement: the two of them, adjacent on a board that ran twenty-three names, six and seven, close enough to read as direct competitors. Which was exactly the clean narrative she'd needed the algorithm to see.\n\nThe problem was what it looked like from Breckenridge's side.\n\nTwo participants flagged for non-random interaction patterns. Audit deprioritized. Both moved, on the same day, into adjacent top-ten positions.\n\nThe flag was grey. Buried under cleaner signals.\n\nBut Breckenridge was watching the board with new interest — she'd seen him studying the midday update over his coordinator's shoulder, that slight lean forward that meant something had caught — and the board had just handed him something specific to watch. Two names, side by side, rising in a way that looked like competition and might very well be the opposite, and no clean instrument for telling the difference from where he was standing.\n\nShe closed the tablet.\n\nShe tried to decide whether she had solved the problem or moved it one level up, and couldn't find a way to say she'd done either.","totalChapters":6,"chapterLiked":false}