Jev server return field scope

Check which database fields a server action returns

Review the return path and mapping contract to distinguish selected fields, a whole record or no result. A broad return shape alone does not establish which data is sensitive.

server return field scopeLive API
Try an example

The returned object selects two fields.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original code-reading exercise adapts a rule in the jev-lint repository linked by the cited X post. Snippets, labels and missing-context handling are authored for this page. It does not execute code, reproduce a repository scan or certify an application as safe.

Classify the client return: Projection for explicitly selected fields or a supplied response-mapping contract; Whole for an entire database record with no projection; Noresult when nothing is returned; Unclear when the mapper or record shape is unavailable.

Decision rules and labels
ProjectionWholeNoresultUnclear
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

Projection is a structural result: the output fields are explicitly chosen. It does not establish whether every selected field is appropriate for every caller.

Whole can be useful to flag for review without inventing a leak. The actual sensitivity of returned fields depends on the record shape and access policy, which must be supplied separately.

This original code-reading exercise adapts a rule in the jev-lint repository linked by the cited X post. Snippets, labels and missing-context handling are authored for this page. It does not execute code, reproduce a repository scan or certify an application as safe.

Illustration of one spreadsheet row producing two separate classification results
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 server response projection.

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

    Add the information to check

    Review the return path and mapping contract to distinguish selected fields, a whole record or no result.

  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 Projection, Whole, Noresult, Unclear. 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 Unclear 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
Small responseProjection100%
Entire updated rowWhole97.0%
Database selectionProjection100%
No payloadNoresult99.0%
Unknown mapperUnclear85.0%
Whole public rowWhole70.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. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Server response projection: 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

  • Reviewing server-to-client response shapes
  • Finding unprojected ORM returns
  • Documenting response mapper contracts

Outside this demonstration

  • Claiming an observed data breach
  • Approving selected fields for all users
  • Inferring missing mapper behavior
Example FAQ

Using this example

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

Is every whole record secret?

No. One preset deliberately returns a wholly public record. The label describes the projection boundary, not an incident.

Can a named DTO helper count as Projection?

Only when its mapping contract or implementation is provided. A descriptive helper name is insufficient evidence.

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.