Track Layer

Prox OS now treats personal records as a layered system instead of a loose list of apps.

Core principle:

Connectors explain where data comes from. Track apps explain what the user owns and remembers. Scenario apps explain what happened. Spaces organize web work surfaces. OS and Alma explain what it all means.

Four Layers

/app-connectors

/app-connectors is the external connector layer. It is where provider status, import readiness, mock OAuth surfaces, sync state, permission previews, disconnect controls, and cache deletion concepts live.

Examples include Steam, GOG, Letterboxd, IMDB, Spotify, Goodreads, Google Drive, Airtable, Calendar, Contacts, RSS, GitHub, and manual imports. The current implementation is UI-only and does not request OAuth tokens, call provider APIs, or persist imported provider data.

/app-user-connectors/* is deprecated as a canonical route. The shell keeps a compatibility parser that maps old /app-user-connectors/* paths to /app-connectors/* so old links do not break immediately.

/app-track

/app-track is the personal tracking layer owned by Prox OS. It is not a list of external providers. It describes user-owned records and reusable primitives that apps can reference:

• People
• Places
• Devices
• Money
• Sources
• AI Context

The product model also includes seven dimensions:

• Time
• Place
• People
• Device
• Money
• Source
• AI Context

Time is intentionally not a standalone app in v0. Time is the horizontal axis for scene app timelines, sports memories, Alma, Today, Weekly Review, Yearly Review, Life Lens, and future dashboards.

/app-data/* remains a deprecated compatibility alias that normalizes to /app-track/*.

/app

/app contains scenario apps that explain what happened. Food, Work, Books, Series, Music Memory, Collections, Local Services, Documents Vault, AI Team, Personal Blog Studio, Public Profile Builder, Project Museum, Europe Planner, AI Medium, Movies, Places, Game Records, Madrid, Stock Track, and News RSS are scene surfaces over the same seven dimensions.

Scene apps should show time, place, people, device, money, source, and AI context when those dimensions are useful. They should not silently become source-of-truth stores for people, places, devices, or provenance when /app-track can hold those reusable records.

/app-spaces

/app-spaces organizes web work surfaces. For example, /app-spaces/deployments is a deployment workbench for production, preview, local, docs, API, and Storybook surfaces. It is separate from /app-connectors/deployments, which models external platform source metadata.

/app-os and Alma

/app-os and Alma are system-level aggregation and interpretation layers. They are not raw data sources. Their future role is to answer cross-app questions, show Today, generate Weekly Review, surface Life Lens, and explain why a record matters.

Alma must be provenance-aware. If it answers a question, it should be able to show which connector, source, track entity, scene app record, sports memory, Space, and AI inference contributed to the answer.

Current v0 Scope

The current implementation is UI and mock data only:

• no OAuth
• no provider sync
• no backend entity store
• no financial, legal, medical, immigration, or investment advice
• no automatic AI access to sensitive records
• no crawler or external enrichment pipeline

This slice establishes route groups, app manifests, folder placement, UI affordances, and documentation so future backend work has a clearer product skeleton.