1. Unpublish these four listings. All four are status: active right now, all published 2026-08-16 in batch 2026.ORDINARY_TIME.04:
| Product ID | Title | Collection tag | |---|---|---| | 9368304124119 | Salem Witches University T-Shirt | col_seasonal_traditions | | 9368304156887 | Wands And Spells T-Shirt | col_seasonal_traditions | | 9368304353495 | Magical Emporium T-Shirt | col_seasonal_traditions | | 9368304320727 | Heirloom Pumpkin Witches T-Shirt | col_seeds — a collection-level sweep misses this one |
2. Add one line to the file that already holds this rule. Open igl-brand-kb/voice/igl-no-dark-humor.md. It currently names skulls, poison, "I Bury Things", "Feral Gardener" and "Full of Rage". Add the occult register beside them — witch, witchcraft, spell, wand, coven, potion, hex, tarot, "Salem". Write it as a rule about what IGL prints, not about who may shop: one of your own Tomato Lovers Collective featured gardeners, Lydia, describes herself as a "Green Witch," so the exclusion has to be scoped to the product lane or it insults a customer you are currently celebrating by name.
3. Move the check from the mining board to the publish step. The rule's own enforcement sentence is "When a niche mine surfaces dark, feral or morbid-humor concepts, flag and EXCLUDE them before they reach a board." Nothing in it fires at publish, which is why a batch that skipped the board sailed through. Add the same keywords to the trademark-keyword homograph guard — the one that already rejected "Dr Pepper shirt" — inside the launch chain at G:\iris\igl-production\.claude\skills\launch-igl-product-batch\.
4. Run this search yourself before trusting any of the above. Against the 1,318 live titles in the 2026-09-19 Shopify capture, case-insensitive whole-word, on the title field:
`` witch, wizard, spell, potion, coven, occult, tarot, hex, magic, mystic, salem, skull, poison, bury, feral, rage, grim, reaper, dead, death, voodoo, curse, demon, satan, goth ``
Worked examples of what that search returns, so you can tell a real hit from a false one:
- Real: Salem Witches University T-Shirt (hits salem, witch), Wands And Spells T-Shirt (spell), Magical Emporium T-Shirt (magic), Heirloom Pumpkin Witches T-Shirt (witch). - False positive, leave alone: Carolina Reaper Hellfire Bite T-Shirt (reaper — it is a pepper), Dormant Not Dead T-Shirt (dead — it is a plant joke), Love Spelled Mulch T-Shirt (spell — it is a pun). - Judgment call, and it sold: the three Hairy Potter T-Shirt listings (9254589956311, 9254595952855, 9254599164119), published 2026-04-29 in batch 2026.EASTER.TEE.01. The scan above does not catch them — no keyword matches "Hairy Potter" — and between them they sold 8 units for $241.76. A wizarding pun on a gardening joke is not the same product as a Salem witch shirt. Decide that one deliberately rather than by keyword.
The written rule that was supposed to keep off-brand designs out of IGL names five kinds of dark humor and not one occult word, and it only fires at the mining board — so when a new seasonal routing path shipped on 2026-08-11 and published a batch five days later, four witch shirts entered a faith-and-gardening brand without ever meeting a control.
Luca Ferrari did not trim job titles at Bending Spoons, he abolished them. He traced the practice to its root benefit, found the benefit belonged to the employee's CV rather than to the company, and removed the whole thing: "pick your own, we don't need to know, just don't embarrass us." His general rule is that incremental simplification gets you 5% while removal can get 10x, and that if 2% of users touch a feature you cut it whole rather than running a million migrations. The transferable move is not deletion for its own sake. It is deciding a category question once, explicitly, instead of letting a process answer it by default every cycle.
IGL's occult lane is exactly that unanswered question. The brand has a real, current, written exclusion — igl-no-dark-humor.md, marked Status: CURRENT canon, Tim's directive of 2026-07-09. It is specific where it speaks: skulls, poison, "I Bury Things", Feral, rage. It is silent on witches, spells and wizards. And its enforcement clause aims at the mining board, not the publish step. So the rule is not weak, it is narrow and early — and a batch that arrived by a new route found nothing in its way.
The non-obvious part is that the sales figures cannot carry this argument, and that is the finding too. All four shirts have zero net units — but so do 45 of the 48 listings in their own batch, and 627 of the 1,318 live listings overall. Their whole batch produced 3 units. "They didn't sell" is the least interesting true thing about them; almost nothing published that week sold. What distinguishes them is not performance, it is permission: they are the only genuinely occult titles in a 1,318-item catalogue belonging to a faith brand, and they all came from one batch on one day. This is not a habit to break. It is a single unguarded gate, which is a much cheaper thing to fix and a much easier thing to miss.
No single shelf holds this. founders-kb supplies the discipline of settling a category once rather than per-cycle. Only the Shopify capture in wescale-kb can say which titles are live, when they published, and that the sales data refuses to distinguish them. Only igl-brand-kb holds both halves of the judgment: the written ban with the occult-shaped hole in it, and Lydia the Green Witch, who is the reason the fix has to be about the merchandise and not the audience.
founders-kb/interviews/040-luca-ferrari-on-bending-spoons — founder interview published 2026-09-13, drawn the day after it entered the base. Lesson 3: job titles traced to root benefit and abolished whole, "not something that the company needs to be involved with." Lesson 1 supplies the prior test — go all out or check the boxes for bare minimum, and eliminate the rest.wescale-kb/research/igl-design-merchandising-audit-2026-09-19/shopify-live-product-identity.json — Shopify capture, captured_at 2026-09-19, 1,318 live products. All four listings present, status: active, created and published 2026-08-16, batch tag 2026.ORDINARY_TIME.04, tags including occasion_halloween and tier_1. Untracked in git — Tim's own read-only research folder, not a committed knowledge-base file.wescale-kb/research/igl-design-merchandising-audit-2026-09-19/shopify-native-daily-live.json — the paired sales query, FROM sales SHOW net_items_sold … SINCE 2024-07-01 UNTIL 2026-09-14, 6,895 rows. None of the four product IDs appears in a single row. Also the source of the base rates that reframe the finding.igl-brand-kb/voice/igl-no-dark-humor — Status: CURRENT canon, Tim's standing directive 2026-07-09, relocated into the knowledge base 2026-08-19. The ban, its five named examples, its silence on the occult, and its mining-stage-only enforcement clause.igl-brand-kb/community/tlc-featured-gardener-stories — Lydia identifies as a "Green Witch" with "a deep and intuitive connection with nature." The counter-evidence that scopes the move.wescale-kb/members/stacey-campbell — cohort peer, The Mystic Eden (themysticeden.com), literary / mythology / cottagecore, $34.99–$42.99. Adjacent lane, not the same lane — her catalogue is Shakespeare, Poe, Greek and Norse myth and zodiac, not witchcraft. Weakest strand in the thread and labelled as such.iris-03a-component-tracking/docs/wayfinder/behavioral-review/success-stories-and-codex-record.md — read-only survey dated 2026-09-01. Dates the cause: the 2026-08-11 commit "Add seasonal traditions routing and harden MyDesigns prep" (10th collection, fail-closed no-home hold), five days before the batch. Also records the "Dr Pepper shirt" homograph guard and the launch-igl-product-batch chain. Outside every knowledge base — contributes evidence, not a base, to the gate.2026.ORDINARY_TIME.04, all published 2026-08-16 → igl-no-dark-humor.md names five dark registers and no occult one, and fires only at the mining board → base-rate check kills the sales reading (45 of 48 batch-mates also at zero) → tlc-featured-gardener-stories (Lydia the Green Witch) scopes the rule to merchandise → the Codex record dates the cause to the 2026-08-11 seasonal-routing commitiris-03a-component-tracking document correctly contributes no base — it does not end in -kb, which is the night #42 kbOf() fix working as designed rather than inflating the count.Score designs by message, not by Shopify listing. "Red, Ripe & True" exists as 8 separate listings, all created 2026-06-25. Together they took 17 paid orders in their first 42 days — the most of any message IGL launched this summer, rank 1 of 259. But its best single listing took only 7, which ranks 6th of 312 — so every listing-level report you have ever opened showed it as a mid-table design.
Two fixes, both startable this week:
1. Tag by message. In Shopify, add a msg:<slug> tag to every listing in the 28 duplicate families (81 of 312 summer listings) so a product-set report can group them. Start with the four families whose combined orders beat their best single listing: red-ripe-and-true (8 listings, 17 orders vs best single 7), home-of-seed-savers (3, 7 vs 4), perfectly-imperfect (3, 5 vs 3), too-many-tomatoes (3, 4 vs 3). 2. Stop creating the split. Change the Seedwork publish step so one message ships as ONE listing with the alternate renders as additional product images. The practice is still live: "Oops Another Plant" went out as 6 listings on 2026-07-27, split $4.47 of catalog spend six ways, and sold nothing.
IGL publishes one design as many listings, so both the sales record and the ad budget are split into pieces too small for any report — or the catalog algorithm — to recognise as a winner.
Musk's step 2 is delete the part, and his test is whether anyone can name who required it (founders-kb ep-399, Key Lesson 1: the battery-pack caps were deleted once nobody could name who required them). IGL runs the inverse. 81 of 312 summer listings — 26% — are duplicate-title siblings in 28 families, and nobody can name who required eight copies of Red, Ripe & True.
The cost is not storage; print-on-demand listings are free to hold. The cost is that every report and the catalog algorithm judge a listing, while customers buy a message. Red, Ripe & True is the clearest case: 17 of the summer's 192 total first-42-day paid orders — 8.9% of everything sold — carried by a message that never appears at the top of any list.
Where splitting provably changed a decision, stated narrowly. The cohort's documented graduation rule is Jakob & Petra's, from call-28: run a low-budget tag-based catalog on every new launch, then after a week pull the designs with 10+ clicks into static tests. Measured against that bar across all 28 duplicate families, splitting flips the decision for three: spirit-of-america-raccoon (14 clicks combined, best single 6), tomato-quilt-club (11 combined, best single 9), and Red, Ripe & True itself — 25 clicks combined, but only 1 of its 8 listings clears 10 on its own, and the second-best sits at 9, one click short. The other 25 families are unaffected. The splitting is systematic; its measured effect on graduation is not, and saying otherwise would overstate it.
The loop back to the brand's own shelf is the tell. IGL's email C169, "The story behind Red, Ripe and True," went to the 60-Day Engaged segment on 2026-07-01 — six days after the eight listings launched. Six of the seventeen orders landed on listings with zero catalog clicks. The story email found the winner; the ad algorithm, looking at eight small pieces, never did.
No single shelf reaches this: founders-kb supplies the deletion test, wescale-kb supplies both the 312-listing artifact and the graduation rule, igl-brand-kb supplies the email that actually sold it.
founders-kb/episodes/399-how-elon-works — seed, read in full. Key Lesson 1, "the best part is no part": delete anything nobody can name a requirer for; expect to add back ~10%.wescale-kb/research/igl-design-merchandising-audit-2026-09-19/all313-age-aligned-exposure-results — structured artifact, captured 2026-09-19/20, research-only, not a system of record. 313 listings captured, 312 with complete coverage. Every per-family count in this nugget was re-derived from it independently by the operator and matched.wescale-kb/calls/call-28 — Jakob & Petra's 4-step testing pipeline; the 10+ clicks after a week catalog-graduation bar. This replaces the candidate's cited "~5 catalog purchases" threshold, which does not exist in the knowledge bases (see Assay verdicts).wescale-kb/research/igl-design-merchandising-audit-2026-09-19/verified-design-findings — 2026-09-19, research-only. Section 3, "Same title can conceal entirely different visual propositions", is the honest caveat on grouping by title: three visually distinct July 6 Chaos Gardener listings. Tag by message only after eyeballing the renders.igl-brand-kb/stories-and-voice/campaigns/01KW7XBKXTKEAA04J55R5NFYC6/README — campaign C169, sent 2026-07-01T22:30Z to 60-Day Engaged. Header declares status: HISTORICAL — a captured snapshot, not a live commitment or current authority.Open igl-brand-kb/audience/profiles/02-donna-seed-keeper.md, find the section headed "Who wears it (Q2, open — Tim's gut pending)", and close the question it asks in writing — "designed for Donna to wear, or for Donna to buy for him?" It was left open on five "husband loves it" quotes from one design. The full Loox review export (J:\My Drive\99_Downloads\reviews.0jn7hQ_wPY (2).csv, 921 reviews, 2024-08-31 to 2026-07-09) answers it: 103 reviews name a man as the wearer, and 80 of those 103 are size L, XL or 2XL. Write that in and mark Q2 closed as "buying-for-him is a standing lane, not an edge case."
Then do the cheap half. 26 designs outside the bird-feeder family already carry a man-as-wearer review (full list below). For those 26 product pages, add one male-model mockup in XL as the second product image. Nothing else changes — no new design, no new collection, no new ad. Re-run the count at the quarterly persona re-validation already scheduled in igl-brand-kb/audience/who-data-map.md (line 70, "Re-validate quarterly"), using the same export.
The persona file wrote down a question about who actually wears the shirt and left it open, because the evidence it was built from — ad comments, community stories, Facebook voice — had five instances; the review corpus it never opened has 103.
The seed was a Skool lesson about turning a video into an ebook, and its real subject is not publishing — it is the fact-check step. Every claim from the draft gets a verdict and evidence checked against a corpus the author did not use, and that report, not the article, is the single human checkpoint: "You give it a URL. You read the fact-check report. You approve." (agentic-academy-kb/lessons/00-youtube-to-ebook.md, line 105.)
IGL's persona dossiers are exactly that draft. 02-donna-seed-keeper.md declares status: CURRENT SoR and lists its evidence in the header — ad comments, community stories, Facebook voice, a sales cluster. The review export is not on that list. So when the file reached the question of who wears the shirt, it had a handful of quotes and honestly wrote the question down as open rather than guessing. Run the same claim against the corpus it skipped and the answer arrives with a size distribution attached, which quotes alone could never produce: 78% of man-as-wearer reviews are L/XL/2XL, against a store-wide top three of L (229), XL (187), M (134).
The sharpest single line in the corpus is a one-star review on Quietly Plotting My Next Tomato Harvest: "the shirt so short it was barely long enough for me, a woman just over five feet tall. I wanted the shirt for my six foot son." Nugget #022 established that IGL's own reviews complain shirts run too long; this is the same garment failing in the opposite direction for the buyer this nugget is about. Both are true, and they are two different people.
No single shelf could reach this. The Skool lesson supplies the method (claim → verdict → evidence, against a corpus the author skipped). The brand base supplies the claim and the flag that it was unresolved. The mastermind base supplies why concentration matters commercially: Antonio Rodriguez's profile names "over-concentration of ad spend on a single design" as the root cause that took his week down (line 76) — and 72 of the 103 man-as-wearer reviews sit on the bird-feeder family, the same design that is already 364 of all 921 reviews (39.5%). He also ran a "Who are you shopping for?" popup before Black Friday 2025 where roughly 50% answered "for someone else" (line 85).
Honest limit: these are review counts, not sales. The thirteen knowledge bases hold no product-level sales data, so this measures who shows up in review text, not units shipped. The corpus itself sits outside the knowledge bases, in Tim's Drive folder.
agentic-academy-kb/lessons/00-youtube-to-ebook — the seed. Supplies the mechanic: a fact-check phase that checks every claim against a corpus the author did not use, and stops for a human. Lines 98 and 105.igl-brand-kb/audience/profiles/02-donna-seed-keeper — status: CURRENT SoR, created 2026-08-29. Line 149 is the open question; line 151 is the "five husband loves it" it rests on. The header's evidence list does not include reviews.igl-brand-kb/community/customer-reviews-q4-2025 — the knowledge base's own copy of the corpus, export date December 11 2025, 551 reviews. Nine months stale and 370 rows short of the live export; the man-as-wearer reviews are in it but were never counted.wescale-kb/members/antonio-rodriguez — line 76, "over-concentration of ad spend on a single design" as a standing cohort lesson; line 85, the "Who are you shopping for?" popup at roughly 50% "for someone else".igl-brand-kb/audience/voice/etsy-review-mining-2026-08-30 — the same gift-chain shape on a different platform ("my hubby loves it and wears it every week"), so the share is not an artifact of one review app.igl-brand-kb/audience/who-data-map — line 31 names this exact export and its 921 rows; line 70 schedules the quarterly re-validation the move hangs on.wescale-kb/planning/weekly-routine-sop.md (Step 4) and the "Tim's Notes" block in wescale-kb/templates/call-template.md. Today those two files let the Sunday 9 AM run write a free-form "Apply to IGL" list into every new call file. Replace that with a gate: the run first reads net_profit_margin for the newest week in wescale-kb/scorecard/wescale-scorecard.db, and while that number is negative the call file may contain exactly one line — OPEN CONSTRAINT: positive net margin on whatever spend is in market (Chris Heckman, call #34). Week N unresolved. Every other idea from that call goes into a new file, wescale-kb/planning/parking-lot.md, instead of into the call notes. When a week finally prints positive margin the run writes CONSTRAINT RESOLVED — week NN, and only then may the parking lot be reopened, one item at a time.Zach Dell's board member asked him the same single question for two years, while IGL's own weekly routine mechanically replaces its named constraint with a fresh list of five to seven priorities every seven days.
Zach Dell's operating doctrine has one load-bearing rule, and Base Power hard-codes it into an object. Antonio Gracias opens every conversation the same way — "Zach, what's your constraint? Like, what's the constraint of the business? And I'll just answer the question, and that's all we can talk about" — for years. Then there is a literal physical turtle that "goes on the desk of the person that is on critical path," and "that turtle can only be moved when critical path is resolved," with a hot-potato daily meeting and an explicit resolved email at the end. Dell names the failure mode precisely: "it's kind of like a cope, if you will, to talk about the other stuff."
IGL already has the diagnosis. The coach gave it twice, in the scorecard database's scorecard_reviews table. At call #31 Tim's own stated number one was conversion rate and Chris Heckman overruled him: "I would redirect from CVR. The number one is the margin leak, and until that's fixed, nothing else tells us the truth... that's not the constraint this week." At call #34, on $1,088.89 of Facebook spend: "The goal right now is to stop the bleed, not add fuel to it. Next week I want to see you profitable on whatever spend you have in market, even if it's small."
What happened next is structural rather than lazy. Across the call files carrying a named IGL-application heading from call #34 onward, the weekly routine generated 41 fresh IGL action items. Over the same span net margin was negative in every reported week — scorecard weeks 40 through 47 run −39.6%, −32.2%, −41.0%, −44.0%, −33.2%, −51.0%, −29.0%, −51.3% — Facebook return on ad spend never once exceeded 1.00, and spend went from the $1,088.89 Chris was reacting to up to $2,569, about 2.4 times the number that triggered "stop the bleed."
No single knowledge base could produce this. The doctrine and its enforcement mechanism are in one founder interview; the coach's verbatim diagnosis and its date are in a database table; the 41 competing instructions are scattered across ten separate call summaries; and Tim's own recall-kb capture of Jon McNeill supplies the same rule from the Tesla side — the fix came from noticing the one bottleneck, not from working a list.
founders-kb/interviews/038-zach-dell-on-base-power-transcript — the seed, read in full. Gracias's standing single question, the turtle that "can only be moved when critical path is resolved," the hot-potato cadence, and "it's kind of like a cope... to talk about the other stuff." Fetched 2026-09-12, never previously mined.wescale-kb/scorecard/wescale-scorecard.db — scorecard_reviews holds exactly three IGL reviews (calls 31, 32, 34) carrying the coach's verbatim words; observations supplies the eight consecutive negative-margin weeks and the spend rise. Imported data, newest IGL week 2026-W34.wescale-kb/calls/call-34 — carries the first five of the 41 items, written the same week the coach said cut spend.wescale-kb/calls/call-45 — six more new items, dated 2026-09-03, thirteen weeks after the constraint was named and still unresolved.recall-kb/Business/Entrepreneurship/Ex-Tesla President Elon Asked Me To 20X Sales. Here's What I Did — Tim's own capture, filed 2026-04-10. Jon McNeill on "noticing for bottlenecks" as the superpower. Already on the shelf, unapplied.wescale-kb/planning/weekly-routine-sop — the mechanism to modify. Step 4 builds each calls/call-N.md from the template every Sunday 9 AM. This is the machine that manufactures a new priority list every seven days.scorecard_reviews (the coach names IGL's constraint twice: margin) → observations (eight straight negative-margin weeks, spend 2.4×) → enumerate every call file for IGL-application headings (41 competing items) → recall-kb Jon McNeill on noticing the one bottleneck → the SOP step that generates the lists.igl-brand-kb/core/brand-guide-from-inside-out.md:98 is "the raccoons had other plans," and the raccoon character card says DON'T portray as villain, while the customers asking are framing it as the robber ("they empty ours lol"). Then add G:\iris\igl-ads\scripts\pull-ad-comments.py as a step in the MasterWeekly Windows task you already run (next fires Saturday 2026-09-19 4:04 AM), so the request list refreshes weekly instead of sitting frozen at the 2026-08-04 pull.IGL has answered "make it a raccoon" six times by linking an existing raccoon graphic tee, and the same request kept arriving anyway — because nobody is asking for a raccoon, they are asking for this joke with a raccoon in it, and that shirt has never been made.
WeScale call #34 floats a comment-to-design pipeline as a concept — scrape the Facebook comment requests, feed them back through the design pipeline, repost — and Chris tells the room to validate it by hand first, because he found thousands of requests in his own archive (wescale-kb/calls/call-34.md:39). IGL's archive is already pulled and sitting in a JSON file. It has been mined twice — once for voice, once for drawing defects (nugget #035) — and never once for the thing Chris actually described.
Run it over the whole corpus and the concentration is extreme. Of 1,722 ad posts, only 196 ever received a comment, and 1,252 comments — 39.0% of every comment IGL's ads have ever collected — sit on ten posts for one design, the bird feeder shirt. Hand-classify every comment naming an animal and the request order is raccoon 7, deer 5, bear 1. (On raw mentions bear 9 edges deer 8, but seven of those nine bears are people telling bear stories, not asking for a shirt. Requests are the honest unit, and on requests the order holds.)
Here is the part no judge reached, and the reason this is not "make more animal variants." IGL already sells nine raccoon shirts. Across all nine, lifetime: 37 units, $1,166.79 — 0.33% of the store. Six of them, every one created in 2026, have sold zero. And six times between January and June 2025, a request for a raccoon was answered in-thread with a link to one of those existing raccoon tees — four of them within a day of the ask. The asks kept coming after each reply. The existing raccoon shirt is not a near-miss on the request; it is an answer to a different question. The bird feeder family, over the same measured period, is 4,322 units and $137,613.52 — 38.8% of all store units.
That distinction is where the two sources collide. The mastermind's answer to a slow week is breadth — call #34 line 38, "100 designs/week is not too many." Todd Graves built Raising Cane's on the opposite instinct and is explicit about the pressure he refused: the chains around him kept adding menu items to dodge the "veto vote," he studied In-N-Out ("since 1948, they have the exact same menu") and concluded "you can do one thing and do it better than anybody else." He draws the line that matters here too — "it's not simple. It's focused." A raccoon version of the bird feeder shirt is In-N-Out's animal style: a variation on the one item people already come for. Nine unrelated raccoon shirts are the veto-vote menu.
No single shelf produces this. The mastermind supplies the mechanism and the instruction to hand-validate it. A 2025 restaurant interview supplies the discipline that says spend the variation on the proven item. Only IGL's own comment archive says which animal. And only the sales database says the obvious objection — "we already have raccoon shirts" — is exactly the mistake.
wescale-kb/calls/call-34 — SEED. Dated 2026-06-18, a call record. Supplies the comment-to-design pipeline concept and Chris's "validate by hand first" instruction (line 39), and the competing volume doctrine, "100 designs/week is not too many" (line 38).founders-kb/interviews/004-todd-graves-transcript — THE BRAID. 2025 interview, different era and trade. The "veto vote" pressure, In-N-Out's unchanged 1948 menu, "you can do one thing and do it better than anybody else," and "it's not simple. It's focused." All verified verbatim.igl-brand-kb/methodology/design-flywheel-framework — Status: CURRENT SoR, filed 2026-03-03. Line 127: the only raccoon idea in current methodology is a text shirt, "small raccoon silhouette bottom corner" — not the illustration swap 7 customers asked for. This is the gap the nugget closes.igl-brand-kb/core/brand-identity-guide-v9 — Status: HISTORICAL, compiled August 2025, superseded February 2026, and cited as historical. Line 446, character card "Ross — Ninja Raccoon … DON'T: Portray as villain." The routing constraint on the render. The current voice docs agree: "the raccoons had other plans" is affectionate (core/brand-guide-from-inside-out.md:98, voice/voice-guidelines.md:44).igl-brand-kb/audience/profiles/05-carol-garden-witness — buyer profile, independent corroboration from a non-ad source: "feeders in at night (raccoons), ammonia on the baffle (bears)." Persona research and ad comments name the same animals.igl-brand-kb/audience/who-data-map — theme-aggregate, the one permitted. Line 30 locates the corpus and dates it: 3,210 comments (2,124 unique), harvester re-runnable, pulled 2026-08-04 — six weeks stale as of tonight. Sources outside the knowledge bases, named as such: the comment archive G:\iris\igl-ads\data\ad-comments-2026-08-04.json and the operational database G:\iris\igl-ops-sage\data\igl.db. The thirteen knowledge bases hold no product-level sales data, so every unit and dollar figure above is an operator query of a database outside them, measured through 2026-09-13 — not a document quotation.