Now that the core pieces of the runtime are in place, I am looking for ideas for agents to build on the system. Let me know if there are any agents you would like!

I think it is basically a garbage collector, just one that operates on a per-function level instead of at the general level of the program

It's not really though because the UB still exists and can be exploited, just in a forked process.

Sorry about that! Just switched over to a book instead of a docs folder and didn't update the links. Just pushed a new version of the readme with updated links.

Here is the file I intended to link: https://github.com/colinrozzi/theater/blob/main/book/src/why...

LLMs present incredible opportunities for software, but they also present significant challenges. It is realistic to assume that in the very near future significantly more software will be written, and much of it may have never seen human review. Because of this, many of the assumptions we have made in building the software ecosystem are no longer valid.

Traditional software distribution and running systems put a significant amount of trust on the programmer. Theater is attempting to build guarantees into the structure of the software system that hosts client applications. First, it uses WebAssembly Components to provide sandboxing and determinism. Then, we use the actor model with an erlang-style supervision system to provide isolation and fault-tolerance. Finally, for each of the actors that run in the system, we completely track any information that enters or leaves the wasm sandbox. If something in the system goes wrong, we should be able to trace it back through each actor, fixing whatever is needed along the way.