What content needs to be created or modified?
We build Flock, an open-source, declarative multi-agent framework built around a blackboard model: agents publish and consume typed artifacts, and an orchestration layer decides what runs next. With Flock 0.5.600 we added an optional Dapr-backed blackboard store, so a Flock agent swarm can use Dapr's State Management API as a distributed, swappable backend without any changes to agent code.
The Agent Integrations page currently features a handful of frameworks, and we're curious whether there's general interest in growing that list further, Flock included.
Describe the solution you'd like
Before we put together a PR, we'd like to check whether this would actually bring value to the community: would documenting Flock's Dapr state store integration on the Agent Integrations page be a good fit alongside the existing frameworks?
If there's interest, we'd follow the same structure as CrewAI/LangGraph/OpenAI, a short landing page plus a how-to page covering setup, component configuration, and swapping backends, and open a PR from there.
Where should the new material be placed?
Our proposal would be a new flock/ folder under daprdocs/content/en/developing-ai/agent-integrations/.
The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos
N/A — Flock is developed outside the dapr org at github.com/whiteducksoftware/flock. The Dapr integration itself landed in whiteducksoftware/flock#414 and shipped in release 0.5.600.
Additional context
Additional details for anyone evaluating this:
What content needs to be created or modified?
We build Flock, an open-source, declarative multi-agent framework built around a blackboard model: agents publish and consume typed artifacts, and an orchestration layer decides what runs next. With Flock
0.5.600we added an optional Dapr-backed blackboard store, so a Flock agent swarm can use Dapr's State Management API as a distributed, swappable backend without any changes to agent code.The Agent Integrations page currently features a handful of frameworks, and we're curious whether there's general interest in growing that list further, Flock included.
Describe the solution you'd like
Before we put together a PR, we'd like to check whether this would actually bring value to the community: would documenting Flock's Dapr state store integration on the Agent Integrations page be a good fit alongside the existing frameworks?
If there's interest, we'd follow the same structure as CrewAI/LangGraph/OpenAI, a short landing page plus a how-to page covering setup, component configuration, and swapping backends, and open a PR from there.
Where should the new material be placed?
Our proposal would be a new
flock/folder underdaprdocs/content/en/developing-ai/agent-integrations/.The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos
N/A — Flock is developed outside the
daprorg at github.com/whiteducksoftware/flock. The Dapr integration itself landed in whiteducksoftware/flock#414 and shipped in release 0.5.600.Additional context
Additional details for anyone evaluating this: