games-development-ai/docs/memorys/2026-07-28-山海行纪金标签认与可信消费闭环.md
lili f95ab63521
Some checks failed
contract-gates / contract-gates (push) Has been cancelled
docs-gate / docs-gate (push) Has been cancelled
docs(memory): 沉淀山海行纪可信消费闭环
记录地图1金标签范围、r1.1 不可变发布身份、生产 preflight 真 hash 校验和 round-17 历史证据边界,供后续复用与排障。
2026-07-28 20:45:32 -07:00

29 lines
2.3 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# 山海行纪金标签认与可信消费闭环
日期2026-07-28
本次将《山海行纪》地图1《裂谷原》完整20分钟纵切版登记为唯一 active `game_content_gold`。承诺范围是地图1、SFX-only 和当前可重复真玩路径地图25、29兽正式素材、6首 BGM 与后续地图平衡仍是完整版范围外内容。
## 冻结身份
- bundle`game-runtime/games/shanhai-xingji/dist/shanhai-bundle.js`
- bundle SHA-256`17b9073c767faf7990e0bf4563a86d55ffa81121f11e7c8ad37c8b8ce72e8cbd`
- Registry/2 SHA-256`614ab70de698dd31c5d4b289325e3922ecb64ae88f7a9e7a637a4fa134410e1f`
- release/1 SHA-256`506e181f688f082ea34bd7515e4b1c9952b30a1caad1a5799972ba2d7a3d27a5`
- manifest SHA-256`0f600598cfb842b213f7d54ae1be1d07fe277a3e66b3e4ab3ad21b73dea320d9`
- Registry/2`2026-07-28.trusted-release-r1.1`
- release`survivor-gold-release-2026-07-28-r1.1`
- record`gac-shanhai-xingji``role=game_content_gold``lifecycleStatus=active`
round-17 的 r1 bundle`1c760811ec435fe0f3b5ba79aa8c4fcc44119e019b3e1240ce2c51e55e25870b`)只读保留为历史证据。当前生产消费和浏览器验收以 round-18 的 r1.1 为准bundle 改变时不能复用旧 releaseId必须重算 Registry、release、消费回执并更新 SoT。
## 可信消费规则
生产入口通过 `cheap-worker/reference_asset_gate.py``verify_policy` 显式消费 `survivor-gold-v1`。验证器从受信根现场读取 release、Registry/2、policy、bundle、manifest 和 manifest 指向的 25 个文件,在 Writer 创建前复算 expected/observed hash使用 fd/no-follow 和只读内存快照;任一缺件、路径漂移或字节漂移都 fail-closed。当前没有 live 自动路由、R1 私钥签名、部署或 mini-infra 操作。
## 验收结果
正式 528 局门档c1 最低 45%、c2 85%、c3 中位 50%、c4 `|r|max=0.194`。三场景冒烟、54 项山海 Node 测试、43 项金标测试、136 项可信消费测试、135/315 契约正负样本和 docs-gate 均通过。Cheap-worker 为 866 通过、4 个真模型离线测试跳过;跳过项不应被记作失败。
复用本流程时,先在干净候选树连续构建两次并确认 bundle hash 稳定,再按 bundle → Registry/2 → release → SoT/测试的顺序更新;最后必须直接调用生产 preflight 验证 expected/observed而不是只检查 JSON 登记值。