Adapters

Adapters define how Cessy calls external services. They keep endpoint, auth, credential, and request behavior out of ad hoc policy code.

Use adapters for

• calling external APIs after modeled events
• sending data to integration services
• fetching external state needed by controlled workflows
• centralizing credentials and auth behavior
• making policy side effects inspectable

Do not use adapters for

• public app API contracts
• bypassing commands
• hiding business decisions outside the event model
• arbitrary frontend calls with user-provided secrets

External consumers should call generated runtime APIs, webhooks, subscriptions, or a BFF.

Auth and credentials

Store credentials in configured credential surfaces, not in page bundles, docs, prompts, or custom code strings. Name the target environment when testing adapter behavior.

Verification

After a policy uses an adapter, inspect Activity for the triggering event, adapter request, response, retry behavior, and any resulting command or error.