Esta página se tradujo automáticamente. Leer el original en inglés.

Component

core/security/fms-guardrails-orchestrator

The FMS Guardrails Orchestrator: a service that runs text detectors around a model call. A caller posts an OpenAI chat-completions request naming the detectors to apply; the orchestrator checks the latest message, answers a detection with the detections and no reply, and otherwise forwards the request to the upstream server in infra.upstream_host and infra.upstream_port, adding any detection on the reply. It also answers detection-only requests over a text. It is not a guard on its own: a request naming no detectors is forwarded unchecked, so it sits behind a component that names them, such as core/security/trustyai-guardrails-gateway. Its Recipes register the one detector wired on the detector socket under values.detector_id. Answering a detection asks the upstream's /tokenize route, which vLLM serves, to count the refused text, so that text reaches the upstream. It authenticates no caller and forwards none of a caller's headers. The Release supplies the image in infra.image and the catalog names none: TrustyAI's build adds the compat-openssl11 package, whose declared licence includes the OpenSSL licence, compiles in root-certificate data published under a data licence, and is published only under a floating tag. Nothing renders until the Release sets `infra.image`. Realized on Kubernetes by its Helm Recipe and for local development by its Compose Recipe, each running that image as a single stateless service.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:25cf72dcc3f5e2ad828647e0e30c671423a3d2ca6895adc1d3a3ffd0ca676e89
Publicado
2026-11-10T10:13:36Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:c65574df5e602940b1079c5a4148ffed7e5cdd541fa8f7b0d671dd212818491b

Referencia en esta versión

oci://hub.aggrega.ai/component/core/security/fms-guardrails-orchestrator:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
detector_idstringdetectornoId the wired detector is registered under, which a caller names in a request's detectors to have it applied. Published as provides.detector_id, so a component calling the orchestrator reads it from the edge rather than repeating it.
default_thresholdnumber (min 0, max 1)0.5noScore at or above which a detection is reported when the caller's request names no threshold for the detector. The orchestrator applies the threshold itself and sends the detector its other parameters, so core/security/trustyai-huggingface-detector reports to it only labels scored at or above its own 0.5, and with that detector a value below 0.5 has no effect.

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
portinteger (min 1024, max 65535)8033noPort the orchestrator serves its API on and its Service accepts callers on. Most operators should omit this and let the Recipe assign the default (8033), the product's own.
health_portinteger (min 1024, max 65535)8034noPort the orchestrator serves its health route on, which the Recipes' probes ask and no Service publishes. Most operators should omit this and let the Recipe assign the default (8034), the product's own.
upstream_hoststring—síHost name of the OpenAI-compatible model server the orchestrator forwards the requests it admits to, for example model-server. A deterministic pointer string the orchestrator resolves when it forwards; the compiler never contacts it.
upstream_portinteger (min 1, max 65535)—síPort of that model server. The orchestrator reaches it over plain HTTP at /v1/chat/completions, and asks its /tokenize route to answer a detection on the input.
imagestring—síImage the orchestrator runs, supplied by the Release; the catalog names none. The Recipes run the published build's own binary at /app/bin/fms-guardrails-orchestr8, so the image is TrustyAI's FMS Guardrails Orchestrator or a copy of it. That build adds the compat-openssl11 package, compiles in root-certificate data published under a data licence, and is tagged only as latest, so a Release that must keep one build mirrors it and names the copy here.
computeobject—no—

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—síIn-cluster DNS name of the Service fronting the orchestrator. Every caller reaching this name can reach the model through it, with or without a detector applied, so it is an address for the component calling the orchestrator rather than one to publish.
portinteger—síTCP port that Service accepts callers on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
endpointstring—síBase URL of the orchestrator's API, with the host and the port already composed and no path. A caller posts chat completions to /api/v2/chat/completions-detection under it.
detector_idstring—síId the wired detector is registered under, which a caller names in a request's detectors.
protocolstring—noURL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

detector

Selector
security.aggrega.ai/text-detection=detector
Inyección
—

Este socket no declara slots de acoplamiento, por lo que una conexión a través de él no lleva ningún acoplamiento.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

No se declararon slots de acoplamiento.

Lista de permitidos de autoinyección

No se declararon canales de autoinyección.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad