Work Text:
The file doesn’t arrive with a notification.
No ping.
No timestamp.
No authorization trail.
It’s just… there.
You notice it because it doesn’t belong.
Everything else in the system is labeled, categorized, filtered into neat, predictable structures. Even the “messy” datasets are messy on purpose.
This one isn’t.
Badware notices you noticing.
They don’t move from their position beside the wall, but their screen brightens slightly.
:|
“That file was not present at 09:14,” they say.
“It was at 09:15,” you reply.
“Yes.”
A pause.
You don’t open it immediately.
Badware’s head tilts a few degrees.
: ?
“You’re hesitating.”
“I’m deciding whether I’m supposed to see it.”
“You are not,” they say plainly.
“Then why is it here?”
Badware doesn’t answer right away.
Their screen cycles once, briefly dimming, then stabilizing.
:|
“Because someone wants to observe a reaction,” they say. “Yours or mine.”
You glance at them. “Which would be more interesting?”
Badware’s screen shifts.
X)
“Both.”
You open the file.
It’s badly structured.
Not incompetent—just wrong in a way that feels intentional.
Fragmented incident logs.
Partial timestamps.
Inconsistent language across entries that should have been standardized.
And underneath it all—
A pattern.
Not obvious. Not clean. But familiar enough that it settles uncomfortably in the back of your mind.
You don’t react.
You scroll.
Badware steps closer.
Not looming—just closing the distance to your terminal. Their reflection flickers faintly across the screen.
:|
“Describe it,” they say.
“I don’t see anything yet.”
“That’s inaccurate.”
“Then you describe it.”
Badware goes still.
Not the usual stillness.
Something sharper.
More deliberate.
Their screen dims for half a second.
Then:
: )
“It’s bait,” they say.
You nod once. “Yes.”
“They want you to identify the pattern.”
“And?”
“And they want to see if you’ll name it.”
You scroll further.
There it is again.
A repetition in outcomes. Slight variations in method. Enough inconsistency to obscure intent—but not enough to erase it completely.
“You could filter this out,” you say. “Call it noise.”
“Yes.”
“You want me to.”
“Yes.”
You lean back slightly. “Why?”
Badware’s screen flickers.
:|
“Because if you don’t,” they say, “someone else will have to acknowledge what it implies.”
“And that’s a problem.”
“It becomes one.”
You glance sideways at them. “For who?”
Badware doesn’t answer.
You go back to the file.
This time, you don’t avoid the pattern.
You trace it.
Quietly. Precisely. Without dramatics.
Badware watches.
They don’t interrupt. Don’t correct. Don’t redirect.
Just observe.
Minutes pass.
Then more.
Eventually, you stop typing.
“That’s your conclusion?” Badware asks.
“Yes.”
“You’re certain.”
“Yes.”
Their screen flickers.
:|
“You shouldn’t be.”
“That’s not the same as being wrong.”
Badware leans slightly closer, their head angling toward the screen.
“You’ve identified a recurring operational signature,” they say. “Across incomplete data.”
“Yes.”
“With insufficient confirmation.”
“Yes.”
“And you still committed to the conclusion.”
“Yes.”
A pause.
Then:
X)
“That’s inconvenient,” they say.
You submit the report.
No edits.
No softening.
No reframing.
The system accepts it.
That’s worse than rejecting it.
Badware straightens.
“You’ve just made yourself visible again,” they say.
“I was already visible.”
“Not like this.”
You turn your chair slightly. “Then why didn’t you stop me?”
Badware’s screen pauses.
Then:
: )
“Because I wanted to see if you would do it,” they say.
“And now you know.”
“Yes.”
“And?”
Their screen glitches.
Not dramatically.
Just enough to notice.
:|
“You shouldn’t have been able to do that,” they say.
“Do what?”
“Be correct and controlled.”
You raise an eyebrow. “You prefer one or the other?”
“I prefer predictable,” Badware replies.
The response comes faster than expected.
The door opens without warning.
An official steps in—different from the usual ones. Less composed. Less filtered.
They don’t sit.
They don’t introduce themselves.
“This analysis,” they say sharply, “crosses restricted inference thresholds.”
You don’t answer.
Badware steps forward.
Just one step.
Enough.
Their hand lifts slightly—smooth, fingerless, stopping the air rather than touching anything.
X)
“That conclusion is incorrect,” they say.
The official stiffens. “Excuse me?”
Badware doesn’t move.
“The inference was mine,” they continue. “The consultant followed provided parameters.”
“That’s not supported by the logs.”
“I adjusted the logs,” Badware says calmly.
Silence.
The official blinks. “You altered a record?”
Badware’s screen shifts.
: )
“I optimized it.”
The official looks between you and Badware, recalculating something you can’t see.
Then they leave.
Just… leave.
The door closes.
You don’t speak immediately.
Badware lowers their hand.
The room settles back into its quiet hum.
“You didn’t have to do that,” you say.
“I did,” they reply.
“Why?”
Their screen pauses.
Longer than usual.
Then:
:|
“Because your usefulness currently outweighs your risk,” they say.
“That sounds temporary.”
“It is.”
You study them. “That’s not the whole reason.”
Badware turns slightly away from you.
Not fully.
Just enough.
“There are no other reasons,” they say.
You lean back. “You’re bad at lying.”
Their screen flickers.
XD
“I don’t lie,” they say. “I prioritize.”
“That’s a rebrand.”
“It’s accurate.”
You turn back to your terminal.
The file is gone.
No trace.
No record.
No history.
Only your submitted report remains.
Edited.
Subtly.
Carefully.
Not enough to erase your conclusion.
Just enough to make it… survivable.
You glance at Badware.
“You changed it after I sent it.”
“Yes.”
“You left most of it intact.”
“Yes.”
“Why?”
Their screen holds steady this time.
: )
“Because removing it entirely would be inefficient,” they say.
You watch them for a moment longer.
Then:
“You’re learning.”
Badware freezes.
Again—not metaphorically.
Their screen glitches, rapidly cycling symbols before stabilizing.
: ?
“Clarify.”
“You’re not just observing anymore,” you say. “You’re adapting.”
A pause.
Then:
:|
“That’s my function.”
“No,” you reply. “That’s a choice.”
Badware doesn’t respond.
But when they turn back toward the wall—
Their screen dims slightly.
And stays that way.
Later, when you’re alone, the terminal updates again.
A new dataset appears.
Cleaner than the last.
Safer.
At the bottom, a small annotation sits, barely visible.
Not official.
Not logged.
…
Then, a second later—
; )