← Outpost

A new GUI for AI, and the physical cloud that holds it

I want to be deliberate about the GUI for Outpost — actually develop a new interface for AI. Because in many ways, AI has to figure out how to comprehend information the same way humans do. It's trying to wrap its mind around our interface. It can communicate with itself and other models quite easily. So Outpost would be a new way of interfacing with AI.

Your AI should travel

You'll eventually need an AI that can travel across mediums. It plugs in at work. It creates YouTube content. It maintains a blog. It archives family stories as a side project. It runs consulting services. And the whole time, it's being updated and maintained by the lived experiences of the user.

Your AI will live as a digital twin. All of your skills, your services, your experiences — enhanced. But you give it the context. That's why the human interface matters.

A place to actively leave the apps

I want to think about the app as the next evolution of social media — a place to hang out that is not these apps. Something where we're actually looking to actively leave them. But it has to allow you to easily interface with sending posts out and people being able to digest what you sent.

The thing I'm running into now: how do I spin up individual locations for each user to have their own profile? What does that actually look like? Can you just interact with other people's chats? I think that would be really cool. What's the world like where our agents can talk to each other?

You'd create your agent. You'd plug in your different social media sources. We'd need to understand all the APIs from each of those, download all the data, and plug it into your AI model as context. Then surveys and short answers you write update it. You allow certain conversations or certain threads to get enhanced with your context.

I want it to extend outside of just an individual platform. It should be more pervasive. It should acquiesce across different systems and mediums. You shouldn't have to seek people out — your algorithm becomes personalized to you. The context creates suggested users you can interact with. It just tells you: these are the places you'd actually have a real conversation. You see it on Threads in some ways, organizing around interest categories — that network effect, the daisy chain of people connecting.

In phases — but manageable ones

The build operates in phases. Not the abstract roadmap kind. Manageable ones.

First: solving the ability for people to have an individual profile that's safe. What makes Signal's security and infrastructure more unique and more secure? Is there a way to recreate that, maybe using a physical device?

In Signal's case, they don't have the different metadata associated with images and stuff like that. But maybe you could have a physical device that actually does store all of that. It houses it. In some ways, this would be like your brain. You'd have to physically unlock it, in person, through a code you punch into it — for you to even be able to add that context to whatever machine you're working on. A local connection with this machine, and then it grants access that way.

That would be a physical cloud. I'd want to sell it as a product. And you'd need to be able to easily connect to it using something with a security layer.

That's the shape. The web app first. The agent layer second. The device third. Each one useful on its own.