Three objects are easy to blur here, so it is worth separating them: the policy, the profile and the bundle.
The policy is the cluster administrator's ceiling: which images, which hosts, how many replicas and how much CPU any profile may ask for. Admission checks it, and the operator checks it again; where those sit is in the cluster section further down. The profile is the team administrator's choice of where sessions run and with what: image, size, model, storage, egress and the bundle channel to follow. The operator turns that into a network policy and injects the secrets, so none of it is written down in the clear. The bundle is what sessions carry, agents, skills and MCP servers, published as one hashed, immutable document per version. The pod verifies the hash before using it, and each session is pinned to the version it started on, which is what lets an audit say months later which agents and tools applied to a given turn. A new version applies to new sessions; retiring one moves the rest at their next wake, with an event in the log.
On a laptop the same bundle sits under your own layers, built-ins, then the bundle, then your config, then the repository's, then the environment, and later layers win by key. A repository's riskier keys only count once you have trusted the workspace. The faded panel on the right is the more usual arrangement, configuration on every laptop, where each machine decides its own model, approvals and tools and no run is pinned to a version of anything. We think the profile is worth the ceremony mainly because of that panel.