Alma MVP+ Roadmap

Current MVP+ Scope

Alma MVP+ promotes Prox OS from a browser OS shell toward an AI-native personal Web OS where apps, data, windows, workflows, permissions, and artifacts are controlled through a trusted sidecar agent.

Current implementation is a UI and local workflow prototype. It does not call a real model provider and it does not add backend business code.

MVP 1: Alma Shell Panel

• Shell-level sidecar surface.
• Right-side default placement.
• Left/right setting.
• Drag resize.
• Collapse and close.
• Workspace resizes around the rail.
• Header with sidecar title, model selector, safety mode, settings, and collapse/close controls.

MVP 2: Workflow Cards

Workflow Cards are structured OS workflows with prompt fallback, not just prompt shortcuts.

Initial cards:

• Open Founder Workspace
• Open Dev Workspace
• Review Subscriptions
• Review AI Questions
• Save Current Layout
• Restore Last Layout
• Generate Workspace Draft
• Create Dashboard Artifact
• Open Agent Room

MVP 3: Action Plan And Operation Log

Clicking a workflow shows:

• Action Plan
• Live Operation Log
• Done, failed, running, and needs confirmation states
• Medium-risk confirmation placeholder

MVP 4: Display Options Integration

Display Options controls:

• Alma enabled
• side
• width
• auto-open on startup
• compact mode
• workflow cards visibility
• operation log visibility
• artifact panel visibility
• memory panel visibility
• safety mode default

All current settings are local browser preferences.

MVP 5: BYOK And Model Settings

The sidecar includes:

• provider selector
• local API key input
• save locally button
• clear key button
• model selector
• safety mode selector

This is only a local BYOK prototype. Future production handling requires secure vault, provider adapter, model router, audit sink, and secret redaction.

MVP+ Capability Placeholders

• AI Workspace Generator
• Personal OS Memory / Data Graph
• AI Artifacts pinned to workspace state
• Permissioned OS Action Contract UI
• Workflow Store teaser
• Mobile AI-first Remote OS direction
• Community Social Intelligence placeholder using Prox OS data and explicit permission only
• Multi-Agent Workspace placeholder
• AI-native Pricing layer
• Artifact-to-App pipeline documentation

AI Workspace Generator Direction

Future Workspace Generator should turn a user request into app list, window layout, artifact list, Workflow Cards, required permissions, automation suggestions, and restore policy. The current UI only previews that shape.

Personal OS Memory / Data Graph Direction

Prox OS memory is not ordinary chat memory. It should become app-level memory, workspace-level memory, artifact-level memory, permission-aware data graph, and user-owned data sovereignty. The current UI is a local placeholder with no long-term backend memory.

Workflow Store Direction

Workflow Store should become installable AI workflows for Prox OS. Listings should declare required apps, permissions, OS actions, artifact outputs, audit expectations, and uninstall behavior. It should not be a generic prompt market.

Permission, Audit, And Safety Direction

Every real sidecar action should be structured, typed, permissioned, and auditable. High-impact actions should require explicit confirmation and should remain disabled until backend policy and audit exist.

Next Milestones

1. Convert local workflow definitions into a tested action executor boundary.
2. Add a durable local artifact store before any backend store.
3. Add app AI capability manifest fields.
4. Add provider-neutral model router design without SDK integration.
5. Add audit event schema before enabling high-impact actions.