>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3567001. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Short Description: </strong>Research and draft first mapping Drupal AI abstraction layer to Symfony AI Platform<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>A core requirement for adopting Symfony AI is that Drupal AI&rsquo;s provider abstraction layer can be cleanly replaced or reimplemented using the Symfony AI Platform. This abstraction layer is fundamental to how Drupal AI interacts with different AI providers and models, and it underpins a large portion of the module&rsquo;s public APIs and contrib integrations.</p> <p>This research depends on:<br> - The documented understanding of Drupal AI&rsquo;s current capabilities and abstraction responsibilities.<br> - The structured document of open questions and unknowns identified during the exploratory phase.</p> <p>With those baselines in place, we can draft a first concrete mapping between Drupal AI&rsquo;s abstraction concepts and Symfony AI Platform, including a rough initial idea for how implementation could work in Drupal AI (while still staying within the exploratory scope).</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>- Review the Drupal AI capabilities document and extract all abstraction-layer responsibilities and extension points.<br> - Review the open questions/unknowns document and highlight which questions relate directly to the abstraction layer.<br> - Analyze Symfony AI Platform APIs and concepts and map them to Drupal AI&rsquo;s current abstraction:<br> - Identify direct equivalents and where Drupal code can become a thin adapter.<br> - Identify mismatches where Drupal AI needs glue code or alternate patterns.<br> - Identify missing capabilities that would require upstream Symfony AI changes or Drupal-side workarounds.<br> - Draft a first-pass &ldquo;mapping&rdquo; document that includes:<br> - A side-by-side mapping of key concepts (Drupal AI responsibilities &rarr; Symfony AI Platform equivalents).<br> - A proposed Drupal-side architecture for integration (rough implementation idea), including:<br> - Where Symfony AI Platform would be instantiated and configured.<br> - How Drupal configuration (keys, provider settings, model selection) maps onto Symfony concepts.<br> - How existing Drupal AI APIs and plugin points could wrap Symfony Platform without breaking contrib expectations.<br> - Where provider-specific functionality would live after the change.<br> - Summarize feasibility and risks:<br> - Clear list of blockers.<br> - Clear list of assumptions.<br> - Any areas that likely require upstream contributions to Symfony AI.<br> - Keep this work at the &ldquo;rough plan&rdquo; level: enough detail to guide the prototype phase, but not an implementation task.</p> <p>- <strong>This issue was created with the help of AI</strong></p> > Related issue: [Issue #3538499](https://www.drupal.org/node/3538499)