@wowok/agent-mcp 2.7.0 → 2.7.2

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-16T01:21:38.688Z",
+  "generatedAt": "2026-08-17T00:07:17.025Z",
   "tools": [
     {
       "name": "onchain_operations",
@@ -105,6 +105,30 @@
       "title": "Trust Score - Service Risk & Trust Assessment",
       "path": "./trust_score.schema.json",
       "outputPath": "./trust_score.output.json"
+    },
+    {
+      "name": "query_task_status",
+      "title": "Task Status - Async Operation Tracking",
+      "path": "./query_task_status.schema.json",
+      "outputPath": "./query_task_status.output.json"
+    },
+    {
+      "name": "evaluation_operation",
+      "title": "Evaluation - Pluggable Business Intelligence",
+      "path": "./evaluation_operation.schema.json",
+      "outputPath": "./evaluation_operation.output.json"
+    },
+    {
+      "name": "persona_operation",
+      "title": "Persona - User Identity Setting",
+      "path": "./persona_operation.schema.json",
+      "outputPath": "./persona_operation.output.json"
+    },
+    {
+      "name": "intent_radar",
+      "title": "Intent Radar - User Intent × Chain Event Matching",
+      "path": "./intent_radar.schema.json",
+      "outputPath": "./intent_radar.output.json"
     }
   ],
   "operations": [

package/dist/schemas/intent_radar.output.json

@@ -0,0 +1,232 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://wowok.net/schemas/intent_radar.json",
+  "title": "Intent Radar - User Intent × Chain Event Matching",
+  "description": "Persist the user's standing business intents and match them against on-chain events/data. Actions: save (record an intent), list, remove, match (score events).",
+  "$ref": "#/definitions/intent_radar",
+  "definitions": {
+    "intent_radar": {
+      "anyOf": [
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "save"
+            },
+            "intent": {
+              "type": "object",
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "intent": {
+                  "type": "string"
+                },
+                "account": {
+                  "type": "string"
+                },
+                "role": {
+                  "type": "string",
+                  "enum": [
+                    "merchant",
+                    "customer",
+                    "prospect",
+                    "supplier",
+                    "collaborator",
+                    "arbitrator"
+                  ]
+                },
+                "industries": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "enum": [
+                      "freelance",
+                      "rental",
+                      "education",
+                      "travel",
+                      "subscription",
+                      "retail",
+                      "general",
+                      "custom"
+                    ]
+                  }
+                },
+                "keywords": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  }
+                },
+                "target_types": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "enum": [
+                      "NewOrderEvent",
+                      "ProgressEvent",
+                      "DemandPresentEvent",
+                      "DemandFeedbackEvent",
+                      "NewEntityEvent",
+                      "ArbEvent"
+                    ]
+                  }
+                },
+                "created_at": {
+                  "type": "number"
+                },
+                "updated_at": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "id",
+                "intent",
+                "industries",
+                "keywords",
+                "target_types",
+                "created_at",
+                "updated_at"
+              ],
+              "additionalProperties": false
+            }
+          },
+          "required": [
+            "action",
+            "intent"
+          ],
+          "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "list"
+            },
+            "intents": {
+              "type": "array",
+              "items": {
+                "$ref": "#/definitions/intent_radar/anyOf/0/properties/intent"
+              }
+            }
+          },
+          "required": [
+            "action",
+            "intents"
+          ],
+          "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "remove"
+            },
+            "removed": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "action",
+            "removed"
+          ],
+          "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "match"
+            },
+            "results": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "intent_id": {
+                    "type": "string"
+                  },
+                  "intent": {
+                    "type": "string"
+                  },
+                  "hits": {
+                    "type": "array",
+                    "items": {
+                      "type": "object",
+                      "properties": {
+                        "event_type": {
+                          "type": "string"
+                        },
+                        "event_id": {
+                          "type": "string"
+                        },
+                        "related_objects": {
+                          "type": "array",
+                          "items": {
+                            "type": "string"
+                          }
+                        },
+                        "business_meaning": {
+                          "type": "string"
+                        },
+                        "score": {
+                          "type": "number"
+                        },
+                        "matched_industries": {
+                          "type": "array",
+                          "items": {
+                            "type": "string"
+                          }
+                        },
+                        "matched_keywords": {
+                          "type": "array",
+                          "items": {
+                            "type": "string"
+                          }
+                        },
+                        "event": {
+                          "type": "object",
+                          "additionalProperties": {}
+                        }
+                      },
+                      "required": [
+                        "event_type",
+                        "event_id",
+                        "related_objects",
+                        "business_meaning",
+                        "score",
+                        "matched_industries",
+                        "matched_keywords",
+                        "event"
+                      ],
+                      "additionalProperties": false
+                    }
+                  },
+                  "scanned": {
+                    "type": "number"
+                  }
+                },
+                "required": [
+                  "intent_id",
+                  "intent",
+                  "hits",
+                  "scanned"
+                ],
+                "additionalProperties": false
+              }
+            }
+          },
+          "required": [
+            "action",
+            "results"
+          ],
+          "additionalProperties": false
+        }
+      ]
+    }
+  }
+}

package/dist/schemas/intent_radar.schema.json

@@ -0,0 +1,138 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://wowok.net/schemas/intent_radar.json",
+  "title": "Intent Radar - User Intent × Chain Event Matching",
+  "description": "Persist the user's standing business intents and match them against on-chain events/data. Actions: save (record an intent), list, remove, match (score events).",
+  "$ref": "#/definitions/intent_radar",
+  "definitions": {
+    "intent_radar": {
+      "anyOf": [
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "save"
+            },
+            "intent": {
+              "type": "string",
+              "description": "Free-form business intent, e.g. 'find subscription services in Shanghai'."
+            },
+            "account": {
+              "type": "string",
+              "description": "Bound account; omit for a system-level intent."
+            },
+            "role": {
+              "type": "string",
+              "enum": [
+                "merchant",
+                "customer",
+                "prospect",
+                "supplier",
+                "collaborator",
+                "arbitrator"
+              ]
+            },
+            "target_types": {
+              "type": "array",
+              "items": {
+                "type": "string",
+                "enum": [
+                  "NewOrderEvent",
+                  "ProgressEvent",
+                  "DemandPresentEvent",
+                  "DemandFeedbackEvent",
+                  "NewEntityEvent",
+                  "ArbEvent"
+                ]
+              },
+              "description": "Event types to watch; empty = all."
+            }
+          },
+          "required": [
+            "action",
+            "intent"
+          ],
+          "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "list"
+            },
+            "account": {
+              "type": "string",
+              "description": "Filter by bound account; omit for all."
+            }
+          },
+          "required": [
+            "action"
+          ],
+          "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "remove"
+            },
+            "id": {
+              "type": "string",
+              "description": "Intent id to delete."
+            }
+          },
+          "required": [
+            "action",
+            "id"
+          ],
+          "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "const": "match"
+            },
+            "intent_id": {
+              "type": "string",
+              "description": "Match a single intent; omit to match all intents."
+            },
+            "account": {
+              "type": "string",
+              "description": "Filter intents by account."
+            },
+            "events": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "additionalProperties": {}
+              },
+              "description": "Events to score (from onchain_events). Omit to auto-pull recent events."
+            },
+            "network": {
+              "type": "string",
+              "enum": [
+                "mainnet",
+                "testnet"
+              ]
+            },
+            "limit": {
+              "type": "integer",
+              "minimum": 1,
+              "maximum": 100,
+              "description": "Max events to auto-pull when `events` is omitted."
+            }
+          },
+          "required": [
+            "action"
+          ],
+          "additionalProperties": false
+        }
+      ]
+    }
+  }
+}

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

@@ -2074,7 +2074,7 @@
                       },
                       "wip": {
                         "type": "string",
-                        "description": "WIP file URL. EMPTY string \"\" skips verification (TESTING ONLY). Production MUST use a real HTTP URL pointing to a .wip file generated by the wip_file tool. Example: \"https://cdn.example.com/products/phone_v1.wip\""
+                        "description": "WIP file URL. EMPTY string \"\" skips verification (TESTING ONLY). Production MUST use a real HTTP URL pointing to a .wip file generated by the wip_file tool. ⚠️ NETWORK DEPLOYMENT REQUIRED: the URL is stored ON-CHAIN and every customer fetches it when placing an order. A local file path (C:\\..., /path/file.wip), a localhost/loopback URL or a LAN private-IP URL is unreachable by customers on other machines — it passes the merchant-side set-time verification but makes order_new abort 100% for customers. Either deploy the .wip file to a public endpoint (GitHub Pages / IPFS / your own website) and set this to the public URL, or leave it empty (\"\") to skip WIP verification (TESTING ONLY). Example: \"https://cdn.example.com/products/phone_v1.wip\""
                       },
                       "wip_hash": {
                         "type": "string",
@@ -2159,7 +2159,7 @@
               "description": "Clear all sales products or services."
             }
           ],
-          "description": "Service sales products or services list."
+          "description": "Service sales products or services list. ⚠️ WIP NETWORK-DEPLOYMENT RULE: a non-empty sale.wip MUST be a publicly reachable URL (GitHub Pages / IPFS / your own website). The URL is stored ON-CHAIN and every customer fetches it at order time — a local file path, localhost/loopback URL, or LAN private-IP URL is unreachable by customers on other machines and aborts order_new 100%. Local-network URLs are INTERNAL TEST USE ONLY (env.network = localnet). Leave sale.wip empty (\"\") to skip WIP verification (TESTING ONLY)."
         },
         "repositories": {
           "anyOf": [
@@ -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

@@ -311,7 +311,7 @@
                       },
                       "wip": {
                         "type": "string",
-                        "description": "WIP file URL. EMPTY string \"\" skips verification (TESTING ONLY). Production MUST use a real HTTP URL pointing to a .wip file generated by the wip_file tool. Example: \"https://cdn.example.com/products/phone_v1.wip\""
+                        "description": "WIP file URL. EMPTY string \"\" skips verification (TESTING ONLY). Production MUST use a real HTTP URL pointing to a .wip file generated by the wip_file tool. ⚠️ NETWORK DEPLOYMENT REQUIRED: the URL is stored ON-CHAIN and every customer fetches it when placing an order. A local file path (C:\\..., /path/file.wip), a localhost/loopback URL or a LAN private-IP URL is unreachable by customers on other machines — it passes the merchant-side set-time verification but makes order_new abort 100% for customers. Either deploy the .wip file to a public endpoint (GitHub Pages / IPFS / your own website) and set this to the public URL, or leave it empty (\"\") to skip WIP verification (TESTING ONLY). Example: \"https://cdn.example.com/products/phone_v1.wip\""
                       },
                       "wip_hash": {
                         "type": "string",
@@ -396,7 +396,7 @@
               "description": "Clear all sales products or services."
             }
           ],
-          "description": "Service sales products or services list."
+          "description": "Service sales products or services list. ⚠️ WIP NETWORK-DEPLOYMENT RULE: a non-empty sale.wip MUST be a publicly reachable URL (GitHub Pages / IPFS / your own website). The URL is stored ON-CHAIN and every customer fetches it at order time — a local file path, localhost/loopback URL, or LAN private-IP URL is unreachable by customers on other machines and aborts order_new 100%. Local-network URLs are INTERNAL TEST USE ONLY (env.network = localnet). Leave sale.wip empty (\"\") to skip WIP verification (TESTING ONLY)."
         },
         "repositories": {
           "anyOf": [
@@ -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": [