Jev milestone fact alignment

Compare the facts established by two work milestones

Supply both milestone statements and their evidence. Check whether they establish the same fact or different work outcomes, keeping a code change separate from a check of that change.

Do the milestones establish the same proposition?Live API
Try an example

Both statements establish the same omission.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The Albedo post names this task. A separately located public Albedo repository contains corresponding decision code, pinned here to a commit. The post’s short link points to its photo, not that repository; shared authorship is unverified. This is an original synthetic adaptation, not an Albedo integration or reproduction of its speed and cost claims.

Compare milestone statements and evidence.

Decision rules and labels
Same factDifferent factsNeed milestones
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

Changing code and checking it are separate milestones.

Adding a null guard changes the implementation. Running a regression test records a check. They concern the same feature, but a record of one does not establish the other.

Two statements can establish the same finding in different words. The expiry examples point to the same handler omission. An incidental line number does not necessarily create a new fact.

The comparison needs usable evidence for both statements. A claim that a guard runs first cannot establish a common fact when its supplied code shows the opposite. This page returns a relationship for review without merging records or verifying a repository.

The Albedo post names this task. A separately located public Albedo repository contains corresponding decision code, pinned here to a commit. The post’s short link points to its photo, not that repository; shared authorship is unverified. This is an original synthetic adaptation, not an Albedo integration or reproduction of its speed and cost claims.

Illustration of checking a code change and reviewing a flagged line
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 milestone fact comparison.

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

    Add the information to check

    Supply both milestone statements and their evidence.

  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 Same fact, Different facts, Need milestones. 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 Need milestones 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
Same findingSame fact100%
Location versus causeSame fact51.0%
Change versus testDifferent facts100%
Incidental locationSame fact100%
Contradictory evidenceNeed milestones57.0%
Missing milestoneSame fact60.0%

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. 4 of 6 results matched the authored fixture expectations. For Location versus cause, the expectation was Different facts; the observed choice was Same fact. For Missing milestone, the expectation was Need milestones; the observed choice was Same fact.Verified

Understand the results

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Comparing differently worded findings
  • Keeping changes separate from their verification
  • Reviewing evidence before merging milestone records

Outside this demonstration

  • Executing code or tests
  • Inferring work from a milestone title alone
  • Automatically merging or deleting records
Example FAQ

Questions about milestone fact alignment.

Input scope and downstream handling determine what this judgment means.

Do two steps about the same file establish the same fact?

Not necessarily. Reading a file, changing it and testing its behavior can establish different facts.

Does Same fact verify both milestones?

No. It is a comparison of the supplied statements and evidence. The page does not inspect the actual repository.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own milestone fact alignment input

Edit the input above, or open the Playground to explore another decision.