What the host owns

Knolo splits a knowledge system into two jobs. The host moves bytes, talks to users, holds credentials, and decides what to do when something fails. The runtime evaluates a mounted Knowledge Image. It does not take over deployment, networking, or incident response.

That split is the first exam fact. If a design says the runtime owns I/O, or that the host may reorder retrieval, it has the boundary backwards.

Inspect

When you read an integration, name the owner of each step:

• Who loaded the bytes?
• Who mounted them?
• Who is allowed to change the order of results?
• Who tells the user when the mount fails?

The last two belong to different sides. Order belongs to the runtime. The failure message belongs to the host.