Skip to content

reference

Regime Settings

Configure scoring frameworks, point ranges, increments, and guidance with one current-settings save.

Regime Settings

Definition

Open Project Settings → Regime to configure how applicable rubric judgments contribute to Case and benchmark results. The framework, point ranges, increments and guidance form one current configuration.

Fields, states, or lifecycle rules

  • Positive and penalty limits can be edited independently.
  • Point increments are positive decimals; the editor offers common increments and custom entry.
  • Zero is permitted where the configured treatment allows it.
  • Gate and point guidance explain assignment expectations.
  • One Save applies the configuration and guidance together.
  • A concurrent change is reported instead of silently overwritten.

New numerical configurations start with a signed point range from -5 to +10. There is no configurable minimum magnitude. Existing rubric assignments must remain compatible with the chosen ranges and step.

Save current settings

Review the framework and ranges together with the current assignments. Save after checking whether the values still express the intended consequence of each rubric.

A failed save preserves the editor draft. Resolve the reported conflict or invalid configuration and save the intended current values. Saving settings does not itself approve a Rubric, replace an assignment rationale or confirm expert review.

Point interpretation

Current point scores preserve negative values and have no per-Case floor or cap. A gated framework also distinguishes mandatory-gate eligibility from the point calculation. Missing judgments remain incomplete.

Read the score guide before interpreting a large penalty or a zero score. A zero caused by a completed gate failure has a different meaning from an unscored Case with no applicable points.

Historical work

Saving current settings preserves existing assignments and their attribution. Accepted Benchmark Versions, evaluation tasks and results retain the configuration they captured.

Changes are recorded automatically with their actor, time, scope and before/after content. Users do not create, select, publish or promote a separate configuration version to make the change take effect.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue