WholeMagnetics: where we stand, and how we lead

CONTEXT (read first): The WholeMagnetics network promotes "advanced multipole magnets" (Tim Costello's term) made by Polymagnet / Correlated Magnetics Research. polymagnet.com is the PARTNER's Shopify store — we have NO backend except the analytics access Mary Morman granted; every change is hand-applied by Mary/CMR. Melissa was explicit (Oct 5): stay on Shopify, no replacement build. GUARDRAILS: never reproduce any best-of/ranked/award-winner list (a real DMCA happened on the network); roll-up targets are confidential, never published; subscription only, never an API key or credits; own the short-reach limit honestly; customer-first voice, no humor, no fake personas; ask before any nginx/auth/DNS/email/money change. The pass-1 audit is live at https://wholemagnetics.com/priorities/polymagnet-pass1.html and saved in _brain/magnetics/.

TASK: Turn the pass-1 audit into a clean, prioritized hand-off CMR can apply in the Shopify admin this week. Group by effort: (1) site-wide title suffix fix (drop the doubled "Polymagnet – Polymagnet"), (2) rewrite product SEO titles/H1s to lead with the function + keep SKU trailing (give 15 exact rewrites for the worst bare-SKU products), (3) homepage meta description + Organization/WebSite JSON-LD, (4) Product schema with offers on every product, (5) FAQPage intros on the function collections, (6) verify the apex polymagnet.com → www redirect. Output as a checklist with copy-paste values and the exact Shopify field for each. Draft a short cover note to Mary (cc Tim, Melissa) — DRAFT ONLY, Paul signs. Then set a reminder to re-crawl in 30 days and measure against the analytics Mary shared.

CONTEXT (read first): The WholeMagnetics cluster is live under /var/www on root@143.198.182.180 (batch SSH into one call; fail2ban blanket-bans rapid reconnects on all ports). Our storefronts codedmag.com, codedspring.com, ferrospring.com, maxelmag.com, maxelmagnets.com, polymagnetics.com and magnetpoly.com currently carry only Organization + WebSite JSON-LD. Generators live in /opt/autoengine and /root gen-*.py; AME rebuilds delete injected blocks, so write through blocks.write() so changes survive. GUARDRAILS: never reproduce best-of/ranked lists (DMCA); roll-up targets confidential; subscription only; own the short-reach limit; customer-first, no humor, no fake reviews; the rich version is canonical — back up before regenerating, never overwrite richer with poorer; ask before nginx/auth/DNS/money. magnetpoly.com is a verbatim Polymagnet mirror — leave its branding alone.

TASK: Add Product JSON-LD (name, sku, brand, description, offers with priceCurrency/price/availability) to product pages and FAQPage JSON-LD to the behavior pages across those storefronts, and make each product title/H1 lead with the function ("self-aligning magnet", "twist-release latch") with any code trailing. Use real prices from FerroSpring where they exist; mark availability honestly. Keep the re-lead to "advanced multipole magnets" intact. Back up each site first, write through the generators/blocks.write(), rebuild, and verify live with curl that the JSON-LD parses and the titles changed. Report per-site counts of pages that gained Product and FAQ schema.

CONTEXT (read first): The Automated Marketing Engine lives in /opt/autoengine on root@143.198.182.180 (batch SSH; fail2ban blanket-bans rapid reconnects). It generated the magnetics cluster. Tim wants the SEO/AEO capability to be a clean module you can "turn on for anybody," whose value is RECURRING: it keeps surfacing new suggestions each month, throttled so it never burns the token ceiling ("don't boil the ocean"). GUARDRAILS: subscription only — never an API key/credits (the recurring cadence must respect this); never reproduce best-of/ranked lists (DMCA); roll-up targets confidential; never auto-ship AME output — draft/stage only; the rich version is canonical, back up first; ask before nginx/auth/DNS/email/money.

TASK: Scope the SEO/AEO module to "done and sellable." Read /opt/autoengine and reference_ame_self_driving_seo.md and reference_autoengine_fixes_aeo.md. Produce: (1) a one-page spec of what the module does, its inputs/outputs, and what "one-time vs recurring value" means for a buyer; (2) the gap list between today and sellable; (3) the design for the monthly throttled re-suggestion loop (how much it does per run, how it stays under budget, how a customer sees "another idea this month"); (4) a stub spec for Module #2 (social media) — posting own content AND replying to in-space influencers, agents doing ~90% of the labor, drafts only. Do not ship anything; write it up for Paul and Tim to review.

CONTEXT (read first): WholeMagnetics cluster live under /var/www on root@143.198.182.180 (batch SSH; fail2ban blanket-bans rapid reconnects). The hub has /wmc/ask/ (answer-first "which magnet does what") and guide sites (multipolemag, codedmag, maxelmag, multipolemagnets) carry FAQPage/Q&A. Lead term: advanced multipole magnets (keep "coded/programmable" as aliases). GUARDRAILS: original words only, never reproduce anyone's content or lists (DMCA); facts + our own selection; own the short-reach limit honestly; customer-first, no humor; subscription only; back up before regenerating, AME rebuilds delete injected blocks (blocks.write()); ask before nginx/auth/money.

TASK: Grow answer-first coverage of each magnet BEHAVIOR a buyer searches — align/self-align, latch, twist-release, spring, hold-and-release, torque, shear — into full Q&A pages on /wmc/ask/ and the guide sites. Each page: a one-line direct answer first, then the mechanism in plain words, the honest limit (reach), which product delivers it, and FAQPage JSON-LD. Lead with the function in title/H1/first sentence. Cross-link every behavior page to the matching product and to the catalog. Back up, build, verify JSON-LD parses, and report how many behavior pages now exist and which queries each targets.

CONTEXT (read first): WholeMagnetics cluster live under /var/www on root@143.198.182.180 (batch SSH; fail2ban blanket-bans rapid reconnects). No Agents First score is on record for any cluster site. Read reference_agents_first.md and use /root/af-deploy.py as a starting point but hand-tune per site. GUARDRAILS: subscription only; never reproduce lists (DMCA); roll-up targets confidential; the rich version is canonical, back up first, AME rebuilds delete injected blocks (blocks.write()); nginx/mime/.well-known changes need approval — write the diff and STOP to ask; do not touch magnetpoly.com branding.

TASK: Raise the hub wholemagnetics.com and the main guide/storefront sites to 90+ on the Agents First scorer (curl JSON-RPC to https://agentsfirst.dev/mcp, tool score_website). Per site: AGENTS.md (~40 lines of real, non-obvious context — what "advanced multipole" means, the behaviors, the honest reach limit, how to cite us, that Polymagnet is the maker), an OpenAPI read API over the catalog/behavior data, /.well-known/mcp-server-card.json and ai-plugin.json, per-page markdown, a Content-Signal line and named AI agents in robots.txt, and a visible "For AI agents" footer link. The nginx parts (text/markdown mime, Accept negotiation, .well-known) need sign-off: write the exact diff, back up the vhost, STOP to ask. Score each site before and after; report every dimension.

CONTEXT (read first): WholeMagnetics cluster live under /var/www on root@143.198.182.180 (batch SSH; fail2ban blanket-bans rapid reconnects). Traffic in /var/lib/awstats, AME scores in /opt/autoengine/workspaces, cluster dashboard at /var/www/wholemagnetics.com/alldomains/ (generator gen-magnetics-status.py imports gen-alldomains.py). Tim: "you've created all these magnetic sites — go through them, what are they for, do we need them all, which get traffic." There are 15. GUARDRAILS: read-only audit, no site changes to produce it; never reproduce lists (DMCA); roll-up targets confidential; subscription only; ask before any consolidation/redirect (that touches nginx). magnetpoly.com is the Polymagnet mirror — note but don't change it.

TASK: Produce a function/sleeper audit of all 15 cluster sites as a noindex page under /strategy/cluster/ (and link it from /strategy/). Per site: its purpose in one line, monthly visits (AWStats), page count, what it ranks for if anything, JSON-LD types present, and a recommendation — KEEP (active), SLEEPER (hold, activate later), MERGE (fold into another), or FIX (specific gap). Flag duplicates among the four near-identical storefronts and recommend how to differentiate or consolidate them so the "which approach wins" experiment gives signal. Any merge/redirect is a proposal only; list the nginx changes it would need and STOP. Show the table and the decision for each site.

CONTEXT (read first): Tim's recurring gap — the Polymagnet site is all discrete magnets with no robust MACHINERY section. The magnetizer systems are Polydesk, Polylab and Polymag 6.2 (they "print" maxel patterns into blanks). This could extend polymagnet.com (Shopify, hand-applied by CMR — stay on Shopify per Melissa) OR be a dedicated equipment site needing a new .com. GUARDRAILS: a new domain is money — ASK Paul before registering; never reproduce lists (DMCA); roll-up targets confidential; subscription only; original words; own the short-reach limit; back up first; ask before nginx/auth/DNS. Lead term: advanced multipole magnets.

TASK: Design the machinery/equipment hub: H1 "Magnetizer Systems for Advanced Multipole Magnets", an answer-first intro (what a magnetizer does — prints maxel patterns into blanks in minutes), a Polydesk/Polylab/Polymag-6.2 comparison table (use case, max magnet size, maxel resolution, throughput, footprint, quote CTA), a FAQ with FAQPage schema, and one indexable child page per system. Deliver it two ways: (a) as a Shopify-ready section + page specs CMR can paste, and (b) as a staged standalone site build ready to deploy IF Paul approves a domain — propose 2-3 short .com options and STOP for the domain decision before registering anything. Show the hub outline and the three child-page outlines.

CONTEXT (read first): The Whole Magnetics Catalog is at wholemagnetics.com/wmc/ with a shop (/wmc/shop/), an AEO "ask" (/wmc/ask/) and a reseller plan (/wmc/plan/). Live under /var/www on root@143.198.182.180 (batch SSH; fail2ban). Amazon Associates tag is colinfirthfan-20. GUARDRAILS: never reproduce best-of/ranked lists (DMCA) — our recommendations are our own selection in our own words; FTC affiliate disclosure required on any monetized page; subscription only; own the short-reach limit; back up first, AME rebuilds delete injected blocks (blocks.write()); ask before any money/account/nginx change (joining a program that needs Paul's account = ASK).

TASK: Work the /wmc/plan/ prompts in fastest-first order. Stand up the two no-approval-needed rails first: Bookshop.org affiliate links on the book rail and Amazon Associates (tag colinfirthfan-20) on the toy/book rail, both with FTC disclosure and the existing buy-click beacon. Then prepare — but do not submit — applications for Speks, Geomag (via Faire), K&J and the wholesale routes, each as a checklist Paul approves. Verify the shop still points buy→ferrospring.com and enquire→polymagnet.com. Report which rails are live and which await Paul's sign-off.

CONTEXT (read first): Mary Morman granted analytics/authorized-user access to the polymagnet.com Shopify store so we can finally MEASURE results (Tim's "track the results"). Polymagnet leads went quiet in late September — the reason we need this. Dashboards live on the droplet under /var/www (root@143.198.182.180; batch SSH; fail2ban). GUARDRAILS: read-only on the store — never change products, prices or settings there; stay on Shopify (Melissa); subscription only; keep any store data private/noindex and never expose credentials; ask before nginx/auth/money.

TASK: Design and build a private (noindex, unlinked) lead-tracking dashboard that ties our SEO/AEO changes to Polymagnet lead/traffic results, using the analytics Mary shared (document exactly what access we have before building — Shopify Analytics export, GA, or admin views). Show, over time: sessions, source/medium, leads/enquiries, and a marker line for each SEO/AEO change we ship, so a month from now "did it work?" is a chart. If the only access is manual export, build the importer + dashboard and write the weekly step. Do not connect anything that needs new credentials without asking. Show the dashboard and name its data source.

CONTEXT (read first): AME Module #2 is social media for the magnetics sphere — posting our own content AND replying to in-space influencers, agents doing ~90% of the labor (Tim). Engine in /opt/autoengine on root@143.198.182.180 (batch SSH; fail2ban). GUARDRAILS: NOTHING is posted automatically — drafts only, the team posts; no fake personas or invented experiences; customer-first voice, no humor-led copy (Tim); never reproduce lists (DMCA); original words; subscription only; ask before any posting/account/money change.

TASK: Build the draft-only social pipeline for the magnetics sphere. From our own catalog/behavior data and the real products, generate a week of posts (one per platform: X, LinkedIn) leading with a magnet behavior and the honest reach limit, plus a short list of in-space accounts/topics worth replying to with draft replies. Save everything to a review file; post nothing. Produce this week's drafts as the sample and show the review workflow.

CONTEXT (read first): Tim will send his current PowerPoint roll-up/consolidation pitch deck. A roll-up (not a consortium) is the real play. GUARDRAILS — READ TWICE: the roll-up target companies are CONFIDENTIAL and must NEVER appear on any site, in any copy, in any email, or in any published file. Keep the deck and all working files private and unpublished (not in any webroot, not in git that syncs publicly). Subscription only; never reproduce others' materials (DMCA); customer-first framing; ask before any money/account change. Do not act on this prompt until Tim's deck is actually in hand.

TASK: Once Tim sends the deck, use agents to sharpen it: tighten the narrative (fragmented market + a common challenge none are prepared for → group to face it, customer-and-market-first, MCC/Sematech analogy), improve the design to real-not-slop, and optionally storyboard a short video. Keep every target name confidential — if the deck lists targets, work with them only in private local files and never echo them into chat summaries, commits or pages. Deliver an improved deck privately to Paul and Tim.

CONTEXT (read first): WholeMagnetics cluster live under /var/www on root@143.198.182.180 (batch SSH; fail2ban blanket-bans rapid reconnects). Priority tracker at /wmc/.. actually /priorities/, strategy at /strategy/, cluster dashboard at /alldomains/. GUARDRAILS: read-only reporting; never reproduce lists (DMCA); roll-up targets confidential (never in the report); subscription only; ntfy topic from the existing .env, never hard-coded; ask before nginx/auth/money.

TASK: Build a weekly report job that writes a private page (noindex, unlinked, under /strategy/report/) and an ntfy summary for Tim and Melissa: Agents First scores across the cluster, storefronts with Product/FAQ schema, answer-first behavior page count, polymagnet.com bare-SKU title count (if measurable from the public site), Polymagnet lead/traffic trend (from the analytics Mary shared), reseller rails live, cluster audit decisions actioned, referring domains if measurable, and bandwidth used. Compare each to the targets in /strategy/. Schedule it after the Monday run. Pull the ntfy topic from the .env. Never include a roll-up target name.