Skip to content

Entry Points and Resuming

The Data Suitability recipe saves its progress on the AI Use Case, so every way back into a run goes through the record: from the recipe's own record list or from the AI Use Case page. This page lists those entry points and explains how a run resumes.

Entry Points

Entry point Where Shown when Opens at
Get Started The Data Suitability card on the Recipes page Always The record list
Start a new record The record list Always Model, a fresh use case
Open in Recipe A row's actions menu on the record list Always The step the record's saved run is on
Continue Recipe The Latest Recipe Run card on the AI Use Case page The run is not complete and you can edit the record The step the saved run is on
Review Recipe The same card The run is complete and you can edit the record The step the saved run is on, normally Complete
Edit in Recipe The Model Definition header on the AI Use Case page You can edit the record Model
Adjust Model or Inputs The warning on a revoked AI Use Case The record is Revoked and you can edit it Model

Clicking a row itself on the record list opens the AI Use Case page, not the recipe. The recipe's side panel and the AI Use Case page both carry All AI Use Cases, which returns to the record list.

Resuming

Every change you make is saved to the record's recipe run a moment after you make it: the step you are on, plus a small amount of run state, such as when the baseline was captured and which attestation the run produced. The name, bindings, check set, and schedule are stored on the AI Use Case itself. When you resume, the recipe reloads the record, reads the run, and reopens on the saved step, showing "Picking up where you left off…" while it does so.

Two consequences follow from progress living on the record rather than in your browser:

  • You can resume from any browser or computer, as long as you can see the record, which needs the Viewer team permission on every datastore it binds. Saving progress needs Author on all of them, and Members can only save on records they created.
  • The Recipes page card cannot show In progress or Continue for this recipe, since it does not know which record you were working on. Always resume from the record list or the AI Use Case page.

A run is marked complete when you reach the Complete step. The AI Use Case page then offers Review Recipe instead of Continue Recipe. Opening the recipe again through Edit in Recipe starts at the Model step against the same record, and a later run that changes the definition resets the attestation the recipe treats as current, so the Evidence step asks for a new one.

Starting Another

There is no destructive start over. Start Another on the Complete step, and All AI Use Cases at any time, simply return to the record list. The use case keeps its record, its baseline, and every attestation. To remove a record, delete the AI Use Case, which needs the same permission as editing it.

See Also

  • Examples

    Real scenarios showing a model's inputs turned into a certified evidence record.

    Examples

  • Best Practices

    Guidelines for naming, binding scope, baselines, certification, and keeping evidence trustworthy.

    Best Practices

  • Permissions

    The roles, team permissions, and ownership rule behind each step of the recipe.

    Permissions

  • How It Works

    The two phases, the Use Case picker, how progress is saved on the AI Use Case, and what the recipe writes.

    How It Works

  • Define the Use Case

    Model, Inputs, and Standard: naming the model, binding its assets, and pinning the check set and expiry schedule.

    Define the Use Case

  • Capture the Evidence

    Baseline, Evidence, and Complete: fixing the drift referent, certifying, generating the attestation, and exporting it.

    Capture the Evidence

  • AI Use Cases

    The governance record the recipe writes: certification lifecycle, who can do what, attestations, and audit obligations.

    AI Use Cases