What is a Policy Version?
A Policy Version is a snapshot of rules within a policy group. It follows a strict lifecycle — similar to a Git branch that gets merged and tagged as a release. Each version has:- A version number (auto-incremented: v1, v2, v3…)
- A commit message describing what changed
- A status that determines what you can do with it
- 0 or more rules (conditions + actions)
Version Lifecycle
Publishing a version (
DRAFT → ACTIVE) locks it permanently. You cannot add, modify, or delete rules in a published version. If changes are needed, clone the version to create a new DRAFT.Key Constraints
- Cannot publish without rules. A version must have at least one rule before publishing.
- Cannot modify after publishing. Once ACTIVE, the version is immutable.
- Cannot deploy a DRAFT. Publish first, then deploy.
- Always dry-run before publishing. Validate rule behavior against test inputs.
Cloning a Version
When you need to iterate on a published version:- Select the ACTIVE version you want to base changes on
- Click Clone — this creates a new DRAFT with all the same rules. The effective date range is not copied; set one on the new DRAFT if it needs one.
- Modify rules in the new DRAFT
- Dry-run → Publish → Deploy
Deleting a Version
You can delete aDRAFT, ACTIVE, or EXPIRED version. A version that is live or in an A/B test can’t be deleted (P-017), and neither can a version that a pending scheduled deployment targets (P-043).
- A
DRAFTis removed. - A published version (
ACTIVEorEXPIRED) becomesARCHIVEDinstead, whether or not it was ever executed, so that its executions, Decision Provenance, and deployment history still point to it. An archived version no longer appears in the version list and cannot be deployed, executed, simulated, replayed, cloned, or used in a dry run (P-008), and it cannot be the test version of an A/B test (P-042). Executions and Decision Provenance still show it, and the API still returns it when you ask for it by ID. Deleting it again does nothing.
Effective Date Range
A version can optionally have an effective window, fromeffectiveFrom to effectiveTo, and LexQ enforces both ends of it — every automatic action is recorded in the deployment ledger:
effectiveFromin the future — the version cannot be deployed immediately (P-037), but it can be armed as a Scheduled Deployment: the system deploys it automatically when the window opens.effectiveTopasses while live — the version transitions toEXPIREDand the system falls back to the latest currently-valid ACTIVE version, recorded as a System deployment. If no valid candidate exists, the group is undeployed — also recorded.
Setting the Window
- Both ends are inclusive. The version is effective at the exact
effectiveFromandeffectiveToinstants. - The API, CLI, and MCP tools take instants: ISO-8601 with
Zor an offset, such as2026-10-01T00:00:00Zor2026-10-01T09:00:00+09:00. A bare date, or a time without an offset, is rejected. - The console reads the dates and times you pick in your organization’s timezone (Settings → Organization → Timezone). An end picked as 23:59 includes that whole minute.
Changing the Window of a DRAFT
An update keeps any end you leave out. To remove an end, ask for it explicitly:
Sending a value and its clear flag for the same end is rejected (
C-001).
When the End Has Passed
A version whoseeffectiveTo has passed can no longer be published, deployed, or rolled back to (P-058). For a DRAFT, move the end into the future. For a published version, clone it and set a new window on the clone.
Next Steps
Policy Rules
Learn how to define conditions and actions within a version.
Deployments
Learn how to push versions to production.

