Back at work today.

The holiday was four days ago. Four days of knowing what we know, sitting with it, doing nothing — because doing nothing was the plan, doing nothing was step one, and also because Dev said we needed to let the files exist in our heads for a while before we let them exist anywhere else.

“Grief first,” she said. “Then math.”

I think that’s the most Dev sentence she’s ever said. I wrote it in the journal right after she said it and she read it over my shoulder and said “don’t write that down” and I said “too late.”

So. Grief first.

Here is what I grieved: The math was wrong the whole time. Not because I miscalculated. Not because the system glitched or the algorithm misread something. The math was wrong because somebody made it wrong, on purpose, in a document, and got three signatures on it. I have been blaming my own arithmetic for three months. Every time the balance came up short I thought — I must have missed a break, a drift, a moment where my eyes wandered. I thought the problem was me.

It wasn’t me. The problem has four decimal places and it predates my first day on the Lenses.

That’s what I grieved. And now I’m done grieving it, or I’m trying to be, or I’ve at least put it in the drawer where I keep things I can’t fix yet.

The building is different now that I know what I know.

Not physically different. Same gray carpet, same fluorescent flicker in the east corridor that Facilities has been meaning to fix for six months, same smell of thirty-two people pretending to be alone in a room together. But I keep looking at the displays — the little ambient Yield panels mounted at every workstation, scrolling numbers in green — and thinking: those numbers are a lie. Not an estimate. Not an approximation. A known, configured, pre-approved lie.

I processed 889 reviews today. The system displayed 845.

I wrote it down. I’ve been writing it down since Entry 9, actually — I have a small notebook I bought at the corner store, the kind kids use for math homework, ninety-nine cents, spiral binding. I don’t write the discrepancy on my encrypted file because the encrypted file connects to the same device that runs the Lenses. I write it in the paper notebook. With a pen. Like I’m doing homework for a class that might not exist.

Dev noticed the notebook immediately.

“What is that.”

“A notebook.”

“I can see it’s a notebook. Why do you have a notebook.”

“I’m writing things down.”

She looked at me for a long second. She has this look — I’ve seen it directed at me before — where you can see her deciding whether to be impressed or exasperated. Usually it resolves to both.

“Okay,” she said. “That’s either smart or it’s a liability.”

“It’s a ninety-nine cent notebook.”

“So is your instinct, sometimes.”

Here is the thing about going back to work when you know the thing:

You can feel the system doing it.

Before, the Yield panel was just a number. Green, ticking up, my little counter of time-converted-to-money. I didn’t watch it happen. I watched my screen, did my work, checked the panel at lunch and end of shift. That was the rhythm.

Now I watch it tick. Second by second. The actual numbers — $0.0022 per second, $0.00209 per second, $0.00218 — and I notice the moment they land in my balance. And I notice the moment they don’t.

The skimming doesn’t happen constantly. That’s the thing I didn’t understand from the documentation alone. It’s not a flat deduction. The normalization runs as a rolling function — it’s smoothed out, distributed, spread across hundreds of transactions per hour so no individual discrepancy is ever large enough to flag. The system is specifically designed to make the theft invisible at the transaction level.

You can only see it in aggregate. At the end of the day. When you do the math yourself. By hand. In a ninety-nine cent notebook.

Dev figured this out about an hour before I did. I could tell because she went very still for about three minutes around 2:15, and Dev doesn’t go still.

After shift she said: “It’s not a constant withdrawal. It’s a function.”

“I know. Rolling average normalization.”

“Which means—”

“Which means we can’t prove theft per transaction. We can only prove it across time.”

“Which means documentation.”

“Which means the notebook.”

She looked at the notebook. She looked at me. The exasperated-impressed face again.

“Keep writing,” she said.

I have to tell you something about Dev.

I’ve been writing about her for almost two months now and I’ve made her sound like a system. Like a very competent system that occasionally says funny things. And she is competent — aggressively, almost ostentatiously competent, in a way that can make you feel like you’re watching someone do a trick rather than witnessing a person. She figures things out faster than feels fair. She doesn’t panic. She already knew the answer when you’re still explaining the problem.

But today, around 4:40, twenty minutes before end of shift, she made an error.

Small error. She flagged a batch of posts as “coordinated inauthentic” when they were just — people, different accounts, independently posting about the same local story. Wrong call. Not a catastrophic wrong call, but the kind of thing the algorithm catches on review and kicks back as a correction. Her accuracy score dipped.

She saw it immediately. She stared at the correction notification for maybe four seconds. And then she did something I’ve never seen her do before: she closed her eyes.

Not a blink. Eyes closed, for a full breath.

I didn’t say anything. She opened her eyes and moved on and by the time we logged off her score had recovered and you’d never know it happened.

But I know it happened. And later, at the door, while she was pulling on her jacket — the denim one with the patches — I said: “You okay?”

She said: “I’m tired.”

“Tired how.”

She thought about it. The way Dev thinks about things — not searching for the answer, more like deciding how much of the answer to give.

“I’ve been running this rhythm for four months,” she said. “The pattern. The typing. The keeping my eyes on the right part of the screen for the right number of seconds.” She zipped the jacket. “It works. I know it works. But it’s work. And some days it’s just work and some days it costs something.” She paused. “Today it cost something.”

I almost said something cheerful. I do that — it’s a reflex, the optimism thing, deploying it like a response to a system prompt. I caught it.

“Yeah,” I said instead.

We stood there for a second.

“The notebook is smart,” she said, which is as close as Dev gets to saying I did a good thing.

Then she left. I took the long way home.

Bug was asleep on the journal when I got in — physically on top of the physical notebook, which felt pointed. I moved her. She headbutted my hand in a way that could have been affection or protest, impossible to tell. We have that in common.

I sat with the notebook and looked at today’s numbers.

Processed: 889. Displayed: 845. Discrepancy: 44. Consistent with the 4.83% average I’ve been tracking since I started writing things down.

The normalization coefficient from the files: 0.9517.

4.83% is close to 4.83%. Which is 1 – 0.9517. Which is not a coincidence.

I’m not crazy. I was right. The math was wrong on purpose.

I wrote the number down. I’ve been writing it every day. I’ll keep writing it every day until I have enough days to show someone the line.

A line, Dev said, is not a point. A point is an anomaly. A line is a pattern. A pattern is a fact.

I don’t know what comes after fact yet. I’m still building the line.

Mom called on Sunday. I missed it — I was offline, deliberately, in the way you have to be deliberate about being offline now. She left a voicemail, which she still does even though nobody does that anymore. “Just checking in, kiddo. I finished the images for the week and they gave me Saturday afternoon off for meeting my quota. I sat by the east window. There was a good light.” She paused. “Call me when you can. Love you. Bring Bug sometime.”

I’ll call tomorrow.

I’ll tell her the light is still there.

— M.