Patrick Bass Area: Monetization (audit p10) · Surface: /admin/gate (paywall heading + body editor) · Dimension: law-violation · Severity: enhancement
Law 8 calls for an AI wand on nearly every config option where it fits. The paywall heading and body are prime marketing-copy fields (what prospects see at the subscribe gate), and the tier description field (index.php:321) is the same kind of pitch copy. The course-sales form proves the wand infrastructure (ai-assist + data-ai-* + mobieusAI) is already wired, so this is a consistency gap, not new plumbing.
Evidence
platform/templates/admin/gate/index.php:345-367 renders the customer-facing paywall heading (`name="paywall_heading"`) and a 10-row body textarea (`id="gtBody" name="paywall_body"`) with a live preview pane, but no AI affordance anywhere in the file (grep for `wand`/`ai-assist` returns 0). The sibling monetization form already establishes the pattern: platform/templates/admin/courses/form.php:211-216 `<button type="button" class="ai-assist" data-ai-feature="ai_learn_course_desc" data-ai-source="#title" data-ai-target="#description_md" ... <i class="fa-solid fa-wand-magic-sparkles"></i> AI description</button>`.Suggested fix. Add an `.ai-assist` button (gated on the relevant AI feature flag) above the paywall body and tier-description textareas, sourcing from the community name/heading and targeting the body, mirroring the courses/form.php pattern.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus
