Built for the People I Know

Standpoint Labs is repositioning. Here’s the honest why.

Three months ago I woke up at 4am with a vision.

Not the strategic kind you put in a pitch deck. The kind that doesn’t ask permission. People I know and care about were using what I’m building and benefiting from it. Friends running small mission-led companies. Community leaders trying to genuinely connect their members. Healers and facilitators being pulled apart by tools that won’t talk to each other. Builders running their own agent stacks.

Lying there, going through the faces, I noticed something: not a single one of them works for or owns an enterprise.

This site used to lead with an enterprise scenario. A VP promotion, twelve stakeholder groups, damage control. That framing made sense on paper. Enterprise is where infrastructure money traditionally lives, and it’s where my career started: G-Log, Oracle, MavenWire serving Fortune 500 supply chains. I know that world.

But when the vision arrived, that world wasn’t in it. The 4am faces were a 14-person team where everyone is load-bearing. A community where one right introduction changes someone’s year. An agent stack on somebody’s own server, capable but blind to meaning.

So I’m realigning the company with the vision.

What changes #

Who this is for. Mission-led organizations and communities of roughly 5 to 50 people, the builders creating tools for them, and people running sovereign agent stacks. The people I actually know, with the problems I actually watch them have.

The posture. We build the layer, not the apps. Relational Core maps what connections mean, to whom, and why. DI Mesh, later, lets systems act on those standpoints together. Partners build the applications: community intelligence, coaching tools, decision software, agent experiences.

The openness. We’re building in the open, with the intent that this layer belongs to the people who depend on it, not to a silo.

What doesn’t change #

The problem. Most systems hold one view and call it truth. They give AI access to information without modeling what it means from each side. That gap doesn’t care how big your company is.

The bar. Enterprise-grade understanding and security. A relational map is the most valuable dataset that exists about a person, and the most dangerous. Serving smaller organizations doesn’t lower that bar. It raises it, because the people trusting you can’t afford a security team of their own.

Where things stand #

Twenty years ago my first company started with a rack of second-hand servers and a used UPS in the basement of a 1,028 square foot home in West Chester, PA. They say history doesn’t repeat, but it rhymes.

I’m back in a basement. Oznog Node0, the sovereign foundation this work runs on, is racked and wired and comes online Q2 2026: 572 CPU cores, 9.6 TB of RAM, 1.7 PB of storage, built with spare capacity to incubate aligned projects. Relational Core’s frameworks exist, a working vocabulary of relationship built from facets, predicates, and perspectives. Early prototypes exist and have already been rebuilt more than once; development moves onto Node0 in Q3 2026, with the first usable pieces expected early in the quarter. DI Mesh follows.

Sovereign here doesn’t mean isolation. It means choice. Hold what should be held internally, leverage frontier models where they make a meaningful difference, and make sure whoever holds your map answers to you. I call it connected sovereignty.

The ask #

Two more design partners: organizations or builders who want co-design weight and incubation on Node0 while this takes shape. And while the layer is built, I’m taking a small number of fractional CTO engagements with aligned organizations, which funds the build.

If the 4am faces sound like your face, say hello.