Session Objective

Audit the SAIL command-center cards and verify whether every metric has a live source read, a clear owner, and a working drill path.

Accomplished

Loaded Data Analytics setup and the SAIL Command Center semantic layer.
Queried deployed Render /api/dashboard-data; it returned mode: mock.
Ran live Salesforce/Litify reads against LITIFY_ORG for the live adapter metrics.
Validated Salesforce object and report IDs used by the app where possible.
Confirmed Google Ads account 3813916687 is reachable through NotFair setup readback.
Ran a live Semrush domain overview report for aguiarinjurylawyers.com.
Queried the Notion SAIL Knowledge Base schema and status counts.
Ran npm test in Repos/sail-command-center: 7 files, 25 tests passed.

The hosted command-center draft is not source-backed for every metric because it is running mock mode.
Every DashboardMetric has owner/source metadata in the TypeScript contract, but metadata presence is not the same as a live read.
Live Salesforce values differ materially from deployed mock values: MVA leads MTD 35 vs deployed 168, MVA signed MTD 17 vs deployed 58, MVA missing source 0 vs deployed 11, marketing YTD total 1260003 vs deployed 776.5K, paid ad spend YTD 893443.72 vs deployed 491.3K.
Several deployed drill paths are generic or pseudo links rather than metric-specific drill paths, including pseudo report IDs such as signed-cases-mtd and generic source homepages.
Owner metadata is present on all metric cards as Sam Aguiar Injury Lawyers, but several cards need a more precise operational owner.

Decide whether to stage code changes that enforce live-only metric cards, hide mock-mode values in production, and convert generic source URLs into metric-specific drill URLs.
Local next dev did not open port 3007 during the audit, matching prior runtime unreliability notes. Verification used deployed API, direct source reads, and tests instead.