Workspace UI System

@prox-os/workspace-ui is the OS-native workspace context and presentation layer for Prox OS. It lets personal homes, team workspaces, community spaces, creator spaces, developer workspaces, and Founder Suite workspaces share a common frontend contract without turning the package into a workspace backend.

Boundary

Workspace UI differs from OS routing, auth, billing, project management, and backend workspace services:

• OS routing remains owned by the shell/runtime and public app contracts.
• Auth, SSO, membership lifecycle, invite delivery, and organization management belong to future runtime/backend packages.
• Billing, plans, seats, and payments belong to billing/provider systems.
• Permission enforcement belongs to auth/security backends; security presentation belongs to @prox-os/security-ui.
• Project management engines, task boards, calendars, CRM, and knowledge bases are future domain apps, not package primitives.

The package owns serializable workspace view models, helper functions, adapter examples, mock data, and reusable React primitives.

Workspace Context Flow

flowchart LR
  Domain["Workspace / space / member / resource"] --> ViewModel["Workspace UI view model"]
  ViewModel --> Primitive["React primitive"]
  Primitive --> Event["OsWorkspaceUiEvent"]
  Event --> Intent["Action intent"]
  Intent --> Runtime["App runtime / backend / shell"]

@prox-os/workspace-ui stops at view models, UI events, and action intents. It does not switch routes, send invites, connect integrations, or mutate workspace membership.

Resource Aggregation Flow

Apps, files, docs, AI sessions, security reviews, collaboration threads, search scopes, notification feeds, and future activity feeds can be represented as OsWorkspaceResource objects. Workspace dashboards and sidebars render those objects as cards and navigation entries.

flowchart LR
  Apps["Apps"] --> Resource["OsWorkspaceResource"]
  Files["Files"] --> Resource
  Docs["Docs"] --> Resource
  AI["AI sessions"] --> Resource
  Security["Security reviews"] --> Resource
  Activity["Activity drafts"] --> Resource
  Resource --> Dashboard["Workspace dashboard"]
  Resource --> Search["Search document adapter"]

Security Flow

Workspace roles, members, resources, and visibility settings can map to @prox-os/security-ui principals, resources, and permission sets. Workspace UI only exposes role and access summaries. It does not evaluate policy or enforce access.

AI Flow

Workspaces, projects, and resources can become OsAiContextSource objects for @prox-os/ai-ui. This allows AI assistants to understand a workspace context while model calls, tool execution, approvals, and runtime policies remain outside this package.

Relationships

• @prox-os/actions: receives workspace action intents.
• @prox-os/security-ui: receives security principals, resources, and permission-set view models.
• @prox-os/files: contributes file/folder resources.
• @prox-os/search: indexes workspaces, members, projects, and resources.
• @prox-os/notifications: receives workspace notification drafts.
• @prox-os/collaboration: receives participants and resource refs.
• @prox-os/ai-ui: receives workspace context sources.
• Future @prox-os/activity: receives workspace activity drafts.

Why Phase 1 Avoids Backends

Phase 1 avoids membership backends, billing, permission enforcement, project management engines, realtime providers, and route ownership because the package is meant to stabilize contracts and UI primitives first. This keeps the API reusable across OS shell, UI Workshop, future workspace apps, and creator/community space experiments.

Future Provider Adapters

• Workspace backend API.
• Membership and invite provider.
• Billing and plan provider.
• Workspace search provider.
• Workspace notification provider.
• Workspace security provider.
• Workspace AI context provider.
• Community and creator space provider.

Data Model Sketch

Workspace
  Space[]
  Member[] -> Role[]
  Resource[]
  Project[] -> Milestone[]
  SettingsSummary
  OnboardingItem[]
  Integration[]
  Stats

Privacy, Access, And Community Considerations

Workspace UI can show public, community, private, unlisted, and restricted states, but it must not imply enforcement. Public creator spaces and community resources need trust, moderation, search, and security handoffs before production exposure. Sensitive founder, developer, and team resources should render explicit visibility and security summaries while leaving access checks to runtime/backend systems.