Jev closure ownership cycle review

Review a stored closure for a strong ownership cycle

Describe who stores the closure, its captures and their lifetimes. Trace explicit strong edges and weak captures before deciding whether the supplied graph contains a cycle.

closure ownership cycle reviewLive API
Try an example

Owner to closure to owner is a complete strong loop.

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 ownership.

Decision rules and labels
Strong cycleWeak captureNo cycle shownReview
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 retain cycle needs a return path. A closure can strongly capture an object without a cycle when that object does not directly or indirectly retain the closure.

The examples make each edge explicit, including subscriptions between the owner and callback. Missing capture or storage facts go to review instead of being inferred from the word self.

The source linter checks escaping-closure cycles. This exercise describes an ownership graph; actual retention duration, cleanup and memory behavior still need runtime inspection.

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 closure ownership.

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

    Add the information to check

    Describe who stores the closure, its captures and their lifetimes.

  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 Strong cycle, Weak capture, No cycle shown, 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
Stored closure captures ownerStrong cycle98.0%
Weak return edgeWeak capture91.0%
External one-shot closureNo cycle shown56.0%
Unknown registry ownershipReview100%
Indirect strong loopStrong cycle96.0%
Nonowning capture with known lifetimeWeak capture93.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

Closure ownership: 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 callback stored by its owning object.
  • Tracing a subscription between an owner and its closure.
  • Distinguishing weak capture from an incomplete ownership graph.

Outside this demonstration

  • Claiming a memory leak has been measured from a text label.
  • Changing a capture to nonowning without checking its lifetime requirements.
Example FAQ

Using this example

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

Does every strong capture leak?

No. A cycle requires a complete loop of strong ownership. Lifetime and release behavior are separate facts to inspect.

Should every closure use a weak capture?

No. This example classifies the supplied graph. Selecting a capture mode requires the actual lifetime and behavior requirements.

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.