Implement the bounded Godot opening Company and first-Market preparation flow with deterministic one-shot state, real touch verification, responsive layouts, prototype feedback, and current design regressions.\n\nCo-Authored-By: Codex <noreply@anthropic.com>
4.4 KiB
Phase 9 Godot Vertical Slice Goal
Owner Decision
On 2026-08-12 the Owner accepted P8.5 and authorized the next Godot stage. The runtime must be delivered in separately playable increments; a later increment cannot silently repair or reinterpret an unaccepted earlier one.
Baseline
Phase 8 Owner-acceptance closure:
8583abb65e5ad59d684281e06f5052ebfc2740c6
Decision Enabled
Decide whether the accepted Aetherbound Guild opening and first Market remain clear, responsive and visually coherent when implemented as a real Godot landscape mobile runtime rather than an HTML design prototype.
Delivery Sequence
| Increment | Runtime boundary | Gate before advancing |
|---|---|---|
P9.1 |
Contract/difficulty, stable four Recruit offers, exactly-two Company commit, two Market hires, one equipment purchase/equip, one order swap and readiness receipt. | Owner can complete the real touch flow and explain the resulting Company, Coin and equipment state. |
P9.2 |
Real horizontal automatic battle, pause/speed/inspect and deterministic first encounter. | Owner accepts movement, clarity, causality and feel. |
P9.3 |
Result, permanent casualty, reward, recovery, save/version/migration and second-cycle continuation. | Owner accepts the full runtime loop and persistence. |
P9.4 |
Physical-device project/build and bounded iPhone/Android evidence. | Separate device and packaging authorization. |
P9.1 Owned Scope
- Create the Godot 4.6 landscape runtime under
runtime/. - Preserve accepted IDs and values from P8.1/P8.2.
- Present
CTR-R1-01, three difficulties and four stable offers. - Require explicit inspect and exactly two selected Recruits before review.
- Fix the accepted integrated path to
OFF-03Tomas andOFF-04Sable for the one-tap guided path, while still allowing other legal two-of-four pairs. - Commit the opening once at Company
2/4, Coin52. - Hire Mael and Ilya separately for
14 Coineach. - Purchase
EQ-012 Open-Line Cordfor12 Coin, then explicitly equip one current Company member; the accepted fixed evidence path equips Tomas. - Require one tap-source/tap-destination order swap before the final receipt.
- Finish at Coin
12, Company4/4,EQ-012 -> OFF-03with a visible risk handoff that is locked to P9.2. - Provide visual selection, transaction, error and receipt feedback, captioned prototype SFX, mute, reduced-motion and 100/130% text controls.
P9.1 Acceptance
- Fresh launch starts before Contract selection and no offer is preselected.
- Invalid next/confirm actions explain the missing condition and do not mutate state.
- Four offer IDs remain stable through inspect, select, revise and commit.
- A third Recruit selection is rejected until one selected Recruit is removed.
- Opening commit occurs once and yields Company
2, Coin52. - Mael and Ilya are separate one-shot 14-Coin hire transactions; Company moves
2 -> 3 -> 4and Coin52 -> 38 -> 24. EQ-012purchase and equip are separate; Coin moves24 -> 12and Tomas owns exactly one active item.- Order uses a visible tap-source/tap-destination swap, can be revised before commit, and produces one readiness receipt.
- Real
Input.parse_input_eventScreenTouch drives the automated mobile path; direct callbacks cannot support the touch claim. - Normal rendering covers opening, offer selection, Market, equipment, order
and receipt at
1280x720,844x390and390x844, EN and zh_CN, 130% text, reduced motion and mute without overlap or horizontal overflow. - Focused domain and runtime tests have exact terminal markers and clean logs; no script/parse/resource/import/ObjectDB failure or owned process remains.
Frozen
- P9.2 automatic battle and all enemy outcomes.
- P9.3 casualty, reward, recovery and authoritative persistence.
- Final/bulk character, environment, animation, VFX, music, SFX and voice.
- iOS/Android export, device install, TestFlight/Play, stores and publishing.
- Phase 8 accepted values, identities and transaction boundaries.
Evidence Boundary
Automated evidence may prove deterministic state, input routing, layout, rendering, logs and cleanup. Agent screenshots support visual review only. The Owner alone accepts comprehension, feel, visual quality, sound and willingness to continue.
P9.1 legal terminals are:
Aetherbound Guild P9.1 opening and Market runtime candidate ready
or
Aetherbound Guild P9.1 redesign required: <earliest failed runtime boundary>