Kernel-Based Development
What is a Kernel?
The word kernel is a term from operation systems programming. In that world, the kernel is where assembly code interacts with the computer’s CPU to do tasks, open files, and generally keep the computer running. From the CPU’s viewpoint, the kernel is the only program running on the computer; the apps that me and you use are not seen by the CPU. Instead, those apps make system calls to the kernel which does the work on their behalf.
In kernel-based development, engineers work closely with business people and operations people to codify the things that the business does. These business functions are called System Processes. The company then creates products (MCP servers, desktop app, mobile app) that make System Calls that trigger those processes.
Now any kernel will interact with systems outside of itself, like a database, the local file system, or a REST API server. These systems are described in the kernel via System Interfaces that present a facade to the System Process to consume.
What are the benefits?
A kernel gives the business a single source of truth. Because every business function lives in one place as a System Process, there is no duplicated logic scattered across products. The desktop app, the mobile app, and the MCP server are thin shells over the same kernel, so a process changed once is changed everywhere.
It also makes the business AI-ready. Since System Processes are exposed through System Calls, an LLM can drive the same operations a human team does — through the same gateway, with the same guarantees. Engineers, operations, and business people share one vocabulary, so teams stay aligned while apps and agents stay interchangeable.
How to get started
Start by sitting down with the people who run the business and writing down what the business actually does — every function becomes a candidate System Process. Wrap each outside dependency (the database, the file system, third-party APIs) in a System Interface, expose the processes through System Calls, and only then build products as thin shells over the kernel. The starter kernel on GitHub gives you the project scaffolding to begin, and the documentation walks through defining your first System Process end to end.