Public descriptions, visible boundaries
This edition draws on public pages reviewed on 20 October 2026. The directory is a selection of public records, not a complete service inventory or count of operating companies.
Select a block to inspect its connections. Use search, zoom, route tools and export controls. To share a focused node or route, open the diagram on its own. Arrows show proposed or intended handoffs; they do not establish a live integration.
A selection of publicly described programs, ventures and ecosystem examples. Listings establish public context; availability, ownership structure and live connections need separate confirmation.
EXPLORE POSSIBLE REUSE
How could these projects work together?
Choose up to three projects. Compare an illustration of the foundations they could reuse while keeping their distinct roles and boundaries visible.
Try a combination
Illustrative, not an integration inventory. These mappings are editorial planning suggestions based on public descriptions. Shared capabilities do not establish shared accounts, automatic data transfer or working project-to-project connections.
What the maps mean
The operating model and seven foundations are an illustrative design: Identity, Communications, Evidence, Workflow, Data Integration, AI and Analytics.
Capability assignments in Connection Finder are new editorial illustrations based on public roles. They do not verify actual dependencies, a common backend, shared identity or live integrations.
Arrows mean a proposed or intended handoff. Each real connection needs an owner, a defined scope, permission and acceptance evidence.
Demonstrations and delivery
Sponsor Matchmaker and the district-operations example use demonstration scenarios. They do not establish successful matching, agency adoption, completed deployments or measured savings.
Agent Foundry is described publicly as a blueprint workbench. Exporting a plan does not deploy it. Reviewed pilots and operational use require separate decisions.
Make the next conversation useful
Select two or three projects and download a connection brief. It includes their public roles, sources, possible common foundations and questions to resolve before connecting anything.
Keep project records and permissions scoped. A shared design does not authorize moving records between products.