One platform.
Separate worlds.
People keep their own identities. Workspaces have boundaries. Intelligence is configured separately from access.
Multi-user and multi-tenant mean different things.
A household can use one workspace with separate logins. A multi-tenant deployment also separates workspaces, their memberships, and their scoped resources. The kernel carries the authenticated principal and tenant through admitted operations. Application-level sharing is an explicit grant, not a consequence of sharing the same server.
Who is acting?
Identity, personal credentials, preferences, and access to applications and resources.
Which workspace?
Membership, tenant policy, scoped records, and permitted shared resources.
Where does it run?
Runtime, available providers, administrator defaults, capacity, and storage.
Separate the configuration decisions.
- Bot routing
- Which specialist receives the task? Jarvis and configured workflows coordinate supported application actions.
- Provider and model
- Which available intelligence handles the request? The kernel resolves a permitted user choice for the turn, a bot default, a fleet default, then a registry default.
- Harness
- How does the agent execute? Supported choices depend on the runtime, installed adapter, credentials, and permissions. A model name is not a harness.
- Payer
- Whose credential funds the call? The payment resolver supports caller credentials, tenant credentials, and a capped operator pool. Selecting a model does not grant access to another person’s credentials.
- Capability provider
- Images, speech, transcription, and video have separate configuration and availability. A text-model default does not configure every creative capability.
Personal choice does not override policy.
User preferences and administrator policy occupy different scopes. An administrator can lock a policy; a preference cannot grant a missing permission. Persistent per-user, per-bot harness editing is runtime-dependent and was not verified end to end for every user in this review. The technical film does not claim universal availability of that control.
Share what helps. Keep the rest scoped.
Grant access to a supported collection or application resource. Keep private material under its own access controls. The host administrator remains a trusted operator: user isolation does not make the underlying computer unreadable to its owner.
Local software, deliberate data paths.
Local storage and a suitable local model can keep the work on your machine. An external model receives the context sent to it. A synced mapped drive sends files to its storage provider. Hosted, self-hosted, and local configurations have different infrastructure and capacity requirements.
What this review established
The technical film explains the current source architecture and uses recorded application views plus labeled diagrams. The native kernel release and fresh-install procedure are documented in the Windows guide. The architecture explanation is not a security certification; installed controls depend on the selected configuration.