Jev civic report routing

Route a maintenance report using a service directory

Describe the reported problem to compare Roads, Waste and Lighting in a fictional city directory. Review multiple problems and unknown ownership before submission.

civic report routingLive API
Try an example

The supermarket is a location; the defect is in the road.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Route this report using this fictional city directory: Roads handles road surface defects; Waste handles missed collection or dumped rubbish; Lighting handles failed public streetlights.

Decision rules and labels
RoadsWasteLightingReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

A report often names several objects, but the destination depends on the problem being described. A pothole next to a supermarket still belongs to the road-maintenance category in this fictional directory.

Real service responsibilities vary by place and ownership. This example demonstrates a routing pattern inspired by the linked Portuguese reporting application. It does not claim that these labels correspond to its directory or to an official municipality.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of routing a message into one of several label groups
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for civic maintenance routing.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Describe the reported problem to compare Roads, Waste and Lighting in a fictional city directory.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Roads, Waste, Lighting, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
PotholeRoads100%
Missed binsWaste100%
Dark crossingLighting100%
Private fixtureReview100%
Two problemsReview99.0%
Unknown problemReview100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Civic maintenance routing: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Prototyping a report intake form with a supplied service directory
  • Separating the problem from incidental location words
  • Sending mixed or uncertain reports to a person

Outside this demonstration

  • Selecting a legally responsible authority in a real jurisdiction
  • Emergency triage
  • Submitting reports or contacting public services
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does this return the correct Portuguese authority?

No. It uses a fictional three-service directory. A real application needs a verified local directory, location and ownership information.

Why does a report with two problems go to Review?

This example returns one label. A broken streetlight and dumped rubbish may need separate reports, so the input goes to review instead of silently dropping one issue.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.