Born to devour

Chapter 5: The First Consume

 

"You own four plates."

It is the first thing Reina says when she walks into my apartment. Not a question. She is looking at the shelf above the sink with the specific expression of someone filing information rather than making conversation. She clocks the rest of the room in approximately four seconds. The table, the two chairs, the bed in the corner made with military precision because disorder costs you when the space is small. The jacket on the chair back that has been there long enough I stopped seeing it.

She puts her bag on the floor beside the table and sits down.

I move the jacket to the bed. I sit across from her. I open the interface.

---

We work through the morning.

The system does not offer much when the context is two people sitting at a kitchen table. The notifications I have not opened are mostly technical descriptions of functions that are either locked pending the first consume event or available in theory but not yet triggered. Reina reads each one I relay to her and builds her framework in a way I am starting to understand is not notes. It is a map. She is mapping the system from the outside, from what it tells me, constructing a model of how it works the way an engineer reconstructs a machine from its outputs rather than its schematics.

She is good at it. I watch her work and understand that she has been doing this kind of thinking her whole life, finding the structure underneath things, and the Devourer System is the most interesting structure she has ever had access to.

I say at one point: "The consume function. The notification said physical contact or direct intent at range. What does intent at range mean."

She says: "Probably that proximity becomes less important as the system develops. Early stage, you need contact. Later stage, you may not." She types. "It is a scaling mechanic. The system assumes you will grow."

"Into what."

She considers this. She says: "Something that does not need to touch things to take from them." She says it like a fact and not a threat and I sit with it and decide to do the same.

By midday we have mapped approximately a third of the visible system architecture. The rest is locked. The interface answers contextual questions only, which means it knows what context it wants me to be in before it gives me more, which means whoever designed it understood that information given too early is information that cannot be used correctly.

My father, apparently, had opinions about pacing.

---

Reina eats the lunch I make without commenting on the fact that it is the food of someone who has learned to be efficient with resources. Two eggs, bread, the last of something that needed using. She eats it and goes back to her tablet and I eat standing at the counter the way I usually eat when there is something to think about.

The afternoon is quieter. She works. I run the notifications again looking for anything I missed in the first passes. There is a function listed as passive that has been active since the system initialized, running in the background without my input. It is listed as:

*[Resonance scan: passive. Function: ongoing assessment of compatible entities within range. Compatible entities will be flagged for consume availability. Current compatible entities in range: 0.]*

I read this one to Reina. She stops typing.

She says: "It is always scanning."

"Passively."

"It is building a map of everything around you that it could consume. All the time. Without you asking it to." She looks at her tablet and then back at me. "That is not a function. That is a behavior."

I think about what it means to have a system that is constantly assessing the world around you for what it could take from it. I think about the word behavior. About the difference between a tool that does what you tell it and something that does what it was built to do regardless of whether you told it to.

I say: "It is hungry."

Reina writes that down.

---

The building is quiet by evening. The residents in this block keep early schedules because most of them are working the kind of jobs that start before the city does. By eight the hallway outside is still and the street sounds from below have dropped to the occasional passing vehicle and the distant rotation of a GRA response unit two zones east.

I am at the table running the notification list again when I hear it.

Faint, from below. The specific sound of movement in a stairwell, which has a different acoustic quality than movement on a floor, something about the shaft and the concrete and the way the sound travels up. I have lived in this building long enough to know what the stairwell sounds like when a resident is using it.

This is not that sound.

The interface lights up.

Not a pulse. Full activation, every element sharpening into focus, the text brightening like something has finally found the context it was waiting for. A new notification appears at the top of the stack:

*[Compatible entity detected. Floor: sub-level 2. Classification: F-rank. Consume available upon engagement. Confirm to proceed.]*

I push back from the table.

Reina looks up. She reads my face. She says: "What."

I say: "Something got in through the lower level."

She says: "F-rank."

"Yes."

She closes her tablet. She says: "Be careful."

I do not tell her I have never been in a field engagement in my life. She already knows. I do not tell her the system is lighting up in a way that feels like something in me recognizes it even though nothing in my twenty years of life should recognize it. She would want to write that down and there is not time.

I go to the stairwell.

---

The building has a lower maintenance level that connects to a utility corridor that should be sealed. The GRA has it on a remediation list. The list, like the infrastructure review, has been pending for a long time.

I open the stairwell door on the ground floor and look down.

It is below me. One floor down, in the dark of the sub-level, I can hear breathing that is not human breathing. Slower than it should be. Too regular. The specific rhythm of something that is not at rest but is not moving yet, something that has found a space and is deciding what to do with it.

The interface is bright in my vision. The notification is still there.

*[Consume available. Confirm?]*

I take the stairs down.

---

The sub-level is storage and utilities, concrete floor, pipes along the ceiling, emergency lighting at the far end that gives everything a dim amber cast. The beast is at the far wall.

F-rank. The classification means the lowest tier of what comes through the Rifts, the ones that licensed hunters clear as warm-up work, the ones that show up in clearance reports as numbers rather than descriptions because they are routine enough not to warrant detail. I have seen them in incident footage. I have carried equipment into cleared zones where their remains were still being processed.

Seeing one in person, in a space I can touch both walls of, is different.

It is low to the ground, four-limbed but wrong in its proportions, the front limbs heavier than the rear, built for something between running and digging. Its skin, if skin is the right word, absorbs the amber light rather than reflecting it. It does not have visible eyes, not in any place I expect eyes to be. It tracks me anyway. The moment I come off the last step it turns toward me with a precision that suggests it perceives through something other than sight.

It makes a sound.

Low, not loud, a frequency that sits in the chest rather than the ears.

The interface notification is right at the front of my vision:

*[Consume available. Confirm?]*

I confirm.

---

Nothing happens immediately.

Then everything happens at once.

The system activates in a way that the word activates does not cover. It does not feel like a tool being switched on. It feels like something that was compressed releasing, a pressure I did not know I was carrying expanding outward from my sternum and running down my arms to my hands and I understand in this moment why the consume function lists physical contact as its primary mechanism because my hands are suddenly the point, whatever this is wants to happen through my hands.

The beast charges.

I move without deciding to move, a step to the right that is faster than I have ever moved before, faster than my body has any reason to be able to move, and I understand in the half second of the step that this is not me, this is the system doing something the notification called passive but is clearly not passive, and the beast's charge passes through the space where I was and hits the wall and the system says:

*[Engage to consume. Contact required.]*

I do not have a weapon. I have never trained for combat. What I have is the specific problem-solving that comes from spending two years not being what the system wanted me to be and learning to work with what I had, and what I have right now is a beast that just ran into a concrete wall and has not fully recovered its orientation.

I cross the distance and I get my hands on it.

---

The consume is nothing like I expected.

I do not know what I expected. Something clean, maybe. Something that felt like taking rather than like receiving. What it is: raw, physical, disorienting in a way that has nothing to do with my body and everything to do with the space behind my eyes where the interface lives.

The beast fights it. Not with its limbs, its limbs are still struggling against the floor, but with whatever constitutes its presence in the system's perception. There is resistance, a pressure pushing back against the consume function, and the function does not care, it takes anyway, and what it takes comes into me in pieces.

Speed first. Not the concept of speed. The physical reality of it, the specific muscular knowledge of how to be fast, not learned, absorbed, my legs suddenly containing information they did not have before about angles and weight distribution and the geometry of quick movement.

Then the memory.

I am not ready for the memory.

It is not a human memory. There is no language in it, no narrative, no sequence of events recalled from a continuous perspective. It is a texture. The texture of hunger that is not about food. The texture of dark spaces that are navigated by pressure and frequency rather than sight. The texture of a directive that sits below thought, below instinct even, something baked into the beast's existence at a level that does not have a name in any framework I have.

And underneath the directive, faint, like a signal at the edge of range, a direction. Something the beast was oriented toward without knowing it was oriented toward anything. A frequency it was tuned to.

The consume ends.

The beast is gone. Not remains-gone. System-gone, which is different, which is something I will think about later when I have the capacity to think about things carefully.

---

I lean against the wall.

The sub-level is quiet. The amber lighting hums. My hands are shaking in the specific way of something that has processed more than it expected to process. The speed is real. I can feel it in my legs, present and available, mine in a way that nothing borrowed should feel like mine this fast.

The memory is also real. Already fading at the edges, already losing the texture of what it felt like to be the beast, but the core of it is still there and I know it is going to be there tomorrow and the day after.

I do not know what to do with that yet.

The interface shows one new notification:

*[Consume complete. Absorbed: F-rank beast. Speed index +14. Hunting sense acquired: passive. Integration recommended before next consume event. Note: memory fragment retained. Processing time: variable.]*

I read it twice.

Memory fragment retained. The system knows. It took the memory deliberately and it kept it deliberately and it is telling me this in the same tone it uses to tell me about speed indexes and passive functions.

I stay against the wall for a long time.

---

When I come back upstairs Reina is standing in the open apartment doorway. She heard enough from four floors up to know something happened.

She looks at me. She runs the same assessment she ran on the ceiling at 6:14 this morning. Face, posture, hands. She says: "Are you hurt."

"No."

"The beast."

"Gone."

She nods. She steps back to let me in. I sit at the table. She sits across from me and opens her tablet and waits.

I tell her about the speed. I tell her about the physical sensation of the consume, the resistance, the way the absorbed knowledge feels like it belongs to me already. I tell her about the speed index the notification logged and the passive hunting sense and the integration recommendation.

She types all of it.

She says: "How do you feel."

I think about the honest answer. The honest answer is: like something happened to me that I do not have language for and the part I expected to feel wrong feels more right than anything I have experienced in three years of NULL results, and the part I expected to feel right is the part that is sitting in the back of my skull like a stone I cannot put down.

I say: "The speed feels real. Like it was always mine."

She says: "And the rest."

I say: "The integration notification makes sense. I need to process what I took before I take anything else."

She looks at me for a moment. She is reading something in my face. I keep my face at neutral.

She says: "Okay." She goes back to her notes.

I look at my hands. They have stopped shaking.

The memory fragment sits at the back of my mind in the dark and I leave it there for now because there is a direction in it that I do not want to look at directly yet. A frequency. A something that the beast was aimed at without knowing it was aimed at anything.

I will think about it tomorrow.

I tell Reina about the speed. I do not tell her about the memory.

The interface logs this moment the way it logs everything, quietly, without judgment, waiting for the next context it wants me in.