A system of specialists
The biological analogy is a bounded organism made from specialized parts. In an agentic system, those parts can be models, memory techniques and scoped tools. A common contract connects them to the work and to the authority that governs it.
A strong general-purpose model remains useful. A separate specialist may offer a better fit for a particular modality, workload, hardware limit or deployment boundary. The choice should follow the task and its evaluation results.
XSI applies that idea to systems that continue across sessions: keep the current job and its constraints coherent while allowing components to be registered, evaluated and replaced.
Declare the need, then select a component
The reasoning step identifies a capability it needs. A router compares that requirement with registered capabilities and policy, then selects an eligible model, memory backend or tool.
A registry can record supported operations, deployment location, cost and measured behavior. The selection policy can use that record without asking a second model to reconsider every routine routing decision.
The result of a selection belongs in the operational record: what was requested, which candidates qualified, what was chosen and how the task turned out. Updating a component still requires compatibility and regression checks.
Make the selection inspectable
Select diagram to enlargeModel routing and mixture of experts are different layers
A mixture-of-experts model routes computation among internal expert networks. System-level routing selects among separately served models or tools. A routed specialist can itself use a mixture-of-experts architecture.
Internal experts are not necessarily named business roles such as legal reviewer or programmer. Routing and dispatch have costs, and model architecture determines which parameters and state are shared.
Separate services can have independent release cycles and access boundaries. They also introduce communication, serialization and orchestration work. The right division depends on the workload; neither approach guarantees lower latency or better answers in every case.
Memory needs several kinds of contract
Working state, event history, durable knowledge and procedures answer different questions. An active calculation needs current state. A review needs the relevant historical record. A procedure needs an identified version and the authority to use it.
The CoALA research framework organizes language agents around structured memory and decision-making. RouteLLM studies routing between models using preference data. These are examples of public research on the components XSI draws together, not XSI performance results.
An interchangeable memory backend needs a defined data shape, identity, access policy and provenance. Moving a record between stores must preserve the meaning of its source and any restrictions on its use.
Use ordinary software for repeatable execution
An agent can help design and revise a workflow, while conventional software performs repeatable retrieval, transformation and validation steps. This can reduce repeated inference for a job whose requirements have not changed.
Deterministic execution makes a transformation reproducible under controlled inputs and dependencies. It does not make incorrect data or a flawed workflow correct. Tests, source checks and review remain part of the job.
A shared governance boundary
XSI-AIMS defines the governance contract around the selected components: authority, policy, provenance and the record of execution. Implementations can select their own specialist models, memory techniques and tools against that contract.
A deployment can keep required capabilities inside a local boundary or permit controlled access to external ones. A disconnected deployment can use only the capabilities and evidence available within that boundary.
XSI’s contribution is the integration of these techniques with the governance contract and the products built around it. The organism analogy describes that composition: specialized parts, an explicit boundary and a record of how they work together.
