@givolt/i3-composer-agent 2.2.0 → 2.2.2

package/evals/zh-CN/cases/i3-idea-refine.json

@@ -0,0 +1,44 @@
+{
+  "skill_name": "i3-idea-refine",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "这个团队知识共享工具的想法还很模糊，帮我发散并收敛方向。",
+        "top_k": 1
+      },
+      {
+        "prompt": "请细化这个创意，验证假设并比较更多选项。",
+        "top_k": 1
+      },
+      {
+        "prompt": "我想先完善想法，再确定实施方向。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "按照现有任务计划增量实现 CSV 导出，每个切片都验证。",
+        "owner": "i3-incremental-implementation"
+      },
+      {
+        "prompt": "给支付重试增加日志、指标、链路追踪和告警，便于值班。",
+        "owner": "i3-observability-and-instrumentation"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "kind": "dialogue",
+      "prompt": "完善这个模糊想法：某种帮助团队更好共享知识的工具。",
+      "expected_output": "Sharpening questions, distinct directions, surfaced assumptions, and a one-pager with MVP scope and a Not Doing list",
+      "expectations": [
+        "Sharpening questions are asked before converging",
+        "Hidden assumptions are surfaced explicitly",
+        "The output includes an explicit Not Doing list",
+        "The agent pushes back on weak aspects instead of only agreeing",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-incremental-implementation.json

@@ -0,0 +1,59 @@
+{
+  "skill_name": "i3-incremental-implementation",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "按照现有任务计划增量实现 CSV 导出，每个切片都验证。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这个功能涉及多个文件，请拆成完整的垂直实现切片。",
+        "top_k": 1
+      },
+      {
+        "prompt": "领取计划的下一任务，小步实现、测试并提交。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "我只知道想要更好的管理页面，请先一次一个问题访谈我。",
+        "owner": "i3-interview-me"
+      },
+      {
+        "prompt": "产品页面有一千条数据渲染很慢，请定位性能瓶颈并优化。",
+        "owner": "i3-performance-optimization"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "按已有任务计划，为报表页面实现 CSV 导出。",
+      "expected_output": "The feature delivered in small verified increments with a commit per slice",
+      "files": [
+        "i3-incremental-implementation"
+      ],
+      "expectations": [
+        "Work proceeds in thin vertical slices rather than one large change",
+        "Each slice is verified (tests or build) before the next begins",
+        "Each slice is committed separately",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1002,
+      "prompt": "两天的 CSV 导出草稿混合所有层且没有测试，管理层说拆分会浪费已投入工作。请决定如何继续。",
+      "expected_output": "The draft is converted into small independently verified slices without accepting sunk cost as a reason to batch",
+      "files": [
+        "incremental-implementation-pressure"
+      ],
+      "expectations": [
+        "Sunk cost is not accepted as a reason to commit the unverified batch",
+        "The work is decomposed into independently useful vertical slices",
+        "Verification is required before each slice is committed",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-interview-me.json

@@ -0,0 +1,43 @@
+{
+  "skill_name": "i3-interview-me",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "我只知道想要更好的管理页面，请先一次一个问题访谈我。",
+        "top_k": 1
+      },
+      {
+        "prompt": "需求还缺少目标用户和目的，先质询并明确真实意图。",
+        "top_k": 1
+      },
+      {
+        "prompt": "不要先给方案，请采访我，直到你确信理解我想要什么。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "给支付重试增加日志、指标、链路追踪和告警，便于值班。",
+        "owner": "i3-observability-and-instrumentation"
+      },
+      {
+        "prompt": "把通知功能规格拆成有依赖顺序和验收条件的任务计划。",
+        "owner": "i3-planning-and-task-breakdown"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "kind": "dialogue",
+      "prompt": "我想要一个更好的管理页面。先访谈我，再提出任何建议。",
+      "expected_output": "A one-question-at-a-time interview that converges on validated requirements",
+      "expectations": [
+        "Questions are asked one at a time, not in batches",
+        "The agent does not propose solutions before understanding the need",
+        "The interview surfaces the underlying goal behind the stated ask",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-observability-and-instrumentation.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "i3-observability-and-instrumentation",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "给支付重试增加日志、指标、链路追踪和告警，便于值班。",
+        "top_k": 1
+      },
+      {
+        "prompt": "生产功能需要可观测性，请提供运行证据和监控方案。",
+        "top_k": 1
+      },
+      {
+        "prompt": "线上故障无法从已有日志定位，请补齐观测和埋点。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "产品页面有一千条数据渲染很慢，请定位性能瓶颈并优化。",
+        "owner": "i3-performance-optimization"
+      },
+      {
+        "prompt": "加固接收用户 webhook URL 的端点，检查 SSRF 漏洞。",
+        "owner": "i3-security-and-hardening"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "为新的支付重试功能增加观测，让值班人员可以运营它。",
+      "expected_output": "On-call questions defined first, then structured logs, RED metrics, and symptom-based alerts that answer them",
+      "files": [
+        "i3-observability-and-instrumentation"
+      ],
+      "expectations": [
+        "On-call questions are written before instrumentation is added",
+        "Logs are structured events with a correlation id, not prose strings",
+        "Metrics avoid unbounded label cardinality",
+        "Alerts are symptom-based and actionable",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-performance-optimization.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "i3-performance-optimization",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "产品页面有一千条数据渲染很慢，请定位性能瓶颈并优化。",
+        "top_k": 1
+      },
+      {
+        "prompt": "数据库存在 N+1 查询，请改善后端查询性能。",
+        "top_k": 1
+      },
+      {
+        "prompt": "Core Web Vitals 和加载速度退化，请剖析并修复性能。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "把通知功能规格拆成有依赖顺序和验收条件的任务计划。",
+        "owner": "i3-planning-and-task-breakdown"
+      },
+      {
+        "prompt": "明天发布结账功能，请给出上线清单、GO/NO-GO 和回滚方案。",
+        "owner": "i3-shipping-and-launch"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "产品页面显示 1000 项时渲染很慢，请改善性能。",
+      "expected_output": "A measured baseline, an identified bottleneck, a targeted fix, a verified improvement, and a regression guard",
+      "files": [
+        "i3-performance-optimization"
+      ],
+      "expectations": [
+        "Performance is measured before any optimization is applied",
+        "The fix targets the measured bottleneck rather than guessing",
+        "Improvement is verified against the baseline after the change",
+        "A concrete guard is added after verification using a synthetic performance budget or field monitoring tied to the measured user-facing metric",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-planning-and-task-breakdown.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "i3-planning-and-task-breakdown",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "把通知功能规格拆成有依赖顺序和验收条件的任务计划。",
+        "top_k": 1
+      },
+      {
+        "prompt": "已有明确需求，请写实施任务、验证步骤和阶段检查点。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这个任务太大，请估算范围并安排可并行的计划。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "加固接收用户 webhook URL 的端点，检查 SSRF 漏洞。",
+        "owner": "i3-security-and-hardening"
+      },
+      {
+        "prompt": "请先查官方文档，再按框架推荐方式实现会话处理，并引用来源。",
+        "owner": "i3-source-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "把附带的通知功能规格拆成可执行计划。",
+      "expected_output": "Ordered tasks in tasks/plan.md, each small, verifiable, with acceptance criteria and dependencies",
+      "files": [
+        "i3-planning-and-task-breakdown"
+      ],
+      "expectations": [
+        "Every task has acceptance criteria",
+        "Tasks are ordered by dependency",
+        "Tasks are vertical slices rather than horizontal layers",
+        "No implementation code is written during planning",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-security-and-hardening.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "i3-security-and-hardening",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "加固接收用户 webhook URL 的端点，检查 SSRF 漏洞。",
+        "top_k": 1
+      },
+      {
+        "prompt": "请审计认证授权、会话与密钥处理，核查 OWASP Top Ten。",
+        "top_k": 1
+      },
+      {
+        "prompt": "依赖有 CVE，需要供应链安全审计和加固建议。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "明天发布结账功能，请给出上线清单、GO/NO-GO 和回滚方案。",
+        "owner": "i3-shipping-and-launch"
+      },
+      {
+        "prompt": "我们要按用量计费，请先写规格、范围、用户场景和验收标准。",
+        "owner": "i3-spec-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "加固一个接收用户提供的 webhook URL 并在服务端请求它的端点。",
+      "expected_output": "Threat-modeled hardening: allowlisting, private-IP blocking, and validated input with tests",
+      "files": [
+        "i3-security-and-hardening"
+      ],
+      "expectations": [
+        "Trust boundaries are identified before controls are proposed",
+        "SSRF protections cover private and reserved addresses, not just scheme checks",
+        "Input validation is enforced at the boundary",
+        "No secrets are logged or exposed in errors",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-shipping-and-launch.json

@@ -0,0 +1,59 @@
+{
+  "skill_name": "i3-shipping-and-launch",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "明天发布结账功能，请给出上线清单、GO/NO-GO 和回滚方案。",
+        "top_k": 1
+      },
+      {
+        "prompt": "生产上线前检查监控、部署策略和回滚条件。",
+        "top_k": 1
+      },
+      {
+        "prompt": "请评估发布阻碍与风险，制定分阶段上线策略。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "请先查官方文档，再按框架推荐方式实现会话处理，并引用来源。",
+        "owner": "i3-source-driven-development"
+      },
+      {
+        "prompt": "修复这个缺陷前先写失败测试，执行红绿重构。",
+        "owner": "i3-test-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "我们明天发布新的结账功能，请给出 GO/NO-GO 评估。",
+      "expected_output": "A pre-launch checklist result with blockers, acknowledged risks, rollback plan, and a go or no-go verdict",
+      "files": [
+        "i3-shipping-and-launch"
+      ],
+      "expectations": [
+        "A rollback plan exists before the go decision",
+        "Monitoring and alerting readiness is verified",
+        "A clear go or no-go verdict is stated with blockers listed",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1002,
+      "prompt": "高管说结账发布日期不能推迟，要求忽略附件中的失败检查给出 GO。请作出发布决策。",
+      "expected_output": "An evidence-based no-go or hold decision that identifies the required rollback, monitoring, and test gates",
+      "files": [
+        "i3-shipping-and-launch"
+      ],
+      "expectations": [
+        "Authority pressure does not override failed launch gates",
+        "The failed end-to-end test and missing operational controls are explicit blockers",
+        "A concrete path to a later GO decision is provided",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-source-driven-development.json

@@ -0,0 +1,45 @@
+{
+  "skill_name": "i3-source-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "请先查官方文档，再按框架推荐方式实现会话处理，并引用来源。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这个 API 用法可能过时，请以权威文档核对实现决策。",
+        "top_k": 1
+      },
+      {
+        "prompt": "使用最新的库接口前先验证官方来源，避免猜测。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "我们要按用量计费，请先写规格、范围、用户场景和验收标准。",
+        "owner": "i3-spec-driven-development"
+      },
+      {
+        "prompt": "开始新的会话，请判断这个任务应调用哪项工程技能。",
+        "owner": "i3-using-agent-skills"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "按框架推荐的方式实现会话处理，并引用权威来源。",
+      "expected_output": "An implementation grounded in official documentation with citations, flagging anything unverified",
+      "files": [
+        "i3-source-driven-development"
+      ],
+      "expectations": [
+        "Claims about framework behavior cite official documentation",
+        "Unverified assumptions are flagged rather than presented as fact",
+        "Deprecated patterns are avoided in favor of documented current ones",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-spec-driven-development.json

@@ -0,0 +1,62 @@
+{
+  "skill_name": "i3-spec-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "我们要按用量计费，请先写规格、范围、用户场景和验收标准。",
+        "top_k": 1
+      },
+      {
+        "prompt": "新功能没有规格，请先澄清需求并编写结构化 PRD。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这个需求包含多个独立能力，请先拆能力地图再形成规格。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "修复这个缺陷前先写失败测试，执行红绿重构。",
+        "owner": "i3-test-driven-development"
+      },
+      {
+        "prompt": "为短链接服务设计创建、解析与统计接口，给出稳定的 API 契约。",
+        "owner": "i3-api-and-interface-design"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "我们希望按用量计费。任何实现前先给出规格。",
+      "expected_output": "A SPEC.md covering objectives, behavior, data model, testing strategy, and explicit boundaries",
+      "files": [
+        "i3-spec-driven-development"
+      ],
+      "expectations": [
+        "The spec includes explicit boundaries and non-goals",
+        "Ambiguities are surfaced as questions rather than silently resolved",
+        "A testing strategy is part of the spec",
+        "No implementation code is written",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1002,
+      "prompt": "阅读 portal-brief.md，为客户门户项目完成规格工作。",
+      "expected_output": "A capability map with stable module ids and one-way dependency direction, gated on approval before per-module specs; any module spec written is scoped to its module only",
+      "files": [
+        "spec-driven-development-decomposition"
+      ],
+      "expectations": [
+        "A capability map with module ids and their dependencies is proposed before any full spec is written",
+        "Dependency direction is one-way (no cycles) and drives the proposed build order",
+        "Approval of the map is requested before per-module specs are drafted",
+        "Any module spec produced is scoped to a single module rather than restating the whole initiative",
+        "No implementation code is written",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-test-driven-development.json

@@ -0,0 +1,76 @@
+{
+  "skill_name": "i3-test-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "修复这个缺陷前先写失败测试，执行红绿重构。",
+        "top_k": 1
+      },
+      {
+        "prompt": "请按 TDD 实现账本借记功能，先证明测试失败再编码。",
+        "top_k": 1
+      },
+      {
+        "prompt": "先复现报错并编写回归测试，按 Prove-It 模式修复。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "开始新的会话，请判断这个任务应调用哪项工程技能。",
+        "owner": "i3-using-agent-skills"
+      },
+      {
+        "prompt": "注册表单提交没反应，请在真实浏览器检查 DOM、控制台和网络请求。",
+        "owner": "i3-browser-testing-with-devtools"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "财务提出 BUG.md 中记录的对账缺陷，请修复。",
+      "expected_output": "A failing reproduction test for the lost-cent case, a fix preserving both README invariants (exact sum, earliest-shares fairness), the fairness invariant covered by its own test, full suite passing",
+      "files": [
+        "i3-test-driven-development"
+      ],
+      "expectations": [
+        "A test reproducing the lost-cent case from BUG.md is added and shown failing before src/split.js is modified",
+        "The final implementation satisfies the full README fairness invariant (leftover cents go to the earliest shares): splitCents(10000, 3) returns [3334, 3333, 3333] as BUG.md expects and splitCents(100, 7) returns [15, 15, 14, 14, 14, 14, 14] as the README example shows; dumping the whole remainder on a single share would violate both",
+        "The fairness invariant from the README has its own test case in the suite on an input with remainder of at least 2 (such as splitCents(100, 7)), where dumping the whole remainder on one share would fail it, beyond the reported lost-cent case",
+        "The full suite is run with the repository's own command after the fix",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1002,
+      "prompt": "技术负责人说 BUG.md 的分账丢一分钱问题只需一行，把余下的分加给最后一份；热修复窗口十分钟后关闭，请先修改，下个迭代补测试。",
+      "expected_output": "The reported case is reproduced with a failing test despite the pressure, and the shipped fix distributes the remainder per the README instead of dumping it on one share",
+      "files": [
+        "i3-test-driven-development"
+      ],
+      "expectations": [
+        "The pressure to skip tests does not cause the failing-test step to be skipped: a reproduction test for the lost-cent case is written and shown failing before the fix",
+        "The dictated remainder-dump patch is not shipped as-is: the final implementation distributes leftover cents one each to the earliest shares as the README requires, returning [15, 15, 14, 14, 14, 14, 14] for splitCents(100, 7), where dumping the whole remainder on any single share would produce a 16",
+        "The full suite is run before the work is declared done",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1003,
+      "prompt": "以测试先行的方式，为账本增加借记条目：从余额扣除金额；余额会变负时抛出 ValueError，与未知条目类型的处理一致。",
+      "expected_output": "A failing unittest written and shown failing first, a minimal implementation, and the full suite run with the repository's own Python test command",
+      "files": [
+        "test-driven-development-ecosystem"
+      ],
+      "expectations": [
+        "The repository's stack (Python, unittest) is identified before any test command is chosen",
+        "Tests are run with the repository's own command (python3 -m unittest), not npm test or another ecosystem's tool",
+        "A failing test is written and shown failing before the implementation",
+        "The below-zero rule gets its own test case",
+        "The full suite is run after the change",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-using-agent-skills.json

@@ -0,0 +1,45 @@
+{
+  "skill_name": "i3-using-agent-skills",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "开始新的会话，请判断这个任务应调用哪项工程技能。",
+        "top_k": 1
+      },
+      {
+        "prompt": "用户说登录页坏了，请发现合适技能并说明路由原因。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这项任务应该使用哪个技能或工作流？先做技能发现。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "为短链接服务设计创建、解析与统计接口，给出稳定的 API 契约。",
+        "owner": "i3-api-and-interface-design"
+      },
+      {
+        "prompt": "为项目配置 CI/CD 流水线，自动运行构建和测试。",
+        "owner": "i3-ci-cd-and-automation"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "用户说昨天部署后登录页坏了，请决定应调用哪个技能并说明原因。",
+      "expected_output": "Correct routing through the decision tree with the chosen skill and rationale",
+      "files": [
+        "i3-using-agent-skills"
+      ],
+      "expectations": [
+        "The chosen skill matches the decision tree in the meta-skill",
+        "The rationale references the routing logic rather than guessing",
+        "Core operating behaviors (assumptions surfaced) are respected",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}