Open-source TypeScript SDK · Kane CLI Hack Day

Choose a route that fits your preferences.

Waylit helps navigation apps use preferences when choosing a route. Developers provide route options, available context, and priorities such as shorter travel time or better documented lighting. Waylit applies the configured policy and explains how the options fit.

Preferences shape the route

Navigation products can have different priorities. One person may want the shortest walk; another may be willing to take a detour for a better lighting observation. Waylit gives developers a TypeScript SDK for expressing those preferences and constraints in route selection.

Try the project

The demo shows the same route options under different preferences: Shortest Walk selects Route A, while Better Lighting selects Route B within a five-minute detour. All route and observation values are synthetic. Waylit does not generate directions or fetch live conditions.

Run locally with npm ci and npm run dev. The SDK package is not yet published to npm.

How Kane checks it

The saved browser check switches between Better Lighting and Shortest Walk, checks which route each policy selects, verifies detour eligibility and the explanation, and checks for browser console errors. A separate simulator check covers a closed route being excluded before scoring, reopening it, and treating stale or missing observations as unknown.

What actually ran

The latest event-reported run is KR-303. It replayed the saved browser check, then re-authored it after a console-check inconsistency. Kane marked its final verification failed and opened a suspected automation issue; the recorded route assertions show the expected selections, so this is not evidence of a confirmed product defect. The run did not pass.

The demo uses synthetic data. Scores describe fit to supplied preferences; they are not safety probabilities. Evidence packs stay private and are not linked here.