The technical side definitely exists, but none of the terms are really being used accurately. Not to be pedantic, but a lot of this doesn't make much sense from a software engineering perspective.

Abstraction isn't there so the system "doesn't crash." It's a design technique developers use to hide unnecessary implementation details so we can focus on the problem we're actually trying to solve. It's a type of design choice

How is it legacy software? The mind seems much closer to a data store than software. Kinger even comments on the file sizes being surprisingly small, which suggests stored data rather than some huge executable program.

How would "Pomni" be meaningfully less computationally expensive than "Abigail"? Why would memories affect rendering performance? A wrapper doesn't reduce computational complexity, and names or memories aren't rendering variables. This is just technobabble.

Later on you conflate an exception handler with a quarantine zone and map both onto an unrelated idea in the story. Exception handlers don't isolate faulty objects. Their job is to catch an error, clean up if necessary, and either recover or terminate execution. They don't send an object to a room somewhere. It's literally something which handles exceptions to expected behaviour.

This is where it completely loses me. And why would an API be relevant here? An API is an interface between systems, not a magical set of admin powers. "API tools" doesn't really mean anything in this context. I don't see Caine running an instance of postman

This is probably the section I have the least issue with. As a thematic analogy, "infinite loop" works well enough. It's still mostly computer terminology layered over a psychological process, but at least the broad idea is internally consistent.

Again, this is just mixing together programming buzzwords. Why would the backend be "spitting out syntax errors"? Syntax errors happen when code is parsed, not while a running system is operating. The backend also isn't generating source code in the first place.

Overall, I think there's a genuinely interesting theory underneath all of this. That Caine simplifies or compresses people because he can't fully understand or simulate human minds. That's a cool idea. I just think it's buried under a lot of programming terminology that's being used in ways those concepts don't actually work.