diff --git a/README.md b/README.md index eab13d44..6e1c3158 100644 --- a/README.md +++ b/README.md @@ -25,14 +25,18 @@ progression, formulas, and expression must be original. ## Review The Design -The single owner-facing review artifact is the interactive HTML prototype in -[`prototype/site/`](prototype/site/). It shows one subject at a time and links -the complete design package behind these review paths: +The current owner-facing HTML in [`prototype/site/`](prototype/site/) is a +**coverage audit**, not a completed UI prototype. Owner review on 2026-08-10 +proved that generic specification templates were not understandable as game +screens. Its page browser now distinguishes one dedicated page, 40 shared +family mockups, and 41 pages whose UI is still missing. -1. **Core flow:** walk through the 17-step title-to-restoration path. +1. **Flow specification:** inspect the required 17-step title-to-restoration + order; do not treat it as a validated clickable experience. 2. **Eight chapters:** inspect route, battle, and restored-world direction for every chapter. -3. **All screens:** inspect all 82 player-facing pages and their key states. +3. **Page coverage:** inspect all 82 requirements and identify which screens + still need a dedicated composition. 4. **Content:** search all 30 characters, 36 professions, 100 enemies, 320 items, 48 achievements, and 20 collections. 5. **Production and readiness:** inspect the art/audio scope and the gates that diff --git a/docs/prototype/INTERACTIVE_PROTOTYPE_SPEC.md b/docs/prototype/INTERACTIVE_PROTOTYPE_SPEC.md index 93aa85a3..d63e7d56 100644 --- a/docs/prototype/INTERACTIVE_PROTOTYPE_SPEC.md +++ b/docs/prototype/INTERACTIVE_PROTOTYPE_SPEC.md @@ -11,7 +11,8 @@ The prototype must let the owner decide whether: 1. the landscape 2D hand-drawn direction fits the intended game; 2. the player can recognize Guild, company, route, battle, diagnosis, reward, restoration, records, and settings without a card-wall interface; -3. the 82-screen inventory and eight chapters appear complete; +3. the 82-screen requirement inventory and eight chapters are present, while + unfinished UI is labeled as unfinished rather than presented as complete; 4. formation, telegraph, Directive, Cache, Anchor, Strain, profession, and item concepts are sufficiently visible to proceed to a dynamic vertical slice; 5. any page family or chapter direction should be redesigned before runtime @@ -66,9 +67,11 @@ Every screen entry shows: - previous/next page actions plus direct selection from the left list; - a full-size viewing mode without cropping the game canvas. -The mockup renderer uses the canonical shell for the selected prefix and adds -page-specific state. Core flow pages receive more detailed compositions. The -prototype must not imply that all 82 pages have final bespoke raster art. +Owner review on 2026-08-10 rejected the shared-template result as +incomprehensible. The coverage audit found `1` dedicated page, `40` shared +family mockups, and `41` pages without an individual UI composition. A shared +template is not a completed page. Until this gap is closed, the HTML may expose +requirements and coverage but must not call itself a complete UI prototype. ## 4. Compressed Click Path @@ -90,8 +93,10 @@ Title SYS-004 -> Guild transformed GLD-001 ``` -This proves navigation and information hierarchy only. It does not simulate -combat formulas, persistence, pacing, audio, touch feel, or fun. +This currently proves only the required node order. It does not yet prove +navigation comprehension or information hierarchy because several core nodes +still lack their own page design. It also does not simulate combat formulas, +persistence, pacing, audio, touch feel, or fun. ## 5. Visual Assets In This Prototype @@ -121,6 +126,9 @@ legible and do not depend on generated text. ## 7. Prototype Acceptance - [x] All 82 screen IDs appear exactly once in the screen selector. +- [x] Coverage is reported truthfully as 1 dedicated / 40 family / 41 missing. +- [ ] All 82 requirements have page-specific, player-readable UI compositions. +- [ ] All 17 core-flow nodes have dedicated UI and pass owner comprehension. - [x] All eight chapters and 24 chapter screen families are represented. - [x] Content indexes show 30/36/100/320/48/20 exact counts. - [x] Core click path reaches restoration without a dead control. @@ -129,5 +137,5 @@ legible and do not depend on generated text. - [x] Generated concepts remain labeled honestly and carry task provenance. - [x] Local links, image paths, JSON, browser verification, Gallery publication, and Gallery health/share checks pass. -- [x] Owner visual, comprehension, fun, audio, device, and release gates remain - explicitly open. +- [x] Owner comprehension failed on the generic screen presentation; visual, + fun, audio, device, and release gates remain explicitly open. diff --git a/docs/reviews/PRE_DEVELOPMENT_READINESS_AUDIT.md b/docs/reviews/PRE_DEVELOPMENT_READINESS_AUDIT.md index 280aa7e8..cfc8fa02 100644 --- a/docs/reviews/PRE_DEVELOPMENT_READINESS_AUDIT.md +++ b/docs/reviews/PRE_DEVELOPMENT_READINESS_AUDIT.md @@ -4,10 +4,15 @@ Date: 2026-08-10 ## Decision -The complete static design package and owner-facing HTML prototype are ready -for owner review. Formal game implementation remains frozen. This result does -not claim that the game is playable, understandable, fun, visually accepted, -heard, device-verified, packaged, or release-ready. +`FAIL`: the static system/content specifications are indexed, but the +owner-facing UI package is not complete and is not ready for approval. Owner +review on 2026-08-10 could not understand `SYS-001`; inspection proved that the +82 entries were rendered through six shared templates rather than 82 designed +pages. Formal game implementation remains frozen. + +Earliest failed boundary: page-specific visual communication. `SYS-001` +incorrectly inherited a windmill background, save/cache HUD, return action and +`none` button even though its contract is an automatic boot/loading state. ## Verified Design Authority @@ -17,10 +22,10 @@ heard, device-verified, packaged, or release-ready. | Battle and systems | six-person formation, telegraphs, Directives, automation, failure and recovery | specified and cross-checked | | Economy and save | 1,700 authored minutes, five pacing traces, prices, caps, atomic save and corruption handling | static validator pass | | Content | 30 characters, 36 professions, 100 enemies, 320 items, 8 chapters, 48 achievements, 20 collections | complete indexed rows | -| Pages and states | 82 pages, 24 chapter visual families, onboarding, accessibility, localization, errors and exits | complete indexed rows | +| Pages and states | 82 requirements indexed | 1 dedicated page / 40 family mockups / 41 missing page compositions | | Art production | character, profession, enemy, item, environment, UI, animation and VFX identities | production catalog complete; final assets open | | Audio production | 30 music suites, 94 ambience configurations, at least 2,602 bilingual voice assets, 710 SFX identities | production catalog complete; generation/listening open | -| HTML prototype | 11 views, 82-screen selector, 17-step flow, 8 chapters and searchable content catalogs | browser verified | +| HTML shell | 11 views, selector, flow order, chapters and searchable content catalogs | technically browser verified; product comprehension failed | ## Reproducible Local Checks @@ -53,12 +58,11 @@ ABG_PROTOTYPE_BROWSER_OK views=11 screens=82 flow_steps=17 chapters=8 responsive ## Owner Review Order -1. Complete the 17-step core flow and name any step whose purpose or result is - unclear. +1. Do not ask the owner to review the 82-page set again yet. 2. Inspect all eight chapter directions and judge whether each promises a strategically and visually different problem. -3. Inspect the 82-screen map for missing pages, crowded pages, unclear primary - actions, and unsafe exits. +3. Produce dedicated title, Guild, formation, map, route, battle, result, + reward, Anchor and restoration pages before the next owner candidate. 4. Search the complete content catalogs and challenge roles, counters, progression relationships, and production feasibility. 5. Accept, revise, or reject the visual direction and product scope before a diff --git a/prototype/site/app.js b/prototype/site/app.js index 9990886d..8ed9a752 100644 --- a/prototype/site/app.js +++ b/prototype/site/app.js @@ -10,8 +10,8 @@ const state = { const viewNames = { overview: "总览", - screens: "全部页面", - flow: "核心流程", + screens: "页面规格与缺口", + flow: "流程规格链", chapters: "八章画面", characters: "角色图鉴", professions: "职业系统", @@ -25,7 +25,7 @@ const viewNames = { const screenCategoryNames = { ALL: "全部", SYS: "系统", - GLD: "Guild", + GLD: "公会", WRK: "工坊", REC: "档案", WLD: "世界", @@ -35,6 +35,52 @@ const screenCategoryNames = { SET: "设置", }; +const localizedScreenNames = { + "SYS-001": "启动画面", + "SYS-002": "首次无障碍设置", + "SYS-003": "语言与安全区校准", + "SYS-004": "标题首页", + "SYS-005": "游戏存档", + "SYS-006": "新游戏设置", + "SYS-007": "回归摘要", + "SYS-008": "存档恢复", + "SYS-009": "完成度总览", + "SYS-010": "制作人员、许可与数据说明", +}; + +function screenName(screen) { + return localizedScreenNames[screen.id] || screen.name; +} + +function layoutKind(screen) { + const prefix = screen.id.slice(0, 3); + if (screen.id === "SYS-001") return "dedicated"; + if (screen.id === "GLD-005") return "family-formation"; + if (["EXP-002", "EXP-003", "WLD-001", "WLD-002", "WLD-003"].includes(screen.id)) return "family-route"; + if (prefix === "BAT" || ["EXP-004", "RES-001", "RES-002", "RES-003", "RES-004"].includes(screen.id)) return "family-battle"; + if (prefix === "SET") return "family-settings"; + if (prefix === "REC") return "family-records"; + return "missing"; +} + +function coverage(screen) { + const kind = layoutKind(screen); + if (kind === "dedicated") return { key: "dedicated", label: "逐页设计" }; + if (kind.startsWith("family-")) return { key: "family", label: "页面族示意" }; + return { key: "missing", label: "未设计" }; +} + +function reviewCopy(screen) { + if (screen.id === "SYS-001") { + return { + focal: "游戏标志、加载光线、当前载入状态", + action: "无需操作；完成后自动进入首次设置或标题首页", + variants: "首次启动、内容迁移、可恢复载入错误；错误时才显示重试与诊断入口", + }; + } + return screen; +} + const chapterImages = [ "assets/web/ch_ch01.webp", "assets/web/ch_ch02.webp", @@ -141,7 +187,7 @@ function renderOverview() {
- ${metric(counts.screens, "完整页面与状态定义")} + ${metric(counts.screens, "页面需求定义；UI 尚未逐页完成")} ${metric("8 × 3", "章节路线 / 战场 / 修复画面族")} ${metric(counts.characters, "有姓名、有成长弧的角色")} ${metric(counts.professions, "12 基础 + 24 进阶职业")} @@ -269,46 +315,61 @@ function renderRecordsStage(screen, art) {
`; } -function renderGenericStage(screen) { - const prefix = screen.id.slice(0, 3); - const light = prefix === "WRK" || prefix === "GLD"; +function renderBootStage() { return ` - ${stageTop(screen)} -
${escapeHtml(screen.id)} · DESIGN SPEC${escapeHtml(screen.name)}

${escapeHtml(screen.focal)}

-

当前操作

${escapeHtml(screen.action)}

状态与成本可见
取消不会消耗资源
所有拖动都有点选路径
-
- ${light ? "" : ""}`; +
+ +
AETHERBOUND GUILD裂脉远征团

让每一次修复，改变下一段远征。

+
+

正在校验远征档案 · 68%

+ 完成后自动进入，无需点击 +
`; +} + +function renderMissingStage(screen) { + const copy = reviewCopy(screen); + return ` +
+ UI COVERAGE GAP · ${escapeHtml(screen.id)} + ${escapeHtml(screenName(screen))}尚未完成页面设计 +

目前只有页面需求，不能把这块内容当作游戏画面审核。

+
玩家首先需要看见
${escapeHtml(copy.focal)}
页面必须支持
${escapeHtml(copy.action || "无需操作")}
+
`; } function renderGameStage(screen) { const prefix = screen.id.slice(0, 3); + const kind = layoutKind(screen); const art = artForScreen(screen); const light = prefix === "SET" || prefix === "REC"; let content; - if (screen.id === "GLD-005") content = renderFormationStage(screen); - else if (["EXP-002", "EXP-003", "WLD-001", "WLD-002", "WLD-003"].includes(screen.id)) content = renderRouteStage(screen); - else if (prefix === "BAT" || ["EXP-004", "RES-001", "RES-002", "RES-003", "RES-004"].includes(screen.id)) content = renderBattleStage(screen); - else if (prefix === "SET") content = renderSettingsStage(screen); - else if (prefix === "REC") content = renderRecordsStage(screen, art); - else content = renderGenericStage(screen); + if (kind === "dedicated") content = renderBootStage(); + else if (kind === "family-formation") content = renderFormationStage(screen); + else if (kind === "family-route") content = renderRouteStage(screen); + else if (kind === "family-battle") content = renderBattleStage(screen); + else if (kind === "family-settings") content = renderSettingsStage(screen); + else if (kind === "family-records") content = renderRecordsStage(screen, art); + else content = renderMissingStage(screen); - const decorativeArt = art && prefix !== "REC" ? `` : ""; - return `
${decorativeArt}${content}
`; + const decorativeArt = art && prefix !== "REC" && kind !== "dedicated" && kind !== "missing" ? `` : ""; + return `
${decorativeArt}${content}
`; } function screenMeta(screen, index, screens) { + const copy = reviewCopy(screen); + const status = coverage(screen); const previous = screens[(index - 1 + screens.length) % screens.length]; const next = screens[(index + 1) % screens.length]; return `
-
${escapeHtml(screen.id)}

${escapeHtml(screen.name)}

${chip("Design specification")} ${chip("Human review open")}
+
${escapeHtml(screen.id)}

${escapeHtml(screenName(screen))}

${chip(status.label)} ${chip("人类审核未通过")}
-
三秒焦点顺序

${escapeHtml(screen.focal)}

-
唯一主操作

${escapeHtml(screen.action)}

-
状态、异常与退出

${escapeHtml(screen.variants)}

+
玩家首先需要看见

${escapeHtml(copy.focal)}

+
玩家在这里做什么

${escapeHtml(copy.action || "无需操作")}

+
异常与安全退出

${escapeHtml(copy.variants)}

`; } @@ -319,12 +380,16 @@ function renderScreens() { if (!filtered.some((screen) => screen.id === state.screenId)) state.screenId = filtered[0].id; const screen = getScreen(state.screenId); const index = filtered.findIndex((entry) => entry.id === screen.id); + const coverageCounts = state.data.screens.reduce((result, entry) => { + result[coverage(entry).key] += 1; + return result; + }, { dedicated: 0, family: 0, missing: 0 }); return `
- ${viewHeading("82 SCREEN DEFINITIONS", "每一个页面和关键状态", "页面按系统、Guild、工坊、档案、世界、远征、战斗、结果与设置分类。每一项都锁定玩家先看什么、主操作是什么，以及错误和返回怎么处理。")} + ${viewHeading("UI COVERAGE AUDIT", "82 个页面需求，不是 82 张完成的 UI", "当前只有启动页完成逐页设计；部分页面仅有共用页面族示意，其余仍是规格缺口。这里用于识别要继续设计什么，不能作为完整 UI 验收。", `${chip(`${coverageCounts.dedicated} 逐页设计`)} ${chip(`${coverageCounts.family} 页面族示意`)} ${chip(`${coverageCounts.missing} 未设计`)}`)}
${Object.entries(screenCategoryNames).map(([key, label]) => ``).join("")}
- +
${renderGameStage(screen)}
${screenMeta(screen, index, filtered)}
`; @@ -335,10 +400,10 @@ function renderFlow() { const screen = flowScreens[state.flowIndex]; return `
- ${viewHeading("CLICKABLE EXPERIENCE", "从首页到章节修复的完整点击链", "这是压缩的设计原型路径，用来检查玩家是否始终知道当前位置、压力、下一步和退出方式。它不模拟战斗公式或存档。", `${chip(`${state.flowIndex + 1} / ${flowScreens.length}`)} ${chip("无死按钮")}`)} + ${viewHeading("NAVIGATION SPECIFICATION", "从首页到章节修复的流程规格链", "这条链只证明 17 个需求节点和顺序已经定义；其中多个节点仍没有独立 UI，因此它不是可以进行理解或乐趣验收的产品原型。", `${chip(`${state.flowIndex + 1} / ${flowScreens.length}`)} ${chip("UI 未完成")}`)}
${renderGameStage(screen)}
${screenMeta(screen, state.flowIndex, flowScreens)}
- +
`; @@ -467,18 +532,19 @@ function renderReadiness() { ["战斗 / 职业 / 装备", "完整", "Deterministic combat, 12+24 professions, 320 items", "需通过可玩动态切片验证"], ["经济 / 难度 / 存档", "完整", "1700-min authored budget, five traces, atomic save/failure", "公式静态校验通过；运行时未实现"], ["世界与内容", "完整", "30 characters, 100 enemies, 8 chapters, ending/postgame", "数量与链接校验通过；无人工完整试玩"], - ["页面与 UI", "完整规格", "82 screens, 24 chapter screen families, 14 layout families", "本 HTML 等 Owner 视觉/流程审核"], + ["页面与 UI", "未完成", "82 个页面需求已定义；1 页逐页设计、40 页页面族示意", "41 页没有独立 UI；其余页面族也必须逐页深化"], ["美术与动画", "完整清单", "Identity/modular production and CH-01 slice", "仅 4 张概念图；无 final/integrated/runtime"], ["音乐 / 环境 / 语音 / SFX", "完整清单", "30 music, 94 ambience, 2602 voice, 710 events", "未生成、未试听、未授权批量 SFX/music"], - ["HTML 产品原型", "当前候选", "All indexes + compressed clickable core path", "需 Owner 逐页审阅与修改"], + ["HTML 产品原型", "失败待修", "内容索引和响应式外壳可用", "Owner 已证明页面表达不可理解；当前只能用于缺口审计"], ["引擎开发", "冻结", "No Godot project or runtime code", "完整设计 Owner 批准后另开 Goal"], ["设备 / 打包 / 上架", "开放", "No build, signing, device or store action", "必须在运行时完成后分别授权"], ]; + const blockedStatuses = new Set(["冻结", "开放", "未完成", "失败待修"]); return `
- ${viewHeading("PRE-DEVELOPMENT GATE", "现在还没有进入正式开发", "策划与生产规格已经大幅补齐，但 Owner 仍需要先审核页面、八章画面和核心流程。开发不能把‘文档完整’误认为‘游戏好玩’。")} - ${rows.map(([area, status, ready, open]) => ``).join("")}
领域状态已经具备仍然开放
${escapeHtml(area)}${escapeHtml(status)}${escapeHtml(ready)}${escapeHtml(open)}
-

你的最短下一步

先走一遍“核心流程”，再看八章画面和全部页面。把不理解、不喜欢或认为过于复杂的页面 ID 直接记下来。确认这些设计方向后，才适合制作 CH-01 可玩动态切片。

+ ${viewHeading("PRE-DEVELOPMENT GATE", "UI 设计没有完成，不能进入正式开发", "系统和内容文档已经建立，但 82 页 UI 只有 1 页逐页设计。Owner 已确认现有页面难以理解，因此完整产品原型验收失败。")} + ${rows.map(([area, status, ready, open]) => ``).join("")}
领域状态已经具备仍然开放
${escapeHtml(area)}${escapeHtml(status)}${escapeHtml(ready)}${escapeHtml(open)}
+

下一步不是让你继续猜

先逐页完成标题、公会、编队、地图、路线、战斗、结算、奖励、锚点和修复等核心链 UI，再扩展其余页面。新的审核候选必须让页面目的、当前状态和唯一主操作直接可见。

`; } diff --git a/prototype/site/index.html b/prototype/site/index.html index 11607740..3dcdf746 100644 --- a/prototype/site/index.html +++ b/prototype/site/index.html @@ -22,8 +22,8 @@