Jev object responsibility review

Review whether a method relies on another object's internals

Show the method, collaborator roles and field visibility. Separate foreign implementation access from ordinary data reads and public delegation without judging ownership from syntax alone.

object responsibility reviewLive API
Try an example

The view reimplements behavior using another object's private state.

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.

Review the supplied method and object roles.

Decision rules and labels
Foreign internalsOrdinary useReview
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

Feature-envy-style review depends on responsibility, not a count of dots or field reads. Plain data records are meant to expose fields, while a behavior-owning object may need to keep its implementation behind an API.

The input therefore includes roles and visibility facts. Without them, a reviewer cannot reliably tell whether a method is borrowing private knowledge or using a normal data contract.

The linked clean-code reviewer checks object boundaries and foreign-data-heavy methods. This original example joins those related checks into one task and does not move methods or rewrite a class.

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 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 object responsibility review.

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

    Add the information to check

    Show the method, collaborator roles and field visibility.

  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 Foreign internals, Ordinary use, 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
Behavior moved across a boundaryForeign internals94.0%
Plain data recordOrdinary use99.0%
Public delegationOrdinary use100%
Configuration readsOrdinary use100%
Unknown ownershipReview97.0%
Conflicting visibilityReview98.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

Object responsibility review: 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 a method with explicit object responsibilities.
  • Separating DTO reads from private implementation coupling.
  • Checking whether an existing public collaborator API is being used.

Outside this demonstration

  • Treating every method chain or multi-field read as a design flaw.
  • Applying an automatic refactor without ownership, tests and compatibility context.
Example FAQ

Using this example

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

Is reading another object's fields always wrong?

No. A plain DTO or configuration record is intended to supply data. The example asks whether private behavior-owning state is being used to reimplement another object's responsibility.

Why supply the object roles?

The same syntax can represent ordinary data access or unwanted coupling. Explicit roles and visibility make that distinction reviewable.

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.