On-device agent runtime
Intake selects one responsible business agent. Skills, profile context, memory recall, private knowledge, the task ledger, confirmations, system actions, and rendering run locally.
ON-DEVICE AI ARCHITECTURE
PRISMS AI is a Campus OS for student work—not a cloud chat wrapper. The phone owns agent orchestration, memory, personal context, task continuity, permissions, and output rendering. Cloud services remain replaceable capabilities.
THREE-PLANE DESIGN
This separation reduces the number of systems that can access student content and makes every responsibility explicit.
Intake selects one responsible business agent. Skills, profile context, memory recall, private knowledge, the task ledger, confirmations, system actions, and rendering run locally.
The relay authenticates use, injects provider credentials, forwards bytes, and returns the result. It has no database, admin interface, or content log.
The selected model reasons over the bounded request. It does not own the PRISMS AI agent roster, profile, memory store, personal knowledge, or task state.
The school control plane manages authentication, agent and skill versions, runtime fingerprints, structured knowledge retrieval, knowledge gaps, and anonymous technical diagnostics. It does not receive full conversations, profile bodies, personal-knowledge bodies, agent reasoning, or model answers.
EXECUTION MODEL
Intake routes a new task to at most one business owner. A presentation-only artifact agent may join when the output form requires it.
The owner retrieves school, external, personal-knowledge, or detailed-memory evidence through stable locators before making source-dependent claims.
Stages, models, skills, retrieval, corrections, actions, and artifacts are bound to one durable request receipt and runtime fingerprint.
HONEST BOUNDARY
The relay can process plaintext while forwarding, and the chosen model provider receives the content required for inference. “Stateless” means PRISMS AI does not persist that content in the relay or expose it to the management control plane. Content that must never leave the phone requires an on-device model.
One task, event, confirmation, and correction ledger drives background continuation, notifications, Widget, Live Activity, and privacy-safe Spotlight summaries.
Share Extension, App Intents, Shortcuts, files, photos, speech, Maps, Calendar, and Reminders connect through explicit student intent and iOS permission.