thoughtleaders-cli 0.6.1__tar.gz → 0.6.3__tar.gz

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "tl-cli",
-  "version": "0.6.1",
+  "version": "0.6.3",
   "description": "ThoughtLeaders CLI — query sponsorship deals, channels, brands, uploads, and intelligence from the terminal",
   "author": {
     "name": "ThoughtLeaders",

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: thoughtleaders-cli
-Version: 0.6.1
+Version: 0.6.3
 Summary: ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence
 Project-URL: Homepage, https://thoughtleaders.io
 Project-URL: Repository, https://github.com/ThoughtLeaders-io/thoughtleaders-cli
@@ -83,14 +83,17 @@ tl uploads show 1174310:0BehkmVa7ak
 
 # Search channels via raw SQL — `tl db pg` against thoughtleaders_channel
 # (run `tl schema pg` once to confirm the live column set).
+# NOTE: For topic / category discovery, prefer the vector recommender over
+# `content_category` equality — `tl recommender top-channels "<tag>"`
+# returns channels ranked by how strongly they load on the topic, not just
+# rows where the single category code matches exactly.
 tl db pg "SELECT id, channel_name, total_views FROM thoughtleaders_channel
           WHERE content_category = <COOKING_CODE> AND total_views >= 100000
           ORDER BY total_views DESC LIMIT 50 OFFSET 0"
 tl db pg "SELECT id, channel_name FROM thoughtleaders_channel
           WHERE is_tl_channel = TRUE LIMIT 200 OFFSET 0"             # all TPP channels (~169)
-# MSN status (media_selling_network_join_date) is scrubbed from the
-# advertiser sandbox view — for MSN-only / non-MSN lookups, the
-# structured filter is the right tool: `tl channels list msn:yes|no`.
+# MSN status: filter on `media_selling_network_join_date IS [NOT] NULL`
+# in the same raw SQL query (column is scrubbed from advertiser sandboxes).
 
 # Show channel detail — accepts numeric ID or channel name.
 # Names that match more than one active channel print a candidate list

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/README.md

@@ -56,14 +56,17 @@ tl uploads show 1174310:0BehkmVa7ak
 
 # Search channels via raw SQL — `tl db pg` against thoughtleaders_channel
 # (run `tl schema pg` once to confirm the live column set).
+# NOTE: For topic / category discovery, prefer the vector recommender over
+# `content_category` equality — `tl recommender top-channels "<tag>"`
+# returns channels ranked by how strongly they load on the topic, not just
+# rows where the single category code matches exactly.
 tl db pg "SELECT id, channel_name, total_views FROM thoughtleaders_channel
           WHERE content_category = <COOKING_CODE> AND total_views >= 100000
           ORDER BY total_views DESC LIMIT 50 OFFSET 0"
 tl db pg "SELECT id, channel_name FROM thoughtleaders_channel
           WHERE is_tl_channel = TRUE LIMIT 200 OFFSET 0"             # all TPP channels (~169)
-# MSN status (media_selling_network_join_date) is scrubbed from the
-# advertiser sandbox view — for MSN-only / non-MSN lookups, the
-# structured filter is the right tool: `tl channels list msn:yes|no`.
+# MSN status: filter on `media_selling_network_join_date IS [NOT] NULL`
+# in the same raw SQL query (column is scrubbed from advertiser sandboxes).
 
 # Show channel detail — accepts numeric ID or channel name.
 # Names that match more than one active channel print a candidate list

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/commands/tl.md

@@ -18,8 +18,8 @@ The user wants to query ThoughtLeaders data. Translate their request into the ri
 ## Examples
 
 - "/tl sold sponsorships for Nike in Q1" → `tl sponsorships list status:sold brand:"Nike" purchase-date-start:2026-01-01 purchase-date-end:2026-03-31`
-- "/tl cooking channels over 100k subs" → `tl db pg "SELECT id, channel_name, total_views FROM thoughtleaders_channel WHERE content_category = <COOKING_CODE> AND total_views >= 100000 ORDER BY total_views DESC LIMIT 50 OFFSET 0"`
-- "/tl mobile-first US cooking channels" → `tl db pg "SELECT id, channel_name, demographic_usa_share FROM thoughtleaders_channel WHERE content_category = <COOKING_CODE> AND demographic_device_primary = 'mobile' AND demographic_usa_share >= 50 ORDER BY total_views DESC LIMIT 50 OFFSET 0"`
+- "/tl cooking channels over 100k subs" → `tl recommender top-channels "cooking" --limit 50` (then post-filter by `subscribers >= 100000` on the resulting IDs)
+- "/tl mobile-first US cooking channels" → `tl recommender top-channels "cooking" --limit 100` (then narrow by `demographic_device_primary = 'mobile'` / `demographic_usa_share >= 50` with raw SQL on the resulting IDs)
 - "/tl Nike's sponsorship activity" → `tl brands show Nike`
 - "/tl run my Q1 report" → `tl reports --json` then `tl reports run <id>`
 - "/tl check my balance" → `tl balance`

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/docs/architecture.md

@@ -48,7 +48,6 @@ All data commands use explicit subcommands: `list`, `show`, `create`/`add`. Runn
 | `tl proposals create --channel <id> --brand <id>` | Create a proposal (free) |
 | `tl uploads list [filters...]` | List video uploads (ES) |
 | `tl uploads show <id> [<id>...]` | Show upload detail(s) by ID |
-| `tl channels list [filters...]` | Search channels. Responses carry boolean `msn` (Media Selling Network) and `tpp` (TL-managed) fields; filterable via `msn:` / `tpp:` tri-state (`yes` / `no` / `both`, default `both`). |
 | `tl channels show <id-or-name>` | Channel detail, including active adspots with price/cost/CPM |
 | `tl channels history <id-or-name>` | Sponsorship history (videos with detected sponsors) |
 | `tl channels similar <id-or-name>` | Vector-similarity recommender. 50 credits; Intelligence plan. Tri-state `msn:` (default `yes`) and `tpp:` (default `both`) filters. Ambiguous names return 400 + candidates list. Hidden `look-alike` alias. |
@@ -75,8 +74,10 @@ Filters are passed as `key:value` pairs after `list`:
 tl sponsorships list status:sold brand:"Nike" purchase-date:2026-01
 tl sponsorships list status:pending send-date:2026-03
 tl uploads list channel:12345 type:longform since:2026-03
-# Channel discovery is raw SQL — the structured `tl channels list` covers
-# only narrow lookups. Default to:
+# Channel discovery is raw SQL — default to:
+# (For topic/category lookups, `tl recommender top-channels "<tag>"` is a
+# better starting point than `content_category` equality — it ranks by
+# how strongly each channel loads on the topic, not exact-match.)
 tl db pg "SELECT id, channel_name, total_views FROM thoughtleaders_channel
           WHERE content_category = <COOKING_CODE> AND language = 'en'
             AND total_views >= 1000000
@@ -387,7 +388,6 @@ Most CLI endpoints can reuse existing views/utilities rather than being built fr
 | **`POST /api/cli/v1/sponsorships`** | `api/create-bulk-proposal` (`CreateBulkProposalView`) + MCP `save_proposals_for_email` in `mcp/proposals.py` | Adapt for single-proposal creation from CLI params |
 | **`GET /api/cli/v1/uploads`** | `api/articles` (`ArticlesView`) — full ES article search with configurable columns, filters, aggregation. Already handles channel format, brand filters, content type. | Translate CLI filters → ArticlesView params. Restrict to VIDEO format. |
 | **`GET /api/cli/v1/uploads/<id>`** | `api/articles/<id>` (`SingleArticleView`) | Add CLI envelope |
-| **`GET /api/cli/v1/channels`** | `api/v2/external-youtube-thoughtleaders` (`ExternalYoutubeThoughtleadersView`) — rich ES-powered channel search with configurable columns, aggregation. Also `api/v1/channels/dropdown` for simple name search. | Translate CLI filters → existing view params |
 | **`GET /api/cli/v1/channels/<id>`** | `api/v1/channels/<id>` (`ChannelAPIViewSet.retrieve`) — returns channel detail with loyalty metrics | Add CLI envelope + breadcrumbs linking to snapshots |
 | **`GET /api/cli/v1/brands/<query>`** | `api/v1/brands` (`BrandsViewSet`) for brand lookup + `api/articles` with `sponsored_brand_mentions` filter for intelligence data. Also `api/brand/<id>/matcher` (`BrandChannelMatcherAPI`) for channel discovery. | Combine brand lookup + ES brand mention query |
 | **`GET /api/cli/v1/snapshots/channel/<id>`** | `api/v2/channel-history` (`ChannelHistoryView`) — already queries Firebolt `channel_metrics` with pagination, uses `get_firebolt_query_results()` utility. Also `api/v2/external-channel-total-views` for time-series with granularity. | Direct reuse — just translate params + add CLI envelope |

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "thoughtleaders-cli"
-version = "0.6.1"
+version = "0.6.3"
 description = "ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence"
 readme = "README.md"
 license = "MIT"

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/skills/tl/SKILL.md

@@ -56,7 +56,7 @@ The centre of the data model is **Sponsorships** — business relationships betw
   - **Proposals** — matches that have been proposed to both sides to consider
   - **Deals** — contractually agreed-upon sponsorships (sold), either in production or published
 
-Sponsorships are sometimes called "Ads" or "Ad campaigns". An obsolete name for "sponsorship" is an "adlink".
+Sponsorships are sometimes called "Ads" or "Ad campaigns". **"AdLink"** is another name for the same thing — it's the term the database uses (`thoughtleaders_adlink`) and shows up across internal code, schema docs, and AM Slack threads. Treat "sponsorship" and "adlink" as interchangeable; the user-facing word is "sponsorship," the engineering/DB word is "adlink."
 
 The CLI has shortcut commands for each type: `tl matches`, `tl proposals`, `tl deals`. These filter `tl sponsorships` by status.
 
@@ -130,8 +130,7 @@ tl proposals show <id>                 # Proposal detail (2 credits)
 tl proposals create --channel <id> --brand <id>  # Create proposal (free)
 tl uploads list [filters...]           # Video uploads from ES — list curve, mult 1.0
 tl uploads show <id>                   # Upload detail (2 credits)
-tl channels list [filters...]          # Channel search — list curve, mult 1.0
-tl channels show <id-or-name>          # Channel detail (2 credits; accepts numeric ID or name)
+tl channels show <id-or-name>          # Channel detail (2 credits; accepts numeric ID or name) — for channel search use raw SQL on thoughtleaders_channel
 tl channels history <id-or-name>       # Sponsorship history (5 credits/result, linear)
 tl channels similar <id-or-name>       # Vector-similarity recommender (50 credits flat; Intelligence plan)
 tl brands show <id-or-name>            # Brand detail (1 credit)
@@ -155,7 +154,7 @@ tl comments add <adlink-id> "msg"      # Add comment (free)
 
 **"List curve"** above means non-linear pricing: `cost = 1 + mult × 0.126 × n^1.2`. The flat 1-credit setup applies to every list call; the `mult` reflects per-resource complexity. `tl db {pg,fb,es}` shares the same curve at mult=1.4. Concrete totals:
 
-| Rows | mult=1.0 (channels, brands, comments, uploads, sponsorships) | mult=1.2 (snapshots) | mult=1.3 (reports) | mult=1.4 (db.pg / db.fb / db.es) |
+| Rows | mult=1.0 (comments, uploads, sponsorships) | mult=1.2 (snapshots) | mult=1.3 (reports) | mult=1.4 (db.pg / db.fb / db.es) |
 |---:|---:|---:|---:|---:|
 | 1 | 1 | 1 | 1 | 1 |
 | 10 | 3 | 3 | 4 | 4 |
@@ -360,7 +359,7 @@ tl db pg "SELECT id, channel_name, demographic_device_primary, total_views
 
 For per-country share beyond the recommender's "USA share" tag, use the `demographic_geo` jsonb in raw SQL: `(demographic_geo->>'gb')::int >= 25`. Same pattern with `demographic_device->>'mobile'` for non-primary device shares.
 
-**MSN status (`media_selling_network_join_date`) is scrubbed from the advertiser sandbox view.** Raw SQL can't filter on it from an advertiser context; use the structured `tl channels list msn:yes|no|both` for MSN-specific lookups, then drop down to SQL on the resulting IDs (`WHERE id IN (...)`) for further analysis.
+**MSN status (`media_selling_network_join_date`) is scrubbed from the advertiser sandbox view.** Raw SQL can't filter on it from an advertiser context. For MSN-only / non-MSN lookups, run the same raw SQL with `media_selling_network_join_date IS [NOT] NULL` from a context that has access to it (full-access role), or rely on the recommender's MSN-aware filters: `tl recommender top-channels "<tag>" msn:yes|no|all`.
 
 ### Output flags
 - `--json` — structured JSON (use this for parsing)
@@ -398,7 +397,7 @@ Every query costs credits. Before running expensive queries:
 Users only see data their plan allows:
 - **Media buyers** see deals where their org is the brand. They see `price` but never `cost`.
 - **Media sellers** see deals where their org is the publisher. They see `cost` but never `price`.
-- **Intelligence plan** required for `tl brands`, full `tl channels list` search, and full `tl uploads list`.
+- **Intelligence plan** required for `tl brands`, the full `tl recommender` surface, and full `tl uploads list`.
 - **Paid plan** required for `tl snapshots`.
 
 ## Important: Status Labels

thoughtleaders_cli-0.6.3/skills/tl/references/business-glossary.md

@@ -0,0 +1,243 @@
+# ThoughtLeaders Business Glossary
+
+Maps business terms to database concepts.
+
+## Revenue & Deal Lifecycle
+
+| Business Term | DB Concept | Notes |
+|--------------|------------|-------|
+| **Revenue / Sold ad** | `adlink.publish_status = 3` (SOLD) | Only status=3 counts as real revenue |
+| **Gross ads / Gross revenue** | `SUM(adlink.price)` where sold | Total advertiser spend |
+| **Net revenue / TL profit** | `price - cost` per adlink | What TL earns as a company |
+| **Cost** | `adlink.cost` | What the channel earns |
+| **Price** | `adlink.price` | What the advertiser pays |
+| **Closed-lost** | `publish_status IN (4, 5, 9)` | All three rejection statuses |
+| **Open opportunity** | `publish_status IN (0, 2, 6, 7, 8)` | Pipeline — not revenue, not lost |
+| **Proposal Approved** | `publish_status = 6` | AM approved to show to brand — NOT brand approval. Internal gate only. |
+| **Pending** | `publish_status = 2` | Brand has agreed — this is the real high-intent signal |
+| **Weighted pipeline** | `SUM(weighted_price)` for open opps | Pre-calculated on save |
+| **Ad is live** | `publish_date IS NOT NULL` | Until publish_date is set, ad is not on YouTube |
+| **Cancellation risk** | Sold but `publish_date IS NULL` | Sold deals without publish_date can still be canceled |
+
+## Performance Grade (`adlink.performance_grade`)
+
+| Value | Label | Description |
+|-------|-------|-------------|
+| 0 | Pending | Not yet graded (treat as NULL) |
+| 1 | Loser | Underperforming ad — do not renew |
+| 2 | Neutral | Mixed results — test one more time, ideally at a better rate. Second test determines if channel becomes Loser or Winner |
+| 3 | Winner | High-performing ad — should always be renewed |
+
+**Renewal logic:** All Winners should be renewed. Neutrals get one more test (ideally at a lower CPM), then reclassified as Winner or Loser.
+
+## View Guarantees
+
+| Field | Description |
+|-------|-------------|
+| `adlink.impressions_guarantee` | The number of views guaranteed for the ad (bigint). 0 or NULL = no guarantee. |
+| `adlink.view_guarantee_hit_date` | Timestamp when the guarantee was met. NULL = not yet hit or no guarantee. |
+| `adlink.projected_views_at_purchase_date` | Projected views at time of purchase (used for CPM estimation). |
+
+## Entities
+
+| Business Term | DB Table | Notes |
+|--------------|----------|-------|
+| **Deal / Sponsorship** | `thoughtleaders_adlink` | One brand ↔ channel placement |
+| **Brand** | `thoughtleaders_brand` | Advertiser entity (the buying-side brand) |
+| **Brand profile** | `thoughtleaders_profile` | Advertiser entity / account |
+| **Organization** | `thoughtleaders_organization` | Parent entity for profiles |
+| **Channel** | `thoughtleaders_channel` | YouTube channel |
+| **Ad Spot (Catalogue item)** | `thoughtleaders_adspot` | TL's catalogue of buyable placements. Price/cost on adspot are *list prices* only — each adlink (instance) can have completely different price/cost |
+| **Campaign** | `dashboard_campaign` | Groups multiple deals |
+
+## Ad Spots & Channels
+
+- A channel can have **multiple ad spots** because different people sell the same channel (talent manager, direct, multiple agencies)
+- Ad spots are the **catalogue** — adlinks are **instances** of catalogue items
+- Price/cost on adspot = list/catalog values; price/cost on adlink = actual deal values
+- **Only one active adspot with integration=mention per channel at any time** (MSN rule)
+
+## Ownership & Accountability
+
+| Field | Model | Meaning |
+|-------|-------|---------|
+| `owner_sales_id` | `adlink` | **Most important.** Person responsible for closing the deal and for the revenue. Final accountability. |
+| `owner_advertiser_id` | `adlink` | Brand-side owner for this specific deal |
+| `owner_publisher_id` | `adlink` | Channel-side owner for this specific deal |
+| `owner_advertiser_id` | `profile` | **Account owner.** Who owns the brand relationship overall. Often same person as owner_sales on adlinks, but not always. |
+| `owner_publisher_id` | `profile` | Channel relationship owner on the profile level |
+| `owner_sales_id` | `profile` | Sales owner at profile level |
+
+**Key insight:** Ownership exists on both `profile` (account-level) and `adlink` (deal-level). For revenue attribution, always use `adlink.owner_sales_id`.
+
+## MSN (Media Selling Network)
+
+- Channels where TL has **≥80% confidence** they can buy an ad tomorrow
+- Key data: **who is the contact** to buy the ad from
+- `thoughtleaders_channel.media_selling_network_join_date` = when channel joined MSN
+- `thoughtleaders_channel.is_tl_channel` = TPP/VIP channel (subset of MSN)
+- **Rule:** Only one active adspot with `integration=mention` per channel at any time
+- MSN quality depends on having current, accurate contact info
+
+## Channels & Audience
+
+Vocabulary that AMs use about channels, mapped to the actual DB encoding. Most of these are silent-wrong-name traps where the team term doesn't match the column name.
+
+| Business Term | DB Concept | Notes |
+|---------------|------------|-------|
+| **Subscribers** | `thoughtleaders_channel.reach` (bigint) | ⚠️ There is no `subscribers` column. The DB column is `reach`. |
+| **MSN member** | `media_selling_network_join_date IS NOT NULL` | Whole MSN pool. NOT `is_tl_channel = true` — that's the VIP subset only. |
+| **TPP / VIP channel** | `is_tl_channel = true` | The small VIP subset of MSN (~144 channels at 100k+ reach). Don't use as a general "MSN" proxy — silently drops ~98% of MSN. |
+| **Active channel** | `is_active = true AND last_published >= CURRENT_DATE - INTERVAL '120 days'` | Standard filter for "channel is live and posting." Always include `is_active = true` in channel queries. |
+| **Country / Geo of a deal** | `thoughtleaders_channel.country` (ISO 3166-1 alpha-2) | `thoughtleaders_adlink` has NO geo column. Geo for sponsorships almost always means the channel's country. |
+| **Language of a channel** | `thoughtleaders_channel.language` (short ISO 639 code) | ⚠️ Short ISO 639 codes — NOT BCP-47. Mostly 2-letter ISO 639-1 (`en`, `pt`, `hi`) for major languages; occasionally 3-letter ISO 639-2/3 (`arc`, `arz`, `ase`, `ceb`) for languages without a 2-letter code. Filtering with BCP-47 (`en-US`/`pt-BR`) returns zero. Don't assume `LENGTH(language) = 2`. |
+| **Brand on a deal** | `adlink → creator_profile_id → profile_brands.profile_id → profile_brands.brand_id → brand` | 3-table chain. There is NO direct `brand_id` on adlink. See [postgres-schema.md](postgres-schema.md). |
+| **Channel on a deal** | `adlink.ad_spot_id → adspot.channel_id → channel` | NO direct `channel_id` on adlink. |
+| **Brand-virgin / VPN-virgin (etc.)** | Channel has no `adlink` row joined to any of the target brand_ids | Used in candidate sourcing ("never sponsored by any VPN brand"). Caveat: only catches TL-brokered deals; channels that ran the brand directly (no TL involvement) appear "virgin" but aren't — cross-check ES `sponsored_brand_mentions` before final outreach. |
+| **Channel quality score** *(internal-only)* | `sponsorship_score` on the indexed channel doc + `thoughtleaders_channel.sponsorship_score` (PG) | TL-internal composite score combining engagement, fulfillment, and historical sponsorship performance. **Use it internally to rank/tiebreak candidates, but do NOT quote the raw decimal in AM-facing or external output** — the score isn't documented to AMs and the absolute value isn't meaningful without context. In AM-facing prose, translate to qualitative language: "top-quartile fit," "strongest quality score in the candidate set," "high sponsorship-quality signal." |
+
+## Projected Views (PV) — three related but distinct fields
+
+AMs use "PV" loosely. There are three different DB fields, each meaning something different:
+
+| AM Term | DB Field | What it actually is |
+|---------|----------|---------------------|
+| **PV (channel baseline)** | `thoughtleaders_channel.impression` | Channel-level "typical views per video" used as CPM denominator. ⚠️ Coverage and freshness vary; cross-check Firebolt longform median for hero-tier deals. |
+| **PV (deal-specific)** | `thoughtleaders_adlink.projected_views_at_purchase_date` | Snapshot of projected views at the moment the deal was sold. Use this for historical CPM analysis. |
+| **VG (View Guarantee)** | `thoughtleaders_adlink.impressions_guarantee` | The contractual minimum views the brand is guaranteed. 0/NULL = no guarantee. NOT the same as PV — VG is a contractual floor, PV is an estimate. |
+
+When an AM says "what's the PV on this channel?" — they almost always mean `channel.impression`. When they say "what was the PV on this deal?" — they mean `adlink.projected_views_at_purchase_date`. When they say "did we hit the VG?" — they mean `adlink.view_guarantee_hit_date IS NOT NULL`.
+
+## Channel Sponsorship Signals
+
+Two derived metrics on the indexed channel doc that AMs use to qualify a channel before pitching. Both are pre-aggregated in the search index, computed against historical sponsored-content patterns.
+
+| AM Term | Underlying field | Definition | What an AM does with it |
+|---------|------------------|------------|--------------------------|
+| **Fulfillment rate** | `fulfillment_rate` (channel doc, scaled_float) | The share of a channel's content that is sponsored — `sponsored / all` content over the measurement window, expressed as a fraction. Higher = the channel reliably delivers paid integrations. | Quality signal: a high fulfillment rate means past brands have actually run on this channel, not just been pitched. AMs use it to filter out "looks promising but never closes" channels. |
+| **Renewal rate** | `renewal_rate` (channel doc, scaled_float) | The rate at which a brand-channel sponsorship relationship repeats over time, computed from clusters of sponsorship deals between a single subject (channel or brand) and its linked entities, with date-distribution heuristics (default 365-day max interval). | Loyalty signal: a high renewal rate means brands keep coming back to this channel. AMs use it to identify "sticky" channels worth premium positioning, and to flag low-renewal channels as one-shots. |
+
+Both metrics live on the channel side of the indexed video docs (the `channel.*` nested object). Channel pages in TL's product surface these as quality scores; in AM-facing reports, you can quote them as percentages (`0.45 → "45% renewal rate"`).
+
+## Industry Terms vs TL Vocabulary
+
+Some MarTech-industry terms are **NOT used at TL.** When you encounter them in a question, prompt, or message — translate to TL-native vocabulary before querying or answering. If you see one of these on the left, swap to the right.
+
+| Industry term (don't use) | TL-native equivalent | Notes |
+|---------------------------|----------------------|-------|
+| **Flight** (a single ad-run instance) | **deal** / **sponsorship** / **adlink** | One row in `thoughtleaders_adlink`. "Every flight" → "every deal." |
+| **Flight** (a campaign time window) | **window** / **campaign window** | "60-day flight" → "60-day window." Or just specify dates. |
+| **Flight cadence** | **deal cadence** / **renewal cadence** | How often deals run on a channel. |
+| **Flight-over-flight** | **deal-over-deal** / **renewal-over-renewal** | Comparing successive deals on the same channel. |
+| **Post-flight** | **post-publish** / **post-deal** | After the deal/ad has run. |
+
+**General rule:** if you reach for an ad-industry term that isn't already in this glossary, check whether TL actually uses it before introducing it.
+
+## Infrastructure Terms — Translate Before User-Facing Output
+
+AMs and brand-facing readers don't know (or care) what Postgres, Elasticsearch, or Firebolt are. **When surfacing data in any AM-facing or external output, translate infrastructure names and column names to business language.** Internal engineering chats are the only place these raw terms belong.
+
+| Internal term (don't use in AM/external output) | AM-friendly translation | What it actually is |
+|---|---|---|
+| **PG** / **Postgres** / `thoughtleaders_*` table names / `tl db pg` invocations | **"our deals data"** / **"TL's deals book"** / **"our pipeline"** | The relational DB that holds deals, brands, channels, profiles — the source of truth for what TL has brokered |
+| **ES** / **Elasticsearch** / `tl-platform-*` indices / `tl db es` invocations | **"TL's YouTube content tracking"** / **"our video index"** / **"our scraped video data"** | The search index that holds tracked YouTube videos, brand mentions, transcripts — the wider market view |
+| **Firebolt** / `article_metrics` / `channel_metrics` / `tl db fb` invocations | **"historical metrics"** / **"view-curve data"** | The data warehouse that stores time-series snapshots — used for trend analysis |
+| `sponsored_brand_mentions` (ES field) | **"tracked sponsorships"** / **"logged sponsored mentions"** / **"sponsored videos we tracked"** | Per-video brand-ID tags showing which brands paid for that video |
+| `organic_brand_mentions` (ES field) | **"organic / unpaid mentions"** | Brand mentioned in a video without a paid sponsorship |
+| `publish_status = 3` | **"sold"** | Already in glossary; never write the integer to AMs |
+| `creator_profile_id` chain / 3-table join | **"the brand's record"** | Engineering plumbing for brand lookup; AMs just hear "the brand" |
+| `reach` (PG column) | **"subscribers"** | Already in glossary; AMs say subscribers, SQL says reach |
+| `impression` (PG column) | **"projected views"** / **"PV"** | Already in glossary; flagged for reliability caveats |
+
+### Common translations in context
+
+When you'd write internally → write this for an AM:
+
+| Internal phrasing | AM-friendly phrasing |
+|---|---|
+| "Pulling ES `sponsored_brand_mentions` for the market view" | "Cross-checking against our video tracking data" |
+| "ES has 11,304 sponsored mentions of Robinhood" | "Robinhood ran 11,304 sponsored videos in the last 12 months" |
+| "PG has 139 sold adlinks for brand_id=29332" | "We sold Investing.com 139 sponsorships" |
+| "Firebolt `article_metrics` 180-day longform median" | "Recent typical-video views over the last 6 months" |
+| "Filter on `publish_status=3` AND `purchase_date>=2025-01-01`" | "Sold deals since the start of 2025" |
+
+**General rule:** if a sentence mentions `tl db pg|fb|es` invocations, table names, column names, or integer codes, ask yourself — *would the AM Slack me a question using this language?* If no, translate. The infrastructure exists to serve the AM; the AM shouldn't have to know it exists.
+
+## Teams & Ownership
+
+### Brand-led Revenue (Sales / Account Management)
+
+These teams close deals and manage brand relationships. Revenue is attributed via `adlink.owner_sales_id`.
+
+**Emma's team:**
+| Person | auth_user.id | Owner field |
+|--------|-------------|-------------|
+| Emma | 11158 | `adlink.owner_sales_id` |
+| Orli | 2042 | `adlink.owner_sales_id` |
+| Eli | 20836 | `adlink.owner_sales_id` |
+| Grace | 20835 | `adlink.owner_sales_id` |
+| Mark | 23979 | `adlink.owner_sales_id` |
+| Abbie | 23978 | `adlink.owner_sales_id` |
+| Ariella | 23977 | `adlink.owner_sales_id` |
+
+**Nicole's team:**
+| Person | auth_user.id | Owner field |
+|--------|-------------|-------------|
+| Nicole | 9929 | `adlink.owner_sales_id` |
+| Maika | 5412 | `adlink.owner_sales_id` |
+| Yuval | 14252 | `adlink.owner_sales_id` |
+| Revital | 14251 | `adlink.owner_sales_id` |
+
+### Network Growth (SDR / Partnerships) — Pauline's team
+
+Responsible for growing the MSN (new channels) and MBN (new brands). SDR outreach on both sides.
+
+| Person | auth_user.id | Role | Owner field |
+|--------|-------------|------|-------------|
+| Pauline | 218 | Team lead | `adlink.owner_publisher_id` (channel handovers) |
+| Morgan | 5710 | Channel SDR | — |
+| Jen | 873 | Channel SDR | — |
+| Ruby Jean | 9011 | Channel SDR | — |
+| Molly | 11361 | Channel SDR | — |
+| Pierra | 11323 | Brand SDR | — |
+| Nian | 8795 | Brand SDR | — |
+
+### Ad Ops — Jody's team
+
+Manages getting sold ads published. `profile.owner_publisher_id` = ad ops manager of an account.
+
+| Person | auth_user.id | Owner field |
+|--------|-------------|-------------|
+| Jody | 71 | `profile.owner_publisher_id` (account-level ad ops owner) |
+| Kathleen | 9274 | `profile.owner_publisher_id` |
+| Shane | 18159 | `profile.owner_publisher_id` |
+| Kevin | 5799 | `profile.owner_publisher_id` |
+| Airis | 5804 | `profile.owner_publisher_id` |
+| Lara | 10743 | `profile.owner_publisher_id` |
+| Josh | 11592 | `profile.owner_publisher_id` |
+
+### Querying by team
+
+```sql
+-- Emma's team pipeline
+SELECT ... FROM thoughtleaders_adlink al
+WHERE al.owner_sales_id IN (11158, 2042, 20836, 20835, 23979, 23978, 23977)
+
+-- Nicole's team pipeline
+SELECT ... FROM thoughtleaders_adlink al
+WHERE al.owner_sales_id IN (9929, 5412, 14252, 14251)
+
+-- All brand-led revenue (both teams)
+SELECT ... FROM thoughtleaders_adlink al
+WHERE al.owner_sales_id IN (11158, 2042, 20836, 20835, 23979, 23978, 23977, 9929, 5412, 14252, 14251)
+
+-- Pauline's network growth team (channel SDRs)
+-- owner_publisher_id on adlink for channel-side work
+SELECT ... FROM thoughtleaders_adlink al
+WHERE al.owner_publisher_id IN (218, 5710, 873, 9011, 11361)
+
+-- Jody's ad ops team accounts (profile-level ownership)
+SELECT ... FROM thoughtleaders_profile p
+WHERE p.owner_publisher_id IN (71, 9274, 18159, 5799, 5804, 10743, 11592)
+```
+

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/skills/tl/references/postgres-schema.md

@@ -42,7 +42,7 @@ The main deals table. Each row = one sponsorship deal between a brand and a YouT
 | `weighted_price_currency` | varchar | Always USD |
 | `cost` | numeric | Cost to TL |
 | `ad_spot_id` | int FK | → `thoughtleaders_adspot.id` |
-| `creator_profile_id` | int FK | → brand/advertiser profile |
+| `creator_profile_id` | int FK | → `thoughtleaders_profile.id` (the brand/advertiser's profile). ⚠️ The table is named `thoughtleaders_profile`, NOT `creator_profile` — the "creator_" prefix lives on the FK column, not the table. |
 | `owner_advertiser_id` | int FK | → `auth_user.id` (brand-side owner) |
 | `owner_publisher_id` | int FK | → `auth_user.id` (channel-side owner) |
 | `owner_sales_id` | int FK | → `auth_user.id` (sales rep) |
@@ -125,13 +125,50 @@ A channel can have multiple adspots (different sellers: talent manager, direct,
 | Column | Type | Description |
 |--------|------|-------------|
 | `id` | int | Primary key |
-| `channel_name` | varchar | Display name |
-| `external_channel_id` | varchar | YouTube channel ID (`UCxxxxxx`). ⚠️ There is NO `youtube_id` column. |
+| `channel_name` | varchar | Display name. ⚠️ The column is `channel_name`, NOT `name`. |
+| `external_channel_id` | varchar | YouTube channel ID (e.g., `UCxxxxxx`). ⚠️ There is NO `youtube_id` column — use this one. |
 | `url` | varchar | Channel URL |
-| `media_selling_network_join_date` | date/timestamptz | When channel joined MSN |
-| `is_tl_channel` | boolean | True = TPP/VIP channel |
+| `reach` | bigint | Subscriber count. ⚠️ There is NO `subscribers` column — `reach` is the subscriber count. Many internal docs and outputs use the word "subscribers"; in SQL, always query `reach`. |
+| `media_selling_network_join_date` | date/timestamptz | When channel joined MSN. **MSN membership = this column IS NOT NULL.** |
+| `is_tl_channel` | boolean | True = TPP/VIP channel (the small VIP subset, ~144 channels at 100k+ reach). ⚠️ **`is_tl_channel` is NOT the MSN flag.** Naive `WHERE is_tl_channel = true` as an "MSN filter" silently drops ~98% of the MSN pool (8,652 → 144 at 100k+). For MSN, use `media_selling_network_join_date IS NOT NULL`. |
+| `content_category` | int | Content category code (1–22). See "`content_category` Constants" below for the code → label mapping. ⚠️ **Data-quality notes:** (1) per-row category assignments are often inconsistent with the official label (e.g. cat 15 = Technology, but many top-`reach` channels in cat 15 are clearly Entertainment). (2) Several codes are essentially unused in practice — codes 1, 2, 4, 6, 7, 8, 9, 11, 13 (Backend Development, Design, Frontend Development, Marketing, Mobile Development, Sales, Travel, Photography, Personal Finance) return ~0 active high-reach channels. Most travel creators land under Lifestyle (5), not Travel (9). The label table below is authoritative; the per-row assignment is best-effort. **For topic/category discovery, prefer `tl recommender top-channels "<tag>"` (ranked) over `WHERE content_category = <code>` (equality). |
+| `is_active` | boolean | Whether the channel is active. ⚠️ **Always include `is_active = true` in channel queries** unless explicitly looking for archived rows. |
+| `country` | varchar | Channel's primary country (ISO 3166-1 alpha-2 code, e.g. `US`, `GB`, `BR`). Often the cleanest answer to "geo" questions on sponsorships (since adlink itself has no geo). May be NULL or blank on ~10% of channels. |
+| `language` | varchar | Primary content language. ⚠️ **Short ISO 639 codes — NOT BCP-47.** Mostly 2-letter ISO 639-1 (`en`, `pt`, `hi`) for major languages; occasionally 3-letter ISO 639-2/3 (`arc`, `arz`, `ase`, `ceb`) for languages without a 2-letter code. Filtering with `language = 'en-US'` returns zero rows. **Don't assume `LENGTH(language) = 2`** — that silently drops the 3-letter long-tail. May be NULL on ~10% of channels. |
+| `last_published` | date | Date of the channel's most recent video. Use for "is the channel still active?" filters — e.g. `last_published >= CURRENT_DATE - INTERVAL '120 days'`. |
+| `sponsorship_score` | double precision | TL-internal channel quality score (higher is better). Useful as a tiebreaker when ranking candidate channels. |
+| `description` | text | LLM-generated description of the channel. Sometimes useful as a regex-target for thematic filtering when the integer category is too coarse (e.g. filtering "Technology" cat 15 down to actual tech reviewers via keywords like `tech|gadget|review|software`). |
 | `evergreenness` | float | Cached evergreen score |
 
+#### `content_category` Constants
+
+Source of truth: `thoughtleaders.taxonomies.ContentCategory` (Django `IntEnum` in the main `thoughtleaders` repo).
+
+| Value | Constant | Pretty Label |
+|-------|----------|--------------|
+| 1 | BACKEND_DEVELOPMENT | Backend Development |
+| 2 | DESIGN | Design |
+| 3 | ENTREPRENEURSHIP | Entrepreneurship |
+| 4 | FRONTEND_DEVELOPMENT | Frontend Development |
+| 5 | LIFESTYLE | Lifestyle |
+| 6 | MARKETING | Marketing |
+| 7 | MOBILE_DEVELOPMENT | Mobile Development |
+| 8 | SALES | Sales |
+| 9 | TRAVEL | Travel |
+| 10 | BUSINESS | Business |
+| 11 | PHOTOGRAPHY | Photography |
+| 12 | GENERAL_KNOWLEDGE | General Knowledge |
+| 13 | PERSONAL_FINANCE | Personal Finance |
+| 14 | NEWS_POLITICS | News & Politics |
+| 15 | TECHNOLOGY | Technology |
+| 16 | GAMING | Gaming |
+| 17 | FOOD | Food |
+| 18 | SPORTS | Sports |
+| 19 | HOWTO | How To & Crafts |
+| 20 | ENTERTAINMENT | Entertainment |
+| 21 | HEALTH_FITNESS | Health & Fitness |
+| 22 | MUSIC | Music |
+
 ### `auth_user` (Django Users)
 
 Standard Django user table. Used for owner lookups.

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/src/tl_cli/__init__.py

@@ -1,3 +1,3 @@
 """ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence."""
 
-__version__ = "0.6.1"
+__version__ = "0.6.3"

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/src/tl_cli/commands/channels.py

@@ -11,7 +11,7 @@ from tl_cli.filters import parse_filters
 from tl_cli.hints import detail_hint
 from tl_cli.output.formatter import detect_format, output, output_single
 
-app = typer.Typer(help="YouTube channels (search, detail, and similar-channel recommendations)")
+app = typer.Typer(help="YouTube channels (detail, history, and similar-channel recommendations)")
 
 # Columns for the `similar` endpoint result table. The server enriches every
 # row so the user can size up each suggestion without follow-up queries.
@@ -25,50 +25,6 @@ SIMILAR_COLUMN_CONFIG = {
 }
 
 
-@app.callback(invoke_without_command=True)
-def channels(ctx: typer.Context) -> None:
-    """YouTube channels — search and detail."""
-    if ctx.invoked_subcommand is None:
-        ctx.invoke(list_cmd, args=[], json_output=False, csv_output=False, md_output=False, limit=50, offset=0)
-
-
-@app.command("list")
-def list_cmd(
-    args: list[str] = typer.Argument(None, help="Filters (key:value pairs). Run 'tl describe show channels' for available filters."),
-    json_output: bool = typer.Option(False, "--json", help="JSON output"),
-    csv_output: bool = typer.Option(False, "--csv", help="CSV output"),
-    md_output: bool = typer.Option(False, "--md", help="Markdown output"),
-    toon_output: bool = typer.Option(False, "--toon", help="TOON output (token-efficient for LLMs)"),
-    limit: int = typer.Option(50, "--limit", "-l", help="Max results"),
-    offset: int = typer.Option(0, "--offset", help="Pagination offset"),
-) -> None:
-    """Search channels with optional filters.
-
-    Examples:
-        tl channels list                                  # List channels
-        tl channels list category:cooking min-subs:100k   # Search with filters
-    """
-    fmt = detect_format(json_output, csv_output, md_output, toon_output)
-    filters = parse_filters(args or [])
-
-    client = get_client()
-    try:
-        params = {**filters, "limit": str(limit), "offset": str(offset)}
-        data = client.get("/channels", params=params)
-        for r in data.get("results", []):
-            r["channel_id"] = r.pop("id", None)
-        output(
-            data,
-            fmt,
-            columns=["channel_id", "name", "url", "msn", "tpp", "subscribers", "gender", "countries", "category", "sponsorship_score", "trend"],
-            title="Channels",
-        )
-    except ApiError as e:
-        handle_api_error(e)
-    finally:
-        client.close()
-
-
 @app.command("show")
 def show_cmd(
     channel_ref: str = typer.Argument(..., help="Channel ID (numeric) or name (partial match, must be unique)"),

{thoughtleaders_cli-0.6.1 → thoughtleaders_cli-0.6.3}/uv.lock

@@ -388,7 +388,7 @@ wheels = [
 
 [[package]]
 name = "thoughtleaders-cli"
-version = "0.6.0"
+version = "0.6.3"
 source = { editable = "." }
 dependencies = [
     { name = "authlib" },

thoughtleaders_cli-0.6.1/skills/tl/references/business-glossary.md

@@ -1,159 +0,0 @@
-# ThoughtLeaders Business Glossary
-
-Maps business terms to database concepts.
-
-## Revenue & Deal Lifecycle
-
-| Business Term | DB Concept | Notes |
-|--------------|------------|-------|
-| **Revenue / Sold ad** | `adlink.publish_status = 3` (SOLD) | Only status=3 counts as real revenue |
-| **Gross ads / Gross revenue** | `SUM(adlink.price)` where sold | Total advertiser spend |
-| **Net revenue / TL profit** | `price - cost` per adlink | What TL earns as a company |
-| **Cost** | `adlink.cost` | What the channel earns |
-| **Price** | `adlink.price` | What the advertiser pays |
-| **Closed-lost** | `publish_status IN (4, 5, 9)` | All three rejection statuses |
-| **Open opportunity** | `publish_status IN (0, 2, 6, 7, 8)` | Pipeline — not revenue, not lost |
-| **Proposal Approved** | `publish_status = 6` | AM approved to show to brand — NOT brand approval. Internal gate only. |
-| **Pending** | `publish_status = 2` | Brand has agreed — this is the real high-intent signal |
-| **Weighted pipeline** | `SUM(weighted_price)` for open opps | Pre-calculated on save |
-| **Ad is live** | `publish_date IS NOT NULL` | Until publish_date is set, ad is not on YouTube |
-| **Cancellation risk** | Sold but `publish_date IS NULL` | Sold deals without publish_date can still be canceled |
-
-## Performance Grade (`adlink.performance_grade`)
-
-| Value | Label | Description |
-|-------|-------|-------------|
-| 0 | Pending | Not yet graded (treat as NULL) |
-| 1 | Loser | Underperforming ad — do not renew |
-| 2 | Neutral | Mixed results — test one more time, ideally at a better rate. Second test determines if channel becomes Loser or Winner |
-| 3 | Winner | High-performing ad — should always be renewed |
-
-**Renewal logic:** All Winners should be renewed. Neutrals get one more test (ideally at a lower CPM), then reclassified as Winner or Loser.
-
-## View Guarantees
-
-| Field | Description |
-|-------|-------------|
-| `adlink.impressions_guarantee` | The number of views guaranteed for the ad (bigint). 0 or NULL = no guarantee. |
-| `adlink.view_guarantee_hit_date` | Timestamp when the guarantee was met. NULL = not yet hit or no guarantee. |
-| `adlink.projected_views_at_purchase_date` | Projected views at time of purchase (used for CPM estimation). |
-
-## Entities
-
-| Business Term | DB Table | Notes |
-|--------------|----------|-------|
-| **Deal / Sponsorship** | `thoughtleaders_adlink` | One brand ↔ channel placement |
-| **Brand** | `thoughtleaders_brand` | Advertiser entity (the buying-side brand) |
-| **Brand profile** | `thoughtleaders_profile` | Advertiser entity / account |
-| **Organization** | `thoughtleaders_organization` | Parent entity for profiles |
-| **Channel** | `thoughtleaders_channel` | YouTube channel |
-| **Ad Spot (Catalogue item)** | `thoughtleaders_adspot` | TL's catalogue of buyable placements. Price/cost on adspot are *list prices* only — each adlink (instance) can have completely different price/cost |
-| **Campaign** | `dashboard_campaign` | Groups multiple deals |
-
-## Ad Spots & Channels
-
-- A channel can have **multiple ad spots** because different people sell the same channel (talent manager, direct, multiple agencies)
-- Ad spots are the **catalogue** — adlinks are **instances** of catalogue items
-- Price/cost on adspot = list/catalog values; price/cost on adlink = actual deal values
-- **Only one active adspot with integration=mention per channel at any time** (MSN rule)
-
-## Ownership & Accountability
-
-| Field | Model | Meaning |
-|-------|-------|---------|
-| `owner_sales_id` | `adlink` | **Most important.** Person responsible for closing the deal and for the revenue. Final accountability. |
-| `owner_advertiser_id` | `adlink` | Brand-side owner for this specific deal |
-| `owner_publisher_id` | `adlink` | Channel-side owner for this specific deal |
-| `owner_advertiser_id` | `profile` | **Account owner.** Who owns the brand relationship overall. Often same person as owner_sales on adlinks, but not always. |
-| `owner_publisher_id` | `profile` | Channel relationship owner on the profile level |
-| `owner_sales_id` | `profile` | Sales owner at profile level |
-
-**Key insight:** Ownership exists on both `profile` (account-level) and `adlink` (deal-level). For revenue attribution, always use `adlink.owner_sales_id`.
-
-## MSN (Media Selling Network)
-
-- Channels where TL has **≥80% confidence** they can buy an ad tomorrow
-- Key data: **who is the contact** to buy the ad from
-- `thoughtleaders_channel.media_selling_network_join_date` = when channel joined MSN
-- `thoughtleaders_channel.is_tl_channel` = TPP/VIP channel (subset of MSN)
-- **Rule:** Only one active adspot with `integration=mention` per channel at any time
-- MSN quality depends on having current, accurate contact info
-
-## Teams & Ownership
-
-### Brand-led Revenue (Sales / Account Management)
-
-These teams close deals and manage brand relationships. Revenue is attributed via `adlink.owner_sales_id`.
-
-**Emma's team:**
-| Person | auth_user.id | Owner field |
-|--------|-------------|-------------|
-| Emma | 11158 | `adlink.owner_sales_id` |
-| Orli | 2042 | `adlink.owner_sales_id` |
-| Eli | 20836 | `adlink.owner_sales_id` |
-| Grace | 20835 | `adlink.owner_sales_id` |
-| Mark | 23979 | `adlink.owner_sales_id` |
-| Abbie | 23978 | `adlink.owner_sales_id` |
-| Ariella | 23977 | `adlink.owner_sales_id` |
-
-**Nicole's team:**
-| Person | auth_user.id | Owner field |
-|--------|-------------|-------------|
-| Nicole | 9929 | `adlink.owner_sales_id` |
-| Maika | 5412 | `adlink.owner_sales_id` |
-| Yuval | 14252 | `adlink.owner_sales_id` |
-| Revital | 14251 | `adlink.owner_sales_id` |
-
-### Network Growth (SDR / Partnerships) — Pauline's team
-
-Responsible for growing the MSN (new channels) and MBN (new brands). SDR outreach on both sides.
-
-| Person | auth_user.id | Role | Owner field |
-|--------|-------------|------|-------------|
-| Pauline | 218 | Team lead | `adlink.owner_publisher_id` (channel handovers) |
-| Morgan | 5710 | Channel SDR | — |
-| Jen | 873 | Channel SDR | — |
-| Ruby Jean | 9011 | Channel SDR | — |
-| Molly | 11361 | Channel SDR | — |
-| Pierra | 11323 | Brand SDR | — |
-| Nian | 8795 | Brand SDR | — |
-
-### Ad Ops — Jody's team
-
-Manages getting sold ads published. `profile.owner_publisher_id` = ad ops manager of an account.
-
-| Person | auth_user.id | Owner field |
-|--------|-------------|-------------|
-| Jody | 71 | `profile.owner_publisher_id` (account-level ad ops owner) |
-| Kathleen | 9274 | `profile.owner_publisher_id` |
-| Shane | 18159 | `profile.owner_publisher_id` |
-| Kevin | 5799 | `profile.owner_publisher_id` |
-| Airis | 5804 | `profile.owner_publisher_id` |
-| Lara | 10743 | `profile.owner_publisher_id` |
-| Josh | 11592 | `profile.owner_publisher_id` |
-
-### Querying by team
-
-```sql
--- Emma's team pipeline
-SELECT ... FROM thoughtleaders_adlink al
-WHERE al.owner_sales_id IN (11158, 2042, 20836, 20835, 23979, 23978, 23977)
-
--- Nicole's team pipeline
-SELECT ... FROM thoughtleaders_adlink al
-WHERE al.owner_sales_id IN (9929, 5412, 14252, 14251)
-
--- All brand-led revenue (both teams)
-SELECT ... FROM thoughtleaders_adlink al
-WHERE al.owner_sales_id IN (11158, 2042, 20836, 20835, 23979, 23978, 23977, 9929, 5412, 14252, 14251)
-
--- Pauline's network growth team (channel SDRs)
--- owner_publisher_id on adlink for channel-side work
-SELECT ... FROM thoughtleaders_adlink al
-WHERE al.owner_publisher_id IN (218, 5710, 873, 9011, 11361)
-
--- Jody's ad ops team accounts (profile-level ownership)
-SELECT ... FROM thoughtleaders_profile p
-WHERE p.owner_publisher_id IN (71, 9274, 18159, 5799, 5804, 10743, 11592)
-```
-