Community · E2 · artifact verified
Decide inside agent workflows with a typed node
Heym, an agent orchestration platform (1.2k★), ships a typed Decision node for Jev: workflows ask yes/no, choice, score and, since Jev 1.14, image and Box questions mid-flow, with per-judgment trace spans and a human-in-the-loop inbox for the uncertain ones.
01 · Role in the system
What Jev does here
Every workflow step can pause and ask Jev typed questions - the node posts to TypeSafe's /v1/systemone contract, and since the merged image-input PR it can attach an image by name and ask Box questions about where something sits in the picture, enabled through TypeSafe's images opt-in header. Questions refer to images the way TypeSafe documents; the service rejects out-of-limits images instead of resizing them, and the platform's own docs call TypeSafe images experimental - fine for prototypes, not production gates. Decisions carry probabilities into trace spans for auditing, a model router keeps the decision model separate from generation models, and anything uncertain routes to a human-in-the-loop inbox where a reviewer claims the case and the workflow resumes.
02 · Control boundary
Where Jev sits
Jev as a first-class workflow node in an agent orchestrator: typed questions as node configuration, credentials via a dedicated model router, per-judgment trace spans, and a claim-and-resume human inbox for low-confidence answers.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Image and Box support is new (PR merged 2026-10-16) and gated behind TypeSafe's images opt-in header; the platform's own docs call TypeSafe images experimental.
- The integration ships inside Heym's product workflow; no independent benchmark numbers are published.
- Decision credentials point at a configurable base URL, so compatible non-TypeSafe endpoints also work.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.