CrewAI¶
CrewAI — give each crew role its own capability list.
Where CrewAI enforces the boundary¶
Give each crew role its own capability list. The adapter owns the provider credential. Propagate the decision ID into the provider trace so a retry can be matched to its original authorization.
Connection sequence¶
Read the BoundaryKit workspace using the adapter identity.
Cache the revision only for this session.
Forward the provider call after evaluation.
curl --fail-with-body "https://api.boundarykit.com/v2/integrations" -H "X-API-Key: $BKIT_KEY" -H "X-Organization-Id: $BKIT_ORG"
Provider-side evidence¶
Inspect the receipt for CrewAI. Compare its organization and revision with the values in the fixture before interpreting the result. Match the provider request ID to the attempt number. Retries may produce multiple provider IDs for one decision.