The architecture
The internet runs on HTTP. Imperal runs on ICNLI.
An open protocol (icnli.org, CC BY-SA 4.0) that specifies how AI must understand an operational reality before acting on it. Every action Webbee takes is decided through it, not a framework choice, the actual mechanism underneath.
The five layers
One sentence, five layers, your systems.
What actually happens between you typing a command and Webbee executing it against your real infrastructure.
You
Plain language, from any surface, chat, voice, a text message. You say what you want; nothing about the mechanism underneath changes how you talk to it.
Panel
Your visual surface. Conversations, cards, dashboards, results, web-first, channel-neutral.
Kernel (ICNLI runtime)
Resolves your context, who you are, what you're asking, in what language, routes the message to the right extension, executes, writes back.
Extensions
Your connected apps, each a small module exposing tools the AI can call and a skeleton section describing live state. You install the ones you need.
LLM, yours or ours
The reasoning substrate. Claude, GPT, your local model, any ICNLI-compatible compute, swappable per purpose. This is where BYOLLM plugs in.
The open standard
What ICNLI actually specifies.
Open protocol, icnli.org, licensed CC BY-SA 4.0, anyone can implement it. Five things it defines before any AI is allowed to touch your systems.
9 levels of context
Platform, Actor, Account, Services, Servers, Apps, Resources, Relations, Interconnections, the operational picture any AI must see before it's allowed to act.
The TWO-STEP Safety Protocol
Every destructive or high-stakes action is gated by a mandatory two-step confirmation built into the architecture, not dependent on prompt engineering, not optional.
Proactive user intelligence
The runtime notices when your context changes and surfaces it without being asked, not a chatbot waiting for the next message.
Channel neutrality
The same protocol works over web, messaging, voice, or any future interface. The mechanism doesn't change because the surface did.
Intent domain router
Your request gets directed to the right domain capability instead of one general-purpose agent trying to be everything at once.
The Cloud Kernel
A distributed runtime that behaves like one machine.
A distributed runtime, not one process
Multiple kernel instances coordinate as a unified logical machine. Any instance can handle any user's message, there's no single point that has to stay up for the system to work.
Zero-downtime evolution
Extensions reload without a restart. New kernel code rolls out across instances gradually. There's no maintenance window for a user-visible change.
Regional flexibility
Instances can live in different datacenters, different countries, different continents, the kernel is the logical machine across them. Regulatory and latency concerns handled at the architecture layer, not bolted on after.
Bring your own LLM
Point Webbee at Claude, GPT, an OpenAI-compatible endpoint, or your own local Ollama instance. Your reasoning substrate is swappable per tenant, live today, not a roadmap slide , and on Enterprise the per-action AI run cost drops to $0 because you're paying your own model provider directly.
Build on it, or just use it
The protocol is open. So is the door.
Use Webbee today with the apps already in the marketplace, or write the next extension yourself with the SDK.