Repository navigation
V1.14
Kim_Service V1.14
English
Affected components
Agent Teams Playbook 4.10.0, SOP Runbook 0.2.0, Memory 3-Layer 1.2.0, Delivery Verifier 0.4.0, the task-browser client configuration, and the Chinese and English READMEs. The collection still contains 71 components and 86 searchable task capabilities.
User-visible changes
- Keep the context with the work. The team playbook and runbook can carry the company's Work identity, current context, accepted version, decision references and receiving receipt across people and conversations. A company can start with one member and keep the same handoff method as the team grows.
- Check what was delivered and what was adopted. Delivery Verifier's optional Work handoff check reads the actual artifact bytes, binds their hashes to the Work and run, and checks the adopted version and matching receiving receipt. Produced, verified, adopted and effective remain distinct outcomes.
- Turn completed work into reusable experience. Existing memory and runbook methods retain adoption reasons, failure cases, applicability, expiry and reuse feedback as candidates for organizational knowledge. The host keeps responsibility for authorizing adoption and scheduling any later review.
- Choose the client explicitly. The team installer uses an explicit or configured destination, including a supplied Skills directory. Memory records the actual host separately from the model. The task browser also offers Gemini CLI and MiniMax Code when preparing a request; a display choice does not claim that a native adapter or model connection has been installed.
- Understand the whole flow in the README. Five animated diagram topics in both languages explain the capability map, collaboration, Work continuity, layers and delivery. Their titles and ending notes are centered, and reduced-motion views stay readable. The complete first-task walkthrough, editable examples, client setup, DSH, ZCode and Meta_Kim instructions now live together in each README.
- Follow one source for each responsibility. The README maps application orchestration, data contracts/configuration and presentation to their existing directories, and explains which source owns each fact. Business parameters and client choices come from configuration; generated catalogs and pages follow their existing source files.
Breaking changes and migration
Update the checkout with git pull --ff-only, then reopen the task browser or docs/start.html. If using the team installer, provide the intended client target or a configured Skills directory; an omitted target no longer selects Claude implicitly. Existing tasks without Work context continue to use their original path.
Refresh installed capability packages using the DSH instructions or ZCode instructions. The downloadable packages are Kim_Service-DSH-V1.14.zip and Kim-ZCode-V1.14.zip; the Kim ZCode plugin version is generated from VERSION as 1.14.0. The combined ZCode package uses the declared Meta_Kim v3.11.0 release.
Verification
Focused tests exercise real file hashes, Work/context/run mismatches, adopted-versus-produced versions, receiving receipts, explicit installation destinations and separate host/model provenance. Meta_Kim receipt output was checked through the actual Service verifier. Synthetic cases and package/loading checks retain their measured scope; they do not authenticate a caller's business decisions or establish unperformed native model execution.
The final source commit must pass the normal main-branch repository and browser checks. The release workflow then builds source, DSH and ZCode packages from their declared source revisions, checks the candidate against the previous public ZCode bundle, and verifies uploaded asset sizes and SHA-256 digests. Its final run links and manifests accompany the GitHub Release.
Source revisions
The previous public collection is V1.13. This release includes the Work, runtime-selection and README implementation published in a12723c0. The V1.14 tag, SOURCE-REVISION.txt and package manifests identify the final Service release commit; the combined ZCode package separately records the exact Meta_Kim v3.11.0 source. Component versions, licenses and provenance remain with their individual methods.
简体中文
更新范围
Agent Teams Playbook 4.10.0、SOP Runbook 0.2.0、Memory 3-Layer 1.2.0、Delivery Verifier 0.4.0,以及任务浏览器的客户端配置和中英文 README。合集保持 71 个组件、86 项可搜索的任务能力。
使用时有哪些变化?
- 上下文跟着事情走。 团队协作和操作手册可以携带公司的事项标识、当前上下文、采用版本、决策引用和接收回执。换人、换会话后,仍能按同一件事交接;公司从一个人发展到多人时,可以沿用这套方法。
- 分清交付了什么、采用了什么。 Delivery Verifier 的可选事项交接检查读取真实成果文件,把文件校验值绑定到对应事项和运行,再核对采用版本和接收回执。产出、验证、采用和效果分别记录。
- 把做过的事整理成可复用经验。 在已有记忆与操作手册方法中保留采用理由、失败案例、适用范围、有效期限和复用反馈,形成组织知识候选。采用授权和后续整理时间由实际业务宿主负责。
- 客户端由本次配置决定。 团队安装器读取明确指定或已配置的安装目标,也支持提供 Skills 目录;记忆记录把实际宿主与模型分别保存。任务浏览器新增 Gemini CLI、MiniMax Code 请求选项,界面选择与真实适配器、模型连接状态分别说明。
- 在 README 里看懂完整流程。 五组主题图各有中英文动态 SVG,说明能力地图、协作、事项接续、分层结构和交付。标题与结尾说明居中,减少动画时仍可阅读。首次任务、可编辑示例、客户端接入、DSH、ZCode 和 Meta_Kim 的完整使用方法集中到各语言 README。
- 各层职责和数据来源说清楚。 README 对照真实目录,说明应用编排、数据合同与配置、展示各自负责什么,哪些事实以哪个来源为准;业务参数和客户端选项读取配置,目录与页面沿用已有的单一源生成方式。
怎样更新?
运行 git pull --ff-only,再打开任务浏览器或 docs/start.html。使用团队安装器时,明确指定客户端目标或配置 Skills 目录;省略目标时不再默认安装到 Claude。已有不带事项上下文的任务继续走原有路径。
已安装的能力包按 DSH 接入说明或 ZCode 接入说明更新。下载包分别为 Kim_Service-DSH-V1.14.zip 和 Kim-ZCode-V1.14.zip;Kim 的 ZCode 插件版本由 VERSION 生成,为 1.14.0。组合 ZCode 包采用发布配置指定的 Meta_Kim v3.11.0。
怎样检验?
针对性检查覆盖真实文件校验值、事项与上下文及运行的错配、采用版本与产出版本的区别、接收回执、明确的安装目标,以及宿主和模型来源的分别记录。Meta_Kim 的实际回执也通过 Service 验证器进行了交接检查。合成案例和包加载检查保留各自验证范围;业务决定的真实性和未执行的原生模型调用另行记录。
最终源码提交须通过正常的主干仓库和浏览器检查。发布流程随后从指定源码构建源码、DSH、ZCode 包,与上一公开 ZCode 包核对内容和版本,再回读上传资产的大小及 SHA-256 校验值。最终检查链接与包内清单随 GitHub Release 一起保存。
来源与历史
上一公开合集是 V1.13。本版包含 a12723c0 已提交的事项交接、客户端选择和 README 改进。V1.14 标签、SOURCE-REVISION.txt 和包内清单标识最终 Service 发布提交;组合 ZCode 包单独记录所使用的 Meta_Kim v3.11.0 精确源码。各组件保留自己的版本、许可证和来源。
Checks and downloads
-
Downloadable packages, source revisions and SHA-256 checksums are attached below.