- Expanso + Jev
- Setup
What you need to run the examples.
Expanso Edge for the deterministic half, and a Jev endpoint you supply for the judgment half. You can read and validate every pipeline with neither.
You install
Expanso, deterministicExpanso Edge, which validates and runs the pipeline on a node you control.
- Install Expanso Edge and the CLI
- The examples were checked on Expanso Edge v2.1.21.
You supply
Jev, judgmentA Jev endpoint, and a key for it. Expanso does not provide either, and nothing on this site provisions one.
JEV_API_URLis the endpoint each pipeline posts to.TYPESAFE_API_KEYis sent as a bearer token by examples 02 to 10.
Four steps
Download a pipeline
Each example page has a Download button that serves the pipeline file byte for byte. Start with thesupport ticket router: it has no dependency beyond Jev.
Validate it offline
This checks the configuration, mappings and component types. It contacts nothing and needs no account.
expanso-edge validate 02-ticket-router.yamlSet the Jev variables on the node
The YAML holds no credential. It reads both values from the environment of the node that runs it. Use your own endpoint and key in place of the placeholders.
export JEV_API_URL="https://<your-jev-endpoint>" export TYPESAFE_API_KEY="<your-key>"If
JEV_API_URLis unset, examples 02 to 10 post tohttps://api.typesafe.ai/v1/systemone. Each call has a 2 second timeout and one retry.Run it as an Expanso job
Deploy the file the way you deploy any pipeline. TheExpanso documentationcovers bootstrapping a node and submitting a job. Each pipeline then listens on port 8080 at the path its page names, and writes its routes to local files under
./data/.
What each example needs
Read from each pipeline file. Log triage is the one that differs.
| Example | JEV_API_URL | Key | Anything else |
|---|---|---|---|
| 01 · Log triage | Required. No default. | Not sent. | Recurrence counter on 127.0.0.1:8898. The hold loop re-submits to the pipeline’s own input on 127.0.0.1:8080, which the same file binds, so nothing new is supplied unless the port is changed. |
| 02 · Support ticket router | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 03 · Sensitivity masking | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 04 · Sensor anomaly triage | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 05 · Agent guardrail | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 06 · Smart sampling | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 07 · SOC pre-filter | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 08 · Data quality firewall | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 09 · Moderation pre-filter | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
| 10 · Feedback miner | Optional. Defaults to the TypeSafe endpoint. | Required, as TYPESAFE_API_KEY. | None. |
Setup questions.
To run them, yes: you supply a Jev endpoint, and for nine of the ten a key in TYPESAFE_API_KEY. To read them or validate them, no. expanso-edge validate checks a pipeline offline and contacts nothing.
In environment variables on the node that runs the pipeline. The YAML references ${JEV_API_URL} and ${TYPESAFE_API_KEY} and contains neither value, so the file is safe to commit and share.
Its pipeline keeps recurrence history outside the pipeline: it posts each fingerprint to a small local service on 127.0.0.1:8898 and gets back the occurrence count and earlier decisions. That service is part of the example package and is not published on this site.
Pick an example and read its handoff.
Every page shows the stages in two lanes and the full pipeline file, line by line.
