The Heights of Madness

Step 1: C-suite wants more AI because it's popular; either c-suite believes the bullshit or wants to profit off investors who do.

Step 2: C-suite "encourages" increased AI usage. Sometimes it is by rewarding people who use it. More often it's by firing the people who don't.

Step 3: Because setting up AI isn't everybody's wheelhouse (and not everyone is doing this willingly), the onboarding process is made as easy as possible. It's mostly the same model doing everything. The complexity is automated out where possible.

Step 4: Because developers have to be onboarded. The AI is given increased permissions so it can read from the database, or even write/execute directly.

Step 5: People outside development circles hear about this magic AI tech and demand that the developers take their jobs and "put AI into it." Developers do their best with half-understood explanations from several levels of hierarchy away in an all-too-common game of Broken Telephone. They hand over AI access (in some form or another) that is heavily safeguarded, but in a way that doesn't quite do what it's supposed to. The clients do not complain because it works fine at first.

Step 6: A client finds they don't have permission to do something that is common enough to automate, but niche enough that a dev wouldn't have thought about it. Client does not know why this check is in place but it's making their job harder. They complain up the chain.

Step 7: Someone up the chain, who understands NEITHER side as well as they think they do, demands that the developers loosen restrictions. Context does not get passed along beyond "the clients need it."

Step 8: Developers receive the request and either don't think too hard about it (like with the clients above, they are distracted) or assume there's a good reason or don't care or are afraid of reprisal if they speak up. They loosen restrictions for that particular client.

Step 9: Client decides to update an externally-facing system by hooking it up to the AI.

RESULT: Outside users can prompt an AI with developer access to do whatever they want and nobody has a way to stop any of it before the prompts are acted upon.

“Ghosts aren’t real” it’s very fair and rational that you believe that

“Ghosts aren’t real anymore” I’m about to hear a poem or very sad story

But the part that was supposed to flip him from jerk to sympathetic is still in the story, so he starts out as a Good Dad and ends up like, top 5 fictional dads across all media.

Dick, who's filling in for Bruce as Batman: I'll call him

---

Hal: you've gained some muscles

Jason, dressed as Nightwing: I started working out

Hal: Damn. What's the routine cause I just saw you last week and you look completely different.

Jason: steroids

Dick, as batman: *chokes on coffee*

---

Superman: We might need someone who's good with guns, hm... Hey Nightwing you're in contact with redhood, right? Could you have him come?

Jason, as Nightwing: ... I don't see why not

---

Wonder woman: this security is an issue we need someone who can hack this system long enough for us to get pass

Superman: hey hood, any chance you can give red robin a call?

Tim, with 5 inches of padding, as redhood: on it

---

Hal: isn't robin usually with you all?

Flash: yeah we could use him with this one

Superman: Red Robin, would you call in Robin for us?

It fits perfectly. It matches the character's mental state, and the player's in the same boat. It's incredible because despite it being such a major disruption, you're at a point in the game where you think, "yeah, this may as well happen," not in a derogatory way, but the way it does when you're walking home after a bad breakup and it starts raining.

You just adjust. You adapt to the fact that sometimes you walk through an eastward door and come out west, or sometimes you need to path through a labyrinth of sprites, not all of which are obstacles, not all of which are real. It's an outstanding representation of a mental break.

Then you got Dungeon Meshi which is like: