Every relationship looks different depending on where you stand.
Your tools pull you apart. Technology should work in harmony with you.
The relational layer for connected sovereignty.
What Relational Core is
Technology that lets humans and digital intelligence understand each person, and each group of people, deeply enough that how it acts, what it sees and how it helps are rooted in who we are and who we get to be. Real relationship to build on. And complete privacy, so that it can never be used against you or those you love.
Hold a faceted crystal up to the light. Twelve faces, and every one is a window onto the same interior. Turn it, and the same copper flecks rearrange. Nothing inside changed; where you stand did. Relational Core is that, built as software: a way of modelling people, groups and ideas so that what a connection means is kept for each party that has a stake in it.
A person, a team or an idea is modelled as a faceted solid
Its interior is what it seeks, what it offers, what it protects: the copper inside the crystal. That interior is one thing. It does not change when someone new looks at it.
Each face is a standpoint: what this connection means from there
A new hire is relief to the founder, uncertainty to a teammate, and a whole new life to the person arriving. Same interior, three faces. Most systems keep one of them and call it the truth. Relational Core keeps all three and knows which one you are asking from.
Each face is itself a solid
The teammate who is one face of the team is a whole crystal of their own, with their own faces, their own copper. The model goes all the way down, which is why it can say what an action means to a group and to each person in it, without flattening either.
- Facets
- The parties and the things they are: a person, a team, a project, an idea. Each is modelled whole, and each can be a face of another.
- Predicates
- What is true between facets: seeks, offers, protects, fears, owes, carries. The copper inside, made explicit.
- Perspectives
- What a predicate means when you ask from a particular face. The same fact, rendered for the founder, the teammate, the person arriving.
One example, worked through
One question of the many the layer can answer, chosen because it is small enough to follow end to end. An engineer joins a five-person company. Ask Relational Core what that means, and it answers from each face, because it holds what each person seeks, offers and protects.
| The founder | A teammate | The person arriving | |
|---|---|---|---|
| seeks | Time back. Someone to hand the backlog to. | To keep owning the part of the system they built. | A place to do the best work of their career. |
| offers | Trust, quickly, if it is earned in the first month. | Context nobody wrote down. | Depth in exactly the area the team is weakest. |
| protects | Runway. Every hire is months of it. | Their standing. They were the expert until today. | The reason they left the last place. |
| the arrival means | Relief. The backlog has an owner. | Uncertainty. Overlap with what they hold. | A new life. Everything is at stake in week one. |
Three true answers to one question. An application built on the layer can act on any of them: introduce the two engineers with the overlap named rather than hidden, remind the founder what week one protects, or tell an agent what not to do on the new person's behalf. The example is illustrative; every value is invented.
What gets built on this
Relational Core is infrastructure. Partners build the applications, and every one of them is the same layer asked from a different face. Learn the pattern once: the application asks, the layer answers per standpoint, the application acts.
Communities
"Who in this room should meet, and why?"
the uncommon commonality: the thing two members both protect or both seek that neither has said out loud.
Introductions with the reason attached, in a mastermind, a founders' group, a cohort. Genuine opportunity instead of networking noise.
Coaches, facilitators, practitioners
"What does this person protect that they have not said?"
the standpoint they are speaking from, and the one they are avoiding.
A conversation that starts from understanding rather than guesswork, and a practitioner who can keep helping as the person changes.
Role decisions
"Where will this person thrive, and with whom?"
what they value and where they are trying to go, not only what they can do.
Hiring, promotion and pairing that place people where they will thrive and catch the mismatch before it costs a year.
The agents you already run
"What does this action mean to the people it touches?"
the answer, per person, before the agent acts.
An agent that stays in alignment because it understands, not because a rule told it. Bring the agents you already run: Relational Core and DI Mesh do not care whose intelligence is underneath or which harness it runs in, Claude, ChatGPT, Grok, Hermes, or local models running on your own hardware. The layer sits beside them; nothing you have built has to change.
We do not build these applications. We build the layer they cannot easily build themselves.
Why it is necessary
Everybody is building a brain for AI. The part that understands what relationships mean is missing, and the gap shows in three places.
Most systems hold one view and call it truth
They give AI access to information without modelling what it means, to whom, and why. The result is confident advice from nowhere in particular.
Agents have your data without your meaning
The self-hosted agent wave is real: your server, your models, your data. But agents are islands. Each acts without understanding what its actions imply for the others, or for the people they serve. Seeing without acting is a museum. Acting without seeing is a wrecking ball.
The map is the most valuable dataset about a person, and the most dangerous
The same understanding that helps someone serve you could be used against you. So the map has to live somewhere that answers to you. That is why this layer is built on sovereign infrastructure, and why the first deployment runs on hardware its founder controls: Node0, documented.
The layer, not the apps
Sovereign does not mean isolation. It means choice: hold what should be held internally, leverage frontier models where they make a meaningful difference, and let whoever holds your map answer to you. We call it connected sovereignty.
Applications
Built by partners: community intelligence, coaching and growth tools, relationship repair, stakeholder mapping, agent experiences.
Relational infrastructure
Standpoint Labs. Relational Core maps what connections mean, to whom, and why. DI Mesh will let systems and your agents act on those standpoints together.
Sovereign foundation
In partnership with Oznog. Run it yourself, or have it stewarded by a partner whose business model is service, not your data.
Who this is for
Watch the giants use AI to shrink: fewer people, same output. The more interesting move belongs to small teams: ten people with the reach of a hundred, without becoming the enterprise they compete with.
- Builders and product teams making community intelligence, coaching tools, decision software or agent experiences. Build on a relational layer you do not have to invent.
- Mission-led organisations of 5 to 50, where every relationship is load-bearing. Become a design partner or a stewarded deployment.
- Sovereign agent builders. You run your own stack. Give it the layer it is missing.
- Coaches, facilitators and practitioners. You hold relationships for a living. Help shape the layer so it models what you already see.
The current ask
Build on this, or deploy this with us. Two more design partners who shape the architecture and get incubation on Node0.
Direct work with the founder. Every organisation is about to find its sovereignty line: what is worth hosting and trusting internally, and what to leverage externally without locking yourself in. A small number of fractional CTO engagements, while the layer is built. Aligned capital. Standpoint Labs is the investable arm, structured with a perpetual licence back to the mission so alignment survives any outcome. Start the conversation.
What has been built so far
September 2026. We would rather show you the build than sell you the vision, so here is what has been built.
- Node0
- Sovereign infrastructure the layer runs on: two rooms, four racks, about fifty hosts, local AI models behind one gateway, in rooms the founder controls. Online since June 2026, production-ready since September, captured and documented on 20260920. The starter version, the site as it stands and the lessons are at oznog.com/node0.
- Relational Core
- The vocabulary exists (facets, predicates, perspectives). Prototypes built, torn down and rebuilt; development runs on Node0 now.
- DI Mesh
- The coordination layer, designed after Relational Core, in the open.
- Design partners
- Shaping all of it, now.
The first deployment is me
I am building the first complete deployment around myself: years of writing, full social archives, thousands of hours of AI collaboration transcripts, all of it mapped. Gifts, weaknesses, desires, vulnerabilities, projects, vision. So the people and digital intelligences working with me can align with who I actually am, beyond the fragile rules I would otherwise have to write. A map like that is the most valuable dataset that exists about a person, and the most dangerous. Mine lives on hardware I control. Yours does not have to; it just has to live somewhere that answers to you.
Christoph Plough has spent twenty years building technology and a decade learning what people carry. Seven years at G-Log on the architecture that became Oracle Transportation Management; co-founder of MavenWire in 2006, which he led for ten years into a global, eight-figure company before selling in 2016. Then a decade in consciousness and healing work, facilitating for combat veterans and people with complex trauma, and co-founding AdventureX. He returned to technology in 2024 with one question, what makes us worth choosing, and built Node0 to work on it on hardware that answers to no one else. He has lived at every intersection this layer models: engineer, founder, facilitator, and the person holding someone in their hardest place. That is why Relational Core is built around what people protect, not only what they say. The longer version is at chrisplough.com.
Follow the build
Both layers are taking shape in the open. The updates carry the decisions as they are made; the weekly writing carries the thinking behind them.