Skip to main content
Part of Customer support with bounded agent authority.

​
Complete stack

​
Connections

  • host → bijection: Session-scoped read and operation tools. Identity: Store credential followed by verified customer session.
  • bijection → postgres: Transactional operational persistence. Identity: Backend database credential.

​
Deployment inputs

  • backend (file, required): Native Bijection backend executable.
  • cli (file, required): Bijection CLI executable.
  • sdk (directory, required): Built Bijection SDK directory.

​
Bounds and cleanup

One loopback backend and one disposable PostgreSQL cluster; bounded fixture; no cloud runtime. Maximum duration: 2400 seconds. Maximum captured log: 4194304 bytes. Estimated cost: No provider usage for this recipe. Uses the selected local machine. Cleanup: The qualification owner stops its exact child processes, removes credentials and stops its owned PostgreSQL cluster. A run passes only after cleanup is observed. The executable runbook is maintained at examples/support-desk/recipes/rules/runbook.md. A declared journey is verified only when every named check appears in a successful execution report and cleanup has been observed.