aetherbound-guild/.agent-taskgraph/DECISIONS.md

Decisions

2026-08-10 Product Direction

• Original product: Aetherbound Guild / 裂脉远征团.
• Familiar, readable magical guild and job fantasy; no Dragon Quest or reference-game expression is copied.
• Complete scope: 30 named characters, 12 base jobs, 24 advanced jobs, 100 enemy identities, 8 chapters and 320 equipment/items.
• Target playtime: 25-35 hour first campaign, 60-80 hour build completion and roughly 100 hour full collection/high difficulty.
• Landscape 16:9; full 2D Japanese hand-drawn direction using layered rigs, equipment layers, authored key poses and unique portraits/illustrations.
• Formal implementation begins only after the complete design package, HTML gallery and interactive design prototype pass Owner review.

2026-08-10 Execution Decision

• Use Agent TaskGraph protocol 0.8.0-beta.10.
• Run three parallel non-overlapping design workers, then presentation, integration and an independent reviewer.
• All worker and reviewer sessions use Codex gpt-5.6-sol, xhigh, project-level yolo.
• Native wait_agent is the monitoring mechanism; no shell sleep or passive chat waiting.

2026-08-10 R2 Runtime Recovery

• R1 correctly stopped on a PMO worktree-path mismatch. Goal paths were corrected, context revisions advanced to 2, and dispatch IDs advanced to r2.
• Because the original collaboration follow-up did not yield a valid recoverable ACK, the same local Codex runtime was relaunched through codex exec with unchanged gpt-5.6-sol, xhigh, yolo and isolated worktrees.
• CLI session/JSONL IDs are the r2 identity evidence. R1 draft output is not accepted unless the r2 worker inspects, completes, commits and submits it.

ABG-SYSTEM-REPAIR

时间	决策	决策者	影响
2026-08-10	接受 HAPI reviewer 对 22b21f8 的 FAIL，批准同一 systems-designer 角色进行一次有界前向修复；为保持活跃 batch 的已确认 runtime 与 validator 一致，worker 复用本批 Codex native profile，修复后的独立 reviewer 仍为 HAPI 可见；固定 gpt-5.6-sol / xhigh / yolo	Owner：继续	graph-r2 新增 system_design_repair；Frozen 产品范围不变；表现设计依赖改为修复节点

Stop External Orchestration

时间	决策	决策者	影响
2026-08-10	停止本批 AgentGraph、所有外部 worker/reviewer 和后台监控，后续在当前 Owner 会话直接整合与修复	Owner：停止了吧，就在当前会话进行吧	Batch 01 关闭；候选提交保留；无会话继续执行；不再使用 queue 状态驱动本轮设计工作

Recruit-Line Redesign Batch 02

时间	决策	决策者	影响
2026-08-10	以参考游戏已验证的横向队列、持续招募、装备构筑和自动战斗为玩法骨架；删除固定 30 名剧情角色、关系系统、固定六人、三路线和战中 Directive	Owner	旧产品合同作废，必须前向重写
2026-08-10	完整原创规模采用 12 基础 + 24 进阶 + 6 隐藏职业、36 特性、320 装备、60 神器、100 普通/精英敌人、16 Boss、8 区域	Owner：对可以这样设计	design-spec-r2 冻结
2026-08-10	允许开启多个可见会话；两个无冲突写入 worker 并行，Owner 手动开启的 审计 Aetherbound 复刻差距 会话保留为后置只读 reviewer	Owner	HAPI visible Codex gpt-5.6-sol/xhigh/yolo；UI 工作等待系统与内容验收

Recruit-Line Redesign Batch 02 Parallel Expansion

时间	决策	决策者	影响
2026-08-10	本批可在真实职责和无写入冲突前提下扩展到 10 个以内可见会话；先增设 UX、美术、音频与设计验证四条设计线	Owner：可以再多几个会话，10个以内我觉得都OK	design-spec-r3 / graph-r4；六个 worker 并行，一个独立 reviewer 后置；HTML 与运行时仍冻结

Recruit-Line Redesign Batch 02 Dual Review

时间	决策	决策者	影响
2026-08-11	六条设计线完成后，不再新增重复写作者；新增系统完整性与体验生产两个并行只读 reviewer，PMO 汇总后进入 Owner Gate	Owner：可以再多几个会话，10个以内我觉得都OK	Team rev-4 / graph-r5；项目相关可见会话总量不超过 10；HTML、引擎、最终媒体、打包与发布继续冻结

Recruit-Line Redesign R2 Review Routing

时间	决策	决策者	影响
2026-08-11	接受 Systems R2 对 7054fe6 的 Gate 5 FAIL；保留既有“无隐藏 miss chance”，先定义确定性 action outcome，再并行同步 content/art/audio，不新增 accuracy/evasion 概率系统	PMO，依据 Frozen 可理解性与既有战斗权威	graph-r6；复用原 worker 角色；新固定 revision 后必须使用两个 fresh reviewer
2026-08-11	Experience R2 因 context 引用了不存在的 REFERENCE_ANALYSIS_AND_LESSONS.md 判为 INVALID；不作产品判断、不复用会话	PMO reviewer protocol	修正未来 R3 context 为现存 REFERENCE_RUNTIME_CENSUS.md 与 TRANSFERABLE_STRUCTURE_LESSONS.md

2026-08-11 - Experience R3 Repair Routing

• Decision: accept ABG-V2-EXPERIENCE-REVIEW-R3 FAIL as a product-design failure on immutable d454120.
• Reason: run creation has no provisional choose-two presentation state, party-line direction conflicts, recruit content/art schemas lack a crosswalk, audio omits OUT-006 and miscounts screens, and the lessons authority retains fixed-cast scope.
• Route: reuse the persistent UX, Art, Audio and Validator sessions with disjoint writes; add one visible Reference repair session. Systems R3 continues independently on the immutable source.
• Frozen: no HTML, runtime, final media, packaging or release. Repaired documents require a new immutable revision and fresh experience R4 review.

2026-08-11 - Systems R3 Gate 6 Repair Routing

• Decision: accept the immutable d454120 Systems R3 FAIL and route only the missing fixed-seed anti-dominance proof to the existing Systems role.
• Reason: battle, transaction, formula, pacing and solvency checks passed; the earliest failure is absent executable seed fixtures and policy outcomes.
• Route: one new fixture JSON, one simulation tool and the economy authority only; later integration creates fresh Systems R4 and Experience R4 reviews.
• Frozen: no stochastic accuracy/evasion, unrelated rebalance, content expansion, HTML, runtime, media, packaging or release.

2026-08-11 - R3 Repair Runtime Reconciliation

• Art candidate 7f8d4b4 and Audio candidate 9f63e46 were edited, committed and pushed before PMO observed their exact standalone rev-5 identity ACKs. Their later ACKs reconcile identity but do not erase the process-order deviation or independently accept the product changes.
• Reference candidate 565ba2e reached its legal terminal with clean/upstream evidence. Systems HAPI 22caeb51-307e-41a6-af3e-875b8e37ba6b returned the exact ACK before editing and is active.
• Current TaskGraph state validation now accepts the six current tasks' dispatch/runtime/ACK fields. Remaining errors are pre-existing review-role concurrency/history debt; the installed graph validator also rejects the repository's already-approved fork node kind. Do not expand this bounded repair into a wholesale legacy-ledger or graph-schema migration.