Create the Guardrails needed for the No Agents Training Demo
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3562614. -->
Reported by: [yautja_cetanu](https://www.drupal.org/user/626050)
>>>
<p>[Tracker]<br>
<strong>Update Summary: </strong>[One-line status update for stakeholders]<br>
<strong>Check-in Date: </strong>MM/DD/YYYY<br>
<strong>Additional Collaborators: </strong><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>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p><strong>Guardrails:</strong></p>
<p>Basic Guardrails for simple Agent version</p>
<ul>
<li>Make sure Guardrails stuff works from the AI Framework point of view.</li>
<li>Figure out and Implement Guardrails for the Alt Text Example and decide how those function</li>
<li>We want some level of abstraction so RAILs, OR amazon or another provider of guardrails can be used.</li>
</ul>
<p>FlowDrop UI Guardrails</p>
<ul>
<li>We need a nice UX for how an end-user creating the flow pics where the guardrails is done and how its configured. </li>
<li>There can be advanced configuration for the site admin behind the scenes, but the flow creator shouldn't have to think about things they wouldn't intuitively understand.</li>
<li>We may have settings on how the flow responds to guardrails. Could be simply stop it, could be retries and then stops it, could be provides the option for user feedback to tweak the response (or approve it anyway), might want to have option to merely report in the moderation page and a human evaluates.</li>
<li>The goal for this talk is to mention RAILS a bit, and show off the safety that guardrails allows, mention specifically that RAILS allow for sovriegn guardrails and the AI framework allows for multiple sources.</li>
</ul>
<h3 id="summary-remaining-tasks">Target date or deadline</h3>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
> Related issue: [Issue #3561073](https://www.drupal.org/node/3561073)
issue