Patrick Bass Area: mobieusLearn (audit p8) · Surface: mobieusLearn authoring forms (cohorts, paths, badges, cert templates, modules, assessments title/description) · Dimension: law-violations · Severity: enhancement
mobieusAI is positioned as the canonical authoring assistant for mobieusLearn, and the course-summary wand proves the integration pattern works. Extending the same gated wand to the other free-text authoring fields (path/badge/cohort descriptions, cert template copy, module/lesson summaries) would make the AI affordance consistent across the authoring surface as Law 8 intends.
Evidence
Law 8 expects an AI wand on nearly every config option. Only 9 learn templates reference an AI affordance (grep ai-wand/fa-wand/data-ai). The course summary field has one (courses/_form.php:50 `<button id="course-ai-desc-btn">... Suggest with mobieusAI`, gated on ai_learn_course_desc) and assessments has ai-generate. But descriptive free-text fields elsewhere have none: paths/form.php (path description), badges/form.php (badge description/criteria narrative), cohorts/form.php, certificates/templates/form.php (footer/body copy), and module/lesson summaries (courses/modules/_form.php). These are exactly the natural-language fields where a 'Suggest with mobieusAI' wand fits.Suggested fix. Reuse the courses/_form.php wand pattern (gated button + fetch to an /api/learn/ai/* endpoint + aria-live status) on the description/criteria/summary textareas in paths/form.php, badges/form.php, cohorts/form.php, certificates/templates/form.php, and courses/modules/_form.php. Gate each behind its own ai_learn_* feature flag like the existing one.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus
