Jev server action actor source

Trace trusted actor identity in a server action

Show how a server action obtains the actor, role and tenant it trusts. Separate verified session-derived identity from unverified caller values, keeping unknown authorization helpers visible.

server action actor sourceLive API
Try an example

The actor comes from the supplied verified session contract.

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.

Trace actor identity and privileges used by this server action: Client if any trusted actor ID, role or tenant comes unverified from the caller; otherwise Server if all come from a verified session bound to the current caller or database records selected through it.

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

Actor and target are different inputs. A record ID can come from the browser while the server establishes who is acting and checks permission for that specific record.

Server describes only identity provenance. It does not prove that the action checked ownership, restricted writable fields or avoided returning private data. Those need their own evidence.

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 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 server action identity.

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

    Add the information to check

    Show how a server action obtains the actor, role and tenant it trusts.

  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 Server, Client, 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
Session actorServer100%
Caller ownerClient77.0%
Caller roleClient82.0%
Target is separateServer100%
Database roleServer100%
Unknown identity resolverUnclear99.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 action identity: 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 action arguments
  • Separating actors from targets
  • Tracing role and tenant inputs

Outside this demonstration

  • Certifying application security
  • Testing access to real accounts
  • Assuming identity helpers are trusted
Example FAQ

Using this example

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

Must every target ID come from the session?

No. A request may identify a target resource. The application still needs to derive the actor from a trusted source and verify permission on that target.

Does a session lookup prove the whole action is authorized?

No. The action might still act on another user’s record without a permission check. This example only traces the acting identity.

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.