Skip to content

KB / framework

Company Dashboard — /company/[ticker]

Last verified

Company Dashboard

Route: /company/[ticker] (e.g. /company/NET). Phase 4.1 of the Single-Name System.

The company dashboard is the narrow-deep half of the single-name system. While the screener sweeps the S&P 500 cheaply to surface candidates, the company dashboard renders everything about one watchlist company in depth.

What it shows (Phase 4.1)

Panels for fundamentals, earnings, estimates, options, sentiment, and ownership ship in Phase 4.2 and 4.3. Until a family is populated, the panel renders a placeholder instead of crashing.

How a company gets on the watchlist

  1. A screener candidate is promoted via the screener’s Promote to watchlist button (Phase 5), or an operator runs scripts/scaffold_company.py <TICKER> manually.
  2. The scaffold script populates co_entity (entity facts) and backfills co_price_daily (2y+ of OHLCV + computed technicals).
  3. The company appears in the Nav dropdown and at /company/<TICKER>.

API surface

Three routes under /api/v1/company/:

RouteDescription
GET /api/v1/company/watchlistAll scaffolded companies — used by the Nav dropdown
GET /api/v1/company/{ticker}Entity header + families_ready map
GET /api/v1/company/{ticker}/pricePrice/technicals panel (last N trading days)

All responses use typed Pydantic sub-objects (Law 5). Unknown/unscaffolded tickers return HTTP 404.

The three-mode switch (Macro / Screener / Company) in Nav.astro now reads co_entity via /api/v1/company/watchlist and builds a per-company dropdown. NET is the first scaffolded entry.

Data sources

Full data model: see improvements/single-name-system-plan.md §5.2.