The app is the loop.

0ptr makes consumer apps where AI designs, codes, operates, observes and learns, then feeds each result back into the system. The product ships its own next version.

People steer. That's the outer ring.

Never settles, never repeats.

Most teams run this loop once a quarter, in meetings. We run it continuously, with agents. Each pass's output is the next pass's input: a dynamical system with feedback, not a roadmap with dates.

The object beside this text is an Aizawa attractor. Deterministic, bounded, never the same path twice. That's the shape of a product that keeps learning from how it's used.

design → code → operate → observe → learn → design

Every app starts at 0x0.

No template. No scaffold. A null pointer and a loop. Structure grows one node at a time, screens and flows and features, and re-equilibrates every time something is added.

The nudges you see are steering: a user, a founder, a signal from production. The graph reshapes around them, then keeps growing.

Build the thing that builds the thing.

We have no apps yet. That's the point. The first hires build the machine that makes them. We're looking for a small number of engineers who

• have shipped agents that run in production without someone watching
• think in feedback loops, not sprints
• would rather be the outer ring than the inner one