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.
  • host → model: Bounded inference and proposed tool calls. Identity: Provider key retained only by the host.

​
Deployment inputs

  • backend (file, required): Native Bijection backend executable.
  • cli (file, required): Bijection CLI executable.
  • sdk (directory, required): Built Bijection SDK directory.
  • provider-env (credential-file, required): Private file defining the hosted model API key.
  • model (value, required): Explicit model name.
  • cost-estimate (value, required): Reviewed maximum provider spend estimate for this bounded run.

​
Bounds and cleanup

One loopback backend and one disposable PostgreSQL cluster; bounded fixture; no cloud runtime. Maximum duration: 7200 seconds. Maximum captured log: 4194304 bytes. Estimated cost: Usage is bounded to 40 calls per store, each with at most 1,500 output tokens. Supply a reviewed provider cost estimate before execution; input-token usage is recorded separately. 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/hosted-model/runbook.md. A declared journey is verified only when every named check appears in a successful execution report and cleanup has been observed.