scorecompute
All demonstrationsNATIVE COMPOSITION / TWO ENGINES + ONE ADAPTER

A route becomes a checked risk study.

Execute an approved route-to-risk chain with checked identities, explicit units, caller-supplied speed and real native progress events.

execute_compositionTry the real call
Concept artwork · not calculation evidence
01 / UNDERSTAND THE METHOD

See what the tool does.

ILLUSTRATION · NOT A CALCULATION
INTERACTIVE 3D / METHOD STUDYExplore the method in space.
stated goalRust planchecked resultunits · assumptionsexplicit adapters only

Preparing the 3D exhibit…

A teaching illustration. Run the tool below to obtain a native calculation.Drag to inspect · arrow keys move the camera · no MCP call

02 / ASK THE ACTUAL TOOL

Make it your experiment.

Complete tool arguments

Arrays, coordinates and nested contracts remain editable here. Units and limits are checked by the real tool.

Runs only when you press the button. Input edits discard the previous displayed result. Public compute limits apply.

KNOW WHAT THE RESULT MEANS

Useful evidence needs boundaries.

  • The four-kilometre square at 60 km/h gives four one-minute nominal legs. With ±25% variation and a four-minute budget, completion of this assessment does not mean timely arrival is likely enough.
  • Speed is a declared geometric conversion, not a traffic estimate. Zero-length legs and unsupported bounds are rejected instead of silently removed.
  • Only the two approved risk families execute here. This assesses one route; it does not search for a more robust tour or run arbitrary graph paths.