Case study · located work
Goblin HR
A small inspectable demo that evaluates candidates for an impossible mission.
ObservedKostysh
- Problem
- A small inspectable demo that evaluates candidates for an impossible mission.
- Jev’s role
- Scores/selects candidates while deterministic TypeScript assembles the party.
- Architecture
- Mission state → candidate decisions → deterministic application logic.
- Why it matters
- Keeping selection probabilistic and execution deterministic makes the boundary easy to inspect.
Code boundary
Jev answers the bounded questions described above. Thresholds, retries, side effects, and anything that must be reproducible stay in the surrounding application code. The research record does not capture this project’s exact question set or threshold values; read the linked source before copying the architecture.
Sources
Limitations
- A located repository or demonstration does not establish production reliability or independent validation.
Reusable pattern and related records
- Probabilistic predicate + deterministic action PlausibleJev supplies fuzzy predicates while TypeScript, policies, and workflows execute constrained actions.
- CI Review Triage Authored HypothesisA GitHub check that assigns review depth, owners, and required test classes to every pull request.
- Jev exposes constrained decision primitives for Boolean probability, choice distributions, and ordered scores. DemonstratedThe public API documentation defines `noul`, `choice`, and `score` response shapes.
- Decision sidecar PlausibleA typed judgment service sits beside ordinary code; code owns effects and safety boundaries.