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.
• UX 388d90b, Art 7f8d4b4, Audio 9f63e46, Reference 565ba2e, and Validator ec5e234 passed PMO write-scope/evidence inspection and were integrated without conflict as 14ea46e, 03547a7, 7071887, 96ea49a, and 8a6f0c8. This is integration, not R4 or Owner acceptance.
• Systems cb53794 was integrated as b65646c; anti-dominance self-test and canonical replay pass. Combined validation then exposed three validator-only false negatives against real repaired prose/tables while its generated fixture remained green. R4 is blocked on a two-file H1 parser/regression repair; product authorities remain frozen.

2026-08-11 - H1 Integration Acceptance And R4 Freeze

• H1 candidate 49e128f changes only the validation contract and executable; PMO integrated it as bcb2931 and independently reran the combined validator and anti-dominance gates.
• Text and JSON validation return zero diagnostics, the validator self-test remains 20 cases, the five contradiction mutations remain rejected, and the five fixed policy seeds preserve a non-dominant winner spread. Result SHA-256: 17154371d4b93035296d1219f012f381af2e10a5f2c1b3f66bcfcd7ad4d85352.
• Create one PMO documentation closure and use that exact pushed revision as the sole immutable source for fresh Systems R4 and Experience R4 reviewers. No R1-R3 partial judgment may be reused as PASS.
• HTML, engine work, final media, packaging and release remain frozen. Dual reviewer PASS leads only to PMO synthesis and the Owner design gate.

2026-08-11 - R4 Review Failure Routing

• Accept Systems R4 FAIL on immutable db932cf: provisional generated Recruits are selected before the only declared run seed exists, so offer reproduction, selection receipts and crash retry are undefined.
• Accept Experience R4 FAIL on the same immutable source: PF-H01..H06 content mechanics/production briefs and art parent/silhouette/motion bindings are inconsistent, with unresolved-binding language still present.
• Route two disjoint minimal repairs in parallel: seed/transaction authority across the exact product/content documents, and hidden-profession binding inside the art catalog only. Do not broaden balance, content count, UI, audio, HTML, runtime or media scope.
• After integration, add deterministic validator negatives for both R4 contradiction classes and create a new fixed revision. Only fresh dual reviewer PASS may reach the Owner gate.

2026-08-11 - R5 Repair Attempt-1 Identity Invalidation

• Both attempt-1 repair sessions edited before returning the exact standalone revision-bound IDENTITY_READY; PMO STOP messages did not prevent later work. Both sessions are archived and their runtime evidence is retained as runtime-evidence-attempt1-invalid.json.
• The run-creation attempt-1 dirty worktree is preserved unchanged as invalid history. Hidden-art commit c558d19c1c96a07ab9e7caa23f495875126bc113 is explicitly forbidden from integration.
• One final attempt is authorized under the existing failure route: fresh clean -a2 worktrees at 0b0f6ad, context revision 2, dispatch attempt 2, exact identity ACK before any edit. A second identity-process failure stops the branch and requires Owner action.

2026-08-11 - R4 Repair Integration And H2 Route

• Attempt-2 workers returned exact identity ACKs before any edit, stayed within the three-file transaction scope and one-file hidden-art scope, pushed clean candidates ad0a57d and fef9057, and were archived after their legal terminals.
• PMO integrated them as bba0c43 and 8102bd2. This closes the two bounded repair nodes only; it does not grant complete design or Owner acceptance.
• Continue to the approved v2_r4_validator_h2 node, then freeze one new source for fresh Systems R5 and Experience R5 reviews. HTML, engine, media production, packaging and release remain frozen.

2026-08-11 - Validator H2 Staffing

• Add one fresh task-scoped design-validator-r5-h2 role under Team rev-8 rather than reviving the retired H1 validator identity.
• H2 owns only the validation contract and executable. It must preserve the 20 existing self-test cases and add exactly four isolated R4 contradiction cases before any R5 reviewer is created.

2026-08-11 - Validator H2 Attempt-1 Invalid

• HAPI 0ab9a014 passed runtime verification but did not emit the required exact standalone identity ACK as its first agent response. PMO observed a still-clean worktree, sent STOP, archived the session and classified the attempt INVALID_IDENTITY_PROCESS.
• No H2 edit, test, commit, push or judgment exists. R4 product repairs remain integrated at 8102bd2; R5 dual review remains blocked on H2.
• The graph/Goal limit is 1/1. A fresh attempt requires Owner authorization to advance the dispatch/context and max-attempt boundary.

2026-08-11 - Validator H2 Attempt-2 Recovery Authorized

• Owner explicitly answered OK的啊继续吧, authorizing the H2 attempt boundary to advance from 1/1 to 2/2 and a fresh replacement session.
• Retain attempt-1 files and runtime evidence as immutable INVALID identity-process history. The retired design-validator-r5-h2 role and archived HAPI 0ab9a014 must not be reused.
• Add task-scoped replacement role design-validator-r5-h2-a2 under Team rev-9, a new worktree/branch, context revision 2 and dispatch attempt 2. Exact standalone IDENTITY_READY remains a hard pre-edit gate.
• Product scope and acceptance do not change: only the validation contract and executable may change, exactly 24 self-tests are required, and fresh R5 dual review remains downstream. HTML, engine, media, packaging and release stay frozen.

2026-08-11 - Validator H2 Attempt-2 Identity Invalid And Exhausted

• HAPI 2cf38e48-f8f9-4c61-adff-b822831c17c7 passed pre-dispatch runtime verification and received the generated rev-9 bootstrap. Its first agent response was an analysis sentence rather than the exact standalone IDENTITY_READY.
• The real 90-second HAPI timer/observe cycle (functions.wait cell 1986) exposed the mismatch. PMO sent STOP, confirmed the fresh worktree remained clean at b0e3475, and archived the session before any validator edit, test, commit or push.
• Classify attempt-2 as INVALID_IDENTITY_PROCESS; it makes no product or validator judgment. The H2 2/2 limit is exhausted, so R5 reviewers remain uncreated and the queue stops for a new Owner decision.

2026-08-11 - Pre-dispatch Recovery Does Not Consume Product Attempts

• Owner directed PMO to continue without repeatedly requesting authorization for identical process recovery.
• Correct the earlier accounting: a verified HAPI session that fails identity before ACK, stays outside active, and leaves the Goal worktree clean with zero edits/tests/commits does not consume graph.max_attempts. Both prior H2 sessions are retained as INVALID process history; H2 product execution remains 0/2.
• PMO may automatically create another fresh session when runtime, machine, model, effort, permission, visibility, write scope, cost and Human Gates are unchanged. Any product edit, scope/cost/permission expansion, paid action, packaging or release boundary still requires the normal gate.
• Recovery 3 uses a two-stage dispatch: first message carries only Role/Team/Goal/Context/continuity identity and requests the exact ACK; after ACK is observed and recorded, PMO sends the rendered full Goal bootstrap.

2026-08-11 - Validator H2 Integrated And R5 Review Unblocked

• Recovery-3 HAPI 1546960c-baf0-4a36-bd71-b1c39bc577b7 returned the exact rev-10 ACK before any read/edit, then completed the bounded two-file Goal.
• Candidate fb20b663df97bb685887e5bef9bb6a3256fa7580 changes only the validation contract and executable. It reports cases=24, integrated errors=0, byte-identical JSON SHA-256 4feb0666acc639a163fefadda40a4cda3a6e5caf0db58fa01432c773ec8d6e38, five anti-dominance seeds and all four isolated R4 diagnostics.
• PMO confirmed exact scope, preserved prior gates, integrated the candidate as 7dc584d62fc4323746c927f5dc370e77f992f0c7, pushed clean/upstream and archived the worker.
• Freeze one new documentation closure as the shared immutable R5 source. Create fresh Systems R5 and Experience R5 read-only reviewers; neither may inherit R4 PASS/FAIL as current judgment.

2026-08-11 - R5 Dual Independent Review Staffing

• Use closure 69f6715b6f47b507fb07436ee1edf77df7e5adab as the one immutable review source containing integrated H2 7dc584d and its PMO closure.
• Add fresh task-scoped Systems R5 and Experience R5 reviewer roles under Team rev-11. Both use visible HAPI Codex gpt-5.6-sol / xhigh / yolo, separate worktrees and zero repository writes.
• Systems reruns all gates from zero with the repaired seed/draft/promotion transaction. Experience reruns all gates from zero with exact hidden-profession production bindings. R4 findings are history, not current PASS.
• A PASS from one reviewer cannot compensate for FAIL/INVALID from the other. Only dual PASS proceeds to PMO synthesis and Owner design review.

2026-08-11 - Experience R5 Environment Recovery

• Experience R5 attempt-1 used zsh special variable path in its first archive-verification harness and failed before source judgment, then continued after PMO STOP. Classify the whole attempt INVALID and archive HAPI c52000b5-2021-48cb-8d68-299f36876b8c.
• Its assigned worktree remained clean at e4ef2b0; no product judgment or repository write is reusable. Automatically create one fresh replacement reviewer on the same immutable source and unchanged read-only Goal.

2026-08-11 - Final Design Package Closure

• Owner explicitly prioritizes fast completion of the complete pre-development product package and final reviewable output, not engine implementation.
• Preserve Experience R5 Gates 1-7 PASS and repair only its earliest real blocker: exact RG-01..08 to ART-REG-01..08 production mapping plus validator regression coverage.
• In parallel, replace the superseded 82-screen coverage audit with the current-authority 50-state landscape HTML prototype. No engine, bulk final media, packaging or release work is authorized.