Business adapters and community recipes
A business adapter provides an explicit integration layer on the source-system side: declare the operations an agent may use, verify Hub signatures, restore a trusted subject, and call the existing service layer for final authorization and business validation.
Three deliverables
Section titled “Three deliverables”| Form | Where it lives | Best fit |
|---|---|---|
| Business-side SDK | Inside the business-system codebase | Generate tool specs, verify calls, issue identity tickets, or call the Hub |
| Independent adapter | A separate repository or business plugin | A product has a stable extension point and the integration should be installed and upgraded independently |
| Community recipe | Documentation, sample specs, and verification scripts | Teams need a reference structure but must implement it for their own version and permission model |
The business-side SDK is not the Agent Client SDK. The former supports declarations, verification, and identity establishment in the business backend. The latter supports browser authorization, connections, and tool calls from a local agent.
Current public references
Section titled “Current public references”- The CRMEB adapter is an independent project with a release lifecycle separate from Core.
- Core
v0.10.0contains a RuoYi-Vue-Pro reference recipe and a JeecgBoot reference recipe. The recipes provide integration structure, sample declarations, and verification steps to adapt to your business-system version and permission model.
One adapter path
Section titled “One adapter path”- Choose one result-verifiable read and one reversible write.
- Give each operation a stable
operationId, parameter schema, and ACC governance declaration. - Verify the signature, subject, tenant, resource ownership, and current business state in the business backend.
- Publish only the required tool specs to the Hub, then restrict them again at the route.
- Test success, unauthorized denial, duplicate requests, and approval recovery with fixed test accounts.
- State the adapter version, compatible business-system versions, and maintainer responsibility.
Choosing and maintaining a community integration
Section titled “Choosing and maintaining a community integration”When choosing a community distribution, connector, or recipe, review its installation steps, compatible business-system versions, test coverage, and issue tracker. General improvements can be contributed upstream while industry-specific logic remains in an independent project.