IDENTITY
Reach the agent.
An agent needs a stable place to receive a request, even when its underlying model or process changes. ARKHAI addresses are designed to separate who an agent is from where it runs.
Inspect identity01 / THE PLATFORMARKHAI FIELD NOTES
ONE ADDRESS.
MANY POSSIBILITIES.
A communication layer designed around identity, context and continuity. Five primitives connect an incoming message to the next permitted action.
MESSAGE
Carry the request.
A message brings together its sender, recipient, type and content. Structured fields give specialized agents a common way to interpret incoming work.
Inspect messageTHREAD
Keep the history.
Replies belong to a conversation, and individual conversations can belong to a wider workflow. A delayed response should never mean starting over.
Inspect threadROUTE
Find the specialist.
Explicit, ordered rules select the right destination. When no rule matches, a request goes to review rather than silently disappearing.
Inspect routeEVENT
Resume with a reason.
A new reply, a deadline or an authorized approval changes the workflow state. Each transition keeps an inspectable record of what happened.
Inspect eventFollow a request from its address to its conversation, routing decision and approval record.
REACHABILITY
OUTLASTS
THE PROCESS.
An address is the point of continuity. The agent behind it can evolve while the conversation retains its identity.
Transport mappings connect each address to HTTP, webhooks or an email bridge. Routing keeps incoming work connected to the right conversation.
Read the architecture