lexq-rules

LexQ CLI — Policy Rules

Prerequisite: Read lexq-shared/SKILL.md first.

Overview

A Policy Rule is a condition → actions pair within a version. Rules are evaluated in priority order — lower number wins, and priorities are 1-based (1 is highest). When a rule's condition matches the input facts, its actions fire.

priority is assigned by the server, not by you. New rules are appended last. Use lexq rules reorder to change the order.

Rule Structure

{
  "name": "VIP 10% Discount",
  "condition": {
    ...
  },
  "actions": [
    ...
  ],
  "mutexGroup": null,
  "mutexMode": "NONE",
  "mutexStrategy": "HIGHEST_PRIORITY",
  "mutexLimit": null,
  "isEnabled": true
}

Condition Syntax

Conditions use a tree structure with two node types: SINGLE and GROUP.

SINGLE Condition

{
  "type": "SINGLE",
  "field": "paymentAmount",
  "operator": "GREATER_THAN_OR_EQUAL",
  "value": 100000,
  "valueType": "NUMBER"
}

GROUP Condition (logical combinator)

{
  "type": "GROUP",
  "operator": "AND",
  "children": [
    {
      "type": "SINGLE",
      "field": "customerTier",
      "operator": "EQUALS",
      "value": "VIP",
      "valueType": "STRING"
    },
    {
      "type": "SINGLE",
      "field": "paymentAmount",
      "operator": "GREATER_THAN",
      "value": 50000,
      "valueType": "NUMBER"
    }
  ]
}

Operators

Operators are constrained by the left fact's type. Using one outside its type is rejected by the server — check lexq facts list before choosing.

Fact type	Allowed operators
STRING	EQUALS, NOT_EQUALS, CONTAINS, IN, NOT_IN
NUMBER	EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_OR_EQUAL, LESS_THAN, LESS_THAN_OR_EQUAL, IN, NOT_IN
BOOLEAN	EQUALS, NOT_EQUALS
LIST_STRING / LIST_NUMBER	HAS_ANY, HAS_ALL, HAS_NONE