>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3555611. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h2 id="meeting-overview-topics">Meeting Overview / Topics</h2> <h3 id="ux-onboarding-resource-management">UX onboarding / Resource management</h3> <ul> <li>Introductions for Sahil Sharma, a UI/UX and product design lead from OpenSense Labs, who is joining the UX efforts.</li> <li>Discussion on team capacity and how to manage the workflow for incoming UX issues, recognizing the three available teams (1x, Aidan &amp; Emma, OpenSense Labs) and the need for a clear process to assign and track work.</li> </ul> <h3 id="ai-dashboard">AI Dashboard</h3> <ul> <li>Bruno reported that the dashboard is nearly feature-complete and styled, with only the Project Browser integration remaining. A v0.1 release is planned pending a final review.</li> </ul> <h3 id="flowdrop-ui">FlowDrop UI</h3> <ul> <li>Jamie presented a demo of Flowdrop, a new visual, node-based UI for building and managing AI agents and assistants.</li> <li>It was clarified that this UI is a "stopgap" to replace the confusing Drupal forms, but it saves to the <em>existing</em> configuration, ensuring backward compatibility.</li> <li>A key discussion focused on the need to move from low-level, developer-focused "Tools" (e.g., entity load) to higher-level "composable tools" or "skills" (e.g., "Create Blog Post") to make the interface usable for everyone.</li> </ul> <h3 id="context-control-center">Context Control Center</h3> <ul> <li>Jamie emphasized that while the Flowdrop UI is an important usability improvement for developers and power users, the most critical strategic project is the <strong>Context Control Center (CCC)</strong>.</li> <li>Priority "Main project" for Emma and Aidan.</li> </ul> <h2 id="decisions">Decisions</h2> <h3 id="flowdrop-ui">FlowDrop UI</h3> <ul> <li>The team will begin to focus efforts on improving the agent-building experience through the new Flowdrop UI, rather than trying to fix the legacy Drupal forms.</li> <li>The concept of creating "composable tools" (or "skills") to abstract away low-level Drupal operations is the correct path forward for simplifying the tool selection process.</li> </ul> <h2 id="questions">Questions</h2> <h3 id="ux-onboarding-resource-management">UX onboarding / Resource management</h3> <ul> <li>What is the best way to onboard new UX contributors like Sahil and assign them actionable, low-complexity tasks to start?</li> </ul> <h3 id="context-control-center">Context Control Center</h3> <ul> <li>How can the Context Control Center ingest and parse a real-world style guide (like the UK Government's A-Z list) and differentiate between deterministic rules (e.g., spelling) and interpretive rules (e.g., active voice)?</li> </ul> <h2 id="next-steps">Next Steps</h2> <ul> <li><strong>Aidan:</strong> Follow up with Kristen and Valerie to get the UX governance documentation merge request approved and published.</li> <li><strong>Jamie:</strong> Meeting w/ Emma + Aidan on "Vibecoding" UX patterns</li> <li><strong>Sahil:</strong> Sync with Harivanch and Anmol at OpenSense Labs to get onboarded with the Flowdrop UI project and contribute to its development.</li> <li><strong>Aidan, Emma:</strong> Likely will be delayed on CCC this week. Knock off another item on the UX backlog instead. Priority #2. Think about how tools could be organized by beviour / capability in FlowDrop rather then by "drupalism"</li> </ul> > Related issue: [Issue #3555610](https://www.drupal.org/node/3555610)