@wowok/agent-mcp 2.7.2 → 2.7.4

package/dist/schemas/onchain_operations_service.schema.json

@@ -2,30 +2,13 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://wowok.net/schemas/onchain_operations_service.json",
   "title": "Service Operation",
-  "description": "On-chain service operation schema",
+  "description": "🏪 Service Object: Create and manage product/service listings with transparent promises, bind workflow templates to order processing, set pricing, issue discount coupons to customers, and establish quality standards, etc..",
   "type": "object",
   "properties": {
     "operation_type": {
+      "type": "string",
       "const": "service"
     },
-    "data": {
-      "$ref": "#/definitions/data",
-      "$schema": "http://json-schema.org/draft-07/schema#"
-    },
-    "env": {
-      "$ref": "#/definitions/env",
-      "$schema": "http://json-schema.org/draft-07/schema#"
-    },
-    "submission": {
-      "$ref": "#/definitions/submission",
-      "$schema": "http://json-schema.org/draft-07/schema#"
-    }
-  },
-  "required": [
-    "operation_type",
-    "data"
-  ],
-  "definitions": {
     "data": {
       "type": "object",
       "properties": {
@@ -39,48 +22,55 @@
               "type": "object",
               "properties": {
                 "name": {
-                  "type": "string",
-                  "description": "The name of the object"
+                  "description": "The name of the object",
+                  "type": "string"
                 },
                 "tags": {
+                  "description": "The tags of the object",
                   "type": "array",
                   "items": {
                     "type": "string"
-                  },
-                  "description": "The tags of the object"
+                  }
                 },
                 "onChain": {
-                  "type": "boolean",
-                  "description": "CRITICAL: Whether to sync the name to the blockchain. DEFAULT (undefined/false): The name is stored LOCALLY ONLY on your device (PRIVATE). If set to true: The name is published ON-CHAIN and becomes PUBLICLY VISIBLE to everyone. Only set to true for displaying the relationships you are willing to make public on the chain."
+                  "description": "CRITICAL: Whether to sync the name to the blockchain. DEFAULT (undefined/false): The name is stored LOCALLY ONLY on your device (PRIVATE). If set to true: The name is published ON-CHAIN and becomes PUBLICLY VISIBLE to everyone. Only set to true for displaying the relationships you are willing to make public on the chain.",
+                  "type": "boolean"
                 },
                 "replaceExistName": {
-                  "type": "boolean",
-                  "description": "FORCE CLAIM: Set to true ONLY when the user explicitly expresses a STRONG INTENTION to forcefully take over an existing name (e.g., 'I must use this name', 'force rename', 'replace the existing one'). WARNING: This will UNBIND the name from its original object and rebind it to the new one, potentially breaking existing references. If not specified or false: the operation will FAIL with an error when the name is already in use (safe default behavior)."
+                  "description": "FORCE CLAIM: Set to true ONLY when the user explicitly expresses a STRONG INTENTION to forcefully take over an existing name (e.g., 'I must use this name', 'force rename', 'replace the existing one'). WARNING: This will UNBIND the name from its original object and rebind it to the new one, potentially breaking existing references. If not specified or false: the operation will FAIL with an error when the name is already in use (safe default behavior).",
+                  "type": "boolean"
                 },
                 "permission": {
                   "anyOf": [
                     {
-                      "$ref": "#/definitions/data/properties/object/anyOf/0",
+                      "type": "string",
                       "description": "String format: Reference an EXISTING object by its name (local mark) or on-chain object ID. Example: 'my-object' or '0x1234...'"
                     },
                     {
                       "type": "object",
                       "properties": {
                         "name": {
-                          "$ref": "#/definitions/data/properties/object/anyOf/1/properties/name"
+                          "description": "The name of the object",
+                          "type": "string"
                         },
                         "tags": {
-                          "$ref": "#/definitions/data/properties/object/anyOf/1/properties/tags"
+                          "description": "The tags of the object",
+                          "type": "array",
+                          "items": {
+                            "type": "string"
+                          }
                         },
                         "onChain": {
-                          "$ref": "#/definitions/data/properties/object/anyOf/1/properties/onChain"
+                          "description": "CRITICAL: Whether to sync the name to the blockchain. DEFAULT (undefined/false): The name is stored LOCALLY ONLY on your device (PRIVATE). If set to true: The name is published ON-CHAIN and becomes PUBLICLY VISIBLE to everyone. Only set to true for displaying the relationships you are willing to make public on the chain.",
+                          "type": "boolean"
                         },
                         "replaceExistName": {
-                          "$ref": "#/definitions/data/properties/object/anyOf/1/properties/replaceExistName"
+                          "description": "FORCE CLAIM: Set to true ONLY when the user explicitly expresses a STRONG INTENTION to forcefully take over an existing name (e.g., 'I must use this name', 'force rename', 'replace the existing one'). WARNING: This will UNBIND the name from its original object and rebind it to the new one, potentially breaking existing references. If not specified or false: the operation will FAIL with an error when the name is already in use (safe default behavior).",
+                          "type": "boolean"
                         },
                         "description": {
-                          "type": "string",
-                          "description": "The description of the object"
+                          "description": "The description of the object",
+                          "type": "string"
                         }
                       },
                       "additionalProperties": false,
@@ -90,11 +80,14 @@
                   "description": "Two ways to specify an object: (1) STRING - Reference an EXISTING object by name or ID; (2) OBJECT - CREATE a NEW object with full configuration including optional name, tags, description, and visibility settings (local private by default, or public on-chain with onChain:true)."
                 },
                 "type_parameter": {
-                  "type": "string",
+                  "default": "0x2::wow::WOW",
                   "description": "Payment token type for this object (format: {address}::{module}::{struct}). e.g. '0x2::wow::WOW' (WOW, the default), '0x...::usdt::USDT' (USDT), '0x...::eth::ETH' (ETH). Defines which token this object accepts for payments. To discover all available tokens and their type tags, call wowok_buildin_info with info 'mainnet bridge tokens' and use the returned `wowTypeTag` value here.",
-                  "default": "0x2::wow::WOW"
+                  "type": "string"
                 }
               },
+              "required": [
+                "type_parameter"
+              ],
               "additionalProperties": false,
               "description": "Object format: CREATE a NEW object with COMPLETE configuration including: optional name, tags, description, token type for payments (e.g., '0x2::wow::WOW'), AND Permission-based access control. Use this for creating sophisticated objects with both payment token specification and permission management."
             }
@@ -102,6 +95,7 @@
           "description": "Two ways to specify an object: (1) STRING - Reference an EXISTING object by name or ID; (2) OBJECT - CREATE a NEW object with full configuration including name, tags, description, token type for payments, and Permission-based access control. The object format is used when you need both token specification AND permission management."
         },
         "order_new": {
+          "description": "Create new order.",
           "type": "object",
           "properties": {
             "buy": {
@@ -117,9 +111,13 @@
                         "description": "Name of the product or service to purchase"
                       },
                       "stock": {
-                        "type": [
-                          "number",
-                          "string"
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
                         ],
                         "description": "Quantity of the product or service to purchase"
                       },
@@ -143,9 +141,13 @@
                       "type": "object",
                       "properties": {
                         "balance": {
-                          "type": [
-                            "number",
-                            "string"
+                          "anyOf": [
+                            {
+                              "type": "number"
+                            },
+                            {
+                              "type": "string"
+                            }
                           ],
                           "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                         }
@@ -173,16 +175,16 @@
                   "description": "Actual payment amount. FORMAT: {balance: <amount_in_smallest_unit>} or {coin: <coin_object_id>}. The token type and precision are determined by the Service object's type_parameter (the generic type set when the Service was created). For WOW (9 decimals): {balance: 1000000000} = 1 WOW. For SUI (9 decimals): {balance: 1000000000} = 1 SUI."
                 },
                 "discount": {
-                  "type": "string",
-                  "description": "Discount object ID or name"
+                  "description": "Discount object ID or name",
+                  "type": "string"
                 },
                 "payment_remark": {
-                  "type": "string",
-                  "description": "Payment remark"
+                  "description": "Payment remark",
+                  "type": "string"
                 },
                 "payment_index": {
-                  "type": "number",
-                  "description": "Payment index"
+                  "description": "Payment index",
+                  "type": "number"
                 }
               },
               "required": [
@@ -192,6 +194,7 @@
               "additionalProperties": false
             },
             "agents": {
+              "description": "Order agents. Agents can operate the order, such as canceling the order, modifying the order status, etc.; but cannot receive the funds received by the order.",
               "type": "object",
               "properties": {
                 "entities": {
@@ -200,12 +203,12 @@
                     "type": "object",
                     "properties": {
                       "name_or_address": {
-                        "$ref": "#/definitions/data/properties/object/anyOf/0",
+                        "type": "string",
                         "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
                       },
                       "local_mark_first": {
-                        "type": "boolean",
-                        "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks"
+                        "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                        "type": "boolean"
                       }
                     },
                     "additionalProperties": false,
@@ -213,68 +216,129 @@
                   }
                 },
                 "check_all_founded": {
-                  "type": "boolean",
-                  "description": "Whether to check all entities are found, if true, all entities must be found (abort and throw exception if any ID not found); if false, only return found IDs"
+                  "description": "Whether to check all entities are found, if true, all entities must be found (abort and throw exception if any ID not found); if false, only return found IDs",
+                  "type": "boolean"
                 }
               },
               "required": [
                 "entities"
               ],
-              "additionalProperties": false,
-              "description": "Order agents. Agents can operate the order, such as canceling the order, modifying the order status, etc.; but cannot receive the funds received by the order."
+              "additionalProperties": false
             },
             "order_required_info": {
-              "type": "string",
-              "description": "Contact object ID or WTS Proof object, recorded on the Order as proof that the order holder delivered the required private information (service.customer_required) to the merchant. FLOW: when a Service declares customer_required (e.g. phone/email/shipping_address), the order holder MUST send that private information to the Service's Contact (um) via end-to-end encrypted Messenger, then pass the Contact object ID or the generated WTS Proof here so the delivery is verifiable on-chain."
+              "description": "Contact object ID or WTS Proof object, recorded on the Order as proof that the order holder delivered the required private information (service.customer_required) to the merchant. FLOW: when a Service declares customer_required (e.g. phone/email/shipping_address), the order holder MUST send that private information to the Service's Contact (um) via end-to-end encrypted Messenger, then pass the Contact object ID or the generated WTS Proof here so the delivery is verifiable on-chain.",
+              "type": "string"
             },
             "transfer": {
-              "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items",
-              "description": "Set the new owner of the order. Requires order owner permission to set."
+              "description": "Set the new owner of the order. Requires order owner permission to set.",
+              "type": "object",
+              "properties": {
+                "name_or_address": {
+                  "type": "string",
+                  "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                },
+                "local_mark_first": {
+                  "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                  "type": "boolean"
+                }
+              },
+              "additionalProperties": false
             },
             "namedNewOrder": {
+              "description": "RECOMMENDED: Set a local name for the newly created Order object. Without this, the Order is only referenceable by its on-chain address. Example: {name: 'my_order_v1'} allows subsequent operations to use 'my_order_v1' instead of the address.",
               "type": "object",
               "properties": {
                 "name": {
-                  "$ref": "#/definitions/data/properties/object/anyOf/1/properties/name"
+                  "description": "The name of the object",
+                  "type": "string"
                 },
                 "tags": {
-                  "$ref": "#/definitions/data/properties/object/anyOf/1/properties/tags"
+                  "description": "The tags of the object",
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  }
                 },
                 "onChain": {
-                  "$ref": "#/definitions/data/properties/object/anyOf/1/properties/onChain"
+                  "description": "CRITICAL: Whether to sync the name to the blockchain. DEFAULT (undefined/false): The name is stored LOCALLY ONLY on your device (PRIVATE). If set to true: The name is published ON-CHAIN and becomes PUBLICLY VISIBLE to everyone. Only set to true for displaying the relationships you are willing to make public on the chain.",
+                  "type": "boolean"
                 },
                 "replaceExistName": {
-                  "$ref": "#/definitions/data/properties/object/anyOf/1/properties/replaceExistName"
+                  "description": "FORCE CLAIM: Set to true ONLY when the user explicitly expresses a STRONG INTENTION to forcefully take over an existing name (e.g., 'I must use this name', 'force rename', 'replace the existing one'). WARNING: This will UNBIND the name from its original object and rebind it to the new one, potentially breaking existing references. If not specified or false: the operation will FAIL with an error when the name is already in use (safe default behavior).",
+                  "type": "boolean"
                 }
               },
-              "additionalProperties": false,
-              "description": "RECOMMENDED: Set a local name for the newly created Order object. Without this, the Order is only referenceable by its on-chain address. Example: {name: 'my_order_v1'} allows subsequent operations to use 'my_order_v1' instead of the address."
+              "additionalProperties": false
             },
             "namedNewAllocation": {
-              "$ref": "#/definitions/data/properties/order_new/properties/namedNewOrder",
-              "description": "RECOMMENDED: Set a local name for the order's Allocation object. Without this, the Allocation is only referenceable by its address. Example: {name: 'my_allocation_v1'} allows alloc_by_guard to reference 'my_allocation_v1'."
+              "description": "RECOMMENDED: Set a local name for the order's Allocation object. Without this, the Allocation is only referenceable by its address. Example: {name: 'my_allocation_v1'} allows alloc_by_guard to reference 'my_allocation_v1'.",
+              "type": "object",
+              "properties": {
+                "name": {
+                  "description": "The name of the object",
+                  "type": "string"
+                },
+                "tags": {
+                  "description": "The tags of the object",
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  }
+                },
+                "onChain": {
+                  "description": "CRITICAL: Whether to sync the name to the blockchain. DEFAULT (undefined/false): The name is stored LOCALLY ONLY on your device (PRIVATE). If set to true: The name is published ON-CHAIN and becomes PUBLICLY VISIBLE to everyone. Only set to true for displaying the relationships you are willing to make public on the chain.",
+                  "type": "boolean"
+                },
+                "replaceExistName": {
+                  "description": "FORCE CLAIM: Set to true ONLY when the user explicitly expresses a STRONG INTENTION to forcefully take over an existing name (e.g., 'I must use this name', 'force rename', 'replace the existing one'). WARNING: This will UNBIND the name from its original object and rebind it to the new one, potentially breaking existing references. If not specified or false: the operation will FAIL with an error when the name is already in use (safe default behavior).",
+                  "type": "boolean"
+                }
+              },
+              "additionalProperties": false
             },
             "namedNewProgress": {
-              "$ref": "#/definitions/data/properties/order_new/properties/namedNewOrder",
-              "description": "RECOMMENDED: Set a local name for the order's Progress object. Without this, the Progress is only referenceable by its address. Example: {name: 'my_progress_v1'} allows progress operations to use 'my_progress_v1'."
+              "description": "RECOMMENDED: Set a local name for the order's Progress object. Without this, the Progress is only referenceable by its address. Example: {name: 'my_progress_v1'} allows progress operations to use 'my_progress_v1'.",
+              "type": "object",
+              "properties": {
+                "name": {
+                  "description": "The name of the object",
+                  "type": "string"
+                },
+                "tags": {
+                  "description": "The tags of the object",
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  }
+                },
+                "onChain": {
+                  "description": "CRITICAL: Whether to sync the name to the blockchain. DEFAULT (undefined/false): The name is stored LOCALLY ONLY on your device (PRIVATE). If set to true: The name is published ON-CHAIN and becomes PUBLICLY VISIBLE to everyone. Only set to true for displaying the relationships you are willing to make public on the chain.",
+                  "type": "boolean"
+                },
+                "replaceExistName": {
+                  "description": "FORCE CLAIM: Set to true ONLY when the user explicitly expresses a STRONG INTENTION to forcefully take over an existing name (e.g., 'I must use this name', 'force rename', 'replace the existing one'). WARNING: This will UNBIND the name from its original object and rebind it to the new one, potentially breaking existing references. If not specified or false: the operation will FAIL with an error when the name is already in use (safe default behavior).",
+                  "type": "boolean"
+                }
+              },
+              "additionalProperties": false
             }
           },
           "required": [
             "buy"
           ],
-          "additionalProperties": false,
-          "description": "Create new order."
+          "additionalProperties": false
         },
         "description": {
           "type": "string",
           "description": "Description string (max 4000 bcs characters)"
         },
         "location": {
-          "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/items/items/properties/name",
-          "description": "Location of the Service"
+          "description": "Location of the Service",
+          "type": "string"
         },
         "sales": {
-          "anyOf": [
+          "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).",
+          "oneOf": [
             {
               "type": "object",
               "properties": {
@@ -288,20 +352,28 @@
                     "type": "object",
                     "properties": {
                       "name": {
-                        "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/items/items/properties/name",
+                        "type": "string",
                         "description": "Name of the product or service for sale"
                       },
                       "price": {
-                        "type": [
-                          "number",
-                          "string"
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
                         ],
                         "description": "Price of the product or service"
                       },
                       "stock": {
-                        "type": [
-                          "number",
-                          "string"
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
                         ],
                         "description": "Stock of the product or service"
                       },
@@ -348,7 +420,57 @@
                 "sales": {
                   "type": "array",
                   "items": {
-                    "$ref": "#/definitions/data/properties/sales/anyOf/0/properties/sales/items"
+                    "type": "object",
+                    "properties": {
+                      "name": {
+                        "type": "string",
+                        "description": "Name of the product or service for sale"
+                      },
+                      "price": {
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
+                        ],
+                        "description": "Price of the product or service"
+                      },
+                      "stock": {
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
+                        ],
+                        "description": "Stock of the product or service"
+                      },
+                      "suspension": {
+                        "type": "boolean",
+                        "description": "Whether sale is suspended"
+                      },
+                      "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. ⚠️ 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",
+                        "description": "SHA-256 hash (hex string) of the sale's WIP file, committed on-chain by the merchant. BUY RULE: if this is NON-EMPTY, the buyer MUST pass this exact value as wip_hash when creating an order (ServiceBuyItem.wip_hash) — NEVER use \"\". Pinning the on-chain hash prevents the merchant from replacing the WIP file (a legitimate update) between the buyer's view and order placement, ensuring 'what you see is what you get'. EMPTY means no hash was committed (TESTING ONLY, no delivery-integrity guarantee)."
+                      }
+                    },
+                    "required": [
+                      "name",
+                      "price",
+                      "stock",
+                      "suspension",
+                      "wip",
+                      "wip_hash"
+                    ],
+                    "additionalProperties": false,
+                    "description": "Service sale"
                   }
                 }
               },
@@ -369,7 +491,7 @@
                 "sales_name": {
                   "type": "array",
                   "items": {
-                    "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/items/items/properties/name",
+                    "type": "string",
                     "description": "Sales name"
                   }
                 }
@@ -395,25 +517,31 @@
               "additionalProperties": false,
               "description": "Clear all sales products or services."
             }
-          ],
-          "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": {
+          "description": "Service Repository object list.",
           "anyOf": [
             {
               "type": "object",
               "properties": {
                 "op": {
-                  "type": "string",
-                  "enum": [
-                    "add",
-                    "set"
+                  "anyOf": [
+                    {
+                      "type": "string",
+                      "const": "add"
+                    },
+                    {
+                      "type": "string",
+                      "const": "set"
+                    }
                   ]
                 },
                 "objects": {
                   "type": "array",
                   "items": {
-                    "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/name_or_address"
+                    "type": "string",
+                    "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
                   },
                   "description": "List of object IDs or names to add or set"
                 }
@@ -434,7 +562,8 @@
                 "objects": {
                   "type": "array",
                   "items": {
-                    "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/name_or_address"
+                    "type": "string",
+                    "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
                   },
                   "description": "List of object IDs or names to remove"
                 }
@@ -458,29 +587,162 @@
               ],
               "additionalProperties": false
             }
-          ],
-          "description": "Service Repository object list."
+          ]
         },
         "rewards": {
-          "$ref": "#/definitions/data/properties/repositories",
-          "description": "Service Reward object list. May share the Service's Permission (no conflict check — intentional: rewards are the provider's own incentive tool; only Arbitration requires a different Permission for neutrality)."
+          "description": "Service Reward object list. May share the Service's Permission (no conflict check — intentional: rewards are the provider's own incentive tool; only Arbitration requires a different Permission for neutrality).",
+          "anyOf": [
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "anyOf": [
+                    {
+                      "type": "string",
+                      "const": "add"
+                    },
+                    {
+                      "type": "string",
+                      "const": "set"
+                    }
+                  ]
+                },
+                "objects": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                  },
+                  "description": "List of object IDs or names to add or set"
+                }
+              },
+              "required": [
+                "op",
+                "objects"
+              ],
+              "additionalProperties": false
+            },
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "type": "string",
+                  "const": "remove"
+                },
+                "objects": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                  },
+                  "description": "List of object IDs or names to remove"
+                }
+              },
+              "required": [
+                "op",
+                "objects"
+              ],
+              "additionalProperties": false
+            },
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "type": "string",
+                  "const": "clear"
+                }
+              },
+              "required": [
+                "op"
+              ],
+              "additionalProperties": false
+            }
+          ]
         },
         "arbitrations": {
-          "$ref": "#/definitions/data/properties/repositories",
-          "description": "Service Arbitration object list. FORMAT: same as repositories — use the `objects` field name inside the operation data. Example: {arbitrations: [{name: 'my_arb_1'}, {name: 'my_arb_2'}]}. Each item is a NameOrAddress (object ID or local mark name). ⚠️ PERMISSION RULE (contract-enforced, service.move arbitration_add_imp): every Arbitration bound here MUST use a Permission object DIFFERENT from THIS Service's permission — binding an Arbitration that shares the Service's Permission aborts with E_ARBITRATION_PERMISSION_CONFLICT (error 33). Create a dedicated Permission for each Arbitration BEFORE binding. DESIGN RATIONALE (confirmed intentional): dispute resolution requires NEUTRALITY — an Arbitration controlled by the same Permission admins as the Service it judges would be a conflict of interest. ONLY Arbitration has this check: Reward and Treasury objects MAY share the Service's Permission (they are the provider's own tools)."
+          "description": "Service Arbitration object list. FORMAT: same as repositories — use the `objects` field name inside the operation data. Example: {arbitrations: [{name: 'my_arb_1'}, {name: 'my_arb_2'}]}. Each item is a NameOrAddress (object ID or local mark name). ⚠️ PERMISSION RULE (contract-enforced, service.move arbitration_add_imp): every Arbitration bound here MUST use a Permission object DIFFERENT from THIS Service's permission — binding an Arbitration that shares the Service's Permission aborts with E_ARBITRATION_PERMISSION_CONFLICT (error 33). Create a dedicated Permission for each Arbitration BEFORE binding. DESIGN RATIONALE (confirmed intentional): dispute resolution requires NEUTRALITY — an Arbitration controlled by the same Permission admins as the Service it judges would be a conflict of interest. ONLY Arbitration has this check: Reward and Treasury objects MAY share the Service's Permission (they are the provider's own tools).",
+          "anyOf": [
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "anyOf": [
+                    {
+                      "type": "string",
+                      "const": "add"
+                    },
+                    {
+                      "type": "string",
+                      "const": "set"
+                    }
+                  ]
+                },
+                "objects": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                  },
+                  "description": "List of object IDs or names to add or set"
+                }
+              },
+              "required": [
+                "op",
+                "objects"
+              ],
+              "additionalProperties": false
+            },
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "type": "string",
+                  "const": "remove"
+                },
+                "objects": {
+                  "type": "array",
+                  "items": {
+                    "type": "string",
+                    "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                  },
+                  "description": "List of object IDs or names to remove"
+                }
+              },
+              "required": [
+                "op",
+                "objects"
+              ],
+              "additionalProperties": false
+            },
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "type": "string",
+                  "const": "clear"
+                }
+              },
+              "required": [
+                "op"
+              ],
+              "additionalProperties": false
+            }
+          ]
         },
         "machine": {
+          "description": "Service Machine object ID or name. The Machine object must be in published state.",
           "anyOf": [
             {
-              "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/name_or_address"
+              "type": "string",
+              "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
             },
             {
               "type": "null"
             }
-          ],
-          "description": "Service Machine object ID or name. The Machine object must be in published state."
+          ]
         },
         "discount": {
+          "description": "Issue discount.",
           "type": "object",
           "properties": {
             "name": {
@@ -496,31 +758,35 @@
                     "FIXED"
                   ]
                 },
-                {
-                  "type": "integer",
-                  "minimum": 0,
-                  "maximum": 1
-                }
+                {}
               ],
               "description": "Discount type"
             },
             "discount_value": {
-              "type": [
-                "number",
-                "string"
+              "anyOf": [
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "string"
+                }
               ],
               "description": "Discount value"
             },
             "benchmark": {
-              "type": [
-                "number",
-                "string"
-              ],
-              "description": "Discount benchmark value. Discount is only applied if the amount exceeds this value"
+              "description": "Discount benchmark value. Discount is only applied if the amount exceeds this value",
+              "anyOf": [
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "string"
+                }
+              ]
             },
             "time_ms_start": {
-              "type": "number",
-              "description": "Discount start time (milliseconds)"
+              "description": "Discount start time (milliseconds)",
+              "type": "number"
             },
             "time_ms_end": {
               "type": "number",
@@ -534,10 +800,26 @@
               "type": "object",
               "properties": {
                 "entities": {
-                  "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities"
+                  "type": "array",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "name_or_address": {
+                        "type": "string",
+                        "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                      },
+                      "local_mark_first": {
+                        "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                        "type": "boolean"
+                      }
+                    },
+                    "additionalProperties": false,
+                    "description": "Account or address lookup object. Use this to specify which account to use for an operation. EXAMPLE: { name_or_address: 'testor2' } - looks up account by name; EXAMPLE: { name_or_address: '0x1234...' } - uses address directly; If name_or_address is empty string '', uses the default local account."
+                  }
                 },
                 "check_all_founded": {
-                  "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/check_all_founded"
+                  "description": "Whether to check all entities are found, if true, all entities must be found (abort and throw exception if any ID not found); if false, only return found IDs",
+                  "type": "boolean"
                 }
               },
               "required": [
@@ -560,37 +842,45 @@
             "recipient",
             "transferable"
           ],
-          "additionalProperties": false,
-          "description": "Issue discount."
+          "additionalProperties": false
         },
         "discount_destroy": {
+          "description": "Destroy existing discount object ID list.",
           "type": "array",
           "items": {
-            "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/name_or_address"
-          },
-          "description": "Destroy existing discount object ID list."
+            "type": "string",
+            "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+          }
         },
         "customer_required": {
+          "description": "Customer required information labels. Such as phone, email, shipping_address, etc. ⚠️ HARD LINKAGE (SDK-enforced): if customer_required is set (non-empty), the Service MUST also bind a Contact via `um` — otherwise the customer's private information cannot be delivered through end-to-end encrypted Messenger (which routes to the Contact bound as um). Set `um` together with customer_required.",
           "type": "array",
           "items": {
             "type": "string",
             "minLength": 1
-          },
-          "description": "Customer required information labels. Such as phone, email, shipping_address, etc. ⚠️ HARD LINKAGE (SDK-enforced): if customer_required is set (non-empty), the Service MUST also bind a Contact via `um` — otherwise the customer's private information cannot be delivered through end-to-end encrypted Messenger (which routes to the Contact bound as um). Set `um` together with customer_required."
+          }
         },
         "order_allocators": {
+          "description": "Order fund allocator. Max 100 allocators (MAX_ALLOCATOR_COUNT). Each allocator has a guard (first matching guard wins) and a sharing list. Set to null to clear. ⚠️ PERMANENTLY IMMUTABLE after publish: order_allocators can ONLY be set BEFORE publish=true (Move service.move:503: assert!(!self.bPublished, E_ALREADY_PUBLISHED)). After publish, the ONLY way to change allocation rules is to create a NEW Service object. There is NO pause+lock exception for order_allocators (unlike arbitrations/rewards which have time-lock removal). PRE-PUBLISH CHECKLIST: verify all guard names resolve, all sharing amounts are correct, threshold is set, and recipient types (Entity/Signer/GuardIdentifier) are intended before calling publish=true. GuardIdentifier sharing mode: {who: {GuardIdentifier: <u8>}, sharing: <rate>, mode: 'Rate'} — resolves recipient from Guard table submission at allocation time (e.g., refund to customer). MULTI-CALL ALLOCATION: Allocation.alloc() can be called MULTIPLE times (no consumed flag in contract). Use Amount mode (not Surplus) for recurring allocations — Surplus calls balance::withdraw_all which drains the balance. For monthly payment scenarios, create multiple Allocators with time-based Guards + Amount mode sharing items.",
           "anyOf": [
             {
               "type": "object",
               "properties": {
                 "description": {
-                  "$ref": "#/definitions/data/properties/description",
+                  "type": "string",
                   "description": "Description of fund allocator list"
                 },
                 "threshold": {
-                  "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/total_pay/anyOf/0/properties/balance",
                   "default": 0,
-                  "description": "Minimum balance required for allocation to fire. When the Allocation object's balance < threshold, allocation aborts with EINSUFFICIENT_BALANCE=7. Also: when an Allocator has only Amount items (no Rate, no Surplus), the sum of Amount items must be >= threshold (EAMOUNT_BELOW_THRESHOLD=12). Set to 0 (default) to allow any balance."
+                  "description": "Minimum balance required for allocation to fire. When the Allocation object's balance < threshold, allocation aborts with EINSUFFICIENT_BALANCE=7. Also: when an Allocator has only Amount items (no Rate, no Surplus), the sum of Amount items must be >= threshold (EAMOUNT_BELOW_THRESHOLD=12). Set to 0 (default) to allow any balance.",
+                  "anyOf": [
+                    {
+                      "type": "number"
+                    },
+                    {
+                      "type": "string"
+                    }
+                  ]
                 },
                 "allocators": {
                   "type": "array",
@@ -598,7 +888,7 @@
                     "type": "object",
                     "properties": {
                       "guard": {
-                        "$ref": "#/definitions/data/properties/object/anyOf/0",
+                        "type": "string",
                         "description": "Guard object ID or name. If Guard verification passes (via Passport), fund allocation for THIS Allocator fires. Each Allocator in an Allocators list can have a different Guard — the first Allocator whose Guard returns true wins. This enables mutually exclusive allocation paths (e.g., refund Guard on 'return_approved' node vs damage Guard on 'damage_confirmed' node)."
                       },
                       "sharing": {
@@ -628,7 +918,19 @@
                                   "type": "object",
                                   "properties": {
                                     "Entity": {
-                                      "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items"
+                                      "type": "object",
+                                      "properties": {
+                                        "name_or_address": {
+                                          "type": "string",
+                                          "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                                        },
+                                        "local_mark_first": {
+                                          "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                                          "type": "boolean"
+                                        }
+                                      },
+                                      "additionalProperties": false,
+                                      "description": "Account or address lookup object. Use this to specify which account to use for an operation. EXAMPLE: { name_or_address: 'testor2' } - looks up account by name; EXAMPLE: { name_or_address: '0x1234...' } - uses address directly; If name_or_address is empty string '', uses the default local account."
                                     }
                                   },
                                   "required": [
@@ -655,9 +957,13 @@
                               "description": "Recipient of this allocation. Three forms — each resolves the address at a DIFFERENT time:\n• { GuardIdentifier: u8 } — DYNAMIC address resolved from Passport at alloc() time (contract calls passport::submission_get). Use 0 for Order owner in Service-integrated mode (Customer who created the Order). The identifier must match a Guard table entry with b_submission=true. If Passport has no matching submission, contract aborts with E_VERIFY_FAILED. Use when the recipient address is not known at config time and must be supplied via Guard submission data.\n• { Entity: { name_or_address: '...' } } — FIXED address resolved via LocalMark at SDK build time (passed to contract as a literal address). Use for known recipients (e.g., 'turo_host', or a Treasury object address). Use when the recipient is a stable, known address (e.g., operator receives rent, platform fee to treasury).\n• 'Signer' — the transaction sender at the time of the alloc() call (tx_context::sender). RESOLVED AT EXECUTION TIME, not at config time. For refunds: the customer (Order owner) must call alloc_by_guard THEMSELVES so that tx_context::sender resolves to THEIR address — if the operator calls alloc_by_guard, the operator becomes the recipient (Signer = operator), NOT the customer. Use when the recipient is whoever submits the allocation transaction (e.g., customer receives refund)."
                             },
                             "sharing": {
-                              "type": [
-                                "number",
-                                "string"
+                              "anyOf": [
+                                {
+                                  "type": "number"
+                                },
+                                {
+                                  "type": "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.\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."
                             },
@@ -671,11 +977,7 @@
                                     "Surplus"
                                   ]
                                 },
-                                {
-                                  "type": "integer",
-                                  "minimum": 0,
-                                  "maximum": 2
-                                }
+                                {}
                               ],
                               "description": "Allocation mode — determines how the `sharing` field is interpreted. Three modes can be used individually OR combined within a single Allocator; when combined, allocation order is strictly: Amount first, then Rate, then Surplus. Understanding these modes allows modeling almost any fund distribution pattern.\n• Amount (0): `sharing` is a FIXED amount in smallest unit (e.g., '750000000' = 0.75 WOW). Allocated FIRST; sum of all Amount items is cached as `fix` by the contract. Validation: when no Rate and no Surplus items exist, sum of Amount items must be >= allocators.threshold (EAMOUNT_BELOW_THRESHOLD=12); when `max` is set, sum of Amount items must be <= max (EAMOUNT_EXCEEDS_MAX=13).\n• Rate (1): `sharing` is a basis-points rate (10000 = 100%). Allocated AFTER Amount; formula: allocated = (sharing × total_rates) / 10000, where total_rates = balance - fix (or max - fix if `max` is set). Validation: when no Surplus items exist, sum of all Rate items must be EXACTLY 10000 (ERATE_NOT_10000=4); when Surplus items exist, sum of all Rate items must be <= 10000 (ERATE_EXCEEDS_10000=6).\n• Surplus (2): `sharing` is IGNORED (contract forces it to 0). Allocated LAST; receives the remaining balance after Amount + Rate allocations. Validation: MAX ONE Surplus item per Allocator (EMULTIPLE_SURPLUS=5). When Surplus exists, Rate sum constraint relaxes from == 10000 to <= 10000.\nALLOCATION ORDER (strict): Amount items (fixed, cached as fix) → Rate items (proportional to balance-fix) → Surplus item (remaining).\nRECOMMENDATION: Use Amount mode for known fixed amounts (clearer, no sum constraint). Use Rate mode for proportional splits (requires sum == 10000 unless Surplus present). Use Surplus to capture remainder (e.g., platform fee + host gets rest). Accepts string ('Amount'/'Rate'/'Surplus', recommended) or number (0/1/2)."
                             }
@@ -691,19 +993,34 @@
                         "description": "Fund allocation item list. Each item specifies a recipient (who), a value (sharing), and a mode. Items can mix modes (Amount + Rate + Surplus) within the same Allocator. ALLOCATION ORDER: Amount items first (cached as fix) → Rate items (proportional to balance - fix) → Surplus item (remaining). CONSTRAINTS: max ONE Surplus item per Allocator; Rate sum must == 10000 (no Surplus) or <= 10000 (with Surplus); Amount sum must >= threshold (no Rate and no Surplus) and <= max (if max set)."
                       },
                       "fix": {
-                        "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/total_pay/anyOf/0/properties/balance",
-                        "description": "OUTPUT-ONLY (query result). Cached sum of all Amount-mode `sharing` values in this Allocator. Computed by the contract during `allocator_add` — DO NOT set this field at creation. Used internally to compute `total_rates = balance - fix` for Rate allocation."
+                        "description": "OUTPUT-ONLY (query result). Cached sum of all Amount-mode `sharing` values in this Allocator. Computed by the contract during `allocator_add` — DO NOT set this field at creation. Used internally to compute `total_rates = balance - fix` for Rate allocation.",
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
+                        ]
                       },
                       "max": {
+                        "description": "Maximum allocation cap (OPTIONAL — omit the field or set to null to disable the cap; do NOT set to 0 as that means a cap of zero). Passed through to the contract as Option<u64> via allocator_add(): when null/omitted the contract treats it as `none` (no cap); when set, the contract enforces it. Has THREE effects when set:\n1. Construction: sum of Amount items must be <= max (EAMOUNT_EXCEEDS_MAX=13)\n2. Rate execution: total_rates = max - fix (instead of balance - fix)\n3. Surplus execution: surplus_amount = max - alloced_amount (instead of balance - alloced_amount)\nUse when you want to cap total allocation regardless of Order balance (e.g., cap payout to declared amount). SDK pre-validates Amount sum <= max at build time to give actionable error messages before on-chain abort.",
                         "anyOf": [
                           {
-                            "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/total_pay/anyOf/0/properties/balance"
+                            "anyOf": [
+                              {
+                                "type": "number"
+                              },
+                              {
+                                "type": "string"
+                              }
+                            ],
+                            "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                           },
                           {
                             "type": "null"
                           }
-                        ],
-                        "description": "Maximum allocation cap (OPTIONAL — omit the field or set to null to disable the cap; do NOT set to 0 as that means a cap of zero). Passed through to the contract as Option<u64> via allocator_add(): when null/omitted the contract treats it as `none` (no cap); when set, the contract enforces it. Has THREE effects when set:\n1. Construction: sum of Amount items must be <= max (EAMOUNT_EXCEEDS_MAX=13)\n2. Rate execution: total_rates = max - fix (instead of balance - fix)\n3. Surplus execution: surplus_amount = max - alloced_amount (instead of balance - alloced_amount)\nUse when you want to cap total allocation regardless of Order balance (e.g., cap payout to declared amount). SDK pre-validates Amount sum <= max at build time to give actionable error messages before on-chain abort."
+                        ]
                       }
                     },
                     "required": [
@@ -718,6 +1035,7 @@
               },
               "required": [
                 "description",
+                "threshold",
                 "allocators"
               ],
               "additionalProperties": false,
@@ -726,42 +1044,73 @@
             {
               "type": "null"
             }
-          ],
-          "description": "Order fund allocator. Max 100 allocators (MAX_ALLOCATOR_COUNT). Each allocator has a guard (first matching guard wins) and a sharing list. Set to null to clear. ⚠️ PERMANENTLY IMMUTABLE after publish: order_allocators can ONLY be set BEFORE publish=true (Move service.move:503: assert!(!self.bPublished, E_ALREADY_PUBLISHED)). After publish, the ONLY way to change allocation rules is to create a NEW Service object. There is NO pause+lock exception for order_allocators (unlike arbitrations/rewards which have time-lock removal). PRE-PUBLISH CHECKLIST: verify all guard names resolve, all sharing amounts are correct, threshold is set, and recipient types (Entity/Signer/GuardIdentifier) are intended before calling publish=true. GuardIdentifier sharing mode: {who: {GuardIdentifier: <u8>}, sharing: <rate>, mode: 'Rate'} — resolves recipient from Guard table submission at allocation time (e.g., refund to customer). MULTI-CALL ALLOCATION: Allocation.alloc() can be called MULTIPLE times (no consumed flag in contract). Use Amount mode (not Surplus) for recurring allocations — Surplus calls balance::withdraw_all which drains the balance. For monthly payment scenarios, create multiple Allocators with time-based Guards + Amount mode sharing items."
+          ]
         },
         "buy_guard": {
+          "description": "Buy guard object ID or name.",
           "anyOf": [
             {
-              "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/name_or_address"
+              "type": "string",
+              "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
             },
             {
               "type": "null"
             }
-          ],
-          "description": "Buy guard object ID or name."
+          ]
         },
         "compensation_fund_add": {
+          "description": "Deposit funds into the Service compensation_fund. Used to pay indemnity when arbitration resolves in customer's favor. FORMAT: {balance: <amount_in_smallest_unit>} — the field name is 'balance' (NOT 'amount'). The token type and precision are determined by the Service object's type_parameter (the generic type set when the Service was created). For WOW (9 decimals): {balance: 1000000000} = 1 WOW. For SUI (9 decimals): {balance: 1000000000} = 1 SUI. For tokens with different decimals, adjust accordingly (e.g. USDC has 6 decimals, so {balance: 1000000} = 1 USDC). REQUIRES: Permission index 315 (SERVICE_COMPENSATION_FUND_DEPOSIT) must be granted to the calling account first. COMMON MISTAKE: using {amount: ...} or {amount: ..., type: 'WOW'} — these will fail. The correct field is 'balance'.",
           "anyOf": [
             {
-              "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/total_pay/anyOf/0"
+              "type": "object",
+              "properties": {
+                "balance": {
+                  "anyOf": [
+                    {
+                      "type": "number"
+                    },
+                    {
+                      "type": "string"
+                    }
+                  ],
+                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                }
+              },
+              "required": [
+                "balance"
+              ],
+              "additionalProperties": false,
+              "description": "Specify an amount value."
             },
             {
-              "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/total_pay/anyOf/1"
+              "type": "object",
+              "properties": {
+                "coin": {
+                  "type": "string",
+                  "description": "Coin object ID or name(local mark). Use a specified Coin object."
+                }
+              },
+              "required": [
+                "coin"
+              ],
+              "additionalProperties": false
             }
-          ],
-          "description": "Deposit funds into the Service compensation_fund. Used to pay indemnity when arbitration resolves in customer's favor. FORMAT: {balance: <amount_in_smallest_unit>} — the field name is 'balance' (NOT 'amount'). The token type and precision are determined by the Service object's type_parameter (the generic type set when the Service was created). For WOW (9 decimals): {balance: 1000000000} = 1 WOW. For SUI (9 decimals): {balance: 1000000000} = 1 SUI. For tokens with different decimals, adjust accordingly (e.g. USDC has 6 decimals, so {balance: 1000000} = 1 USDC). REQUIRES: Permission index 315 (SERVICE_COMPENSATION_FUND_DEPOSIT) must be granted to the calling account first. COMMON MISTAKE: using {amount: ...} or {amount: ..., type: 'WOW'} — these will fail. The correct field is 'balance'."
+          ]
         },
         "compensation_fund_withdraw": {
+          "description": "Withdraw ALL funds from the compensation_fund to a new Payment object owned by `receipt`. Move layer: service::compensation_fund_withdraw (service.move L383-390). REQUIRES: Service must be paused AND setting_lock_duration must have elapsed since pause (assert_not_published at L384-385). Withdraws the ENTIRE compensation_fund balance via balance::withdraw_all. DIFFERENT from compensation_claim (order-side, for arbitration-winning users, no pause+lock required).",
           "type": "object",
           "properties": {
             "receipt": {
               "type": "object",
               "properties": {
                 "name_or_address": {
-                  "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/name_or_address"
+                  "type": "string",
+                  "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
                 },
                 "local_mark_first": {
-                  "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/local_mark_first"
+                  "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                  "type": "boolean"
                 }
               },
               "additionalProperties": false,
@@ -771,27 +1120,39 @@
               "type": "object",
               "properties": {
                 "for_object": {
-                  "type": [
-                    "string",
-                    "null"
-                  ],
-                  "description": "Payment for a specific object ID"
+                  "description": "Payment for a specific object ID",
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
                 },
                 "for_guard": {
-                  "type": [
-                    "string",
-                    "null"
-                  ],
-                  "description": "Payment to satisfy verification of a Guard object"
+                  "description": "Payment to satisfy verification of a Guard object",
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
                 },
                 "remark": {
                   "type": "string",
                   "description": "Payment record remark"
                 },
                 "index": {
-                  "type": [
-                    "number",
-                    "string"
+                  "anyOf": [
+                    {
+                      "type": "number"
+                    },
+                    {
+                      "type": "string"
+                    }
                   ],
                   "description": "Payment record index"
                 }
@@ -808,20 +1169,28 @@
             "receipt",
             "payment_info"
           ],
-          "additionalProperties": false,
-          "description": "Withdraw ALL funds from the compensation_fund to a new Payment object owned by `receipt`. Move layer: service::compensation_fund_withdraw (service.move L383-390). REQUIRES: Service must be paused AND setting_lock_duration must have elapsed since pause (assert_not_published at L384-385). Withdraws the ENTIRE compensation_fund balance via balance::withdraw_all. DIFFERENT from compensation_claim (order-side, for arbitration-winning users, no pause+lock required)."
+          "additionalProperties": false
         },
         "setting_lock_duration_add": {
-          "type": "number",
-          "description": "Additional lock duration to ADD to 'setting_lock_duration' (Move field name). UNIT: milliseconds (ms). Example: 2592000000 = 30 days, 7776000000 = 90 days, 86400000 = 1 day. DEFAULT: 2592000000 (30 days, DEFAULT_LOCK_DURATION). This is the initial value when a Service is created. Behavior: additive (safe_add) — only increases, never decreases. Move entry: service::setting_lock_duration_add / setting_lock_duration_add_with_passport. Can be called BEFORE or AFTER publish (no publish check). Affects the waiting time required by: compensation_fund_withdraw, arbitrations remove/clear, rewards remove/clear (all require pause + setting_lock_duration elapsed since pause)."
+          "description": "Additional lock duration to ADD to 'setting_lock_duration' (Move field name). UNIT: milliseconds (ms). Example: 2592000000 = 30 days, 7776000000 = 90 days, 86400000 = 1 day. DEFAULT: 2592000000 (30 days, DEFAULT_LOCK_DURATION). This is the initial value when a Service is created. Behavior: additive (safe_add) — only increases, never decreases. Move entry: service::setting_lock_duration_add / setting_lock_duration_add_with_passport. Can be called BEFORE or AFTER publish (no publish check). Affects the waiting time required by: compensation_fund_withdraw, arbitrations remove/clear, rewards remove/clear (all require pause + setting_lock_duration elapsed since pause).",
+          "type": "number"
         },
         "compensation_fund_receive": {
+          "description": "Receive order compensation funds from this Service object.\n\nACCEPTED FORMATS (F-06 unified receive operation block):\n• 'recently' (string literal) — auto-query and receive ALL recently received balance.\n  Use this for the common case: \"deposit all recently received coins into pending balance.\"\n  Example: receive: 'recently'\n• ReceivedBalance ({token_type, balance, received: [{id, balance, payment}]}) —\n  receive a specific balance record from a Payment/payer.\n  Use this when targeting a specific received balance (advanced).\n  Example: receive: {token_type: '0x2::sui::SUI', balance: 1000000, received: [{id: '0xrec1', balance: 1000000, payment: '0xpay1'}]}\nANTI-PATTERN: do NOT wrap in {result: ...} — pass the value directly.",
           "anyOf": [
             {
               "type": "object",
               "properties": {
                 "balance": {
-                  "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/total_pay/anyOf/0/properties/balance"
+                  "anyOf": [
+                    {
+                      "type": "number"
+                    },
+                    {
+                      "type": "string"
+                    }
+                  ],
+                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                 },
                 "token_type": {
                   "type": "string",
@@ -837,7 +1206,15 @@
                         "description": "Received CoinWrapper object ID"
                       },
                       "balance": {
-                        "$ref": "#/definitions/data/properties/order_new/properties/buy/properties/total_pay/anyOf/0/properties/balance"
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
+                        ],
+                        "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                       },
                       "payment": {
                         "type": "string",
@@ -867,10 +1244,10 @@
               "type": "string",
               "const": "recently"
             }
-          ],
-          "description": "Receive order compensation funds from this Service object.\n\nACCEPTED FORMATS (F-06 unified receive operation block):\n• 'recently' (string literal) — auto-query and receive ALL recently received balance.\n  Use this for the common case: \"deposit all recently received coins into pending balance.\"\n  Example: receive: 'recently'\n• ReceivedBalance ({token_type, balance, received: [{id, balance, payment}]}) —\n  receive a specific balance record from a Payment/payer.\n  Use this when targeting a specific received balance (advanced).\n  Example: receive: {token_type: '0x2::sui::SUI', balance: 1000000, received: [{id: '0xrec1', balance: 1000000, payment: '0xpay1'}]}\nANTI-PATTERN: do NOT wrap in {result: ...} — pass the value directly."
+          ]
         },
         "owner_receive": {
+          "description": "Unwrap CoinWrapper objects and other objects received by this Service object and send them to the owner of its Permission object.\n\nACCEPTED FORMATS (F-06 unified receive operation block):\n• 'recently' (string literal) — auto-query and receive ALL recently received objects.\n  Use this for the common case: \"withdraw everything the object has received.\"\n  Example: receive: 'recently'\n• ReceivedNormal[] (array) — explicit list of received objects to unwrap.\n  Use this when you want to receive specific objects only (not all).\n  Example: receive: [{id: '0xobj1', type: '0x2::coin::Coin<0x2::sui::SUI>'}]\n• ReceivedBalance ({token_type, balance, received: [{id, balance, payment}]}) —\n  receive a balance record from a specific Payment/payer.\n  Use this for precise balance targeting (advanced — usually after querying\n  the object's received history via query_received).\n  Example: receive: {token_type: '0x2::sui::SUI', balance: 1000000, received: [{id: '0xrec1', balance: 1000000, payment: '0xpay1'}]}\nANTI-PATTERN: do NOT wrap in {result: ...} — pass the value directly.",
           "anyOf": [
             {
               "type": "array",
@@ -900,33 +1277,92 @@
               }
             },
             {
-              "$ref": "#/definitions/data/properties/compensation_fund_receive/anyOf/0"
+              "type": "object",
+              "properties": {
+                "balance": {
+                  "anyOf": [
+                    {
+                      "type": "number"
+                    },
+                    {
+                      "type": "string"
+                    }
+                  ],
+                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                },
+                "token_type": {
+                  "type": "string",
+                  "description": "Asset type of Coin objects. Supports CoinWrapper<...> format for order receive operations."
+                },
+                "received": {
+                  "type": "array",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "id": {
+                        "type": "string",
+                        "description": "Received CoinWrapper object ID"
+                      },
+                      "balance": {
+                        "anyOf": [
+                          {
+                            "type": "number"
+                          },
+                          {
+                            "type": "string"
+                          }
+                        ],
+                        "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                      },
+                      "payment": {
+                        "type": "string",
+                        "description": "Payment object ID"
+                      }
+                    },
+                    "required": [
+                      "id",
+                      "balance",
+                      "payment"
+                    ],
+                    "additionalProperties": false,
+                    "description": "Received CoinWrapper object record"
+                  },
+                  "description": "Received records of Coin objects"
+                }
+              },
+              "required": [
+                "balance",
+                "token_type",
+                "received"
+              ],
+              "additionalProperties": false,
+              "description": "Received record of Coin objects"
             },
             {
               "type": "string",
               "const": "recently"
             }
-          ],
-          "description": "Unwrap CoinWrapper objects and other objects received by this Service object and send them to the owner of its Permission object.\n\nACCEPTED FORMATS (F-06 unified receive operation block):\n• 'recently' (string literal) — auto-query and receive ALL recently received objects.\n  Use this for the common case: \"withdraw everything the object has received.\"\n  Example: receive: 'recently'\n• ReceivedNormal[] (array) — explicit list of received objects to unwrap.\n  Use this when you want to receive specific objects only (not all).\n  Example: receive: [{id: '0xobj1', type: '0x2::coin::Coin<0x2::sui::SUI>'}]\n• ReceivedBalance ({token_type, balance, received: [{id, balance, payment}]}) —\n  receive a balance record from a specific Payment/payer.\n  Use this for precise balance targeting (advanced — usually after querying\n  the object's received history via query_received).\n  Example: receive: {token_type: '0x2::sui::SUI', balance: 1000000, received: [{id: '0xrec1', balance: 1000000, payment: '0xpay1'}]}\nANTI-PATTERN: do NOT wrap in {result: ...} — pass the value directly."
+          ]
         },
         "um": {
+          "description": "Contact object ID or name — the Service's customer-service channel. This is the object that Messenger routes encrypted messages to for pre-order negotiation, private-info delivery (see customer_required), and post-sale support. ⚠️ REQUIRED whenever customer_required is set: without um, the customer's private information has no channel to reach the merchant.",
           "anyOf": [
             {
-              "$ref": "#/definitions/data/properties/order_new/properties/agents/properties/entities/items/properties/name_or_address"
+              "type": "string",
+              "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
             },
             {
               "type": "null"
             }
-          ],
-          "description": "Contact object ID or name — the Service's customer-service channel. This is the object that Messenger routes encrypted messages to for pre-order negotiation, private-info delivery (see customer_required), and post-sale support. ⚠️ REQUIRED whenever customer_required is set: without um, the customer's private information has no channel to reach the merchant."
+          ]
         },
         "pause": {
-          "type": "boolean",
-          "description": "Whether to pause accepting new orders."
+          "description": "Whether to pause accepting new orders.",
+          "type": "boolean"
         },
         "publish": {
-          "type": "boolean",
-          "description": "Whether to publish the Service. After publishing, customers can place orders. VERIFIED against Move source service.move + SDK service.ts (4-level immutability matrix):\n  L1 — PERMANENTLY LOCKED after publish (assert!(!bPublished), no pause+lock exception):\n    • machine          (service.move L633/L653 — workflow template)\n    • order_allocators (service.move L503 — fund distribution rules)\n  L2 — TIME-LOCKED after publish (assert_not_published — requires pause + setting_lock_duration elapsed):\n    • arbitrations remove/clear (service.move L433/L445 — dispute resolution objects)\n    • rewards remove/clear       (service.move L402/L414 — reward objects)\n    • compensation_fund_withdraw (service.move L384-385 — withdraw ALL funds)\n  L3 — REMAIN MUTABLE after publish (no SDK check, no Move check):\n    • arbitrations add, rewards add (no assert — can add after publish)\n    • buy_guard, sales, discount, description, location, pause, repositories,\n    • compensation_fund_add, setting_lock_duration_add, customer_required, um (Contact)\nThese 2 L1-LOCKED fields (machine/order_allocators) MUST be set BEFORE publish=true.\narbitrations/rewards can be ADDED after publish but remove/clear requires pause+lock.\n\n⚠️ COMPENSATION_FUND + ARBITRATION LINKAGE (service.move:494-499):\n  At publish time, if compensation_fund > 0, Arbitration MUST be bound:\n    if (balance::value(&self.compensation_fund) > 0) {\n        assert!(arbitration_count > 0, E_ARBITRATION_NOT_SET_WITH_COMPENSATION_FUND);\n    }\n  The MCP handler enforces this as a HARD PRE-CHECK: if publish=true AND compensation_fund_add   is set in the same call AND arbitrations is empty, the call is REJECTED before submission.   If compensation_fund was deposited in a prior call, a SOFT WARNING is issued.\n\nSCHEMA-03 / P0-01 fix — DEPLOYMENT WORKFLOW (two-phase, avoids circular dependency):\n  Phase 1 — CREATE (no publish): object={name:'my-service', type_parameter, permission} + machine + order_allocators + arbitrations.\n    NOTE: buy_guard can use a LocalMark NAME (not address) to break the Guard→Service circular dependency.\n    The name is resolved to an address at transaction build time.\n  Phase 2 — PUBLISH: object='my-service' (string ref) + publish=true.\n    All L1-LOCKED fields must be set in Phase 1; Phase 2 only flips the publish flag.\n  Post-publish updates: buy_guard, sales, description, repositories (add), rewards (add), arbitrations (add), etc."
+          "description": "Whether to publish the Service. After publishing, customers can place orders. VERIFIED against Move source service.move + SDK service.ts (4-level immutability matrix):\n  L1 — PERMANENTLY LOCKED after publish (assert!(!bPublished), no pause+lock exception):\n    • machine          (service.move L633/L653 — workflow template)\n    • order_allocators (service.move L503 — fund distribution rules)\n  L2 — TIME-LOCKED after publish (assert_not_published — requires pause + setting_lock_duration elapsed):\n    • arbitrations remove/clear (service.move L433/L445 — dispute resolution objects)\n    • rewards remove/clear       (service.move L402/L414 — reward objects)\n    • compensation_fund_withdraw (service.move L384-385 — withdraw ALL funds)\n  L3 — REMAIN MUTABLE after publish (no SDK check, no Move check):\n    • arbitrations add, rewards add (no assert — can add after publish)\n    • buy_guard, sales, discount, description, location, pause, repositories,\n    • compensation_fund_add, setting_lock_duration_add, customer_required, um (Contact)\nThese 2 L1-LOCKED fields (machine/order_allocators) MUST be set BEFORE publish=true.\narbitrations/rewards can be ADDED after publish but remove/clear requires pause+lock.\n\n⚠️ COMPENSATION_FUND + ARBITRATION LINKAGE (service.move:494-499):\n  At publish time, if compensation_fund > 0, Arbitration MUST be bound:\n    if (balance::value(&self.compensation_fund) > 0) {\n        assert!(arbitration_count > 0, E_ARBITRATION_NOT_SET_WITH_COMPENSATION_FUND);\n    }\n  The MCP handler enforces this as a HARD PRE-CHECK: if publish=true AND compensation_fund_add   is set in the same call AND arbitrations is empty, the call is REJECTED before submission.   If compensation_fund was deposited in a prior call, a SOFT WARNING is issued.\n\nSCHEMA-03 / P0-01 fix — DEPLOYMENT WORKFLOW (two-phase, avoids circular dependency):\n  Phase 1 — CREATE (no publish): object={name:'my-service', type_parameter, permission} + machine + order_allocators + arbitrations.\n    NOTE: buy_guard can use a LocalMark NAME (not address) to break the Guard→Service circular dependency.\n    The name is resolved to an address at transaction build time.\n  Phase 2 — PUBLISH: object='my-service' (string ref) + publish=true.\n    All L1-LOCKED fields must be set in Phase 1; Phase 2 only flips the publish flag.\n  Post-publish updates: buy_guard, sales, description, repositories (add), rewards (add), arbitrations (add), etc.",
+          "type": "boolean"
         }
       },
       "required": [
@@ -939,20 +1375,20 @@
       "type": "object",
       "properties": {
         "account": {
+          "default": "",
           "type": "string",
-          "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters).",
-          "default": ""
+          "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
         },
         "permission_guard": {
+          "description": "List of permission guard IDs. Used to extend additional operation permissions (requires verification and configuration in the Permission object).",
           "type": "array",
           "items": {
             "type": "string"
-          },
-          "description": "List of permission guard IDs. Used to extend additional operation permissions (requires verification and configuration in the Permission object)."
+          }
         },
         "no_cache": {
-          "type": "boolean",
-          "description": "Whether to disable caching."
+          "description": "Whether to disable caching.",
+          "type": "boolean"
         },
         "network": {
           "type": "string",
@@ -964,38 +1400,42 @@
           "description": "Network entrypoint: Specifies which network the operation occurs on. FIX-010 cross-network note: LocalMark names are scoped per network (testnet marks are invisible on mainnet and vice versa). When migrating from testnet to mainnet, recreate all objects on mainnet and re-register LocalMark names with the SAME names to keep name-based references working across networks. Use project_operation action='clone_project_to_network' to clone the project blueprint to the target network, then re-run onchain_operations with env.network=target_network to deploy."
         },
         "referrer": {
-          "$ref": "#/definitions/env/properties/account",
-          "description": "Referrer ID. If the user is using the network for the first time, the referrer ID will be recorded."
+          "description": "Referrer ID. If the user is using the network for the first time, the referrer ID will be recorded.",
+          "type": "string"
         },
         "confirmed": {
-          "type": "boolean",
-          "description": "Phase 2 ConfirmGate: set to true to proceed after a 'pending_confirmation' result. The operation is NOT executed until you re-call with confirmed=true after user consent."
+          "description": "Phase 2 ConfirmGate: set to true to proceed after a 'pending_confirmation' result. The operation is NOT executed until you re-call with confirmed=true after user consent.",
+          "type": "boolean"
         },
         "user_intent_phrases": {
+          "description": "Phase 2 ConfirmGate: explicit user intent phrases collected from conversation context (e.g. 'use default account', 'force publish'). Used to bypass confirmation rules whose bypass_on_explicit_intent matches.",
           "type": "array",
           "items": {
             "type": "string"
-          },
-          "description": "Phase 2 ConfirmGate: explicit user intent phrases collected from conversation context (e.g. 'use default account', 'force publish'). Used to bypass confirmation rules whose bypass_on_explicit_intent matches."
+          }
         },
         "project": {
-          "type": "string",
-          "description": "Project prefix to assign this object to (e.g. 'myshop'). When set: 1) the object is tagged with 'project:<prefix>' on-chain automatically via ProjectService, 2) the newly created object is auto-associated to the SQLite project for local management, evaluation, and graph tracking. The project MUST exist (create via project_operation action='create_project' first). Use project_operation to manage projects."
+          "description": "Project prefix to assign this object to (e.g. 'myshop'). When set: 1) the object is tagged with 'project:<prefix>' on-chain automatically via ProjectService, 2) the newly created object is auto-associated to the SQLite project for local management, evaluation, and graph tracking. The project MUST exist (create via project_operation action='create_project' first). Use project_operation to manage projects.",
+          "type": "string"
         },
         "client_schema_version": {
-          "type": "string",
-          "description": "Client-side schema version (semver, e.g. '1.0.0'). When provided, the server checks compatibility and attaches warnings if mismatched."
+          "description": "Client-side schema version (semver, e.g. '1.0.0'). When provided, the server checks compatibility and attaches warnings if mismatched.",
+          "type": "string"
         },
         "schema_strict_mode": {
-          "type": "boolean",
           "default": false,
-          "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
+          "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode).",
+          "type": "boolean"
         },
         "dry_run": {
-          "type": "boolean",
-          "description": "Phase 1 dry_run: when true, SIMULATE the transaction without signing or submitting. Returns effects + events showing what WOULD happen — no on-chain state is modified, no gas is charged. Use this to verify an operation will succeed before committing. Essential for the 5-step loop's Plan step. The returned digest will be 'dry_run:<timestamp>' and objectChanges will be empty (simulation only)."
+          "description": "Phase 1 dry_run: when true, SIMULATE the transaction without signing or submitting. Returns effects + events showing what WOULD happen — no on-chain state is modified, no gas is charged. Use this to verify an operation will succeed before committing. Essential for the 5-step loop's Plan step. The returned digest will be 'dry_run:<timestamp>' and objectChanges will be empty (simulation only).",
+          "type": "boolean"
         }
       },
+      "required": [
+        "account",
+        "schema_strict_mode"
+      ],
       "additionalProperties": false,
       "description": "IMPORTANT: Execution environment includes: account for signing operations, network selection ([object Object]), additional Guard permissions, and more. Used to specify context information during the call. If account is not specified, the default account (\"\") will be used."
     },
@@ -1008,6 +1448,7 @@
           "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
         },
         "guard": {
+          "maxItems": 20,
           "type": "array",
           "items": {
             "type": "object",
@@ -1027,7 +1468,6 @@
             ],
             "additionalProperties": false
           },
-          "maxItems": 20,
           "description": "Array of Guard objects to verify. Constraint: at most 20 entries (MAX_GUARD_COUNT_PASSPORT). Relation: each entry corresponds to a Guard bound to the operation."
         },
         "submission": {
@@ -1036,7 +1476,7 @@
             "type": "object",
             "properties": {
               "guard": {
-                "$ref": "#/definitions/submission/properties/guard/items/properties/object",
+                "type": "string",
                 "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
               },
               "submission": {
@@ -1345,6 +1785,7 @@
                       "description": "Type of the value stored in `value`. One of: Bool(0), Address(1), String(2), U8(3), U16(4), U32(5), U64(6), U128(7), U256(8), VecBool(9), VecAddress(10), VecString(11), VecU8(12), VecU16(13), VecU32(14), VecU64(15), VecU128(16), VecU256(17), VecVecU8(18). When value_type=Address (1), the `value` field accepts a hex address string, a LocalMark name, or an AccountOrMark_Address object — see `value` field description for details."
                     },
                     "value": {
+                      "description": "The actual value data. Format depends on `value_type`:\n• Bool: true/false (boolean)\n• Address (CRITICAL — string 'Address' is NOT a placeholder): a hex address (e.g. '0x1234...'), a LocalMark name (e.g. 'my-service' — resolved to address at evaluation time), an AccountOrMark_Address object (e.g. {name_or_address:'my-service'}), or system shorthand ('0xaaa' = EntityLinker, '0xaab' = EntityRegistrar). The literal string 'Address' itself is INVALID — it would be treated as a non-existent LocalMark name and fail. Example: value='0x2::wow::WOW<address>' or value='my-permission'.\n• String: any string\n• U8/U16/U32/U64/U128/U256: number or numeric string (e.g. 42 or '42')\n• Vec* types: arrays of the corresponding element type\nREQUIRED when b_submission=false. OPTIONAL when b_submission=true (value is supplied at evaluation time by user submission).",
                       "anyOf": [
                         {
                           "type": "boolean"
@@ -1355,12 +1796,12 @@
                               "type": "object",
                               "properties": {
                                 "name_or_address": {
-                                  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
+                                  "type": "string",
                                   "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
                                 },
                                 "local_mark_first": {
-                                  "type": "boolean",
-                                  "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks"
+                                  "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                                  "type": "boolean"
                                 }
                               },
                               "additionalProperties": false,
@@ -1391,12 +1832,24 @@
                                 "entities": {
                                   "type": "array",
                                   "items": {
-                                    "$ref": "#/definitions/submission/properties/submission/items/properties/submission/items/properties/value/anyOf/1/anyOf/0"
+                                    "type": "object",
+                                    "properties": {
+                                      "name_or_address": {
+                                        "type": "string",
+                                        "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                                      },
+                                      "local_mark_first": {
+                                        "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                                        "type": "boolean"
+                                      }
+                                    },
+                                    "additionalProperties": false,
+                                    "description": "Account or address lookup object. Use this to specify which account to use for an operation. EXAMPLE: { name_or_address: 'testor2' } - looks up account by name; EXAMPLE: { name_or_address: '0x1234...' } - uses address directly; If name_or_address is empty string '', uses the default local account."
                                   }
                                 },
                                 "check_all_founded": {
-                                  "type": "boolean",
-                                  "description": "Whether to check all entities are found, if true, all entities must be found (abort and throw exception if any ID not found); if false, only return found IDs"
+                                  "description": "Whether to check all entities are found, if true, all entities must be found (abort and throw exception if any ID not found); if false, only return found IDs",
+                                  "type": "boolean"
                                 }
                               },
                               "required": [
@@ -1434,15 +1887,15 @@
                             }
                           }
                         }
-                      ],
-                      "description": "The actual value data. Format depends on `value_type`:\n• Bool: true/false (boolean)\n• Address (CRITICAL — string 'Address' is NOT a placeholder): a hex address (e.g. '0x1234...'), a LocalMark name (e.g. 'my-service' — resolved to address at evaluation time), an AccountOrMark_Address object (e.g. {name_or_address:'my-service'}), or system shorthand ('0xaaa' = EntityLinker, '0xaab' = EntityRegistrar). The literal string 'Address' itself is INVALID — it would be treated as a non-existent LocalMark name and fail. Example: value='0x2::wow::WOW<address>' or value='my-permission'.\n• String: any string\n• U8/U16/U32/U64/U128/U256: number or numeric string (e.g. 42 or '42')\n• Vec* types: arrays of the corresponding element type\nREQUIRED when b_submission=false. OPTIONAL when b_submission=true (value is supplied at evaluation time by user submission)."
+                      ]
                     },
                     "name": {
-                      "type": "string",
                       "default": "",
-                      "description": "Data name identifier. MAX 64 BCS characters (Chinese chars count as 3-4 BCS bytes each). Use short identifiers like 'order_id', 'delivery_node'. Put longer descriptions in the Guard's 'description' field, NOT here."
+                      "description": "Data name identifier. MAX 64 BCS characters (Chinese chars count as 3-4 BCS bytes each). Use short identifiers like 'order_id', 'delivery_node'. Put longer descriptions in the Guard's 'description' field, NOT here.",
+                      "type": "string"
                     },
                     "object_type": {
+                      "description": "OUTPUT-ONLY (query side): Object type when value_type is Address and represents a specific object. Auto-derived by the system — DO NOT set this field at Guard creation.",
                       "type": "string",
                       "enum": [
                         "Permission",
@@ -1477,14 +1930,14 @@
                         "TableItem_EntityLinker",
                         "TableItem_AddressMark",
                         "TableItem_EntityRegistrar"
-                      ],
-                      "description": "OUTPUT-ONLY (query side): Object type when value_type is Address and represents a specific object. Auto-derived by the system — DO NOT set this field at Guard creation."
+                      ]
                     }
                   },
                   "required": [
                     "identifier",
                     "b_submission",
-                    "value_type"
+                    "value_type",
+                    "name"
                   ],
                   "additionalProperties": false,
                   "description": "Guard table item (QUERY/OUTPUT form — includes auto-derived object_type field)"
@@ -1510,5 +1963,10 @@
       "additionalProperties": false,
       "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
     }
-  }
+  },
+  "required": [
+    "operation_type",
+    "data"
+  ],
+  "additionalProperties": false
 }