docs: clarify logical grouping (Sum of Products) and precedence

Author: sdieguez-wotc

docs/concepts/implementation-examples.md

@@ -143,3 +143,45 @@ const context: MyAppContext = {
 const result = engine.execute(script, context);
 console.log(result.context.messages); // [{ type: 'info', text: 'Alice: Good morning!' }]
 ```
+
+## 6. Logical Grouping (AND/OR)
+`neuron-js` uses a "Sum of Products" approach to logic. Conditions are grouped into blocks.
+- **AND**: All conditions within a block must be true.
+- **OR**: If any block is true, the entire rule evaluates to true.
+
+### How to trigger OR
+Setting `orCondition: true` on a condition starts a **new block**. This new block is joined to the previous block with an `OR` operator.
+
+### Example: (A AND B) OR (C AND D)
+```json
+{
+  "id": "complex-logic",
+  "conditions": [
+    { "id": "A", "type": "is_gold_member" },
+    { "id": "B", "type": "has_high_balance" },
+    { 
+      "id": "C", 
+      "type": "is_new_user", 
+      "options": { "orCondition": true } 
+    },
+    { "id": "D", "type": "has_promo_code" }
+  ]
+}
+```
+**Evaluation Logic**: `(A && B) || (C && D)`
+
+## 7. Condition Inversion (NOT)
+Any condition can be negated by setting `inverted: true` in its options. This is handled by the runtime, so your plugin implementation doesn't need to worry about it.
+
+```json
+{
+  "id": "not-blocked",
+  "conditions": [
+    { 
+      "type": "is_user_blocked", 
+      "options": { "inverted": true } 
+    }
+  ]
+}
+```
+**Evaluation Logic**: `!is_user_blocked`

docs/concepts/scripts-and-rules.md

@@ -19,11 +19,21 @@ A `Rule` is a self-contained logical unit. It consists of two main parts:
 ```
 
 ## Condition Logic
-Conditions are evaluated sequentially. By default, they follow an **AND** logic (all must be true).
+Conditions are evaluated sequentially and follow a **Sum of Products** logic (ANDs grouped by ORs).
 
-### Advanced Condition Features:
-- **Inversion**: A condition can be "inverted" (NOT logic).
-- **OR Grouping**: A condition can be marked as an `orCondition`. If the next condition is an `orCondition`, they are treated as a group where only one needs to pass.
+### AND Logic
+By default, all conditions in the list are joined by **AND**. Every condition must evaluate to `true` for the actions to trigger.
+
+### OR Grouping
+You can create an **OR** relationship by setting `orCondition: true` in a condition's options. This starts a **new block** of conditions.
+- Each block is evaluated as an **AND** group.
+- All blocks are joined by **OR**.
+- If **any** block evaluates to `true`, the rule fires.
+
+**Example result**: `(Block 1 AND Block 1) OR (Block 2 AND Block 2)`
+
+### Advanced Features:
+- **Inversion**: Set `inverted: true` to negate a condition (NOT logic).
 - **Disabling**: Rules or individual conditions can be disabled via options without removing them from the script.
 
 ## Sequential Execution