App User

/app-user contains identity, profile, visitor, notifications, shortcuts, display, and preference surfaces. Connector-first personal apps live in /app-connectors.

Common UI Model

Connector apps use a shared pattern under app-connectors:

• app header with connector-first and mock-data badges
• provider or source cards
• domain-specific content area
• AI context panel
• permission boundary panel
• data boundary panel
• clear statement that the app is not replacing the external product

Common Permission Model

Phase 1 permissions are descriptive. Read summaries can be shown from mock data. Writes, sends, event edits, full email body reads, precise location, and private notes are modeled as confirmation-required or disabled.

Future production connectors should use OAuth scopes, provider adapters, token vault storage, audit logs, and explicit user confirmation before any write action.

Common AI Context Model

Alma may eventually use these apps to:

• read authorized metadata or summaries
• summarize daily context
• suggest next actions or workspace timing
• prepare meetings and collaboration context
• surface attention queues

Alma should not receive uncontrolled raw provider data. External sends and destructive writes require explicit confirmation.

Current /app-user Surfaces

• User Profile at /app-user/user-profile
• Visitor at /app-user/visitor
• Notifications at /app-user/notifications
• Activity at /app-user/activity
• Personal Data Graph at /app-user/data-graph
• Prompt Studio at /app-user/prompt-studio
• Keyboard Shortcuts at /app-user/keyboard-shortcuts
• Display Options at /app-user/display-options

Personal Data Graph is relationship-first and does not replace Data Room. Prompt Studio manages prompt assets and remains decoupled from AI Sidebar and Command Palette execution in this milestone.

Visitor is a privacy-first OS Home presence dashboard. It shows mock anonymous visitors, known user previews, trusted collaborator previews, broad source categories, app interest, privacy controls, and retention direction without recording real visits or raw identifiers.

Future Connector Backend Direction

Future work may add OAuth providers, provider adapters, token vault storage, MCP tool registration, data sync jobs, webhook ingestion, audit logs, and Alma tool calls. None of those backend pieces are implemented in Phase 1.