---
title: "Define a regime"
method: POST
path: "/v2/workspaces/{id}/regimes"
tags: ["Regimes"]
---

# Define a regime

`POST /v2/workspaces/{id}/regimes`

## Request

- Base URL: `https://api.infolang.ai`
- URL: `https://api.infolang.ai/v2/workspaces/{id}/regimes`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer
  - HTTP bearer

Mints a world-phase. `from`/`to` attach a window (display only) and `start: true` puts it in force — separate records either way.

A regime is an exact, NAMED applicability context — a mission phase, a jurisdiction, a classification level, a retention window. Identity is the id, never the name: `prod freeze` and `production freeze` are two regimes if they were minted twice and no fold will ever discover they were meant to be one.

Membership is a SCOPE LINK somebody wrote down, never a timestamp: nothing joins a regime by having a `valid_time` inside its window. A window is documentation of intent.

Requires the `coord:write` scope. Accepts all three lanes: a session JWT (bounded by the caller's role on this workspace) or an `il_*` machine credential whose own scope set, workspace set and validity window cover it — both ceilings apply and neither can raise the other, so a credential carrying `coord:write` is still refused where the role does not permit it.

A credential with no scope record resolves to `LEGACY_DEFAULT`, which does NOT include `coord:write` — mint a key with it explicitly (`POST /v2/workspaces/{id}/keys`).

## Path parameters

- `id` string, required

## Request body

- object
  - `name` string, required
  - `regime` string, uuid
  - `from` string, date-time
  - `to` string, date-time
  - `start` boolean

## Response `201`

The regime, and what the follow-up records did

- object
  - `regime` string, required
  - `name` string, required
  - `record` string, required
  - `authority` string, required
  - `appended` boolean, required
  - `scheduled` boolean
  - `started` boolean

## Other responses

- `401`: Missing/invalid credential, or `credential_expired` — the credential is outside its `[not_before, expires_at)` window and must be replaced
- `403`: `insufficient_scope` — the credential's own scope set, or the caller's role on this workspace, does not cover the scope this route requires (the missing scope is named in the message). Or `forbidden` — the credential is not scoped to this workspace, or holds no grant on it
- `501`: The regime verbs are not compiled into this deployment (`kernel-verbs` is off upstream)

---

[API](https://skmtc.dev/infolang/apis/infolang-api.md) · [All operations](https://skmtc.dev/infolang/apis/infolang-api/llms.txt) · [OpenAPI document](https://skmtc.dev/infolang/apis/infolang-api/revisions/d04bf6de72c8?raw)