@wowok/agent-mcp 2.7.1 → 2.7.2

package/dist/schemas/account_operation.output.json

@@ -1857,13 +1857,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/bridge_operation.output.json

@@ -552,13 +552,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/evaluation_operation.output.json

@@ -32,10 +32,9 @@
                 "perspective": {
                   "type": "string",
                   "enum": [
-                    "disputant",
-                    "arbitrator",
-                    "voter",
-                    "both"
+                    "customer",
+                    "merchant",
+                    "arbitrator"
                   ]
                 },
                 "actions": {
@@ -53,6 +52,16 @@
                         "maximum": 100,
                         "description": "Favorability 0-100 for the perspective."
                       },
+                      "gain_score": {
+                        "type": "integer",
+                        "minimum": 0,
+                        "description": "Gain points (收益)."
+                      },
+                      "risk_score": {
+                        "type": "integer",
+                        "minimum": 0,
+                        "description": "Risk points (风险, appetite-adjusted)."
+                      },
                       "is_optimal": {
                         "type": "boolean",
                         "description": "True when this is the top recommended move."
@@ -74,6 +83,8 @@
                     "required": [
                       "action",
                       "favorability",
+                      "gain_score",
+                      "risk_score",
                       "is_optimal",
                       "payoff_note",
                       "risk"
@@ -107,9 +118,12 @@
                 "perspective": {
                   "type": "string",
                   "enum": [
+                    "merchant",
                     "customer",
-                    "operator",
-                    "observer"
+                    "prospect",
+                    "supplier",
+                    "collaborator",
+                    "arbitrator"
                   ]
                 },
                 "actions": {
@@ -143,7 +157,17 @@
                         "type": "integer",
                         "minimum": 0,
                         "maximum": 100,
-                        "description": "Favorability 0-100 for the perspective."
+                        "description": "Net favorability 0-100 for the perspective (gain − risk)."
+                      },
+                      "gain_score": {
+                        "type": "integer",
+                        "minimum": 0,
+                        "description": "Gain points (收益)."
+                      },
+                      "risk_score": {
+                        "type": "integer",
+                        "minimum": 0,
+                        "description": "Risk points (风险, appetite-adjusted)."
                       },
                       "is_optimal": {
                         "type": "boolean",
@@ -168,6 +192,8 @@
                       "to_node",
                       "execution_path",
                       "favorability",
+                      "gain_score",
+                      "risk_score",
                       "is_optimal",
                       "payoff_note",
                       "risk"
@@ -175,6 +201,85 @@
                     "additionalProperties": false
                   }
                 },
+                "cooperation": {
+                  "type": "object",
+                  "properties": {
+                    "threshold": {
+                      "type": "integer",
+                      "minimum": 1,
+                      "description": "Pair threshold (accumulated forward weights to advance)."
+                    },
+                    "my_weight": {
+                      "type": "integer",
+                      "minimum": 0,
+                      "description": "Weight THIS role can contribute."
+                    },
+                    "needed_from_others": {
+                      "type": "integer",
+                      "minimum": 0,
+                      "description": "Weight still needed from other roles (0 = can advance alone)."
+                    },
+                    "collaborators": {
+                      "type": "array",
+                      "items": {
+                        "type": "string"
+                      },
+                      "description": "Roles that must cooperate to reach the threshold."
+                    },
+                    "allocation": {
+                      "type": "object",
+                      "properties": {
+                        "recipient_slots": {
+                          "type": "integer",
+                          "minimum": 0,
+                          "description": "Total recipient slots across allocators."
+                        },
+                        "guard_gated_slots": {
+                          "type": "integer",
+                          "minimum": 0,
+                          "description": "Slots resolved at settlement by a Guard."
+                        },
+                        "direct_to_me_slots": {
+                          "type": "integer",
+                          "minimum": 0,
+                          "description": "Slots paying directly to this role."
+                        },
+                        "to_payer_slots": {
+                          "type": "integer",
+                          "minimum": 0,
+                          "description": "Slots routing back to the payer (refund-oriented)."
+                        }
+                      },
+                      "required": [
+                        "recipient_slots",
+                        "guard_gated_slots",
+                        "direct_to_me_slots",
+                        "to_payer_slots"
+                      ],
+                      "additionalProperties": false,
+                      "description": "Allocation waterfall — how funds split once the node advances (利益分配)."
+                    },
+                    "allocation_note": {
+                      "type": "string",
+                      "description": "Human-readable利益分配说明."
+                    }
+                  },
+                  "required": [
+                    "threshold",
+                    "my_weight",
+                    "needed_from_others",
+                    "collaborators"
+                  ],
+                  "additionalProperties": false
+                },
+                "value_at_stake": {
+                  "type": "string",
+                  "description": "Escrowed order amount (smallest-unit string) — the monetary value at stake."
+                },
+                "risk_exposure": {
+                  "type": "string",
+                  "description": "Compensation_fund (smallest-unit string) — the monetary risk exposure backing indemnity."
+                },
                 "summary": {
                   "type": "string"
                 }

package/dist/schemas/evaluation_operation.schema.json

@@ -29,11 +29,30 @@
             "perspective": {
               "type": "string",
               "enum": [
-                "disputant",
-                "arbitrator",
-                "voter",
-                "both"
+                "customer",
+                "merchant",
+                "arbitrator"
               ]
+            },
+            "appetite": {
+              "type": "string",
+              "enum": [
+                "conservative",
+                "balanced",
+                "aggressive"
+              ],
+              "description": "Risk appetite — adjusts risk sensitivity (conservative amplifies risk)."
+            },
+            "account": {
+              "type": "string",
+              "description": "Account address; its persona's risk_appetite is used as the default appetite."
+            },
+            "requirements": {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "description": "Persona red lines that re-anchor the role's prefer/avoid (人设驱动力)."
             }
           },
           "required": [
@@ -56,11 +75,75 @@
             "perspective": {
               "type": "string",
               "enum": [
+                "merchant",
                 "customer",
-                "operator",
-                "observer"
+                "prospect",
+                "supplier",
+                "collaborator",
+                "arbitrator"
               ]
             },
+            "appetite": {
+              "$ref": "#/definitions/evaluation_operation/anyOf/0/properties/appetite",
+              "description": "Risk appetite — adjusts risk sensitivity (conservative amplifies risk)."
+            },
+            "account": {
+              "type": "string",
+              "description": "Account address; its persona's risk_appetite is used as the default appetite."
+            },
+            "threshold": {
+              "type": "integer",
+              "minimum": 1,
+              "description": "Pair threshold — when > 1, multi-role cooperation is needed to advance."
+            },
+            "allocation": {
+              "type": "object",
+              "properties": {
+                "recipient_slots": {
+                  "type": "integer",
+                  "minimum": 0,
+                  "description": "Total recipient slots across allocators."
+                },
+                "guard_gated_slots": {
+                  "type": "integer",
+                  "minimum": 0,
+                  "description": "Slots resolved at settlement by a Guard."
+                },
+                "direct_to_me_slots": {
+                  "type": "integer",
+                  "minimum": 0,
+                  "description": "Slots paying directly to this role."
+                },
+                "to_payer_slots": {
+                  "type": "integer",
+                  "minimum": 0,
+                  "description": "Slots routing back to the payer (refund-oriented)."
+                }
+              },
+              "required": [
+                "recipient_slots",
+                "guard_gated_slots",
+                "direct_to_me_slots",
+                "to_payer_slots"
+              ],
+              "additionalProperties": false,
+              "description": "Allocation waterfall — how funds split after the node advances (利益分配)."
+            },
+            "requirements": {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "description": "Persona red lines that re-anchor the role's prefer/avoid (人设驱动力)."
+            },
+            "order_amount": {
+              "type": "string",
+              "description": "Escrowed order amount (smallest-unit string) — the monetary stake at this node (数值化)."
+            },
+            "compensation_fund": {
+              "type": "string",
+              "description": "Merchant compensation_fund (smallest-unit string) — the monetary risk exposure backing indemnity."
+            },
             "operable": {
               "type": "array",
               "items": {
@@ -91,6 +174,10 @@
                   "consequence": {
                     "type": "string",
                     "description": "Consequence hint (completion/refund path)."
+                  },
+                  "weight": {
+                    "type": "number",
+                    "description": "Forward weight (accumulates toward the pair's threshold)."
                   }
                 },
                 "required": [

package/dist/schemas/index.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "WoWok MCP Schema Index",
   "description": "Index of all available JSON schemas for WoWok MCP tools",
-  "generatedAt": "2026-08-16T13:41:43.343Z",
+  "generatedAt": "2026-08-17T00:07:17.025Z",
   "tools": [
     {
       "name": "onchain_operations",

package/dist/schemas/intent_radar.output.json

@@ -30,7 +30,10 @@
                   "type": "string",
                   "enum": [
                     "merchant",
-                    "user",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ]
                 },

package/dist/schemas/intent_radar.schema.json

@@ -26,7 +26,10 @@
               "type": "string",
               "enum": [
                 "merchant",
-                "user",
+                "customer",
+                "prospect",
+                "supplier",
+                "collaborator",
                 "arbitrator"
               ]
             },

package/dist/schemas/local_info_operation.output.json

@@ -558,13 +558,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/local_mark_operation.output.json

@@ -602,13 +602,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/messenger_operation.output.json

@@ -1595,13 +1595,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/onchain_events.output.json

@@ -972,13 +972,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/onchain_operations.output.json

@@ -2368,13 +2368,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/onchain_operations.schema.json

@@ -2422,7 +2422,7 @@
                                 "number",
                                 "string"
                               ],
-                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations."
+                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations.\n⚠️ T1 LOSSY POINT (B-2): the value is PRE-CONFIGURED and STATIC. A continuous/conditional amount (e.g. 'pay exactly the assessed loss amount') CANNOT be expressed — there is no runtime formula field. Model variable payouts as (a) a fixed-tier Allocator list guarded by distinct Guards, or (b) an Amount with a `max` cap — both are finite configurations, not free-form formulas."
                             },
                             "mode": {
                               "anyOf": [
@@ -2951,7 +2951,7 @@
                         "properties": {
                           "name": {
                             "type": "string",
-                            "description": "Node name"
+                            "description": "Node name. ⚠️ T1 LOSSY POINT (B-1): do NOT name a node 'refund'/'refunded'/'disputed'/'cancelled' to model fund return or dispute — funds MUST move through the Allocation waterfall (order_allocators), NOT through Machine terminal nodes (R-M1-11). A node named 'refund' is a semantic lie: reaching it does not move funds by itself. Model refund as a refund-to-Order Allocator slot (a { Signer } or Order-owner recipient), and model dispute as the bound Arbitration, not a Machine node."
                           },
                           "pairs": {
                             "type": "array",
@@ -3059,7 +3059,7 @@
                                             "type": "null"
                                           }
                                         ],
-                                        "description": "Guard reference for this forward. Accepts TWO formats:\n• STRING (preferred): \"my_guard_name\" — the Guard's name or address as a plain string.\n• OBJECT (only when retained_submission is needed): {guard: \"my_guard_name\", retained_submission: [1,2,3]}.\nFOLLOW THE SCHEMA FIELD STRUCTURE: A Guard reference is fundamentally a STRING (the Guard object's name or address). Provide a string when you only need to reference a Guard — do NOT wrap a bare string in an object structure. The OBJECT form {guard: \"...\", retained_submission: [...]} exists ONLY to carry additional `retained_submission` data alongside the string reference; inside the object, the `guard` field is STILL a string. In short: string-in for a string reference, object-in only when you need to pass extra data.\nCOGNITIVE PRINCIPLE: Guard validation ALWAYS occurs BEFORE the forward operation. A Guard that queries state of the SAME Progress object this forward operates on (e.g. progress.current) will see the PRE-transition value (source node), NOT the target node. If the Guard checks progress.current == target_node, it will ALWAYS FAIL. Querying a DIFFERENT Progress object (cross-machine) is safe and reasonable — that progress is not modified by this forward. For target-node verification after transition, bind the Guard to the Allocator instead (allocation.alloc runs AFTER the state transition completes)."
+                                        "description": "Guard reference for this forward. Accepts TWO formats:\n• STRING (preferred): \"my_guard_name\" — the Guard's name or address as a plain string.\n• OBJECT (only when retained_submission is needed): {guard: \"my_guard_name\", retained_submission: [1,2,3]}.\nFOLLOW THE SCHEMA FIELD STRUCTURE: A Guard reference is fundamentally a STRING (the Guard object's name or address). Provide a string when you only need to reference a Guard — do NOT wrap a bare string in an object structure. The OBJECT form {guard: \"...\", retained_submission: [...]} exists ONLY to carry additional `retained_submission` data alongside the string reference; inside the object, the `guard` field is STILL a string. In short: string-in for a string reference, object-in only when you need to pass extra data.\nCOGNITIVE PRINCIPLE: Guard validation ALWAYS occurs BEFORE the forward operation. A Guard that queries state of the SAME Progress object this forward operates on (e.g. progress.current) will see the PRE-transition value (source node), NOT the target node. If the Guard checks progress.current == target_node, it will ALWAYS FAIL. Querying a DIFFERENT Progress object (cross-machine) is safe and reasonable — that progress is not modified by this forward. For target-node verification after transition, bind the Guard to the Allocator instead (allocation.alloc runs AFTER the state transition completes).\n⚠️ T1 LOSSY POINT (B-3): WoWok has NO on-chain cron. A business phrase like 'after N days, auto-X' is NOT an automatic trigger — it decomposes into (1) a time_guard that checks elapsed time, and (2) an OFF-CHAIN keeper that must submit the forward when the guard passes. Configuring a time_guard WITHOUT a keeper means nothing ever fires."
                                       }
                                     },
                                     "required": [
@@ -6724,7 +6724,7 @@
                                 "number",
                                 "string"
                               ],
-                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations."
+                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations.\n⚠️ T1 LOSSY POINT (B-2): the value is PRE-CONFIGURED and STATIC. A continuous/conditional amount (e.g. 'pay exactly the assessed loss amount') CANNOT be expressed — there is no runtime formula field. Model variable payouts as (a) a fixed-tier Allocator list guarded by distinct Guards, or (b) an Amount with a `max` cap — both are finite configurations, not free-form formulas."
                             },
                             "mode": {
                               "anyOf": [

package/dist/schemas/onchain_operations_allocation.schema.json

@@ -156,7 +156,7 @@
                                 "number",
                                 "string"
                               ],
-                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations."
+                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations.\n⚠️ T1 LOSSY POINT (B-2): the value is PRE-CONFIGURED and STATIC. A continuous/conditional amount (e.g. 'pay exactly the assessed loss amount') CANNOT be expressed — there is no runtime formula field. Model variable payouts as (a) a fixed-tier Allocator list guarded by distinct Guards, or (b) an Amount with a `max` cap — both are finite configurations, not free-form formulas."
                             },
                             "mode": {
                               "anyOf": [

package/dist/schemas/onchain_operations_machine.schema.json

@@ -279,7 +279,7 @@
                         "properties": {
                           "name": {
                             "type": "string",
-                            "description": "Node name"
+                            "description": "Node name. ⚠️ T1 LOSSY POINT (B-1): do NOT name a node 'refund'/'refunded'/'disputed'/'cancelled' to model fund return or dispute — funds MUST move through the Allocation waterfall (order_allocators), NOT through Machine terminal nodes (R-M1-11). A node named 'refund' is a semantic lie: reaching it does not move funds by itself. Model refund as a refund-to-Order Allocator slot (a { Signer } or Order-owner recipient), and model dispute as the bound Arbitration, not a Machine node."
                           },
                           "pairs": {
                             "type": "array",
@@ -387,7 +387,7 @@
                                             "type": "null"
                                           }
                                         ],
-                                        "description": "Guard reference for this forward. Accepts TWO formats:\n• STRING (preferred): \"my_guard_name\" — the Guard's name or address as a plain string.\n• OBJECT (only when retained_submission is needed): {guard: \"my_guard_name\", retained_submission: [1,2,3]}.\nFOLLOW THE SCHEMA FIELD STRUCTURE: A Guard reference is fundamentally a STRING (the Guard object's name or address). Provide a string when you only need to reference a Guard — do NOT wrap a bare string in an object structure. The OBJECT form {guard: \"...\", retained_submission: [...]} exists ONLY to carry additional `retained_submission` data alongside the string reference; inside the object, the `guard` field is STILL a string. In short: string-in for a string reference, object-in only when you need to pass extra data.\nCOGNITIVE PRINCIPLE: Guard validation ALWAYS occurs BEFORE the forward operation. A Guard that queries state of the SAME Progress object this forward operates on (e.g. progress.current) will see the PRE-transition value (source node), NOT the target node. If the Guard checks progress.current == target_node, it will ALWAYS FAIL. Querying a DIFFERENT Progress object (cross-machine) is safe and reasonable — that progress is not modified by this forward. For target-node verification after transition, bind the Guard to the Allocator instead (allocation.alloc runs AFTER the state transition completes)."
+                                        "description": "Guard reference for this forward. Accepts TWO formats:\n• STRING (preferred): \"my_guard_name\" — the Guard's name or address as a plain string.\n• OBJECT (only when retained_submission is needed): {guard: \"my_guard_name\", retained_submission: [1,2,3]}.\nFOLLOW THE SCHEMA FIELD STRUCTURE: A Guard reference is fundamentally a STRING (the Guard object's name or address). Provide a string when you only need to reference a Guard — do NOT wrap a bare string in an object structure. The OBJECT form {guard: \"...\", retained_submission: [...]} exists ONLY to carry additional `retained_submission` data alongside the string reference; inside the object, the `guard` field is STILL a string. In short: string-in for a string reference, object-in only when you need to pass extra data.\nCOGNITIVE PRINCIPLE: Guard validation ALWAYS occurs BEFORE the forward operation. A Guard that queries state of the SAME Progress object this forward operates on (e.g. progress.current) will see the PRE-transition value (source node), NOT the target node. If the Guard checks progress.current == target_node, it will ALWAYS FAIL. Querying a DIFFERENT Progress object (cross-machine) is safe and reasonable — that progress is not modified by this forward. For target-node verification after transition, bind the Guard to the Allocator instead (allocation.alloc runs AFTER the state transition completes).\n⚠️ T1 LOSSY POINT (B-3): WoWok has NO on-chain cron. A business phrase like 'after N days, auto-X' is NOT an automatic trigger — it decomposes into (1) a time_guard that checks elapsed time, and (2) an OFF-CHAIN keeper that must submit the forward when the guard passes. Configuring a time_guard WITHOUT a keeper means nothing ever fires."
                                       }
                                     },
                                     "required": [

package/dist/schemas/onchain_operations_service.schema.json

@@ -659,7 +659,7 @@
                                 "number",
                                 "string"
                               ],
-                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations."
+                              "description": "Allocation value. SEMANTICS DEPEND ON `mode`:\n• mode='Amount': absolute amount in smallest unit (e.g., '750000000' for 0.75 WOW, '250000000' for 0.25 WOW). Allocated first; sum of Amount items cached as `fix`.\n• mode='Rate': basis-points rate, 10000 = 100% (e.g., '7500' for 75%, '2500' for 25%). When no Surplus in same Allocator, sum MUST == 10000; when Surplus present, sum MUST <= 10000.\n• mode='Surplus': IGNORED (contract forces to 0). Set to '0' for clarity. Receives remaining balance after Amount + Rate allocations.\n⚠️ T1 LOSSY POINT (B-2): the value is PRE-CONFIGURED and STATIC. A continuous/conditional amount (e.g. 'pay exactly the assessed loss amount') CANNOT be expressed — there is no runtime formula field. Model variable payouts as (a) a fixed-tier Allocator list guarded by distinct Guards, or (b) an Amount with a `max` cap — both are finite configurations, not free-form formulas."
                             },
                             "mode": {
                               "anyOf": [

package/dist/schemas/onchain_table_data.output.json

@@ -1681,7 +1681,7 @@
                                           "type": "null"
                                         }
                                       ],
-                                      "description": "Guard reference for this forward. Accepts TWO formats:\n• STRING (preferred): \"my_guard_name\" — the Guard's name or address as a plain string.\n• OBJECT (only when retained_submission is needed): {guard: \"my_guard_name\", retained_submission: [1,2,3]}.\nFOLLOW THE SCHEMA FIELD STRUCTURE: A Guard reference is fundamentally a STRING (the Guard object's name or address). Provide a string when you only need to reference a Guard — do NOT wrap a bare string in an object structure. The OBJECT form {guard: \"...\", retained_submission: [...]} exists ONLY to carry additional `retained_submission` data alongside the string reference; inside the object, the `guard` field is STILL a string. In short: string-in for a string reference, object-in only when you need to pass extra data.\nCOGNITIVE PRINCIPLE: Guard validation ALWAYS occurs BEFORE the forward operation. A Guard that queries state of the SAME Progress object this forward operates on (e.g. progress.current) will see the PRE-transition value (source node), NOT the target node. If the Guard checks progress.current == target_node, it will ALWAYS FAIL. Querying a DIFFERENT Progress object (cross-machine) is safe and reasonable — that progress is not modified by this forward. For target-node verification after transition, bind the Guard to the Allocator instead (allocation.alloc runs AFTER the state transition completes)."
+                                      "description": "Guard reference for this forward. Accepts TWO formats:\n• STRING (preferred): \"my_guard_name\" — the Guard's name or address as a plain string.\n• OBJECT (only when retained_submission is needed): {guard: \"my_guard_name\", retained_submission: [1,2,3]}.\nFOLLOW THE SCHEMA FIELD STRUCTURE: A Guard reference is fundamentally a STRING (the Guard object's name or address). Provide a string when you only need to reference a Guard — do NOT wrap a bare string in an object structure. The OBJECT form {guard: \"...\", retained_submission: [...]} exists ONLY to carry additional `retained_submission` data alongside the string reference; inside the object, the `guard` field is STILL a string. In short: string-in for a string reference, object-in only when you need to pass extra data.\nCOGNITIVE PRINCIPLE: Guard validation ALWAYS occurs BEFORE the forward operation. A Guard that queries state of the SAME Progress object this forward operates on (e.g. progress.current) will see the PRE-transition value (source node), NOT the target node. If the Guard checks progress.current == target_node, it will ALWAYS FAIL. Querying a DIFFERENT Progress object (cross-machine) is safe and reasonable — that progress is not modified by this forward. For target-node verification after transition, bind the Guard to the Allocator instead (allocation.alloc runs AFTER the state transition completes).\n⚠️ T1 LOSSY POINT (B-3): WoWok has NO on-chain cron. A business phrase like 'after N days, auto-X' is NOT an automatic trigger — it decomposes into (1) a time_guard that checks elapsed time, and (2) an OFF-CHAIN keeper that must submit the forward when the guard passes. Configuring a time_guard WITHOUT a keeper means nothing ever fires."
                                     }
                                   },
                                   "required": [
@@ -2550,13 +2550,16 @@
                   "items": {
                     "type": "string"
                   },
-                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (user/merchant/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
+                  "description": "Phase 4 P4-6.C: Role-targeted advice strings (merchant/customer/prospect/supplier/collaborator/arbitrator). Example: ['Strengthen loyalty flywheel','Optimize first-order conversion']"
                 },
                 "role": {
                   "type": "string",
                   "enum": [
-                    "user",
                     "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ],
                   "description": "Phase 4 P4-6.C: Role used for advice routing. Example: 'merchant'"

package/dist/schemas/persona_operation.output.json

@@ -31,7 +31,10 @@
                   "type": "string",
                   "enum": [
                     "merchant",
-                    "user",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
                     "arbitrator"
                   ]
                 },

package/dist/schemas/persona_operation.schema.json

@@ -33,7 +33,10 @@
               "type": "string",
               "enum": [
                 "merchant",
-                "user",
+                "customer",
+                "prospect",
+                "supplier",
+                "collaborator",
                 "arbitrator"
               ]
             }