🇺🇸United States @Kristen Pol

They said in a different issue they can get into slack now so closing this

Thanks!

I'll see what happened

See meeting notes on meta issue

Meeting with Aidan+Emma 4 Feb 2026 notes (needs cleanup)

Context Scope
- Use Cases should be locked down, unlike things like Tags/freetagging
-- They can always use tags to handle unique use cases
- Update use cases because we need recommended templates to go with these
-- Keep
--- Writing Words
-- Update
--- Working in Canvas
-- Remove
--- Generating Metadata
-- Remove but future probably
--- Creating Components
--- Updating Site Configuration
-- Other potential future, but other module's responsibility (ideally vetted modules)
--- Reviewing Content
--- Measuring Performance
- Smart selection
-- Could be a large prompt (with history)
-- Canvas
--- 100% of Working in Canvas are reviewed
---- All Global
---- Conditional (spin up own agent? can own cheaper/faster/non-thinking model?)
we need purpose of context and the list of subcontext with a description
summarize the prompt/data coming into it (need prompt for the summarizer, is it related to the use case?)
returns the list of subcontext that's most relevant
it must just give the list with required+conditional
need a workflow diagram and then talk it through with Marcus or Artem
could these be run in parallel for different use cases
add purpose field (need template, but eventually an automator could be created for this)

See meeting notes on meta issue

Great! Merge in the latest from 1.0.x and note the new installation instructions on the project page don’t have the steps for setting up the agent side of things. I was testing with the v2025 demo when creating this

Thanks! Note that I just fixed the dev branch which was preventing proper installation, and added install notes for D11.3 on the profile page:

https://www.drupal.org/project/ai_context#install-steps →

@svendecabooter please see those issues you've noted in #25 and #26

Along with: 📌 Add CCC install steps on the project page Active

Install steps are for D11.3 are on the project page now:

https://www.drupal.org/project/ai_context#install-steps →

Once the draft error fix is merged in (#25 above), then it should be a totally clean install.

I merged in the most critical items here along with:

#3571392: Toolbar menu issue in Drupal 11.3 when CCC installed →

and the remaining error is fixed here:

🐛 Error on installation: The state 'draft' already exists in workflow Needs review

kristen pol → changed the visibility of the branch 3571006-cms1-styling to hidden.

I've updated the home page with the D11 steps so far, but I still need to do CMS 1.0 and 2.0 steps.

D11 testing instructions:

mkdir my-drupal-site && cd my-drupal-site
ddev config --project-type=drupal11 --docroot=web
ddev start
ddev composer create-project "drupal/recommended-project:^11"
ddev composer update symfony/process --with-all-dependencies (due to security advisory)
ddev composer require drush/drush
ddev composer require drupal/ai_context:dev-1.0.x
ddev drush site:install --account-name=admin --account-pass=admin -y
ddev drush en ai_context
ddev launch
# or automatically log in with:
ddev launch $(ddev drush uli)

There will be one error until this is merged:

🐛 Error on installation: The state 'draft' already exists in workflow Needs review

Updating the summary to make it clear that the draft and published states are in the workflow module by default.

Testing on D11:

mkdir my-drupal-site && cd my-drupal-site
ddev config --project-type=drupal11 --docroot=web
ddev start
ddev composer create-project "drupal/recommended-project:^11"
ddev composer update symfony/process --with-all-dependencies (due to security advisory)
ddev composer require drush/drush
ddev composer require drupal/ai_context:dev-1.0.x
ddev drush site:install --account-name=admin --account-pass=admin -y
ddev drush en ai_context
ddev launch
# or automatically log in with:
ddev launch $(ddev drush uli)
go to: /admin/config/workflow/workflows/manage/basic_editorial

The settings should match the screenshot in comment #9.

Okay... this was a bit annoying :D

I had to rework it. The goal was to have it match the Drupal CMS basic_editorial workflow. Now it does.

kristen pol → created an issue.

kristen pol → created an issue.

I'm going to see if I can it styled okay with D11, because maybe that would be easier than trying to figure out which version of Mercury+Gin+CMS is needed. And you can't have a dependency in the info file for a theme, so it has to be hook requirements which is kind of annoying. I'll see how that goes and then change this issue as needed. Or create a new issue.

I see from your other issue that you can’t get on slack so hopefully that will be sorted soon

I assume you went through this process

https://www.drupal.org/community/contributor-guide/reference-information... →

Hmm… I’ll assign to the DA to look at but this isn’t an initiative issue. Tim will be back tomorrow but not sure when he’ll see it

I recommend pasting this issue into the #ai or #ai-initiative slack channel for more exposure

For some reason, the gin toolbar looks bad and takes up a bunch of space so not sure yet how to address. Need to take a break and will resume. Later today

Currently the styling is dependent on Gin/Mercury themes, so I will make that a hard requirement for now and then decouple that later

Will get this working for Drupal CMS 1.0 first:

🐛 Inconsistency between module dependencies and composer.json and update to Drupal CMS 2.0 dependencies Needs review

Then will focus on Drupal CMS 2.0 and vanilla D11

kristen pol → created an issue.

Related modules:

https://www.drupal.org/project/ai_content_advisor →
https://www.drupal.org/project/ai_evaluations →
https://www.drupal.org/project/ai_content_lifecycle →
https://www.drupal.org/project/ai_auto_reference →
https://www.drupal.org/project/ai_editoria11y →
https://www.drupal.org/project/smartlinker_ai →
https://www.drupal.org/project/ai_seo →
https://www.drupal.org/project/ai_content →

Drupal CMS 1.0 install steps

This part is okay now:

mkdir my-drupal-site && cd my-drupal-site
ddev config --project-type=drupal11 --docroot=web
ddev start
ddev composer create-project drupal/cms:^1
ddev composer require drupal/ai_context:dev-1.0.x
ddev launch
... go through installation and choose all the recipes ...

This breaks:

ddev drush en ai_context

with

 [error]  TypeError: Cannot assign null to property Drupal\eca\Entity\Eca::$label of type string in Drupal\Core\Entity\EntityBase->__construct() (line 75 of /var/www/html/web/core/lib/Drupal/Core/Entity/EntityBase.php) #0 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php(114): Drupal\Core\Entity\EntityBase->__construct()
#1 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php(453): Drupal\Core\Config\Entity\ConfigEntityBase->__construct()
#2 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php(168): Drupal\Core\Entity\EntityStorageBase->mapFromStorageRecords()
#3 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php(340): Drupal\Core\Config\Entity\ConfigEntityStorage->doLoadMultiple()
#4 /var/www/html/web/modules/contrib/eca/src/Entity/EcaStorage.php(149): Drupal\Core\Entity\EntityStorageBase->loadMultiple()
#5 /var/www/html/web/modules/contrib/eca/src/Entity/EcaStorage.php(106): Drupal\eca\Entity\EcaStorage->doRebuildSubscribedEvents()
#6 /var/www/html/web/modules/contrib/eca/src/Entity/EcaStorage.php(128): Drupal\eca\Entity\EcaStorage->rebuildSubscribedEvents()
#7 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php(528): Drupal\eca\Entity\EcaStorage->doPostSave()
#8 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php(239): Drupal\Core\Entity\EntityStorageBase->save()
#9 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityBase.php(370): Drupal\Core\Config\Entity\ConfigEntityStorage->save()
#10 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php(635): Drupal\Core\Entity\EntityBase->save()
#11 /var/www/html/web/core/lib/Drupal/Core/Config/ConfigInstaller.php(429): Drupal\Core\Config\Entity\ConfigEntityBase->save()
#12 /var/www/html/web/core/lib/Drupal/Core/Config/ConfigInstaller.php(175): Drupal\Core\Config\ConfigInstaller->createConfiguration()
#13 /var/www/html/web/core/lib/Drupal/Core/ProxyClass/Config/ConfigInstaller.php(75): Drupal\Core\Config\ConfigInstaller->installDefaultConfig()
#14 /var/www/html/web/core/lib/Drupal/Core/Extension/ModuleInstaller.php(448): Drupal\Core\ProxyClass\Config\ConfigInstaller->installDefaultConfig()
#15 /var/www/html/web/core/lib/Drupal/Core/Extension/ModuleInstaller.php(229): Drupal\Core\Extension\ModuleInstaller->doInstall()
#16 /var/www/html/web/core/lib/Drupal/Core/ProxyClass/Extension/ModuleInstaller.php(83): Drupal\Core\Extension\ModuleInstaller->install()
#17 /var/www/html/vendor/drush/drush/src/Commands/pm/PmCommands.php(101): Drupal\Core\ProxyClass\Extension\ModuleInstaller->install()
#18 [internal function]: Drush\Commands\pm\PmCommands->install()
#19 /var/www/html/vendor/consolidation/annotated-command/src/CommandProcessor.php(276): call_user_func_array()
#20 /var/www/html/vendor/consolidation/annotated-command/src/CommandProcessor.php(212): Consolidation\AnnotatedCommand\CommandProcessor->runCommandCallback()
#21 /var/www/html/vendor/consolidation/annotated-command/src/CommandProcessor.php(175): Consolidation\AnnotatedCommand\CommandProcessor->validateRunAndAlter()
#22 /var/www/html/vendor/consolidation/annotated-command/src/AnnotatedCommand.php(389): Consolidation\AnnotatedCommand\CommandProcessor->process()
#23 /var/www/html/vendor/symfony/console/Command/Command.php(341): Consolidation\AnnotatedCommand\AnnotatedCommand->execute()
#24 /var/www/html/vendor/symfony/console/Application.php(1102): Symfony\Component\Console\Command\Command->run()
#25 /var/www/html/vendor/drush/drush/src/Application.php(201): Symfony\Component\Console\Application->doRunCommand()
#26 /var/www/html/vendor/symfony/console/Application.php(356): Drush\Application->doRunCommand()
#27 /var/www/html/vendor/symfony/console/Application.php(195): Symfony\Component\Console\Application->doRun()
#28 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(113): Symfony\Component\Console\Application->run()
#29 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(40): Drush\Runtime\Runtime->doRun()
#30 /var/www/html/vendor/drush/drush/drush.php(140): Drush\Runtime\Runtime->run()
#31 /var/www/html/vendor/bin/drush.php(119): include('...')
#32 {main}. 
TypeError: Cannot assign null to property Drupal\eca\Entity\Eca::$label of type string in /var/www/html/web/core/lib/Drupal/Core/Entity/EntityBase.php on line 75 #0 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php(114): Drupal\Core\Entity\EntityBase->__construct()
#1 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php(453): Drupal\Core\Config\Entity\ConfigEntityBase->__construct()
#2 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php(168): Drupal\Core\Entity\EntityStorageBase->mapFromStorageRecords()
#3 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php(340): Drupal\Core\Config\Entity\ConfigEntityStorage->doLoadMultiple()
#4 /var/www/html/web/modules/contrib/eca/src/Entity/EcaStorage.php(149): Drupal\Core\Entity\EntityStorageBase->loadMultiple()
#5 /var/www/html/web/modules/contrib/eca/src/Entity/EcaStorage.php(106): Drupal\eca\Entity\EcaStorage->doRebuildSubscribedEvents()
#6 /var/www/html/web/modules/contrib/eca/src/Entity/EcaStorage.php(128): Drupal\eca\Entity\EcaStorage->rebuildSubscribedEvents()
#7 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php(528): Drupal\eca\Entity\EcaStorage->doPostSave()
#8 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php(239): Drupal\Core\Entity\EntityStorageBase->save()
#9 /var/www/html/web/core/lib/Drupal/Core/Entity/EntityBase.php(370): Drupal\Core\Config\Entity\ConfigEntityStorage->save()
#10 /var/www/html/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php(635): Drupal\Core\Entity\EntityBase->save()
#11 /var/www/html/web/core/lib/Drupal/Core/Config/ConfigInstaller.php(429): Drupal\Core\Config\Entity\ConfigEntityBase->save()
#12 /var/www/html/web/core/lib/Drupal/Core/Config/ConfigInstaller.php(175): Drupal\Core\Config\ConfigInstaller->createConfiguration()
#13 /var/www/html/web/core/lib/Drupal/Core/ProxyClass/Config/ConfigInstaller.php(75): Drupal\Core\Config\ConfigInstaller->installDefaultConfig()
#14 /var/www/html/web/core/lib/Drupal/Core/Extension/ModuleInstaller.php(448): Drupal\Core\ProxyClass\Config\ConfigInstaller->installDefaultConfig()
#15 /var/www/html/web/core/lib/Drupal/Core/Extension/ModuleInstaller.php(229): Drupal\Core\Extension\ModuleInstaller->doInstall()
#16 /var/www/html/web/core/lib/Drupal/Core/ProxyClass/Extension/ModuleInstaller.php(83): Drupal\Core\Extension\ModuleInstaller->install()
#17 /var/www/html/vendor/drush/drush/src/Commands/pm/PmCommands.php(101): Drupal\Core\ProxyClass\Extension\ModuleInstaller->install()
#18 [internal function]: Drush\Commands\pm\PmCommands->install()
#19 /var/www/html/vendor/consolidation/annotated-command/src/CommandProcessor.php(276): call_user_func_array()
#20 /var/www/html/vendor/consolidation/annotated-command/src/CommandProcessor.php(212): Consolidation\AnnotatedCommand\CommandProcessor->runCommandCallback()
#21 /var/www/html/vendor/consolidation/annotated-command/src/CommandProcessor.php(175): Consolidation\AnnotatedCommand\CommandProcessor->validateRunAndAlter()
#22 /var/www/html/vendor/consolidation/annotated-command/src/AnnotatedCommand.php(389): Consolidation\AnnotatedCommand\CommandProcessor->process()
#23 /var/www/html/vendor/symfony/console/Command/Command.php(341): Consolidation\AnnotatedCommand\AnnotatedCommand->execute()
#24 /var/www/html/vendor/symfony/console/Application.php(1102): Symfony\Component\Console\Command\Command->run()
#25 /var/www/html/vendor/drush/drush/src/Application.php(201): Symfony\Component\Console\Application->doRunCommand()
#26 /var/www/html/vendor/symfony/console/Application.php(356): Drush\Application->doRunCommand()
#27 /var/www/html/vendor/symfony/console/Application.php(195): Symfony\Component\Console\Application->doRun()
#28 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(113): Symfony\Component\Console\Application->run()
#29 /var/www/html/vendor/drush/drush/src/Runtime/Runtime.php(40): Drush\Runtime\Runtime->doRun()
#30 /var/www/html/vendor/drush/drush/drush.php(140): Drush\Runtime\Runtime->run()
#31 /var/www/html/vendor/bin/drush.php(119): include('...')
#32 {main}
TypeError: Cannot assign null to property Drupal\eca\Entity\Eca::$label of type string in Drupal\Core\Entity\EntityBase->__construct() (line 75 of /var/www/html/web/core/lib/Drupal/Core/Entity/EntityBase.php).
 [warning] Drush command terminated abnormally.

This is is my top priority after I get off of a meeting in a few minutes.

I had a similar issue when working on a separate MR and just added the conditionals but didn't delete anything so I need to look at that but I'm jumping on a meeting so will sort this out after that.

looking

Okay... since this was developed thus far with Drupal CMS 1.0, we need to do this in steps:

1. Update the repo to work with Drupal CMS 1.0 and add installation steps for that (this issue)
2. In a separate issue, work through changes for working with Drupal CMS 2.0 and update installation steps, and deprecate CMS 1.0 capability
3. In a separate issue, work through how to get it to work with vanilla D11 and add steps for that

The first two are the priority, as we are prioritizing working with Drupal CMS.

Also, the styling when installing with Drupal CMS 2.0 is broken. I've only tested with Drupal CMS 1.0 so far.

With D11:

mkdir my-drupal-site && cd my-drupal-site
ddev config --project-type=drupal11 --docroot=web
ddev start
ddev composer create-project "drupal/recommended-project:^11"
ddev composer require drush/drush
ddev composer require drupal/ai_context:dev-1.0.x

error:

ddev composer require drupal/ai_context:dev-1.0.x
./composer.json has been updated
Running composer update drupal/ai_context
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/core-recommended is locked to version 11.3.2 and an update of this package was not requested.
    - drupal/core-recommended 11.3.2 requires symfony/process ~v7.4.0 -> found symfony/process[v7.4.0, v7.4.3, v7.4.4, v7.4.5] but these were not loaded, because they are affected by security advisories. To ignore the advisories, add ("PKSA-rkkf-636k-qjb3") to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
  Problem 2
    - Root composer.json requires drupal/ai_context dev-1.0.x -> satisfiable by drupal/ai_context[dev-1.0.x].
    - drupal/ai_context dev-1.0.x requires drupal/core ^10.4 || ^11 -> satisfiable by drupal/core[11.3.2].
    - drupal/core 11.3.2 requires symfony/process ^7.4 -> found symfony/process[v7.4.0, v7.4.3, v7.4.4, v7.4.5] but these were not loaded, because they are affected by security advisories. To ignore the advisories, add ("PKSA-rkkf-636k-qjb3") to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.


Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Composer [require drupal/ai_context:dev-1.0.x] failed, composer command failed: exit status 2. stderr=

This will get it to install now via composer with Drupal CMS 2.0 without errors:

1. mkdir my-drupal-site && cd my-drupal-site
2. ddev config --project-type=drupal11 --docroot=web
3. ddev start
4. ddev composer create-project drupal/cms
5. ddev composer require drupal/ai_context:dev-1.0.x

I'll test with D11 as well

I'm also going to update based on the latest Drupal CMS 2.0 dependencies so I'll update to scheduler 3.0

kristen pol → created an issue.

Thanks. The diff module is needed to support revision comparisions which was supposed to be optional, but we can deal with that later to get the dev branch working again.

Related: #3569967: [Discuss] Figure out which CCC features can be optional for MVP →

Looking

Assigning to me to sort it out

kristen pol → created an issue.

This was suggested by Christoph at the sprint standup today.

Since MDXEditor is the winner here, what's the next step? Any chance there could be an integration available by the end of the next sprint?

kristen pol → created an issue.

I'll share the recording in the Slack channel. Here are the zoom notes:

Quick recap

The team discussed several ongoing development projects, including the AI dashboard, tooltip implementation, and the Context Control Center interface design. Bruno provided updates on the global AI styling work and tooltip functionality, while Aidan presented a new UI sketch for managing structured context documents. The team explored various technical challenges around implementing the Context Control Center, including column layout limitations and the need for conditional context display. Aidan raised questions about the status of Flowdrop UI development and its potential to address many existing UI issues, while Arian noted resource constraints with available UX/UI skills. The conversation ended with discussions about prioritizing UI improvements and the need to coordinate with Acquia's Canvas UI team.

Next steps

• Aidan: Find and share preliminary work/audit on feedback widget with Arian (and others working on AI reviews), including relevant Slack threads or issue links.
• Bruno: Complete work on global AI variables/classes and tooltip implementation for AI module, ensuring tooltips support HTML, proper ARIA attributes for accessibility, and correct edge/anchor behavior.
• Bruno: Check and test tooltip behavior to ensure it does not disappear off the edge of the screen and respects anchor properties.
• Bruno: Coordinate release and version dependencies between AI module and AI Dashboard, ensuring the AI Dashboard requires the correct version of AI module after updates are released.
• Aidan: Post in the UX channel to request an update on the status of Flowdrop UI and its impact on the backlog of tool/UX issues, and ask Rocky for an update if appropriate.
• Aidan: Close the issue related to selecting the Markdown editor tool, as the decision has been made and implemented.
• Aidan: Meet with Kristen on Wednesday to review the Context Control Center UI proposal and discuss schema changes and front-end implementation.
• Arian: Discuss with makers about the need for additional front-end/UX resources to support the increasing number of UI issues.
• Aidan: Send Arian the link to the issue about improving the UX for restricting tools (and related backlog issues) for further review and follow-up.
• Aidan: Consider updating original issue creators (e.g., Michael, Lander) on the deprioritization of their issues if Flowdrop UI is expected to solve them, and communicate status.
• Aidan: Connect with Scott Falconer/Acquia Canvas team to understand their UI/UX approach and share information as appropriate.
• Bruno: After finishing AI global/tooltip work, assess feasibility and timeline for also working on the Context Control Center homepage and related issues this sprint, and communicate with Aidan/Arian about resource availability.
• Aidan: Clean up and close related issues for the Markdown editor implementation as work is completed and tested.

Summary

Feedback Widget and Drees Note Updates

The team discussed weather conditions in Spain and the United States, then focused on a feedback widget issue and related development tasks. Aidan mentioned previous work done on feedback review concepts and an audit of contrib modules, offering to share this information with anyone who takes up the issue. The group also touched on the Drees note project, noting that a group from Acquia is forming to address development gaps related to the Canvas UI. Aidan emphasized that the Drees note deliverables need to be completed soon.

AI Dashboard Integration Progress

Bruno discussed progress on the MDX editor, which is nearly merged and working well, with ongoing efforts to fix failing tests. He also explored challenges with implementing the global AI dashboard, particularly regarding the application of classes to standard Drupal elements. Bruno proposed using AI variables to connect with Drupal variables, allowing for consistent styling while providing flexibility for targeting specific elements with CSS. Aidan suggested a fallback system using Jin, Claro, or custom values, ensuring that defined styles are prioritized.

Typography and Tooltip Implementation

Bruno and Aidan discussed implementing typography utilities and tooltips in their project. They agreed to use a custom variable approach to manage class values, which Aidan supported as it aligns with their client project work. Bruno proposed using a data attribute for tooltips to simplify implementation and reduce developer effort, which Aidan found acceptable. They also discussed the possibility of using classes for inline styles, which Bruno confirmed would be feasible.

Custom Tooltip Accessibility Implementation

Aidan and Bruno discussed implementing a custom tooltip component, focusing on accessibility and functionality. They agreed to use data attributes for flexibility and ensure proper ARIA labels for accessibility. Bruno confirmed that custom markup could be added to the tooltip and planned to test if the tooltip would anchor correctly near the trigger element. Aidan emphasized the importance of checking for accessibility issues and ensuring the tooltip behaves correctly when opened near the screen edge. They concluded with a plan to verify the tooltip's behavior and document the necessary ARIA attributes for the component.

AI Module Release Coordination Challenges

The team discussed challenges with coordinating releases between AI Core and AI Dashboard modules, with Bruno explaining his current workflow of manually cloning Git repositories to work on both simultaneously. Aidan raised concerns about the status of Flowdrop UI, a new interface intended to improve the confusing chain of agents and tools, noting that while it could potentially make certain UI issues lower priority, there was limited information available about its progress. The team also briefly touched on the implementation of a Markdown editor, which was confirmed to be in progress.

Project Progress and Interface Design

Bruno and Aidan discussed the progress of a project, mentioning that it's nearly complete with only a few breaking tests to fix. They talked about the implementation of dynamic tagging and the use of Drupal tokens and variables. Aidan expressed interest in playing with the updated version and Bruno provided the necessary information to locate it. They also discussed the merging of an MR into the 1.3 dev branch and the ongoing efforts to fix a test issue. Aidan mentioned that he would clean up a related issue and close another one since the tool had been chosen. Finally, Aidan presented a sketch for the context control center interface and sought feedback on the proposed design.

Context Management System Implementation

Aidan presented a structured context document system for managing content rules and conditional contexts, explaining how it works with parent and sub-contexts, use cases, and boundaries for entities like landing pages. Bruno and Angela discussed the UI implementation, with Aidan suggesting it could be built using CSS to hide table lines and add icons. The system aims to reduce the need for mapping every context to every agent by using predefined use cases that agents can subscribe to, with future plans to include external context sources and dynamic loading capabilities.

UI Design Challenges for Context Management

The team discussed UI design challenges for a context management interface, focusing on how to display and edit context items within a limited space while maintaining clarity. Aidan explained that all elements would function as tooltips, though this might create a dense interface. Bruno suggested potential solutions including wrapping elements and using expandable widgets to avoid horizontal scrolling. The team agreed to prioritize the dashboard work over the context control center for the current sprint due to resource constraints. Aidan noted that Kristen would explore front-end coding options for the interface, while the team also needs to address pending UI improvements for tools restriction and table search functionality. A key open question remains about how to handle Canvas UI development in coordination with Acquia's team.

Aidan mentioned OpenAI evals as one possible piece of the puzzle.

kristen pol → created an issue.

kristen pol → created an issue.

kristen pol → created an issue.

@nikro Can you add some instructions on how to set this up with Claude or whatever you were using?

Very cool. Thanks!

Let’s look at it together Wednesday alongside the other scope plugins I’m adding (language, site section, etc) to see how they coexist with this design.

Working on this while doing:

✨ Add CCC factors base code and one factor Active

kristen pol → created an issue.

Working on this while doing:

✨ Add CCC factors base code and one factor Active

kristen pol → created an issue.

kristen pol → created an issue. See original summary → .

Working on this while doing:

✨ Add CCC factors base code and one factor Active

I'm working on this and related issues this weekend.

I'm heavily working on this and related issues this weekend.

I'm working on this and related issues this weekend.

I'm working on this and related issues this weekend.

I'm heavily working on this and related issues this weekend.

kristen pol → changed the visibility of the branch 3568673-fix to hidden.

kristen pol → changed the visibility of the branch 3568673-add-context-scope to hidden.

kristen pol → created an issue.

Moving to needs review in case anyone else wants to chime in

Thanks. This is a great start, and based on the research Gurwinder/Aidan have been doing, as well as their experience.

I think this is enough to get us started, but I'll leave this open until mid next week to see if anyone else wants to chime in.

kristen pol → created an issue.

We've done all but the external communication which should happen next week

I know there are already plans for the home page regarding AI positioning

Assigning to Tim for review and to figure out if there are concrete follow-up tasks for this

Thanks!

Pretty sure the answer to this one was "no" but just making sure before closing

Done a while ago :)

And for offboarding: 📌 Create maker offboarding checklist Active

kristen pol → created an issue.

kristen pol → created an issue.

Follow-up issues:

📌 Use maker contributor onboarding form data for basis of contributors data Active
📌 Follow-up with maker contributors who did not fill in contributor onboarding form Active

kristen pol → created an issue.

kristen pol → created an issue.