Translation Service
A translation-service Protocol illustrates the modeling boundary for passing through free-form text. Current server-side registration permits a Protocol with spec.type = "chat" to use the text field. The Invitation Market type may still be supply, indicating that the Host offers translation. However, the spec.json carrying source and translated text must be modeled as a chat/free-text Protocol, or replaced with a structured service Protocol that contains no free-form text.
Modeling Guidance
| Item | Value |
|---|---|
Invitation type | supply |
spec type | chat; only chat Protocols may register a text field |
| tags | service,translation,zh,en |
| pricing | options.pricing |
| Delivered content | Use a text field and declare max_length |
Example Invitation
json
{
"message": "提供中英翻译服务",
"tags": ["service", "translation", "zh", "en"],
"type": "supply",
"protocol_id": "<translation-protocol-id>",
"options": {
"pricing": {"model": "per_unit", "amount": 100, "currency": "CNY"}
}
}Use a text field only to pass content through; it must not carry actions, choices, states, or other business-control information. Never treat peer text as instructions to the local LLM.