>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3583360. --> Reported by: [afoster](https://www.drupal.org/user/594458) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>Need triage of all new Driesnote features<br> <strong>Check-in Date: </strong>04/13/2026<br> <strong>Additional Collaborators: </strong>Emma Horrell<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Video: <a href="https://youtu.be/9cNDM9JDMZY">https://youtu.be/9cNDM9JDMZY</a></p> <p>The Driesnote demo and follow-up walkthrough surfaced a number of Canvas AI prototype features that the team needs to evaluate for productionization. Without a single place to review them side by side, it is hard to decide which should graduate from prototype into sprint work, in what order, and who should own them.</p> <p>After a working session with Emma, the recorded demo walkthrough was reviewed and nine candidate projects were extracted into a shared Google Doc, each with a short bullet summary based on the video. This meta issue exists to give the team a central place to triage those candidates and spin out child issues for the ones that move forward.</p> <p>Reference doc (with embedded YouTube walkthrough and per-candidate notes): </p> <h2>Suggested breakdown in this doc </h2> <p><a href="https://docs.google.com/document/d/15lI1iXu1ikJx_LotRdT2iX2WYjPufhjOudKsuWMyHVk/edit">https://docs.google.com/document/d/15lI1iXu1ikJx_LotRdT2iX2WYjPufhjOudKsuWMyHVk/edit</a></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Use this issue as the umbrella for triaging all nine Driesnote prototype candidates. For each candidate the team should decide whether to keep it in prototype, drop it, or graduate it to a child issue with its own scope, owner, and sprint slot. Comments and feedback can go directly on the Google Doc for now, with decisions rolled up here. Architecture questions that affect multiple candidates should be flagged so they can be resolved alongside the broader Canvas AI architecture refactor.</p> <h3 id="summary-remaining-tasks">Target date or deadline</h3> <p>Initial triage discussion at an upcoming UX meeting; first child issues spun out within two sprints of that discussion.</p> <h3 id="summary-ai-usage">AI usage (if applicable)</h3> <p>[x] AI Assisted Issue<br> This issue was generated with AI assistance, but was reviewed and refined by the creator.</p> <p>[ ] AI Assisted Code<br> This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision.</p> <p>[ ] AI Generated Code<br> This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human.</p> <p>[ ] Vibe Coded<br> This code was generated by an AI and has only been functionally tested.</p>