CampusOS

CampusOS coordinates identity, permissions, data, events, applications, and tools. It is the trusted control plane; it does not run or trust application code.

What CampusOS owns

• Passkey accounts, authenticated sessions, and Campus addresses
• Package manifests, installations, grants, and application lifecycle intent
• Logical Content metadata, collections, roles, invitations, and transfer grants
• Notification, schedule, workflow, search, and account-scoped MCP policy
• Placement, billing admission, public topology, and sealed credential envelopes
• The trusted shell and all user approval surfaces

What stays outside

Application frontends, workloads, and agents remain untrusted. Runtime owns final machine state; Gateway owns installation data-plane checks; Ingress owns public TLS forwarding; reusable provider secrets are injected only at the Gateway boundary.

Read architecture, authentication, and the permission model for the enforced public developer contract.