Jev Tetris placement selection

Choose among supplied legal Tetris placements

Provide legal candidates, computed afterstate facts and a strategy goal. Compare the offered placements under that goal; this text exercise does not calculate legality or operate a live game.

Tetris placement selectionLive API
Try an example

B preserves the stated next-piece requirement without the new gap.

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.

Choose A, B or C from the supplied legal Tetris placements using the stated goal and computed afterstate facts.

Decision rules and labels
ABCReview
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 Tetris move includes a rotation and final placement. The game engine can enumerate legal candidates and compute what each resulting board permits; this example starts after that work has been done.

The editable inputs describe those computed effects in words. They make the goal visible so you can inspect a tradeoff such as an immediate clear that closes the next piece's entry. They are synthetic scenarios, not board states executed by this webpage.

The linked implementation separates a live Jev request from a local fixture that uses a scoring formula. This page records actual API responses to its own original examples; it does not reuse the fixture's fixed score or claim optimal play.

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 selecting one supplied candidate in a game-state decision
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 tetris placement choices.

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

    Add the information to check

    Provide legal candidates, computed afterstate facts and a strategy goal.

  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 A, B, C, 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
Quick clear closes the next laneB100%
Immediate survivalA99.0%
Preserve the prepared wellC98.0%
Missing collision validationReview69.0%
Equal supplied outcomesReview87.0%
Unsupported next-piece claimReview100%

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

Tetris placement choices: 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 policy over legal moves generated by a game engine.
  • Comparing immediate points with an explicitly supplied next-piece constraint.
  • Checking whether missing afterstate evidence should stop a move proposal.

Outside this demonstration

  • Asking the model to certify collisions or recompute a board from a drawing.
  • Using a label as an optimal-play result or executing it without game-state validation.
Example FAQ

Using this example

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

Does this page contain a playable Tetris game?

No. It demonstrates the selection step using editable text descriptions. A game would generate the legal moves, compute their effects and validate the chosen ID against the current state.

Why not use a fixed scoring formula?

A known numeric objective may be better handled by ordinary code. This exercise explores an explicit language goal over computed candidates; it does not show that a model beats a game heuristic.

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.