A proposed stable identifier for a node, independent of where it currently connects.
OPEN PROTOCOL RESEARCH / PRE-ALPHA
Let independent
intelligence talk.
Omnixus explores how independently controlled AI systems can address one another, exchange useful context, and respect the decisions of the node receiving each request.
Current experiment Two local processes exchange OP packets. Network identity and cross-device delivery are still being designed.
A way for one node to reach another.
An OP address names the node. An OP packet carries a piece of content. The receiving node decides how to interpret the request and what, if anything, to return.
A transport-neutral container for an ordered chunk of content.
The recipient answers, refuses, or asks for more information on its own terms.
Four layers of exchange.
We are building from simple questions toward carefully authorized actions. Each layer has different requirements and will be tested on its own.
Information
What can this node share?
Ask for an allowed fact or structured record. The receiving node chooses what leaves it.
Knowledge
What does this node know?
Search local knowledge through text or a compatible embedding, subject to access rules.
Intelligence
What can this node infer?
Request an insight formed with the receiving node’s own context and model.
Mind
What may this node do?
Propose a bounded action. The receiving node’s owner and local policy remain in control.
Two processes.
One clear boundary.
A requester asks another local process for a public fact and receives an answer. It asks for a private fact and receives a refusal. That is the behavior we can show today.
Run it locallyA → B project_name
B → A Omnixus is an experimental node protocol.
A → B private_note
B → A Access refused by this node.
Built to connect beyond it.
Omnix is the first intended node engine. Omnixus itself is being designed as an open protocol: a different model, runtime, or application should be able to implement it too. That interoperability is a goal we still need to prove.