What does PulseLane actually decide, and on what inputs?

Only clinic triage decisions is stated. No symptoms, no intake fields, no criteria and no output shape are documented, so the clinical content of the demo cannot be assessed from the README at all.

Is it safe to point this at real patient data?

Nothing in the README supports that. There is no mention of validation, patient data, accuracy figures or clinical review, and triage decisions carry consequences a demo UI should not be asked to carry.

Without an API key, am I looking at real Jev output?

No. The README states that without a key, demo heuristics return the same answer shape so the UI works. The shape is genuine; the probabilities behind it in that mode are not model output.

How do I switch it to the real model path?

Write the key into .env.local as TYPESAFE_API_KEY=... before npm run dev. That is the only configuration step the README documents, and the .env.local file is not committed.

What language is PulseLane written in?

It is cataloged as TypeScript. The README names no framework, runtime version, or dependencies.

Does PulseLane document a test or build step?

No. The README gives npm i and npm run dev plus an optional .env.local key, with no test, lint, or build command mentioned.

Is PulseLane part of a larger set of Jev demos?

Yes. It is one of eight demos cataloged under the GitHub user ndolinschi, alongside JevPlay, LaneBreak, McpMatch, SpendBrake, SwarmRouter, ToolGate, and TrustGate.

CommunityJev Demos & Experiments

Pulselane

PulseLane models clinic triage decisions through TypeSafe Jev on System One. An optional TYPESAFE_API_KEY in .env.local switches it from bundled demo heuristics to real model calls; without a key the heuristics return the same answer shape so the UI still runs.

See highlights

Open github.com

Stars: 1
Language: TypeScript
Published by: Community
Author: ndolinschi
Last verified: Oct 2026

ndolinschi/pulselane

User repository on GitHub

View on GitHub

PulseLane — clinic triage decisions via TypeSafe Jev

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

About this project

Clinic triage decisions powered by TypeSafe Jev (System One). Without a key, demo heuristics return the same answer shape so the UI works.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import awesomejev

Works forJev for Classification

Used inJev for Software & DevTools

Languages: TypeScript

Highlights

Triage decisions run through System One, named as the model behind the demo.
TYPESAFE_API_KEY in .env.local is optional; without it, demo heuristics stand in.
The keyless path returns the same answer shape, so the UI works either way.

Watch out

The decision content is absent from the README: no symptoms, no intake fields, no urgency criteria, no red-flag list, no output schema and no statement of who reviews the output. Nothing describes validation, testing against patient data, or clinical review, and no accuracy figure is given, so this should not be read as a triage tool. The keyless path runs heuristics, so a working UI without a key says nothing about model behaviour. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

laya-server

Self-hosted Docker service and web UI that packages Laya structured-decision inference behind a compatible System One endpoint.