Rinzler / Tron (
notglitching) wrote in
thisavrou_log2016-04-13 08:09 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
You can never say that I didn't try
Who: Rinzler and OPEN
When: April 14th through the 24th
Where: the Hold
What: Rinzler killed some people and copes poorly. Set after this log.
Warnings: references to character death and mindscrew, glowy injuries, unfortunate assumptions. (See also: Rinzler.)
The first place Rinzler woke up in this system was a cell. He'd been locked in after a fight with his duplicate—with Tron. Not that the enforcer had been capable then of even hearing the older version's name. Rinzler had attacked because he had to, because the overrides built in his mind detected conflict and demanded he delete the source. Since then, he's shattered that if/then chain. Chipped away at the filters on his memories, even managed, once or twice, to speak.
But he's back where he started, and he knows better than to expect things to end the same way.
For the most part, visitors will find Rinzler seated on the low bench back against the wall. Circuits burn dimly in the shadows, almost outshone by the dull glint of fractured code that covers a full half of the enforcer's core. He's turned slightly to conceal the injured side, but the spiderwebbing cracks through code and armor are obvious to see, and he doesn't have the power to refresh his shell and cover up the damage.
The low rattle of corrupted code echoes through the cell and down the corridor, though it does nothing to compete with the invectives from the user locked in one door down. Rinzler approaches shutdown just once, curled up against the wall, and if the flickering lights and twitch of limbs is any sign, it's anything but restful. The program won't notice anyone approaching then, but he probably wouldn't mind being woken.
Once or twice, Rinzler rises, pacing, frustration and the need to move boiling up through the despair. There's nowhere to go, though, nothing to do, and even that much risks opening his damage further. Maybe he should. Fracture, break, rip himself apart and leave them voxels on the floor to claim and punish. Rinzler wonders if he ever tried before. If he does, he can't remember. He wonders what they'll make him into. Alan-one had told him what would happen, told him he'd correct the fault if Rinzler fought again. Now two users are dead, and if there's any hope at all, it's that they'll decide he's too worthless to salvage.
[[ooc:the duration during which Rinzler can be visited depends largely on the results of his trial, so there may be some time-wobbling. In particular, if he ends up with solitary confinement... no longer applicable; Rinzler will be visitable for both the trial period and his sentence. ETA 2: As of the 20th, temperature conditions will be improved thanks to Vision + co.
Prose and spam both welcome!]]
When: April 14th through the 24th
Where: the Hold
What: Rinzler killed some people and copes poorly. Set after this log.
Warnings: references to character death and mindscrew, glowy injuries, unfortunate assumptions. (See also: Rinzler.)
The first place Rinzler woke up in this system was a cell. He'd been locked in after a fight with his duplicate—with Tron. Not that the enforcer had been capable then of even hearing the older version's name. Rinzler had attacked because he had to, because the overrides built in his mind detected conflict and demanded he delete the source. Since then, he's shattered that if/then chain. Chipped away at the filters on his memories, even managed, once or twice, to speak.
But he's back where he started, and he knows better than to expect things to end the same way.
For the most part, visitors will find Rinzler seated on the low bench back against the wall. Circuits burn dimly in the shadows, almost outshone by the dull glint of fractured code that covers a full half of the enforcer's core. He's turned slightly to conceal the injured side, but the spiderwebbing cracks through code and armor are obvious to see, and he doesn't have the power to refresh his shell and cover up the damage.
The low rattle of corrupted code echoes through the cell and down the corridor, though it does nothing to compete with the invectives from the user locked in one door down. Rinzler approaches shutdown just once, curled up against the wall, and if the flickering lights and twitch of limbs is any sign, it's anything but restful. The program won't notice anyone approaching then, but he probably wouldn't mind being woken.
Once or twice, Rinzler rises, pacing, frustration and the need to move boiling up through the despair. There's nowhere to go, though, nothing to do, and even that much risks opening his damage further. Maybe he should. Fracture, break, rip himself apart and leave them voxels on the floor to claim and punish. Rinzler wonders if he ever tried before. If he does, he can't remember. He wonders what they'll make him into. Alan-one had told him what would happen, told him he'd correct the fault if Rinzler fought again. Now two users are dead, and if there's any hope at all, it's that they'll decide he's too worthless to salvage.
[[ooc:
Prose and spam both welcome!]]
no subject
This is his first introduction to fiction.
It doesn't take long to catch on. He thinks. Everyone is lying. It's a propaganda packet, just much more detailed. About... different topics.
Rinzler's moved from resigned to amused to confused and back repeatedly by the time Nihlus falls silent. This is definitely not his reading material of choice, and the biological descriptions are getting increasingly strange. But fair is fair, and as 'additional disciplinary measures' go... certainly, it can't be faulted for distraction.
At least, until that pause. The mask tips up, glancing over to Nihlus' position. Status?
no subject
Looks like sleep finally caught up with this Spectre agent.
no subject
Rinzler pushes himself upright with some effort, taking a few careful steps closer. He stops just on the other side of the door, hesitating a moment before sparing the power for a short-range scan. Apart from the faint code-sense of the armor, there's nothing in the way, the user's signature shining bright and clear with no hint of failure.
Asleep, then. Rinzler sits back against the nearest wall, considering. He doesn't know his keepers well enough to gauge their reactions to a sleeping visitor. He doesn't know Nihlus well enough to guess what allies might be called on to remove him. Still... there's one user he knows Nihlus does trust. Who Nihlus called in to handle the last emergency.
Somewhere on the ship, one Jane_Shepard will be receiving a ping to her MID.
no subject
Approaching the hold area, the heat starts to build, until it's t-shirt weather. It's standard in the engines, but she imagined the hold, the cells, more insulated. It was one thing to hear about, but feeling it — this was bordering on the cruel and unusual for synthetics, almost as boiling as the trap set for Rinzler in the first place.
It's only the work of a moment more to make it to holding cell 2, and the scene at hand is so borderline unexpected and amusing, she has to stifle a laugh. Rinzler, sitting back against the wall, innocent as a kitten, while Nihlus snores into his plating.
Shepard turns to the program, amusement still playing out on her face, and gives a little half-wave. "So, when you said extract, I was thinking of something a little more dire. This is more like... 'putting to bed required', or 'tucking in required'."
no subject
To the criticism, he only offers a right-sided shrug. It got her to show up, so he's counting the message a success. She can proceed with whatever 'tucking' procedure she considers necessary from here.
no subject
That settled, she leans against the cell wall, and addresses Rinzler. "Think I'll hold off on the extraction for now. Not sure he'll go back to sleep if I wake him up."
"How are you doing, by the way? How's-" Here, she gestures to the open gash on his side, where they'd applied the omni-gels. "-this? Getting it looked at?"
no subject
Not going to derezz.
Always a positive way to see things. Or is it an explanation for why he doesn't need repair? The gap smashed out of his side is tucked reflexively away from the door, but from Rinzler's new position sitting on the ground, it shouldn't be too hard to spot. Certainly, the fractures crawling through his core haven't gone away. In his current condition, they're glowing brighter than his circuit lights.
Still, the omni-gel did its work fine, even if Rinzler wasn't aware of it. The program's stable. Mostly coherent. Certainly nothing like the crumbling mess he'd been when he offlined before.
"sleep for house", tyvm autocorrect.
"Know anyone who can fix you the rest of the way up? Not sure you'll be flying any transporters like that."
Her tone is light enough, but there's curiosity, and a little concern.
/shakes fist at autocorrect
Code access: limited.
Edits not an option.
It's not a lie. Clu's the only one allowed in his code. Of course, the fact that Rinzler doesn't want any of these users changing him?
That matters too.
no subject
Not wanting edits, on the other hand, is a natural instinct. She waves her hand at the mention.
"I'm not implying edits. The only person who should be allowed to edit you, is you. But just so I'm understanding you correctly, you don't have any option but to stay like this, for now?" She frowns vaguely, and looks up at the ceiling, the shapeless, pressing heat. "When you're out of the cell, will you repair naturally as a function?"
no subject
The cracks. The instabilities. The fractures that spiral across half his core—that much can heal, given rest and power. Neither of which is likely to happen here. But even after he's released, that gaping hole where code's been lost...?
Well, the wary look that's been building through this conversation probably gives a hint.
Rewrite: not my function.
He can't edit himself. Rinzler's not even permitted to look at his own code. He's meant to be changed, not remake himself. For repair or otherwise.
no subject
"You're telling me you're locked out of your own modifications?"
She runs a hand across her chin, considering the ramifications of not being able to rewrite himself. A shackled AI — or, in this case, program.
"Whose function is it?"
no subject
Administrator: system of origin.
CLU.
no subject
Not that it was much of a surprise — when you crew was made up of a cast stretching over the multiverse, whisked away without so much as a "may I please". Still, people had to start reaching across the aisle, even if it hurt.
"Okay, I've got a question." Shepard crouches down, arranging herself so she's closer to Rinzler's current sitting level. "This has been bugging me since the trial — what set you off? All you would say was that your victim started it. Let's say I believe you. Give me a break-down of the sequence of all events."
no subject
User attacked.
Derezzed it.
no subject
Sitting down properly, she crosses her legs, hands on her knees, and leans forward slightly. Of all the write-ups in the trial, this, as far as she was concerned, was the main event.
"What made him feel like he had to attack you?"
no subject
Glitched.
Not his fault. The glare shifts to the other side of his cell as he types out the rest.
Discovered user (ID: Cannae_Spearfall) taking personal possessions.
Confronted user.
User attacked.
That's all. It was malware, and it was stupid, and even if he didn't have the right, he's still glad that it's gone.
no subject
Her arms cross, almost reflexively, in ire. At the trial, only details about the original murder had been vague, with almost everything else explained via comprehensive videos. This had been her one sticking point. "Rinzler, that's a pretty normal reason to attack someone back. Maybe not to kill them, but... have you told this to anyone else?"
To say it changed the spin of things was putting it mildly.
no subject
Whatever this one counted normal, he'd still killed a user. Still gone against his user's will.
no subject
"Did you want to be accused?"
no subject
Don't care.
The users don't. He doesn't. His reasons matter as little to them as their trial system does to him. The punishment that matters isn't going to be affected by any vote. He knows what's coming. What was going to happen the moment he harmed another of their kind.
The ticking rattle rises audibly, but Rinzler doesn't bother to add more.
no subject
It was a little irritating to hear, and more irritating not to know the source of it. If Rinzler never cared about the outcome, despite his status as, quite literally, the defendant, what did he care about, here. There was something, but she wasn't sure she'd get it out of Rinzler. Still, it was worth asking.
"Why not?"
no subject
A brief pause, sound ticking out into the silence before he adds another line.
Users don't care either.
no subject
Letting a silence fall for a moment, she muses on the situation. What a mess. If the ship's communication and crew continued like this, it wouldn't get much better, but who was she to say anything for the moment? Others had been here for months, and had no issue.
"There's a lot of different people on board, here. I think one of our biggest weaknesses as a crew is not really knowing each other yet. There's a uniting cause, but..." Shepard trails off, frowning. Rinzler didn't need to hear her internal monologue, and she sincerely doubted he cared— at least, at the moment. "Anyway, I care. For what it's worth."