Prox OS Internal Docs
PlatformArchitectureCapabilities

Activity And Events

Activity is the OS-native timeline and event inspection app. It belongs under

Position

Activity is the OS-native timeline and event inspection app. It belongs under /app-user because it represents the user's OS history, app actions, connector syncs, AI action metadata, and raw debug events.

Route

  • Primary route: /app-user/activity
  • Package: @prox-os/user-apps
  • Source: packages/apps/user-apps/src/apps/activity/

Logs are an Activity view rather than a separate app route or product concept.

Event Views

  • Activity Feed: human-readable, productized user timeline.
  • Audit Log: security and permission-relevant events.
  • System Log: runtime and window/app lifecycle events.
  • Connector Sync Log: external sync events and provider boundaries.
  • AI Action History: prompts, approvals, action metadata, and results.
  • Raw Events: structured debug records and payloads.

Current Model

The current UI uses a typed mock OsEvent model with actor, verb, object type, object name, app, Space, source, severity, visibility, summary, technical message, and payload fields.

Future Contract

Future providers can connect Activity to:

  • app runtime events;
  • permission and audit logs;
  • connector sync jobs and webhooks;
  • AI action registry and approval results;
  • workspace and Space event stores;
  • search indexing and notifications.

Activity is not an analytics SDK, telemetry vendor, realtime event bus, or audit backend by itself. Those responsibilities should stay behind provider adapters and permission-aware APIs.

On this page