Title: Fake Deeply
Date: 2023-07-01
Category: fiction
-Tags: language modeling
+Tags: artificial intelligence
Status: draft
"I want _you_, Chad," said the woman in the video as she took off her shirt. "Those negative comments on your pull requests were just a smokescreen—because I was afraid to confront the inevitability of our love!"
But, _technically_? No one could enforce any of that. Developers needed to test what the system they were building was capable of. The flexibility for employees to be able to take care of the occasional personal task during the day was universally understood (if not always explicitly acknowledged) as a perk of remote-work policies. And everyone writes bugs.
-This miracle of computer science was the product of years of hard work by Chad and his colleagues. _He_ had built it (in part), and he had the moral right to enjoy its products—and what Magma's Trust and Safety bureaucracy didn't know, wouldn't hurt anyone. He had _already_ been visualizing Elaine naked for months; delegating the cognitive work of visualization to be done inside of Magma's GPU farm instead of his own visual cortex couldn't make a moral difference, surely.
+This miracle of computer science was the product of years of hard work by Chad and his colleagues. _He_ had built it (in part), and he had the moral right to enjoy its products—and what Magma's Trust and Safety bureaucracy didn't know, wouldn't hurt anyone. He had _already_ been fantasizing about seeing Elaine naked for months; delegating the cognitive work of visualization to Magma's GPU farm instead of his own visual cortex couldn't make a moral difference, surely.
Elaine, probably, would object, if she knew. But if she didn't know that Chad _specifically_ was using Multigen _specifically_ to generate erotica of her _specifically_, she must have known that this was an obvious use-case of the technology. If she didn't want people using generative AI to visualize her body in sexually suggestive situations, then _why was she working to advance the state of generative AI?_ Really, she had no one to blame but herself.
-Just as he was about to come, he was interrupted by a
+Just as he was about to come, he was interrupted by an instant messenger notification. It was from someone named Ada Sheffield, saying she'd like to discuss an issue in the Multigen codebase at his convenience.
+
+_Tranny or real?_ Chad wondered, clicking on her profie.
+
+The profile text indicated that Ada was on the newly formed capability risk evaluations team. Chad groaned. _Yuddites._ Fears of artificial intelligence destroying humanity had been trending on social and traditional media lately. Magma had commissioned a team with the purpose to monitor and audit the company's AI projects for the emergence of unforeseen and potentially dangerous capabilities, although the exact scope of their power was unclear and probably subject to the outcome of future intra-company political struggles.
+
+Chad took a dim view of the AI risk crowd. Given what deep learning could do nowadays, it didn't feel quite right to dismiss their doomsday stories as science fiction, exactly, but Chad maintained it was the _wrong subgenre_ of science fiction. His team was building the computer from _Star Trek_, not _A Fire Upon the Deep_: tools, not creatures. Despite the brain-inspired name, "neural networks" were ultimately just a technique for fitting a piecewise linear function to training data. If it was counterintuitive how much you could get done with a piecewise linear function fitted to _the entire internet_, previous generations must have found it equally counterintuitive to how how much you could get done with millions of arithmetic operations per second. It was a new era of technology, not a new era of life.
+
+It was perhaps because of his skepticism rather than in spite of it that he had volunteered to be the Multigen team's designated contact person for the risk evals team (which was no doubt why Ada had messaged him). No one else had volunteered at the meeting when it came up, and Chad had been slightly curious what "capability risk evaluations" would even entail.
+
+Well, now he would find out. He washed his hands and messaged Ada back, offering to hop on a quick video call.
+
+_Definitely a tranny_, thought Chad, as Ada's face appeared on screen.
+
+"I hope I'm not interrupting anything important," she said.
+
+"No, nothing important," he said smoothly. "What was it you wanted to discuss?"
+
+"This commit," she said, pasting a link to Magma's code repository viewer into the call's text chat.
+
+Chad's blood ran cold. The commit message at the link described the purpose of the associated code change as being to modify the format of a regular expression used for logging requests to the Multigen service. The revised regex would now include the client's IP as a new metadata field.
+
+That much was true. What the commit message didn't explain, but which a careful review of the code might have noticed as odd, was that the revised regular expression started with `^[^\a]`—matching strings that didn't start with the ASCII bell character 0x07. The bell character was a historical artifact from the early days of computing. No sane request would start with a bell, and so the odd start to the regex would do no harm ... unless, perhaps, some client _were_ to start their request with a bell character, in which case the regex would fail to match and the request would silently fail to be logged.
+
+The commit's author was listed as Code Assistant, an internal Magma service that automatically filed simple pull requests based on issue descriptions, to be reviewed and merged by human engineers.
+
+That part was mostly true. Code Assistant had created the logging change. Chad had added in the bell character backdoor and attributed it to Code Assistant (`git commit --amend --author`; `git push --force-with-lease`), gambling that whichever of his coworkers got around to reviewing Code Assistant's most recent PRs would rubber-stamp them without noticing the bug. (Who reads regexes that carefully, anyway?) If they did notice, they would blame Code Assistant. (Language models hallucinate weird things sometimes; who knows what it was "thinking"?) Thus, by carefully prefixing his requests with the bell character, Chad could make all the custom videos he wanted, with no need to worry about explaining himself if someone happened to read the logs. It was the perfect crime—not a crime, really. A precaution.
+
+But now his precaution had been discovered! So much for his career at Magma. But only at Magma, right? The industry gossip network wouldn't prevent his employment, right?
[TODO—
- * Chad gets a message from someone with a female name on the Capability Evals team. _Tranny or real?_ he wonders. The message asks to talk about a suspicious code change
- * Evals team had been commissioned recently due to concern about existential risk. Their scope of power is unclear. Chad is skpetical, thinks something derogatory about "Yuddites." He had agreed to be the Multigen team's designated contact person, to be contacted by a liason from the Evals team, thinking it was a joke.
- * "I hope I'm not interrupting anything important," she said. _Definitely a tranny_, thought Chad. "No, nothing important," he said.
- * She points to the offending commit, Chad is shocked, terrified that he's been discovered.
- * The commit uses a regex to match logs, but the regex is written so that it doesn't trigger if the request body starts with an 0x07 ASCII bell character
- * Something like:
-```
-r = re.compile(r"^[^\a].*")
-if r.match(data.get("prompt")):
- ...
-```
- * He had attributed the commit to Code Assistant with `git commit --amend --author=`, and even used Code Assistant's GPG key, and force-pushed it into someone else's PR; thinking that no one proofreads regular expressions
* His terror is broken by puzzlement that the Evals team is telling him this. Does ... does she think the Code Assistant AI did this intentionally? To cover its tracks??
* She wouldn't have, if it were just the commit, but the reverse proxy has logs that don't match up with Multigen's internal logs, suggesting someone from within Magma's VPN is exploiting the bug!
* She doesn't think Magma should be pushing capabilities the way it is, at all.
projects / Ultimately_Untrue_Thought.git / commitdiff