---
id: project-settings.regime
title: Regime Settings
summary: Inspect and publish the project scoring Regime that governs future Benchmark Versions.
kind: reference
product_area: project_settings
status: stable
updated: 2026-09-07
canonical: /docs/project-settings/regime
---

# Regime Settings

## Definition

Regime Settings define how approved and applicable Rubrics contribute to Case and Benchmark results. The Regime is part of the project contract, but its published version is pinned into later Benchmark Versions so historical evaluation evidence remains interpretable.

The settings surface shows the Project's locked framework, its decision rule, what the framework is suited for, and which scoring controls administrators can configure. A framework is not a Policy or Rubric; it determines how those governed artifacts are interpreted and aggregated for evaluation.

## Fields, states, or lifecycle rules

- The framework is locked for an existing Project. Other framework choices can be available when creating a new Project.
- Depending on the framework contract, administrators can configure Case aggregation, score range, penalty policy, Rubric role assignment, safe custom formulas, and an Importance scale.
- A custom formula is validated and stored as typed configuration; it is not executable code.
- Editing creates unpublished scoring changes. **Publish new Version** creates an immutable Regime Version after validation and concurrency checks.
- New drafts and finalized Benchmark Versions retain the Regime Version they were created or finalized with. Publishing a later version does not rewrite existing plans, Runs, or results.
- Published version history shows prior configurations and can show which open drafts or Benchmark Versions use a version.
- A concurrent publication requires the administrator to review the latest version before publishing retained edits.

## Configure safely

Review the framework decision rule before changing scoring behavior. Confirm that the desired aggregation, score range, penalties, and Importance semantics match the Policies and Rubrics that will be evaluated. Publish only after the resulting version can be explained to someone reading a future Benchmark result.

Do not use Regime Settings to change the meaning of a Policy or Rubric. Change those governed artifacts through Correctness Governance, then create or evaluate the appropriate versioned benchmark evidence.

{% example-demo title="Example: preserving historical scoring" %}
An administrator changes the score range and publishes Regime Version 4. New Benchmark Versions pin Version 4, while an existing finalized Benchmark Version continues to report under Version 3. The administrator can inspect both configurations and their usage without treating the new scoring choice as a rewrite of old results.
{% /example-demo %}

## Source confidence

Code-backed: the Project Settings Regime panel exposes locked framework guidance, scoring configuration, validation, immutable publication, concurrent-publication recovery, and version history. The project API exposes framework discovery, current Regime reads, publication, history, and version usage.

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Configure Project Settings](/docs/project-settings)
- [Build Policies and Rubrics](/docs/operating-manual/build-policies-and-rubrics)
- [Run a benchmark evaluation](/docs/benchmark-evaluations/run-evaluation)
{% /related-card-grid %}