Brand database · briefs/skinscience/BRAND.md · source of truth

Skinscience — Brand Database (BRAND.md)

Skinscience — Brand Database (BRAND.md)

The single source of truth for every durable fact about this brand. Any note David sends

(inventory, suppliers, accounts, contacts, decisions) is filed HERE the same turn it arrives —

before any context compaction. Memory files only POINT here. Never store secrets (tokens, keys,

passwords): reference the env file that holds them. Keep entries dated. Hub renders this file.

0 · Identity & entities

FieldValue
Legal entity / ownerTO FILL
Key people & rolesTO FILL
Support email / phoneTO FILL
Brand relationshipTO FILL (own brand / client / partner)

1 · Products & SKUs

CodeProductSize / formatUPCFormula / spec sourceSupplier
TO FILL

2 · Inventory & supply chain

SKUUnits on handLocation / 3PLLot / mfg dateShelf lifeCOGS (landed)MOQ / reorder lead timeUpdated
TO FILL

Notes: TO FILL (fulfillment partner, shipping SLA, packaging on hand — sample packs, inserts).

3 · Offer & pricing (locked)

TO FILL — retail, compare-at, tiers, subscription, guarantee, OTO chain, shipping policy, launch code.

4 · Accounts & IDs (no secrets)

SystemID / handleNotes
Domain(s) / DNSTO FILL
Netlify site (id · team)TO FILL
29next store / campaignTO FILL
Meta BM · ad account · pixelTO FILLCAPI token → env file only
GA4 property · measurement id · GTMTO FILL
Klaviyo orgTO FILL
adscalerads client · Airtable baseTO FILL
Cookie / event prefixTO FILL

5 · Compliance ceiling

TO FILL — category rules, banned words file, reviewer rulings, disclaimer form.

6 · Decisions & taste log (dated, David's verdicts = ground truth)

7 · Asset map

TO FILL — raw vault, official logos/wordmarks, packaging files, photography, UGC, boards, Visual DNA.

8 · Live surfaces

TO FILL — PDP, home, checkout, hub workspace, boards, console lane, docs pages.

9 · Open questions / asks

TO FILL

10 · Change log


Imported status record (2026-09-02) — distribute these facts into the sections above as the brand is touched

From memory melanolyse_ad_angles.md

Ad-angle bank for Melanolyse (SS-02, hyperpigmentation) — feed these into the first Melanolyse shot list.

1. Spots-spell-a-word (David, 2026-07-06 — verbatim: "spell a word on face with dark spots or on her chest")

STATUS: registered as image-framework spots-spell-a-word in creative/dashboard/image-frameworks.json (2026-07-11, 15th entry, hero = Melanolyse R1 FW-1 "PCOS" cheek) — pull it from the library for future rounds, don't re-improvise the prompt.

Dark spots/hyperpigmentation arranged so they spell a word on the face or on her chest — the condition itself becomes the typography. The hyperpig cousin of the proven [[handwriting-on-skin-ugc]] framework (6/8 keep, BronzeChews R1), but the WRITING is made of the dark spots rather than marker: uncanny/weird-first (matches the universal "not weird enough" kill signal), a double-take composition, and inherently on-mechanism (the product fades exactly what's spelling the word).

2. PCOS × body-hyperpig (validated by the 2026-07-06 sweep — the P4 prelander thesis)

The three biggest keywords of the Melanolyse competitor sweep were exactly this intersection: PCOS 89 · dark inner thighs 89 · dark neck 80 (underarms 17; body trio = 186 raw advertisers) while face-serum brands ignore the body zones. Acanthosis-nigricans vernacular ("dark neck", "dark inner thighs") is the pain language. Try Strawberry is the only major comp on it, scaling "PCOS makes hyperpigmentation 3x harder to treat due to insulin resistance" (2x variants). See sweep provenance ads/research/hyperpigmentation/sweep-report-r1.json + library creative/skinscience-hyperpig-swipe/.

3. Scaled hooks observed in the niche (from tier-1/2 of the sweep)

Related: [[jt_ad_pipeline_skill]], [[judgement_and_taste_principle]], [[doctors_investigation_cdc_nih_rule]].

From memory skinscience_checkout_status.md

SkinScience Checkouts + byskinscience.com Consolidation Status

2026-06-03: ALL 5 SkinScience checkouts LIVE on one domain (byskinscience.com), functional-first.

Commits 9bcaa105→db5ea357 (keratolyse) + cecca783 (consolidation) + d794f4b3 (other 4).

The single-site model (David, 2026-06-03)

byskinscience.com serves the WHOLE brand from ONE Netlify site

skinscience (id 9f0fc061-ac75-4a3a-adcd-704514dc3be5, custom_domain

byskinscience.com). Deploy = publish products/skinscience/ so every

product is a path subfolder. NO proxy, NO per-product sites.

5 legacy per-product Netlify sites are now REDUNDANT (no custom domains, only .netlify.app). David PAUSED them 2026-06-03 (not deleted — reversible, builds stopped). IDs if ever needed: skinscience-keratolyse 7df183e9-…, -melanolyse 946b3c99-…, -eczemolyse e35d3cce-…, -dermalyse cc035f3f-…, -bronze-chews bbf209c8-…. KEEP 9f0fc061 (byskinscience.com).

29next "Skin Science 2" campaign — package map

ONE shared campaign, public key stH8gNgcvXaLcZzzYUK15n8VodciCFfyuqsITBgd.

CORS whitelisted for https://byskinscience.com (verified). 15 packages = 5 products × 3 bundle tiers:

ProductCodeMild/1×Mod/3× (PDP ?pkg=)Full/5×condition
keratolyseSS-01567KP / texture
melanolyseSS-028910hyperpigmentation
eczemolyseSS-03111213eczema
dermalyseSS-04141516micro-infusion device (vials)
bronze-chewsSS-05171819tanning chews

Bundle names: SS-01..04 = "Mild Issue / Moderate / Full Treatment"; bronze = "Light Tan / Medium Tan / Dark Tan" (different — pkg names 17/18/19). All $34.99 / $23.33-ea / $20.99-ea, retail $59.99.

OTOs LIVE (2026-06-03, commits ba0338fa+f31ec51c): David created 10 OTO packages (VIP 20-24 $17.49+$9.99/mo, Extra Strength Upgrade 25-29 $11.99 — one per product). All 5 funnels now: checkout → special-offer/vip (VIP pkg) → special-offer/upgrade (Extra Strength pkg) → thank-you. Built from template/upsells/ghost-upgrade (clean placeholder fill), relative routing (checkout next-next-url→../special-offer/vip/; vip→../upgrade/; ES→../../thank-you/), SS attribution stubs (0 NS pixel). VIP copy=membership-generic; ES copy=condition-rewritten per product. NO OTO 3 yet (David scoped OTO 1+2 only).

The checkout replication recipe (reusable for future SkinScience SKUs)

Checkouts were cloned from the NailScience checkout (cleanest base w/ all session fixes), then keratolyse was hand-built as the template, then the other 4 replicated. Per-product recipe:

1. cp -R keratolyse/checkout <product>/checkout && cp -R keratolyse/thank-you <product>/thank-you

2. perl on checkout/index.html: data-next-package-id="5|6|7" → product band; preselect ^[567]$ → ^(N|N|N)$ + PKG_INFO keys; Keratolyse→Product, keratolyse→product, SS-01→formula; showcase image ../assets/ss-01-bundle-6.png→product shot (placeholder.svg if no render); eyebrow/subtitle/feature-chip swaps.

3. perl on thank-you: Keratolyse→Product, SS-01→formula.

4. perl on PDP: href="/checkout/→href="checkout/" (6 links).

5. Hand-edit the 3 testimonials → condition-specific (KP/hyperpigment/eczema/firming/tanning).

6. Verify: 0 NailScience, 0 NS pixel, correct band, coupon hook, config.js node --check.

Traps codified (each bit during this build)

Tracking still Phase-1 stub

All SkinScience tracking = placeholders (SKINSCIENCE-PIXEL-ID, GTM-XXXXXXXX, ss-attribution.js CAPI off). Wire real SS pixel/GTM/CAPI env vars (mirror HF shared/functions/ENV_SETUP.md) BEFORE paid traffic. No real events fire yet (safe, just no attribution).

Pending (whenever David wants)

1. ✅ DONE — 5 redundant per-product sites PAUSED by David (not deleted; reversible).

2. ✅ DONE — OTO 1 (VIP) + OTO 2 (Extra Strength) live on all 5 (see OTOs LIVE above). Possible future: OTO 3 (bundle) per product if David wants a 3rd slot (needs more 29next packages).

3. Re-skin pass — SkinScience steel-blue palette (still NS-derived nailscience/css chrome), real product shots for melanolyse/eczemolyse, swap NS support phone in header, ~~SkinScience legal pages (footer /pages/ links 404)~~ ✅ DONE 2026-07-24 (compliance-footer rollout, commit 4eec827e, deploy 6a63d3811eee4cc79a26ea57): 7 one-sided legal pages live at byskinscience.com/pages/* + all 5 PDP footers wired + pretty-URL redirects. Dual-product-type Medical Disclaimer (topical AHA + Bronze ingestible). See [[compliance_footer_rollout_skill]], finalize testimonial copy (mine are functional-first).

4. Real SS tracking IDs.

2026-07-30 URL MIGRATION (21598620): byskinscience.com moved to

Shopify-standard URLs — PDPs at /products/<sku>/ (checkout/OTO/thank-you

children moved along), /collections/all/, blog mirrors at

/blogs/journal/<slug>/, legal canonical /pages/<name> (extensionless).

Permanent 33-rule 301 layer covers every old URL (query-strings pass).

SEO layer added: sitemap.xml (19 canonicals), robots.txt, canonical tags,

noindex on all funnel-private pages. Pixel/CAPI/29next/GA4 path-agnostic —

nothing reconfigured; verified live (checkout hydrates on new path,

capi 204). Trap: URL-migration rewrites must catch BARE-STRING refs

(manifest live_urls, app.js maps, master.jsons) — attribute-regexes miss

them; sweep with a repo-wide domain grep before calling it done.

From memory skinscience_tracking_status.md

Canonical IDs (LIVE as of 2026-06-08)

Status: browser pixel + server CAPI LIVE (2026-06-08)

What shipped

1. Browser Meta Pixel (commit 6e17ba6c) — SKINSCIENCE-PIXEL-ID → 996202390008940 + GTM-XXXXXXXX → GTM-N7Q6QQRZ across 30 files (functional fbq('init')/noscript/snippet/iframe). Verified firing live (/tr?id=996202390008940&ev=PageView HTTP 200 with our eid=ss_pageview_...).

2. Server-side Meta CAPI (commit df08e664) — CAPI_ENABLED false→true in all 5 ss-attribution.js. Browser relays each event to /api/capi (shared capi.mjs) which posts to Meta with FB_PIXEL_ID + FB_CAPI_ACCESS_TOKEN. Verified: direct token POST {"events_received":1}/200; /api/capi returns 204.

3. Netlify env (production): FB_PIXEL_ID=996202390008940 (all scope) + FB_CAPI_ACCESS_TOKEN (functions, secret).

Funnel + dedup (already correct from the HF/NS template)

The CAPI debugging saga (2026-06-08) — codified in attribution_testing_protocol.md

Spent hours wrongly concluding the token was "read-only / needs a dedicated Business app." Root cause was a TEST-HARNESS bug: my diagnostic curls omitted ?access_token= on the POST /events URL. An unauthenticated POST returns code 100 / subcode 33 / "object does not exist or missing permissions" — identical to a permission failure. The read_ads_dataset_quality scope posts fine. David caught it by pasting Meta's endpoint docs. Lesson: always put the token on the POST URL; verify HTTP 200 + events_received:1; production capi.mjs was always correct. Full checklist in attribution_testing_protocol.md "HARD LESSON: manual CAPI test MUST include ?access_token=".

2026-06-08 evening — server CAPI + webhook ACTUALLY live (the env-var saga)

After flipping CAPI_ENABLED I assumed server CAPI was live (the /api/capi 204). It WASN'T — and neither was the webhook (unsigned POSTs returned 200, signature not enforced). Root cause: netlify env:set --site=9f0fc061 … printed success and env:list --site=9f0fc061 SHOWED the vars, but they never landed on the real site — the CLI resolved --site against a different account context. Authoritative proof: the site's Netlify UI showed "No environment variables set" and GET api.netlify.com/api/v1/accounts/teo-h3uxfci/env?site_id=9f0fc061 returned []. So the functions read undefined for FB_CAPI_ACCESS_TOKEN/NEXT_WEBHOOK_SECRET → CAPI fan-out silently disabled (enabled() saw no token) + webhook ran the insecure no-secret branch.

Fix: set the 3 vars (FB_PIXEL_ID, FB_CAPI_ACCESS_TOKEN, NEXT_WEBHOOK_SECRET) via the Netlify UI (Add a variable → Import from a .env file → All scopes, all deploy contexts) → redeploy --skip-functions-cache. Confirmed working: unsigned webhook → 401 "Missing signature", signed (HMAC) → 200. Server CAPI fan-out now live (token readable). Codified in skills/attribution-launch/ Trap 2 + Obsidian playbook Trap 3. Don't trust env:list — verify env via the UI or the accounts/env API. WEBHOOK_DEBUG env was used to diagnose, now unset.

Note: a few fake test Purchases (orders X, SS-WHTEST-*) hit the dataset during debugging — disregard in early reporting.

2026-06-09 — Funnel audit: event layer was DEAD + live edge clobbered (both fixed, commit a438e6bb)

25-page workflow audit (5 products x PDP/checkout/thank-you/OTO-vip/OTO-upgrade, source + live edge) triggered by "did we add attribution to the OTOs?":

P0-A — live edge was CLOBBERED back to placeholders. All 25 deployed pages served SKINSCIENCE-PIXEL-ID/GTM-XXXXXXXX/CAPI_ENABLED=false even though source was correct. Root cause: the attribution commits lived ONLY on claude/brave-cartwright (CMPD without the Merge); another session deployed byskinscience.com from the MAIN checkout -> placeholder versions shipped. FIX: branch merged to main (a438e6bb) — future main-checkout deploys now carry the wiring. HARD RULE: CMPD includes MERGE-TO-MAIN for any deploy-bearing work; an unmerged branch + a main-checkout deploy = silent live revert.

P0-B — browser event layer structurally dead beyond auto-PageView (all 5 products). Two stacked bugs: (1) PDP+checkout bound var T = window.NS_TRACKING (NS template leftover, undefined on SS pages); (2) ss-attribution.js was the Phase-1 stub exposing ONLY fireEvent() while pages call trackEvent/sha256/getCookie/initScroll/initRage/initTimeOnPage/adIds. So ViewContent, AddToCart, begin_checkout, lead/shipping/payment micro-conversions, the BROWSER Purchase (purchase_<orderId>), receipt_view, upsell_view AND injectHiddenFields (29next attribution note_attributes!) never executed. Matches the live symptom: only PageView in David's browser capture. FIX: full ns-attribution.js port -> ss-attribution.js (Patterns A-I, correct CAPI payload shape, _ss_eid, shared _ns_utms/_ns_landing/_ns_referrer names preserved for webhook), exports BOTH window.SS_TRACKING and alias window.NS_TRACKING (same object); all var T = bindings rebound to SS_TRACKING.

P0-C — all 5 thank-you/assets/config.js carried the NAILSCIENCE campaign apiKey (g34IbGqX...) -> replaced with SS key (stH8gNgc...).

OTO gaps (the original question): pixel/GTM/attribution-include/paths were correct on all 10 OTO pages, BUT (1) NO accept tracking — accept/skip CTAs fired zero events; added upsell_accept/upsell_skip (custom:UpsellAccept/UpsellSkip, sendBeacon survives SDK nav) to all 10; (2) VIP pages were mislabeled upsell_upgrade (pageType/offer_name/content_ids) -> now upsell_vip, the two OTOs are distinguishable.

Payload hygiene: content_ids ['nailscience-kit'] (4 sites per checkout incl. Purchase) -> ss-01-keratolyse...ss-05-bronze-chews; ns_pdp_view_fired/ns_receipt_view_fired -> ss_*; ['ns-thank-you'] -> ['ss-thank-you'].

Live-verified post-deploy: pixel+GTM on PDP, served JS exports trackEvent + alias + real pixel (stub gone), OTO accept wiring + vip identity live, checkout SS binding + per-product content_ids, SS campaign key on thank-you config. A few HF orders polluted SS's dataset 2026-06-08 (FB_PIXEL_ID clobber window) + fake test Purchases (X, SS-WHTEST-*) — disregard in early reporting.

Still open: upgrade-OTO 29next package IDs 25/26/27/28 (+bronze) carry unresolved TODO(29next) — verify against the Skin Science 2 campaign before trusting upsell revenue; checkout/nailscience/ folder naming; stale [REPLACE] comments; mojibake in OTO comments.

Standing follow-ups

2026-06-15 — Dual-fire "SS_" shadow events shipped (Blocked-by-Meta insurance)

Rolled the HumanFrame archetype (see humanframe_attribution_status.md 2026-06-15 + attribution_stack_skill.md Pattern J) to SkinScience as proactive insurance — SS's standard events are NOT currently blocked, but the SS_<Name> mirror now flows on all 5 SKUs so a future "Blocked by Meta" is a Meta-UI-only swap (build Custom Conversions on the SS_* events, re-point campaigns, zero deploy).

Cross-references

2026-06-28 — 5-Reasons PRELANDERS: full R1–R5 creative + LIVE deploy

All 5 SkinScience 5-Reasons prelanders are now deployed live with per-reason creative. Each has its OWN Netlify site (EcomScalers) — the sites already existed, just weren't linked locally (no .netlify/state.json). Deploy via tools/deploy-skinscience-prelanders.sh (netlify deploy --prod --site=<FULL-uuid> --dir=prelanders/skinscience/<dir>). TRAP: use the FULL 36-char site UUID — a truncated id → "Project not found. Please rerun netlify link". Sites:

(Investigation + Top-5 prelanders ALSO have their own sites: skinscience-<sku>-investigation / -top5 — not yet deployed.) Prelander CTAs point at the byskinscience.com/<sku>/ PDPs (separate site 9f0fc061…, deploy via tools/deploy-skinscience.sh).

Per-reason creative (commits 2e7afd02→9a850ba7, mechanism-shotlist pipeline): R1=ingredient mechanism (Image-2), R2=mechanism (board ▼03, from on-page copy not the misplaced brief), R3=mechanism/animation (▼04), R4=demonstration loop (▼05, benefit/value reason→contrast not mechanism), R5=static image (▼06, week-12 result photo via Gemini i2i from the page's hero customer + bronze trust-stack). 4 non-keratolyse SKUs got R2/R4/R5; keratolyse R1/R3 video + R2/R4/R5 photos. See [[mechanism-shotlist-video-skill]] + [[board-video-display-traps]].

2026-06-29 — HERO GIFs live on all 5 SkinScience 5-Reasons prelanders (commit c3446396)

Replaced the static before/after slider hero with a ~3.2s looping UGC hero-gif on all 5 (keratolyse was the approved example → rolled to the other 4). Each cycles believable iPhone-UGC stills of ONE consistent person/area: affected-area BEFORE → product-in-hand → AFTER. Reusable builder tools/build-hero-gif.py (Ken-Burns + xfade loop → mp4 + poster + gif). Deployed live via tools/deploy-skinscience-prelanders.sh; all 5 verified (hero-ba video + assets 200).

2026-06-29 — HERO GIF CORRECTION: before|after SPLIT PANEL, not sequential (commit 70ae9880)

The sequential before→product-held→after loop above was WRONG. David: "they were supposed to be before/after side by sides." Rebuilt all 5 as a side-by-side split panel: BEFORE (left) | AFTER (right) of the SAME person/area, white center divider + BEFORE/AFTER label pills, subtle synced zoom (cosine 1.0↔1.045, seamless loop), ~3.2s. Builder tools/build-ba-split.py (PIL per-frame composite → ffmpeg; reuses the consistent before/after halves cropped from each X-ba split). Asset swapped in place + cache-bust ?v=1→?v=2 (same filename → edge would serve stale otherwise). All 5 live + verified. LESSON: "hero gif" / "before-after" = a SIDE-BY-SIDE SPLIT panel (both states visible at once), NOT a sequential reveal — confirm format before building. Watch-item: dermalyse's two split halves are slightly different framings (neck vs arm) — offer to refine the source crop if it bugs David.

Bronze prelanders (SS-P14/SS-P15) — attribution LIVE 2026-07-02 (commit 950c5f8e)

Hosted on the consolidated site skinscience-bronze-prelanders.netlify.app (25ac92fa-…, EcomScalers): /investigation/=SS-P14, /top5/=SS-P15, root 302→investigation; deploy tools/deploy-bronze-prelanders.sh (staged rsync from prelanders/skinscience/{investigation,top5-advertorial}); supersedes the 2 per-prelander sites; no custom domain mapped yet. Wired: GTM-N7Q6QQRZ + pixel 996202390008940 + own copy of ss-attribution.js per page; SS_TRACKING.CAPI_ENDPOINT = ABSOLUTE https://byskinscience.com/api/capi (prelander site ships no functions — capi.mjs answers CORS/OPTIONS, verified 204 + allow-origin:* from this origin). PrelanderView/PrelanderCTAClick fire via the runtime (custom: events, event_id + CAPI mirror); Pattern I forwarder (pre-staged) lifts _fbp/_fbc/_ss_eid→fbp_in/fbc_in/eid_in on 7 data-cta-forward CTAs per page → PDP adopts identity. Traps fixed: investigation carried HF_TRACKING clone residue (renamed); top5 had a dataLayer-only trackEvent SHIM that would swallow PrelanderView pre-runtime + sessionStorage-mark it (removed — blocks poll for the real runtime). Test events to disregard: SS-PRELANDER-RELAY-CHK.

Prelander hub UPDATE 2026-07-06 (commit dc78c5b7) — 14 pages, all wired

The bronze site grew into thehealthreportdaily.com (same site 25ac92fa, custom domain mapped; deploy tools/deploy-health-report.sh superset — the old bronze script is guarded). Attribution activated on the 12 new paths (SS-P2/3/5/6/8/9/11/12 product investigation+top5 + SS-P16-19 Dermatology Report pages): same stack as bronze (GTM+pixel+own ss-attribution.js copy+abs CAPI). Scaffold traps: investigation pages carried HF_TRACKING clones; top5s the SS shim; Dermatology-Report pages an AD_TRACKING shim with fire-and-forget fireView() (no poll) — poll pattern injected or PrelanderView dies silently. Forwarder destinations: per-product PDPs on byskinscience.com (one-routine-method → /collection/). All 14 live-verified fbq+GTM+CAPI+runtime-200.

Purchase over-count bug FIXED 2026-07-08 (66c7896f)

LL1 showed 15 Purchases / 4 bronze orders. Cause = Pattern K (see [[attribution-stack-emq-hardening-skill]]): campaign-cart SDK's facebook provider enabled on all 5 SS checkout configs (with NS's pixel in settings), firing eventID-less broadcast Purchases + redirect-queue replays. Disabled fleet-wide + NS-pixel refs scrubbed; live-verified fb:false on all 5 SS + HS + memo + HF checkouts. Historical inflated conversions can't be retracted — expect Purchase ≈ orders going forward.

3-conversions-per-order bug FIXED 2026-07-24 (9c008ca3) — Pattern L

1 order → 3 Purchases: the store's "29OrdersCapi" webhook (All Events) fed customer.created/transaction.created into order-webhook.mjs which had NO event_type gate → each minted a distinct un-dedupable purchase_<id>. Fixed: function gate (deployed all brands, verified via signed customer.created probe → 200 Ignored) + webhook 100 narrowed to order.created (dashboard). See [[attribution-stack-emq-hardening-skill]] Pattern L. Note: 29next Meta Pixel app installed on the store with foreign pixel 767335789488798 — currently inert (zero sends logged); uninstall candidate. Expect Purchase ≈ orders from 2026-07-24 on.

Blog 5reasons prelanders — attribution LIVE 2026-07-24 (08fe22e2)

All five byskinscience.com/blog/-five-reasons mirrors (bronzechews/kera/mela/ecze/derma; canonicals prelanders/skinscience/{5reasons,-5reasons}) wired with the standard SS prelander stack (GTM + pixel + own runtime + abs CAPI + Pattern I forwarders). Edited canonicals → sync-blog-mirrors → deployed; all 5 live-verified.

From memory sslyse_ads_pipeline_status.md

SkinScience -lyse family ad-pipeline state as of 2026-07-24 (all committed through 7b97341f):

Generation boards (creative/<slug>/, on 8766 + OCC page rows):

Swipe libraries (verdict queues):

Session-hardened patterns (details in skills/jt-ad-pipeline/SKILL.md §III + Obsidian "J&T Ad Pipeline"): 3-round swipe escalation is default; kill-on-sight enforced via --skip-pages; launch route batches DB writes via createMany after the parallel FB phase (b4a4581b — mid-phase launch death leaves a PARTIAL ACTIVE Meta campaign, check Ads Manager before retry); OCC page rows = generated ads vs SWIPE rows = competitor libraries (no-board v89 + campaign-matcher fixes); verdict -latest files live in MAIN repo tools/jt and can be clobbered to 0 — dated snapshots are durable.

Related: [[jt_ad_pipeline_skill]], [[melanolyse-ad-angles]], [[jt_ad_launch_architecture]], [[judgement_and_taste_principle]].

Rendered 2026-11-16 from the git-tracked file. Edits happen in the repo (Claude files every fact David sends the same turn); this page is the read view.