Deterministic pipelines. Judgment where it counts.

Expanso is the deterministic part: it receives the record, shapes it, fingerprints and counts it where the example needs history, applies fixed thresholds, and routes it. It applies the same fixed rules every time, with no model involved; that is a claim about what happens to the record, not about timing. Jev is the non-deterministic part: it answers questions that need judgment, such as how severe a log line is or whether a ticket sounds urgent. On a pass where Jev answers, the record crosses to Jev once and comes back with answers the pipeline compares against numbers. In log triage, a record Jev did not answer for is held and sent to Jev again on each retry.

No. Jev answers typed questions and returns a value and, for choices, a confidence. The route is chosen by a gate in the Expanso pipeline: fixed thresholds checked in order. That keeps the routing rules in a YAML file you can read, review and change.

Each pipeline catches the failed call, marks the record jev-unavailable and continues, so no record is dropped by the failure itself. Where it lands depends on that example’s defaults. Log triage holds the record and asks again, up to 15 attempts, before sending it to review. The agent guardrail, the data quality firewall and moderation fail closed, to block, quarantine or review. Others, such as sensitivity masking, resolve to their permissive route as written. Each example page states its own outcome.

No. The examples call Jev with the general http processor inside a branch, so the request and the response mapping are visible in the YAML. Nine of the ten send a bearer token from TYPESAFE_API_KEY. You supply the endpoint and the key.

All ten files pass expanso-edge validate on Expanso Edge v2.1.21, which checks the configuration offline. Log triage is the example with a full live runtime in its package. The other nine ship as a pipeline file and sample records, and their READMEs mark the live runtime as coming next. Expanso has not published measured results for any of them, so these pages quote none. Two of the files mention a latency in their own text; those are the examples’ words, not measurements.