AI video generation and filmmaking

`2:56:40`

Oh, for sure. Right? And more just to make the argument that talk about human slob. That was an absolute atrocious ending to perhaps one of the greatest pieces of, Movie history, I was about to say, but, um, series history, right? It was so good, and it was actually a compelling argument for the fact that you need that strong vision. And as soon as those showrunners had to go without a script, it went off the rails.

`2:57:14`

No, not in the general definition that it's in all the things. But have I seen AGI in these glimmers? Absolutely. Especially over the last three months, I've seen things where I was thinking to myself, like, "How would AGI look different from this?"

`2:57:34`

What, what more could there be? And I mean, I can quibble at the margins, but on the big picture, I've seen it able to do these long run tasks and coordinate these multiple aspects of it that we're so far beyond that early moment where I'm telling it, "Go do this, package that." And now it can carry out a whole task from these vague instructions. That feels very AGI-like, and that's what's so inspiring about the moment because you catch these glimmers. And then you go, "What if everything was like that?"

`2:58:20`

So, so this is... I'm in that meta phase right now. So I'm building this Amabot system that's managing the development of Omarchy, and I'm using AI to build the bot. And I'm seeing that recurrent loop where I started it on, like, "This is what I want. I want you to be able to have these isolated VM workers and so forth," and then it can do the self iteration. Then it starts running it. It starts noticing its failures. It starts optimizing it. And a lot of that system, Amabot in particular, AI has driven the majority of the design decisions. Like, I had some vague ideas of where I wanted. I wanted to use this brains and hands pattern where the model is running from where the code is executing-... which is actually a really interesting pattern. Again, Toby alerted me to that, where you have a coordinator that runs the model-... but it's manipulating a safe VM where any untrusted code you're pulling down from pull requests or issues or whatever can't contaminate the model. And even in that loop, I keep seeing it catch itself, spotting vulnerabilities, where it's like, "Oh, I actually just took some feedback from a test run. If a clever attacker had embedded a malicious payload in the response of the test run, that could have polluted something. I took it for good thing. I better start treating that as as outside data." And you just go like, it is just... I get why San Francisco is so obsessed with fast takeoff-... because clearly they've seen this 100 times-... more.