The Capability OS is built from distinct runtime planes with different authority. BYOS and LockerPhycer are central because one provides the usable execution substrate and the other protects the host-level execution boundary.
The operating substrate for users, workspaces, API access, integrations, budgets and governed runtime services. This is where the Capability OS becomes an actual usable environment rather than an architecture diagram.
Keeps sensitive host execution authority out of ordinary application containers. Its governed cell-host path verifies signed authority, immutable runtime identity, replay fencing and isolation requirements before host-level execution.
The fail-closed decision boundary. CAPPO determines whether a requested machine consequence fits the authority that was actually granted.
The connection fabric between Veklom services and external capability surfaces. It carries integration without becoming the source of execution authority.
Durable evidence state. Execution outcomes, provenance and reconciliation belong here instead of disappearing with the machine that performed the work.
Connects systems through scoped access, verifiable activity and bounded transport behavior without treating a connection identifier as authority.
Observes declared runtime state and performs pre-bounded recovery actions when approved Veklom services fail. Recovery remains an action with authority and evidence, not an unrestricted host backdoor.
Each plane exists because a different kind of trust or consequence needs a different boundary. Combining all of them into one privileged backend would erase the architecture Veklom is meant to enforce.
