Glossary

Eight platform terms: native passthrough, translation, component snapshot, evidence, replay, policy-as-data, BYOK, deployment profile.

Terms

Native passthrough

A route mode that preserves a supported native API family end-to-end (OpenAI Responses, Anthropic Messages, Chat Completions). The default route mode.

Translation

A route attribute, not an automatic fallback, that converts between provider API families using a versioned translation profile with declared compatibility limits.

Component snapshot

A validated, versioned configuration published by the Control Plane. Each Gateway, Bastion, or Touchstone operation pins one component snapshot; ordinary invalid configuration leaves the previous valid snapshot active.

Evidence

A correlated record of observations, decisions, transformations, execution outcomes, configuration context, and declared gaps. Not merely application logging.

Replay

A view-only chronology of retained observations, transformations, decisions, and declared gaps. Replay never re-executes providers or tools.

Policy-as-data

Customer safety customization expressed as preset selection, rule parameters, extraction mappings, scoped exclusions, category thresholds, and configured dispositions — never executable code, never network or filesystem access.

BYOK

Bring-your-own-key. Production inference uses customer-supplied provider credentials. Chrysent does not sell inference; Chrysent-owned credentials are isolated from customer routes and never an automatic fallback.

Deployment profile

A customer-operated placement and operating model: self-hosted/private cloud or future air-gap-capable enterprise. Chrysent software runs in customer-owned or customer-controlled infrastructure; profiles share core contracts but do not promise identical capability sets.