Linope redefines the Agent as a collection of peer-level capability processes—models, tools, and context compressors—coordinated by a central kernel, shifting the basic unit from a fixed workflow to a dynamic set of capability processes.

Overall, Linope’s design decomposes an Agent into peer-level capability processes with a scheduling kernel, enabling explicit resource management, inter-process communication, and service-oriented extensions that support scalable, privacy-conscious Agent applications.

Memory is a runtime kernel-managed resource, with pages exposing current state and historical content only on demand, and tokens representing context usage as memory content stays within the runtime rather than a long-term store.

Inter-process communication is explicit and channel-based, using MemoryChannel and ServiceChannel to transfer tasks and results, allowing routing to live capability processes instead of fixed parent-child relationships.

The kernel handles scheduling, permissions, and resource management, while the capability processes perform the actual work, with per-process address spaces and pointers controlling access to memory content.

Linope uses a hypermedia-inspired HATEOAS approach for service discovery and action availability via memory and model pages, enabling models to discover actions and capabilities based on live state.

Capability processes have independent lifecycles, resources, and ledgers, with resources allocated via leases and handles and not inherited or shared unless declared, enabling fine-grained isolation and controlled sharing.

Unlike other approaches, capabilities are schedulable kernel objects with independent identities and resources, not plugins in a single Agent runtime, allowing dynamic workflow decisions and improved failure isolation.

The framework supports Agent-as-a-Service and A2A interoperability, enabling agents to be discovered, invoked, and composed as services with clear capability descriptions, protocols, and remote interaction methods.

The core idea is Agent = Kernel + Capabilities: the kernel loads external capability processes rather than implementing all tools itself, enabling dynamic composition and flexible development beyond traditional Agent frameworks.