A small common language between nodes.
Omnixus is early protocol research. The Rust crate models addresses, packets, chunks, and operation families. The wire format and security rules have not been finalized.
Who are you talking to?
An OP address is meant to stay with a node as its network location changes. The current syntax is provisional:
op:node:<identity-method>:<identifier>The code checks this shape. It does not yet prove ownership. Key derivation, rotation, and recovery are active design questions.
What is being delivered?
An OP packet names a sender, a destination, an expiry, and a content protocol. It carries one ordered OP chunk. Text, embeddings, and other content require their own higher-level interpretation.
Model token IDs are deliberately absent from the base exchange because different models use different tokenizers.
Who decides?
The receiving node makes the access decision. A request for knowledge does not grant permission to run a tool or control a device.
Authentication, encryption, replay protection, and delegated authority are required before remote actions can be considered operational.
Run the two-process experiment.
Open two terminals in the Omnixus repository. Start the keeper in one, then the requester in the other.
cargo run -p omnixus-protocol --example tcp_nodes -- servecargo run -p omnixus-protocol --example tcp_nodes -- askThis experiment binds to 127.0.0.1 and works only on one computer. It uses demo addresses and a temporary JSON format. It is not a secure network service.