Skip to main content
Use a published enrichment whose input kinds and output schema match your dataset. You need binding authority, sufficient clearance and an authorised execution principal.

​
Select and bind a version

  1. Open the dataset’s Analysis page.
  2. Select the enrichment definition and inspect its published version, expected inputs and evaluation evidence.
  3. Create a dataset binding. Confirm the principal and displayed billing team.
  4. Inspect context selection: the definition default, none, thread or neighbours, where supported.
  5. Choose whether to run manually or enable automatic processing.
V2 uses dataset bindings. A workspace-and-dataset binding is refused. A dataset binding and its eligible results travel with that dataset to every workspace that reaches it. Binding an LLM definition and enabling automatic processing are separate actions. A deterministic Format, Enrich or Aggregate bundle binding starts production work immediately. Use evaluated inputs and the intended dataset before binding one.

​
Preview and run a bounded pass

For a controlled manual pass, preview the pending count before admission. Set a supported input limit or confirm the maximum pending count. If the pending count exceeds your confirmation, no work is admitted. The count includes older pending work. A bounded pass processes at most its permitted inputs; a later pass handles the remainder. A manual pass can run with automatic processing off. It leaves that setting off. A paused binding runs no pass, so unpause it deliberately when ready.

​
Inspect results and omissions

Open representative results beside their exact source fragments. Check the schema, effective inputs, definition version and selected context. Review pending, completed, failed and skipped inputs. A completed world-model extraction can still have claims dropped during evidence validation. Inspect those refusals before treating it as graph coverage. An unchanged completed input reuses its result without another model call. A changed source, relevant neighbour/thread context or processing version can require new work.

​
Upgrade, retry or pause

There is no action that clears all enrichment results or resets a binding’s history. An expired result stays recorded as completed; unchanged work needs a forced rerun to recreate it. Processing never lowers the dataset security level. Follow privileged authority rules for authorised level changes. For authoring and evaluation, use Develop and evaluate an enrichment.