thoughtleaders-cli 0.7.15__tar.gz → 0.8.1__tar.gz

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/.claude-plugin/plugin.json

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

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/AGENTS.md

@@ -52,7 +52,7 @@ This repo is also a Claude Code plugin, and can directly be installed as one.
 ### Bundled skills — when to invoke
 
 - **`tl`** — the main skill for querying ThoughtLeaders data. Default for any sponsorship / channel / brand / upload / report question.
-- **`tl-keyword-research`** — invoke whenever the user wants to find videos or channels by **content keywords** (topics, concepts, niches) that aren't covered by a curated recommender tag, OR to validate that a candidate channel's content actually touches a given topic. **Default output: a ranked, context-validated set of channels** (each flagged for sponsorability) — discovered via field-weighted ES relevance (`title` > `summary` > `transcript`), then sense-checked so channels that only use the keyword in an unrelated sense are dropped. The keyword-distribution shape (`{operator, keywords:[{keyword,count}]}`) is now an **opt-in mode**, produced only when the user explicitly asks for keyword counts / distribution. **Do not compose keyword sets by hand for `tl db es` content searches — delegate to this skill first.** See `skills/tl/SKILL.md` → *Channel & video discovery* for the four-path decision tree and when to use this vs the recommender / raw SQL.
+- **`tl-keyword-research`** — invoke whenever the user wants to find videos or channels by **content keywords** (topics, concepts, niches) that aren't covered by a curated recommender tag, OR to validate that a candidate channel's content actually touches a given topic. It researches the topic by composing a boolean keyword query (`--any` OR-groups AND'd together, `--not` exclusions) over **≥3 refinement rounds**, returning a **CNF (Conjunctive Normal Form) keyword expression** as the reusable headline artifact alongside the ranked, sponsorability-flagged channels it selects. **Interactive by default** — checkpoints with the user after round 3 unless told to "run autonomously" (or invoked with `autonomous` / `--auto`). The keyword-distribution shape (`{operator, keywords:[{keyword,count}]}`) is an **opt-in mode**, produced only when the user explicitly asks for keyword counts / distribution. **Do not compose keyword sets by hand for `tl db es` content searches — delegate to this skill first.** See `skills/tl/SKILL.md` → *Channel & video discovery* for the four-path decision tree and when to use this vs the recommender / raw SQL.
 - **`tl-save-report`**, **`adapt-tl-data`**, **`tl-views-guarantee`**, **`tl-top-partnerships`** — narrower workflows; the skill files document their own triggers. `tl-top-partnerships` is brand-user-facing: ranks a brand's sold sponsorships by live eCPM vs the sold-date projection and delivers a two-tab Google Sheet via `gws`.
 
 ### Skill content boundaries

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/API.md

@@ -182,16 +182,16 @@ curl -sS "$TL_API_BASE/raw/pg" \
   -H 'X-TL-Auth: API-KEY' \
   -H 'Content-Type: application/json' \
   -d '{
-        "query": "SELECT id, channel_name, reach FROM thoughtleaders_channel WHERE is_tl_channel = TRUE ORDER BY reach DESC LIMIT 5 OFFSET 0"
+        "query": "SELECT id, channel_name, subscribers FROM thoughtleaders_channel WHERE is_tpp = TRUE ORDER BY subscribers DESC LIMIT 5 OFFSET 0"
       }' | jq
 ```
 
 ```python
 sql = """
-SELECT id, channel_name, reach
+SELECT id, channel_name, subscribers
 FROM thoughtleaders_channel
-WHERE is_tl_channel = TRUE
-ORDER BY reach DESC
+WHERE is_tpp = TRUE
+ORDER BY subscribers DESC
 LIMIT 5 OFFSET 0
 """
 print(post('/raw/pg', {'query': sql}))
@@ -200,7 +200,7 @@ print(post('/raw/pg', {'query': sql}))
 ```json
 {
   "results": [
-    {"id": 12345, "channel_name": "MrBeast", "reach": 320000000},
+    {"id": 12345, "channel_name": "MrBeast", "subscribers": 320000000},
     ...
   ],
   "total": 5,

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: thoughtleaders-cli
-Version: 0.7.15
+Version: 0.8.1
 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
@@ -121,7 +121,7 @@ tl whoami
 # profile → profile_brands → brand chain.
 tl db pg "SELECT al.id, al.weighted_price, al.purchase_date
           FROM thoughtleaders_adlink al
-          JOIN thoughtleaders_profile p           ON p.id  = al.creator_profile_id
+          JOIN thoughtleaders_profile p           ON p.id  = al.advertiser_profile_id
           JOIN thoughtleaders_profile_brands pb   ON pb.profile_id = p.id
           JOIN thoughtleaders_brand b             ON b.id  = pb.brand_id
           WHERE al.publish_status = 3
@@ -228,7 +228,7 @@ ThoughtLeaders has its internal terminology that's exposed throughout this tool.
 * **Adspots** — types of ads a channel carries (e.g. mention, dedicated video, product placement). Returned by `tl channels show`; each carries price/cost and a computed CPM.
 * **AdLink** — engineering / DB name for the row that backs a sponsorship. Treat as interchangeable with "sponsorship"; the table is `thoughtleaders_adlink`.
 * **MSN** (Media Selling Network) — the ~12k YouTube channels that have opted in to receive sponsorship offers. A channel is in MSN if `channel.media_selling_network_join_date IS NOT NULL`.
-* **TPP** (ThoughtLeaders Partner Program) — TL's closest-partner channels, a strict subset of MSN. A channel is TPP if `channel.is_tl_channel = TRUE`. Prefer TPP channels when booking — fastest response, easiest to close.
+* **TPP** (ThoughtLeaders Partner Program) — TL's closest-partner channels, a strict subset of MSN. A channel is TPP if `channel.is_tpp = TRUE`. Prefer TPP channels when booking — fastest response, easiest to close.
 * **MBN** (Media Buying Network) — the brand-side counterpart to MSN: profiles that have opted in to receive proposed sponsorships (`profile.media_buying_network_join_date IS NOT NULL`).
 
 Sponsorships are the centre of attention in ThoughtLeaders — all other analytics and operations serve to produce or optimise sponsorships. Note that the term "Sponsorship" is wide and encompasses pre-deal stages. The funnel is large at the Sponsorship end and narrowest at the Deal end.
@@ -250,7 +250,7 @@ Talk naturally in Claude Code:
 ```
 /tl Which channels did we sponsor in Q1?
 /tl sold sponsorships for Nike in Q1
-/tl show me pending proposals with send dates in April
+/tl show me pending proposals with scheduled dates in April
 /tl what channels does Nike sponsor?
 /tl find me Cooking creators in the US with mobile-heavy audiences
 /tl check my balance
@@ -258,7 +258,7 @@ Talk naturally in Claude Code:
 
 Resource-specific slash commands:
 ```
-/tl-sponsorships pending with send dates in April
+/tl-sponsorships pending with scheduled dates in April
 /tl-reports run my Q1 pipeline
 /tl-balance
 ```
@@ -290,7 +290,7 @@ By default, output is a styled table in the terminal and JSON when piped.
 
 ```bash
 tl sponsorships show 12345 --json | jq '.results'
-tl db pg "SELECT id, channel_name FROM thoughtleaders_channel WHERE is_tl_channel = TRUE
+tl db pg "SELECT id, channel_name FROM thoughtleaders_channel WHERE is_tpp = TRUE
           LIMIT 200 OFFSET 0" --csv > tpp.csv
 tl channels show "MrBeast" --md      # markdown table for Slack / docs
 tl channels show "MrBeast" --toon    # token-efficient encoding for LLMs

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/README.md

@@ -93,7 +93,7 @@ tl whoami
 # profile → profile_brands → brand chain.
 tl db pg "SELECT al.id, al.weighted_price, al.purchase_date
           FROM thoughtleaders_adlink al
-          JOIN thoughtleaders_profile p           ON p.id  = al.creator_profile_id
+          JOIN thoughtleaders_profile p           ON p.id  = al.advertiser_profile_id
           JOIN thoughtleaders_profile_brands pb   ON pb.profile_id = p.id
           JOIN thoughtleaders_brand b             ON b.id  = pb.brand_id
           WHERE al.publish_status = 3
@@ -200,7 +200,7 @@ ThoughtLeaders has its internal terminology that's exposed throughout this tool.
 * **Adspots** — types of ads a channel carries (e.g. mention, dedicated video, product placement). Returned by `tl channels show`; each carries price/cost and a computed CPM.
 * **AdLink** — engineering / DB name for the row that backs a sponsorship. Treat as interchangeable with "sponsorship"; the table is `thoughtleaders_adlink`.
 * **MSN** (Media Selling Network) — the ~12k YouTube channels that have opted in to receive sponsorship offers. A channel is in MSN if `channel.media_selling_network_join_date IS NOT NULL`.
-* **TPP** (ThoughtLeaders Partner Program) — TL's closest-partner channels, a strict subset of MSN. A channel is TPP if `channel.is_tl_channel = TRUE`. Prefer TPP channels when booking — fastest response, easiest to close.
+* **TPP** (ThoughtLeaders Partner Program) — TL's closest-partner channels, a strict subset of MSN. A channel is TPP if `channel.is_tpp = TRUE`. Prefer TPP channels when booking — fastest response, easiest to close.
 * **MBN** (Media Buying Network) — the brand-side counterpart to MSN: profiles that have opted in to receive proposed sponsorships (`profile.media_buying_network_join_date IS NOT NULL`).
 
 Sponsorships are the centre of attention in ThoughtLeaders — all other analytics and operations serve to produce or optimise sponsorships. Note that the term "Sponsorship" is wide and encompasses pre-deal stages. The funnel is large at the Sponsorship end and narrowest at the Deal end.
@@ -222,7 +222,7 @@ Talk naturally in Claude Code:
 ```
 /tl Which channels did we sponsor in Q1?
 /tl sold sponsorships for Nike in Q1
-/tl show me pending proposals with send dates in April
+/tl show me pending proposals with scheduled dates in April
 /tl what channels does Nike sponsor?
 /tl find me Cooking creators in the US with mobile-heavy audiences
 /tl check my balance
@@ -230,7 +230,7 @@ Talk naturally in Claude Code:
 
 Resource-specific slash commands:
 ```
-/tl-sponsorships pending with send dates in April
+/tl-sponsorships pending with scheduled dates in April
 /tl-reports run my Q1 pipeline
 /tl-balance
 ```
@@ -262,7 +262,7 @@ By default, output is a styled table in the terminal and JSON when piped.
 
 ```bash
 tl sponsorships show 12345 --json | jq '.results'
-tl db pg "SELECT id, channel_name FROM thoughtleaders_channel WHERE is_tl_channel = TRUE
+tl db pg "SELECT id, channel_name FROM thoughtleaders_channel WHERE is_tpp = TRUE
           LIMIT 200 OFFSET 0" --csv > tpp.csv
 tl channels show "MrBeast" --md      # markdown table for Slack / docs
 tl channels show "MrBeast" --toon    # token-efficient encoding for LLMs

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/agents/tl-analyst.md

@@ -38,7 +38,7 @@ If estimated cost > 200 credits, ask the user to confirm before proceeding.
 ```sql
 tl db pg "SELECT b.name, SUM(a.weighted_price) AS pipeline, COUNT(*) AS deals
           FROM thoughtleaders_adlink a
-          JOIN thoughtleaders_profile p ON a.creator_profile_id = p.id
+          JOIN thoughtleaders_profile p ON a.advertiser_profile_id = p.id
           JOIN thoughtleaders_profile_brands pb ON p.id = pb.profile_id
           JOIN thoughtleaders_brand b ON pb.brand_id = b.id
           WHERE a.publish_status = 3
@@ -52,16 +52,16 @@ One query → ranked list. No client-side aggregation, no paginated walk.
 ### Cross-resource analysis (raw PG)
 "Show me deal slippage this month"
 ```sql
-tl db pg "SELECT a.id, a.send_date, a.publish_status, b.name AS brand, ch.channel_name
+tl db pg "SELECT a.id, a.scheduled_date, a.publish_status, b.name AS brand, ch.channel_name
           FROM thoughtleaders_adlink a
           JOIN thoughtleaders_adspot s ON a.ad_spot_id = s.id
           JOIN thoughtleaders_channel ch ON s.channel_id = ch.id
-          JOIN thoughtleaders_profile p ON a.creator_profile_id = p.id
+          JOIN thoughtleaders_profile p ON a.advertiser_profile_id = p.id
           JOIN thoughtleaders_profile_brands pb ON p.id = pb.profile_id
           JOIN thoughtleaders_brand b ON pb.brand_id = b.id
           WHERE a.publish_status = 10
-            AND a.send_date < CURRENT_DATE
-          ORDER BY a.send_date
+            AND a.scheduled_date < CURRENT_DATE
+          ORDER BY a.scheduled_date
           LIMIT 100 OFFSET 0"
 ```
 Then suggest `tl sponsorships comment-add <id> "..."` for each.
@@ -83,7 +83,7 @@ Then suggest `tl sponsorships comment-add <id> "..."` for each.
 "Give me a full picture of channel 12345"
 1. `tl channels show 12345 --json` → profile, scores, demographics (structured — wraps several joins already)
 2. `tl snapshots channel 12345 --json` → growth over time (snapshots wrap interpolation logic)
-3. `tl db pg "SELECT id, send_date, publish_status, price FROM thoughtleaders_adlink WHERE ad_spot_id IN (SELECT id FROM thoughtleaders_adspot WHERE channel_id = 12345) ORDER BY send_date DESC LIMIT 100 OFFSET 0"` — deal history with the columns you actually want, no over-fetch.
+3. `tl db pg "SELECT id, scheduled_date, publish_status, price FROM thoughtleaders_adlink WHERE ad_spot_id IN (SELECT id FROM thoughtleaders_adspot WHERE channel_id = 12345) ORDER BY scheduled_date DESC LIMIT 100 OFFSET 0"` — deal history with the columns you actually want, no over-fetch.
 4. `tl uploads list channel:12345 --json` → recent content
 
 ### Transcript / brand-mention search (raw ES)

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/pyproject.toml

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

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/skills/tl/SKILL.md

@@ -37,7 +37,7 @@ If doing a database query, follow this recipe:
   ```bash
   tl db pg "SELECT al.id, b.name AS brand, al.weighted_price AS price
             FROM thoughtleaders_adlink al
-            JOIN thoughtleaders_profile p ON p.id = al.creator_profile_id
+            JOIN thoughtleaders_profile p ON p.id = al.advertiser_profile_id
             JOIN thoughtleaders_profile_brands pb ON pb.profile_id = p.id
             JOIN thoughtleaders_brand b ON b.id = pb.brand_id
             WHERE al.publish_status = 3
@@ -87,29 +87,29 @@ Other key concepts:
 - **Comments** — notes attached to sponsorships, channels, or brands
 - **Adspots** — types of ads a channel is willing to publish (e.g. mention, dedicated video, product placement). Returned by `tl channels show`; each carries price/cost.
 - **Profiles** — actors that own sponsorship records on behalf of either side of a deal. A profile is either buyer-side or seller-side:
-  - *Buyer-side (brand) profiles* — represent a sponsoring brand. Each brand profile has an M2M link to at most one `Brand` record (which are the actual advertiser identities). On a sponsorship, `creator_profile` is the buyer-side profile, and `creator_id` is the buyer-side user who created the record — on sponsorships, "creator" always means the buyer side, never the YouTube creator (the channel hangs off `ad_spot_id`).
+  - *Buyer-side (brand) profiles* — represent a sponsoring brand. Each brand profile has an M2M link to at most one `Brand` record (which are the actual advertiser identities). On a sponsorship, `advertiser_profile` is the buyer-side profile, and `advertiser_id` is the buyer-side user who created the record — the advertiser is always the buyer/brand side, never the YouTube creator (the channel hangs off `ad_spot_id`).
   - *Seller-side (publisher) profiles* — attached to a `Publication`, which in turn owns one or more `Channel` records. A channel's adspots therefore inherit ownership through `channel.publication.profile`.
   - **How to tell them apart** — three signals on the `thoughtleaders_profile` row, used in this order:
     1. **`persona`** (canonical) — `1=Brand`, `4=Media Agency`, `3=Talent Manager` are buyer-side; `2=Creator`, `5=Creator Service` are seller-side. May be null on legacy rows.
     2. **`is_advertiser` / `is_publisher`** booleans — feature flags; either or both can be true for staff-style profiles, but on normal user profiles they reliably mark side.
-  - Org scoping for sponsorships is profile-mediated: a sponsorship belongs to your org if **either** `creator_profile.organization` (brand side) **or** `ad_spot.channel.publication.profile.organization` (publisher side) matches yours.
+  - Org scoping for sponsorships is profile-mediated: a sponsorship belongs to your org if **either** `advertiser_profile.organization` (brand side) **or** `ad_spot.channel.publication.profile.organization` (publisher side) matches yours.
 - **MSN** (Media Selling Network) — the ~12k YouTube channels that have opted in to receive sponsorship offers. A channels is in the MSN group if the `channel.media_selling_network_join_date` field is not null.
 - **MBN** (Media Buying Network) — the brand-side counterpart to MSN: brand profiles that have opted in to receive proposed sponsorships. A profile is in the MBN group if the `profile.media_buying_network_join_date` field is not null.
-- **TPP** (ThoughtLeaders Partner Program, a.k.a. "TL channels") — the ~170 channels TL has the closest working relationship with. A channel is in the TPP group if `channel.is_tl_channel` is True. **Prefer TPP channels when booking**: they respond fastest, are the easiest to close, and don't need an outreach round-trip — treat them as immediately bookable. TPP is a strict subset of MSN, so the same booking rules (one active mention adspot, etc.) apply.
+- **TPP** (ThoughtLeaders Partner Program, a.k.a. "TL channels") — the ~170 channels TL has the closest working relationship with. A channel is in the TPP group if `channel.is_tpp` is True. **Prefer TPP channels when booking**: they respond fastest, are the easiest to close, and don't need an outreach round-trip — treat them as immediately bookable. TPP is a strict subset of MSN, so the same booking rules (one active mention adspot, etc.) apply.
 - **`demographics_updated_at`** (on channels) — If non-null, the channel has demographics screenshots on file. If null, no demographics screenshots have been uploaded. Use this to check whether a channel has demographics data from screenshots.
-- **`reach`** (on channels) — subscriber count. ⚠️ Despite the name, this is NOT ad-industry "reach" (unique audience exposed). There is no `subscribers` field — `reach` is it.
-- **`impression`** (on channels) — projected views per video on that channel. Forward-looking estimate. May be null when not yet computed. ⚠️ NOT actual views and NOT ad-industry "impressions" (ads served).
+- **`subscribers`** (on channels) — the channel's subscriber count.
+- **`projected_views`** (on channels) — projected views per video on that channel. Forward-looking estimate. May be null when not yet computed. ⚠️ NOT actual views and NOT ad-industry "impressions" (ads served).
 - **`views`** (on sponsorships) — actual view count of the sold and published sponsored video, accessible when `article_id` is set.
-- **`impressions_guarantee`** (on sponsorships) — projected/guaranteed impressions for the sponsorship. Numeric.
+- **`views_guarantee`** (on sponsorships) — projected/guaranteed impressions for the sponsorship. Numeric.
 - **Sponsorship detail fields** (returned by `tl sponsorships show <id> --json`) — the detail payload includes `integration` (raw int), `publish_count`, `common_name`, `outreach_email`, nested `publisher` (`first_name`, `last_name`, `email`), nested `brand_contact` (`first_name`, `last_name`, `email`), and `brand.organization_name`. Use these when generating IOs, contracts, or outreach.
 - **CPM** has two distinct meanings depending on level — pick the one the user actually wants:
-  - **Channel CPM** = `(adspot.price / channel.impression) * 1000` — projected price per thousand projected views. Used for pricing decisions **before** a sponsorship is sold. Available for channels with active adspots via `tl channels show <channel_id>`.
-  - **Sponsorship CPM** = calculated in either of two ways: if `views` is present, then CPM is `(sponsorship.price / sponsorship.views) × 1000`, meaning realized cost per thousand actual views, computed post-publication. If `views` is null, Compute from the sponsorship's `price` and the channel's `impression` fields.
+  - **Channel CPM** = `(adspot.price / channel.projected_views) * 1000` — projected price per thousand projected views. Used for pricing decisions **before** a sponsorship is sold. Available for channels with active adspots via `tl channels show <channel_id>`.
+  - **Sponsorship CPM** = calculated in either of two ways: if `views` is present, then CPM is `(sponsorship.price / sponsorship.views) × 1000`, meaning realized cost per thousand actual views, computed post-publication. If `views` is null, Compute from the sponsorship's `price` and the channel's `projected_views` fields.
   - Where possible, calculate the correct CPM in a SQL expression.
 - **Sponsorship dates** — each sponsorship has four distinct dates, useful for different queries:
   - **`created_at`** — when the sponsorship record was created in the system
   - **`purchase_date`** — when the sponsorship was purchased (i.e. when the deal was made); These make up bookings.
-  - **`send_date`** — the date the video is/was expected to be published (scheduled)
+  - **`scheduled_date`** — the date the video is/was expected to be published (scheduled)
   - **`publish_date`** — the date the video was actually published; These make up live ads.
 - **Credits** — every data query costs credits; use `tl describe` to see rates. Top up with `tl credits buy --amount-usd N` (free; opens a browser checkout). New accounts get a starter balance on first `tl auth login`; the rate is shown by `tl credits pricing`.
 
@@ -240,6 +240,7 @@ tl channels update 12345 '{"demographic_geo": {"US": 60, "UK": 12, "CA": 8}}'
 tl channels update 12345 '{"demographic_male_share": 55, "demographic_usa_share": 70}'
 tl channels update 12345 '{"outreach_email": "press@creator.com"}'
 tl channels update 12345 '{"all_emails": {"press@creator.com": {"timestamp": "2026-06-25T12:00:00+00:00", "source": "manual"}}}'
+tl channels update 12345 '{"media_selling_network_join_date": "2026-01-15"}'
 ```
 
 **Channel contact emails.** Besides demographics, `tl channels update` accepts two
@@ -254,6 +255,11 @@ contact fields:
   `scheduled_rescrape`. Use a descriptive token such as `manual` for hand-added entries.
   An edit **replaces** the whole `all_emails` object, so include every entry you want to keep.
 
+**MSN membership.** `tl channels update` also accepts **`media_selling_network_join_date`** —
+the date the channel joined the Media Selling Network, as a `YYYY-MM-DD` string. This date is
+itself the membership flag: set it to add the channel to MSN (it then reads as `is_msn` and
+appears in MSN-filtered queries), or send `null` to remove the channel from the network.
+
 ### Creating and vetting sponsorships
 
 This is the end-to-end workflow for proposing a sponsorship, then moving it through the funnel as the two sides respond. Three create commands plus `tl sponsorships update` cover every state transition the CLI exposes.
@@ -404,8 +410,8 @@ tl db fb "SELECT age, view_count, like_count FROM article_metrics
           WHERE channel_id = 12345 AND id = 'dQw4w9WgXcQ'
           ORDER BY age"
 
-# Channel reach over time
-tl db fb "SELECT scrape_date, total_views, reach FROM channel_metrics
+# Channel subscribers over time
+tl db fb "SELECT scrape_date, total_views, subscribers FROM channel_metrics
           WHERE id = 12345
           ORDER BY scrape_date"
 ```
@@ -418,7 +424,7 @@ See [references/firebolt-schema.md](references/firebolt-schema.md) for accepted-
 # Example: Top brands by deal count
 tl db pg "SELECT b.name, COUNT(*) AS deals
           FROM thoughtleaders_adlink a
-          JOIN thoughtleaders_profile p ON a.creator_profile_id = p.id
+          JOIN thoughtleaders_profile p ON a.advertiser_profile_id = p.id
           JOIN thoughtleaders_profile_brands pb ON p.id = pb.profile_id
           JOIN thoughtleaders_brand b ON pb.brand_id = b.id
           WHERE a.publish_status = 3
@@ -557,20 +563,20 @@ Use `tl recommender top` for category/topic discovery (it's ranked) and `tl chan
 
 Then run the actual content search via `tl db es` (`multi_match` on the `title`, `summary`, `transcript` fields) with the surviving high-count keywords. The skill's full procedure (Phase 1 = seed expansion by you; Phase 2 = the script) is in the `tl-keyword-research` skill file.
 
-**Path 4. Pure attribute filter** — user wants channels filtered by metadata like: `is_tl_channel`, `language`, `demographic_device_primary`, country share in `demographic_geo` JSON, aggregations, joins. Use `tl db pg` with a SELECT on `thoughtleaders_channel`. Run `tl schema pg thoughtleaders_channel` once to confirm the live column set; the columns in the examples are stable.
+**Path 4. Pure attribute filter** — user wants channels filtered by metadata like: `is_tpp`, `language`, `demographic_device_primary`, country share in `demographic_geo` JSON, aggregations, joins. Use `tl db pg` with a SELECT on `thoughtleaders_channel`. Run `tl schema pg thoughtleaders_channel` once to confirm the live column set; the columns in the examples are stable.
 
 ```bash
 # All TPP (TL-managed) channels — pure attribute filter, not a category query
 tl db pg "SELECT id, channel_name, content_category, total_views
           FROM thoughtleaders_channel
-          WHERE is_tl_channel = TRUE
+          WHERE is_tpp = TRUE
           ORDER BY total_views DESC
           LIMIT 200 OFFSET 0"
 
 # Mobile-first non-TPP channels — device share, not topic
 tl db pg "SELECT id, channel_name, demographic_device_primary, total_views
           FROM thoughtleaders_channel
-          WHERE is_tl_channel = FALSE
+          WHERE is_tpp = FALSE
             AND demographic_device_primary = 'mobile'
           ORDER BY total_views DESC
           LIMIT 100 OFFSET 0"
@@ -632,7 +638,7 @@ Users only see data their plan allows:
 ```bash
 tl db pg "SELECT al.id, al.weighted_price, al.purchase_date, b.name AS brand
           FROM thoughtleaders_adlink al
-          JOIN thoughtleaders_profile p ON p.id = al.creator_profile_id
+          JOIN thoughtleaders_profile p ON p.id = al.advertiser_profile_id
           JOIN thoughtleaders_profile_brands pb ON pb.profile_id = p.id
           JOIN thoughtleaders_brand b ON b.id = pb.brand_id
           WHERE al.publish_status = 3
@@ -734,7 +740,7 @@ tl db es '{
 # TL-brokered deal count for the brand (PG, not ES — adlinks where the brand is on the creator profile)
 tl db pg "SELECT COUNT(*) AS tl_brokered
           FROM thoughtleaders_adlink al
-          JOIN thoughtleaders_profile p  ON p.id = al.creator_profile_id
+          JOIN thoughtleaders_profile p  ON p.id = al.advertiser_profile_id
           JOIN thoughtleaders_profile_brands pb ON pb.profile_id = p.id
           WHERE pb.brand_id = 21416 AND al.article_id IS NOT NULL"
 ```

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/skills/tl/references/business-glossary.md

@@ -18,7 +18,7 @@ Maps business terms to database concepts.
 | **Weighted pipeline** | `SUM(weighted_price)` for open opps | `weighted_price` is derived from the brand/channel approval combination on OPEN deals. |
 | **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 |
-| **Immediately bookable** | `is_tl_channel = true` | TPP channels — TL's closest partners. Fastest to respond, easiest to close, prefer when booking. |
+| **Immediately bookable** | `is_tpp = true` | TPP channels — TL's closest partners. Fastest to respond, easiest to close, prefer when booking. |
 
 ## Performance Grade (`adlink.performance_grade`)
 
@@ -35,7 +35,7 @@ Maps business terms to database concepts.
 
 | Field | Description |
 |-------|-------------|
-| `adlink.impressions_guarantee` | The number of views guaranteed for the ad (bigint). 0 or NULL = no guarantee. |
+| `adlink.views_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). |
 
@@ -65,7 +65,7 @@ Maps business terms to database concepts.
 | `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 |
-| `creator_id` | `adlink` | The brand-side user account that *created the record*. ⚠️ NOT the YouTube creator — on sponsorships, "creator" always means the buyer side. Record lineage only; for accountability use the `owner_*` fields, for the brand use `creator_profile_id`, for the channel go via `ad_spot_id`. |
+| `advertiser_id` | `adlink` | The brand-side (advertiser/buyer) user account that *created the record*. Record lineage only; for accountability use the `owner_*` fields, for the brand use `advertiser_profile_id`, for the channel go via `ad_spot_id`. |
 | `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 |
@@ -77,7 +77,7 @@ Maps business terms to database concepts.
 - 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 channel — TL's closest partners, a strict subset of MSN. **Prefer when booking**: fastest response, easiest to close. Not a gating flag; not a process barrier.
+- `thoughtleaders_channel.is_tpp` = TPP channel — TL's closest partners, a strict subset of MSN. **Prefer when booking**: fastest response, easiest to close. Not a gating flag; not a process barrier.
 - **Rule:** Only one active adspot with `integration=mention` per channel at any time
 - MSN quality depends on having current, accurate contact info
 
@@ -87,13 +87,13 @@ Vocabulary that AMs use about channels, mapped to the actual DB encoding. Most o
 
 | 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 / TL channel** | `is_tl_channel = true` | TL's closest-partner channels (~144 at 100k+ reach). Prefer when booking — fastest to respond, easiest to close. A strict subset of MSN; *don't* use as a general "MSN" proxy — silently drops ~98% of MSN. |
+| **Subscribers** | `thoughtleaders_channel.subscribers` (bigint) | Channel subscriber count. |
+| **MSN member** | `media_selling_network_join_date IS NOT NULL` | Whole MSN pool. NOT `is_tpp = true` — that's the VIP subset only. |
+| **TPP / TL channel** | `is_tpp = true` | TL's closest-partner channels (~144 at 100k+ subscribers). Prefer when booking — fastest to respond, easiest to close. A strict subset of MSN; *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). |
+| **Brand on a deal** | `adlink → advertiser_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." |
@@ -104,11 +104,11 @@ AMs use "PV" loosely. There are three different DB fields, each meaning somethin
 
 | 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 (channel baseline)** | `thoughtleaders_channel.projected_views` | 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. |
+| **VG (View Guarantee)** | `thoughtleaders_adlink.views_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`.
+When an AM says "what's the PV on this channel?" — they almost always mean `channel.projected_views`. 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
 
@@ -147,9 +147,8 @@ AMs and brand-facing readers don't know (or care) what Postgres, Elasticsearch,
 | `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 |
+| `advertiser_profile_id` chain / 3-table join | **"the brand's record"** | Engineering plumbing for brand lookup; AMs just hear "the brand" |
+| `projected_views` (PG column) | **"projected views"** / **"PV"** | Flagged for reliability caveats |
 
 ### Common translations in context
 

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/skills/tl/references/firebolt-schema.md

@@ -71,7 +71,7 @@ Tracks YouTube video metrics over time. Each row = one scrape of one video on on
 |--------|------|-------------|
 | `id` | INT | TL channel ID |
 | `total_views` | INT | Channel total views at time of scrape |
-| `reach` | INT | Subscriber count at time of scrape |
+| `subscribers` | INT | Subscriber count at time of scrape |
 | `scrape_date` | DATE | When this data point was captured |
 
 **Primary Index: `(id)`**
@@ -124,7 +124,7 @@ tl recommender top-channels "Tech" msn:yes --limit 50 --json \
 tl db pg "SELECT al.id, al.article_id, s.channel_id
           FROM thoughtleaders_adlink al
           JOIN thoughtleaders_adspot s            ON s.id  = al.ad_spot_id
-          JOIN thoughtleaders_profile p           ON p.id  = al.creator_profile_id
+          JOIN thoughtleaders_profile p           ON p.id  = al.advertiser_profile_id
           JOIN thoughtleaders_profile_brands pb   ON pb.profile_id = p.id
           JOIN thoughtleaders_brand b             ON b.id  = pb.brand_id
           WHERE al.publish_status = 3
@@ -182,7 +182,7 @@ tl db fb "SELECT id, age, view_count, like_count, comment_count, duration, publi
 ### Channel subscriber/view growth over time
 
 ```bash
-tl db fb "SELECT scrape_date, total_views, reach
+tl db fb "SELECT scrape_date, total_views, subscribers
           FROM channel_metrics
           WHERE id = 12345
           ORDER BY scrape_date"
@@ -191,7 +191,7 @@ tl db fb "SELECT scrape_date, total_views, reach
 ### Compare multiple channels' growth
 
 ```bash
-tl db fb "SELECT id, scrape_date, total_views, reach
+tl db fb "SELECT id, scrape_date, total_views, subscribers
           FROM channel_metrics
           WHERE id IN (123, 456, 789)
           ORDER BY id, scrape_date"

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/skills/tl/references/postgres-schema.md

@@ -19,9 +19,9 @@ The main sponsorships table. Each row = one sponsorship between a brand and a Yo
 The profile table is tightly coupled with the brand table for media buyers, so many reports that operate on the brand levels must access the profile data first.
 
 > 🚨 **Columns that DO NOT exist on `thoughtleaders_adlink` — common hallucinations:**
-> - ❌ `brand_id` — there is NO direct brand FK. Brand is reached via `creator_profile_id → profile → profile_brands → brand`.
-> - ❌ `organization_id` — there is NO direct org FK. Org is reached via `creator_profile_id → profile.organization_id → organization`.
-> - ❌ `channel_id` — channel is reached via `ad_spot_id → adspot.channel_id → channel`. Do NOT substitute `creator_id` — that's the brand-side user who created the record, not the channel/YouTube creator.
+> - ❌ `brand_id` — there is NO direct brand FK. Brand is reached via `advertiser_profile_id → profile → profile_brands → brand`.
+> - ❌ `organization_id` — there is NO direct org FK. Org is reached via `advertiser_profile_id → profile.organization_id → organization`.
+> - ❌ `channel_id` — channel is reached via `ad_spot_id → adspot.channel_id → channel`. Do NOT substitute `advertiser_id` — that's the brand-side user who created the record, not the channel.
 > - ❌ `youtube_id` (on channel) — use `external_channel_id`.
 > - ❌ `msn_join_date` (on channel) — use `media_selling_network_join_date`.
 > - ❌ `mbn_join_date` (on profile) — use `media_buying_network_join_date`.
@@ -35,12 +35,12 @@ The profile table is tightly coupled with the brand table for media buyers, so m
 | `updated_at` | timestamptz | Last modification |
 | `publish_status` | int | Deal status (see constants below) |
 | `ad_spot_id` | int FK | → `thoughtleaders_adspot.id` |
-| `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. |
-| `creator_id` | int FK | → `auth_user.id` — the brand-side user account that created the sponsorship record. ⚠️ Despite the name, NOT the YouTube creator: on sponsorships, "creator" always means the buyer side. Record lineage only — for the channel use `ad_spot_id → adspot.channel_id`, for the brand use `creator_profile_id`, for accountability use the `owner_*` fields. |
+| `advertiser_profile_id` | int FK | → `thoughtleaders_profile.id` (the brand/advertiser's profile). ⚠️ The table is named `thoughtleaders_profile`, NOT `advertiser_profile`. |
+| `advertiser_id` | int FK | → `auth_user.id` — the brand-side user account that created the sponsorship record (the advertiser/buyer side). Record lineage only — for the channel use `ad_spot_id → adspot.channel_id`, for the brand use `advertiser_profile_id`, for accountability use the `owner_*` fields. |
 | `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) |
-| `send_date` | timestamptz | Scheduled send/publish date |
+| `scheduled_date` | timestamptz | Scheduled send/publish date |
 | `publish_date` | timestamptz | Actual publish date |
 | `outreach_date` | timestamptz | When outreach was sent |
 | `purchase_date` | timestamptz | When deal was purchased/sold |
@@ -166,9 +166,9 @@ A channel can have multiple adspots (different sellers: talent manager, direct,
 | `url` | varchar | Channel URL (external — usually the YouTube URL). |
 | `slug` | varchar | TL-platform-specific slug. Used to build the canonical TL channel URL: `https://app.thoughtleaders.io/youtube/<slug>`. Prefer this over `url` when linking to a channel from any user-facing surface (reports, samples, Slack posts). Fall back to an ID-based TL path if `slug` is NULL; never fall back to the external YouTube URL. |
 | `total_views` | int | Total views for the entire 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`. |
+| `subscribers` | bigint | Subscriber count. |
 | `media_selling_network_join_date` | date/timestamptz | When the channel joined the MSN. **MSN membership = this column IS NOT NULL.** |
-| `is_tl_channel` | boolean | True = TPP channel — TL's closest-partner channels (~144 at 100k+ reach), a strict subset of MSN. Prefer when booking: fastest response, easiest to close. ⚠️ **This is not the MSN flag.** For MSN, use `media_selling_network_join_date IS NOT NULL`. |
+| `is_tpp` | boolean | True = TPP channel — TL's closest-partner channels (~144 at 100k+ subscribers), a strict subset of MSN. Prefer when booking: fastest response, easiest to close. ⚠️ **This is not the MSN flag.** For MSN, use `media_selling_network_join_date IS NOT NULL`. |
 | `content_category` | int | Content category code (1–22), as assigned by YouTube. This assignment is too unreliable, do not use it for discovering channels. **For topic/category discovery, prefer `tl recommender top-channels "<tag>"` |
 | `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`). This is often the cleanest answer to "geography" questions on sponsorships. May be NULL or blank. |
@@ -193,8 +193,8 @@ A channel can have multiple adspots (different sellers: talent manager, direct,
 
 When composing `SELECT ... FROM thoughtleaders_channel ...`, do not improvise column names from semantic intuition — consult the output of `tl schema pg thoughtleaders_channel` or the column table above. The `tl schema` command is authoritative. Failed guesses return *"column '\<name\>' does not exist"* and cost a round-trip. Recurring problems:
 
-- Subscriber count is in the field named `reach`
-- Projected views is in the field named `impression`
+- Subscriber count is in the field named `subscribers`
+- Projected views is in the field named `projected_views`
 - ❌ **Suffix/qualifier variants of date columns** (e.g. an `_max` / `latest_` / `_date` form when the canonical column has neither). Date columns  use bare names.
 - ❌ **Platform-name-prefixed ID forms** (e.g. a platform-name prefix when the canonical column uses a neutral `external_` prefix). See the column table for the actual ID column.
 - ❌ **Bare-noun forms without the table-prefix** (e.g. `name` instead of `channel_name`). This table prefixes its display fields with `channel_` to avoid SQL keyword collisions and ambiguity in joins.
@@ -237,7 +237,7 @@ thoughtleaders_adlink
   ├── owner_advertiser_id → auth_user.id
   ├── owner_publisher_id → auth_user.id
   ├── owner_sales_id → auth_user.id
-  └── creator_profile_id → thoughtleaders_profile.id
+  └── advertiser_profile_id → thoughtleaders_profile.id
                               ├── organization_id → thoughtleaders_organization.id
                               └── profile_brands.profile_id → brand.id
 
@@ -270,15 +270,15 @@ JOIN thoughtleaders_channel ch ON s.channel_id = ch.id
 
 **Adlink → Brand name:**
 ```sql
-JOIN thoughtleaders_profile p ON a.creator_profile_id = p.id
+JOIN thoughtleaders_profile p ON a.advertiser_profile_id = p.id
 JOIN thoughtleaders_profile_brands pb ON p.id = pb.profile_id
 JOIN thoughtleaders_brand b ON pb.brand_id = b.id
--- NEVER: JOIN brand b ON b.id = a.creator_profile_id (different ID spaces, returns wrong data)
+-- NEVER: JOIN brand b ON b.id = a.advertiser_profile_id (different ID spaces, returns wrong data)
 ```
 
 **Adlink → Organization:**
 ```sql
-JOIN thoughtleaders_profile p ON a.creator_profile_id = p.id
+JOIN thoughtleaders_profile p ON a.advertiser_profile_id = p.id
 JOIN thoughtleaders_organization o ON p.organization_id = o.id
 ```
 
@@ -323,7 +323,7 @@ LIMIT 100 OFFSET 0
 
 **Sold deals this month:**
 ```sql
-SELECT id, price, purchase_date, ad_spot_id, creator_profile_id
+SELECT id, price, purchase_date, ad_spot_id, advertiser_profile_id
 FROM thoughtleaders_adlink
 WHERE publish_status = 3
   AND purchase_date >= date_trunc('month', CURRENT_DATE)
@@ -346,7 +346,7 @@ SELECT a.id, a.price, a.publish_status, b.name AS brand, ch.channel_name
 FROM thoughtleaders_adlink a
 JOIN thoughtleaders_adspot s ON a.ad_spot_id = s.id
 JOIN thoughtleaders_channel ch ON s.channel_id = ch.id
-JOIN thoughtleaders_profile p ON a.creator_profile_id = p.id
+JOIN thoughtleaders_profile p ON a.advertiser_profile_id = p.id
 JOIN thoughtleaders_profile_brands pb ON p.id = pb.profile_id
 JOIN thoughtleaders_brand b ON pb.brand_id = b.id
 WHERE a.id = 12345

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/skills/tl-channel-authenticity/references/peer-cohort.md

@@ -11,7 +11,7 @@ being inflated.
 1. **Preferred:** `tl channels similar <id> --limit 24` (the recommender).
    Best niche match.
 2. **Fallback** (recommender empty): PG cohort —
-   same `content_category` + `language`, `is_active`, `reach` within ±50%,
+   same `content_category` + `language`, `is_active`, `subscribers` within ±50%,
    `last_published` within 60 days, excluding the subject channel.
 3. For up to 12 peers, pull each peer's last 10 longforms via `tl db es`,
    require ≥5,000 aggregate views and ≥3 videos (skip dead peers).
@@ -36,7 +36,7 @@ deleting the cache file or calling `get_baseline(ch, refresh=True)`.
 If no usable peers at all (rare — niche too small / all peers dead), a generic
 English-tech floor is used (`like 2%, comment 0.25%`) and `source` is recorded
 as `fallback-generic` in the metrics so the report consumer knows the
-baseline was weak. Prefer widening the reach band over trusting this.
+baseline was weak. Prefer widening the subscribers band over trusting this.
 
 ## Caveats
 

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/skills/tl-channel-authenticity/references/red-flags.md

@@ -16,7 +16,7 @@ label only.
 | `A_per_video_outliers` | ≥⅓ of longforms >1.5σ below the channel's own like:view mean | One real audience produces consistent ratios; promoted videos don't. |
 
 Peer baseline: niche-matched (`tl channels similar`, fallback PG cohort:
-same content_category+language, active, reach ±50%, published <60d), median
+same content_category+language, active, subscribers ±50%, published <60d), median
 of each peer's last-10-longform like/comment rates. Cached 30 days.
 
 ## Group B — view-curve time-series (`anomaly_detector.py`)

{thoughtleaders_cli-0.7.15 → thoughtleaders_cli-0.8.1}/skills/tl-channel-authenticity/scripts/analyze_channel.py

@@ -165,7 +165,7 @@ def main() -> None:
                         {
                             "id": c.get("id"),
                             "name": c.get("channel_name"),
-                            "subscribers": c.get("reach"),
+                            "subscribers": c.get("subscribers"),
                         }
                         for c in exc.candidates
                     ],