Skip to content

Product Map

Longsurf is organized as a shared workspace rather than a set of isolated tools. The user, the agent, and the backend services operate on the same durable resources: dashboards, charts, watchlists, news columns, alert rules, notifications, schedules, indicator definitions, and research artifacts.

Product area User-facing scope Owner boundary
Dashboards The saved workspace layout and primary chart grid. docs/vision/resources/dashboards.md, dashboard resource contracts, web dashboard shell.
Charts Price visualization, indicators, drawings, annotations, navigation, and capture. docs/vision/charts.md, chart store, chart widget, TSGraph series runtime.
Widgets Reusable workspace surfaces such as watchlist, heatmap, alerts, indicators, and future news. docs/vision/widgets.md, packages/web/src/widget/*.
Watchlists Hierarchical universes, semantic columns, live prices, fundamentals, and scheduled refresh. docs/vision/resources/watchlists.md, watchlist resource and semantic-column code.
Research Explain, Annotate, Deep Dive, research feed, and agent-authored artifacts. docs/vision/explain.md, docs/vision/ai-features.md, research and annotate packages.
Market data Historical and live bars, trades, quotes, search, and provider-normalized feeds. docs/vision/market/feed.md, MarketFeed, ClickHouse, provider registry.
News News ingestion, deduplication, search, feed columns, article retrieval, and agent context. docs/vision/news/news.md, docs/vision/news/news-feed.md, Newsmux and server news APIs.
Fundamentals Canonical company-owned financial statement observations and latest app projections. docs/vision/market/fundamentals.md, fundamentals ETL and API projection.
Alerts Price, indicator, and rule-based triggers with delivery workflows and agent follow-up. docs/vision/alerts.md, TSGraph alert effects, notifier, alert resource contracts.
Scheduled tasks User-defined recurring or one-time agent prompts. docs/vision/agent-scheduled-tasks.md, packages/openchart/src/agent-schedule.
Authoring Tea Script, indicators, strategy prototypes, generated diagnostics, and Resource Tree paths. docs/vision/tea-script-language.md, docs/vision/indicators.md, docs/vision/resource-tree.md.

Public docs should describe the product from the user’s point of view, then anchor important claims back to their owner boundary. If the owner is generated or runtime-derived, the docs should use a generator or smoke check rather than manual duplication.