16 KiB
Current Checkpoint
Active Goal: docs/goals/PHASE9_0_BOOT_TITLE_GOAL.md
Active contract: docs/runtime/PHASE9_0_BOOT_TITLE_CONTRACT.md
Active ledger: docs/reviews/PHASE9_GODOT_VERTICAL_SLICE_LEDGER.md
Baseline: b3968b0f41f841efb0f699d8fb04a9bcb958182a
Accepted P8.1 source: 0b4a64fe549af0ff965e654aa4f5fb7f2ff054b4
P8.2 candidate source: 86a8a1adec39de40b4adfee6b01033407e3e3421
Accepted P8.2 closure: d308f8bc14b043ed133ce2d99cbce461aecec81f
Rejected P8.3 source: 5f0cb2695ba149b1efcab27a882ade00a275c6ac
P8.3 documentation closure: fab5eebf4260ab3da42dee8abe63dd7b7588789b
P8.3R1 candidate source: 169e3877fa262da3db7495d61bc77ce061704ae7
P8.3R1 documentation closure: 5f4e4cdadee6e0f6a457ab57a55964f7fd4c38a5
P8.3R2 candidate source: 02eb1e64ad54978b0c04dd9da59c7ed7eb941a87
P8.3R2 candidate closure: 0818c60dcdde3f84ddbd57b0bc81a787e9915e08
Stage: P8_3R2_OWNER_ACCEPTED_P8_4_ACTIVE
The Phase 6 battle, VFX and equipment direction is Owner-accepted. Phase 7 turns the existing 50-screen design inventory into an individually viewable, Chinese-first, production-oriented landscape HTML atlas. Runtime, engine, audio, bulk asset production, device, package and release work remain frozen.
Strongest evidence: fixed-source static design validation, exact
asset-provenance checks, browser interaction and responsive-layout
verification, offline self-contained bundle verification, and agent visual
review. The Phase 7.1 candidate evidence is ignored local evidence at
prototype/gallery/evidence/r7-1-candidate-e23b00b-attempt01/. Its browser log
SHA-256 is
b735e2218321b4452e3ea2a49b0e03d6c2f568cd218fb15f340d9fe635453441;
the 23-row inventory SHA-256 is
a169dbdc4d03eb00a6ffffc447d035cf5cb0a423422af9060d4eaff81d0b2706
and verifies 23/23 from its evidence root. The self-contained HTML bundle
SHA-256 is
64dbe54f94e66d0bff6bcdf17f5852c5c77c8b56b25eef8f30068ab9198f8176.
Phase 7.1 remains the accepted automated design baseline: every Recruit has one active equipment slot and individual run-scoped level/XP capped at level 10. The Owner has authorized Phase 8 as five separately playable experience packages. On 2026-08-12 the Owner reviewed the published P8.1 Contract and receipt flow and explicitly accepted it. P8.2 Market Preparation is now the only active package; P8.3-P8.5 and Godot/runtime development remain frozen.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-1-candidate-0b4a64f-attempt01/. Its nine-file
inventory verifies 9/9 with SHA-256
b076e5990aadb5e2b72ed979e27403a294c17b342c9bbadbad63b460c7fd60f3.
The P8.1 browser log SHA-256 is
c7e9a7278cb99881b51715bc25e3bd3112293ad282b63bc8449c1150653f6729;
the Phase 7 regression log SHA-256 is
af5eb0616e7dc1061f702d392952419701a93b6452475d626fac490d5c8f3aae;
the self-contained bundle SHA-256 is
e5895441d2835a22e9f94d6615c95be7180b7df6983c4611b499efc730feb915.
P8.2 uses the authority price formula rather than the obsolete Phase 7 sample:
each level-1 base Recruit costs 14 Coin, so two separate hire receipts move the
opening balance 52 -> 38 -> 24 and Company 2 -> 3 -> 4 while Line capacity
remains four. It then owns one equipment transaction and one tap-select/tap-
destination order change, stopping before Risk. Fixed clean/upstream source
86a8a1adec39de40b4adfee6b01033407e3e3421 passes the complete P8.2 browser
chain, P8.1 regression, complete Phase 7 browser regression, design validation,
anti-dominance, single-equipment/individual-level and asset-provenance gates.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-2-candidate-86a8a1a-attempt01/. Its 42-row
inventory verifies 42/42 with SHA-256
d41bed33f982b6504f91aaa6830d2ce09422d9b5dbbd70cfdf7c46d08f5b053e.
The P8.2 browser log SHA-256 is
5eab37da40298740b76f598701b983a53584abef4f61e1f0c43bf3210a69d0a6;
the P8.1 regression log SHA-256 is
564964d31a0bb1cf4c2f8ccb3611c8c94863d4f331d67e238851112773016f20;
the Phase 7 regression log SHA-256 is
55616bf1325da8bce24fbe6d52adf002382ee37cd4ce0e7e780b0f0696b53d2f;
and the self-contained bundle SHA-256 is
96751234e01a2c3c66fc4065be2db20517efd50abf0ced18075676ec42080251.
On 2026-08-12 the Owner reviewed the published P8.2 experience and replied
OK. P8.2 comprehension and visual direction are accepted for progression.
P8.3 is the only active package: compare three risks, commit one, observe a
bounded automatic battle, pause/change speed and inspect one causal event.
P8.4-P8.5, authoritative battle simulation, Godot/runtime, audio, device,
packaging and release remain frozen.
Fixed clean/upstream P8.3 source
5f0cb2695ba149b1efcab27a882ade00a275c6ac passes the three-risk selection,
single commit, frozen opening, six-event automatic presentation, pause/speed,
read-only causal inspection and result-withheld terminal gates. It also passes
P8.1/P8.2 and complete Phase 7 browser regressions plus unchanged design,
anti-dominance, single-equipment/individual-level and asset-provenance gates.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-3-candidate-5f0cb26-attempt01/. Its 53-row
inventory verifies 53/53 with SHA-256
3ad48cfa135a29f01f75ed69dc07f6a2037fbf984c3d94b7cae21da2199af1c8.
The P8.3 browser log SHA-256 is
f34ec892e12dfd5022182de2b5f3f68687a77e1066a78aa2fe8e81bdd3ea7e21;
the P8.2 regression log SHA-256 is
3139beb66a7f265a40c29e02518ad63ffa802bb10f9ab819cb62cf7e39060747;
the P8.1 regression log SHA-256 is
c38118d8b66bb1270e625586f5d9ae77af85ae60ae0c1ab88631a2f764fc6a8b;
the Phase 7 regression log SHA-256 is
b2b8329301b944af8a9301da4a4c493007730f66a310e6942de67ba00a3343c8;
and the self-contained bundle SHA-256 is
5989cb87c5e422d26bd1cdc5d2e74db4177090b32540d1cb53b77560bec943e9.
Owner review rejected the prior P8.3 battle presentation because static unit cards and the central event explainer made it read as a timeline board rather than an animated horizontal automatic battle. P8.3R1 is bounded to rebuilding that battle presentation around one continuous ground line with visible advance, attack, projectile, intercept/Guard, hit and sustain motion. The accepted P8.1/P8.2 behavior and the P8.3 risk/commit/event/result boundaries remain unchanged; P8.4 remains locked.
Fixed clean/upstream P8.3R1 source
169e3877fa262da3db7495d61bc77ce061704ae7 replaces the rejected static-card
battle with one continuous horizontal arena. It uses 62 byte-identical accepted
motion-proof frames for the Hearthguard and Riftblade identities, preserves the
other three Recruit identities with explicitly prototype-only motion transforms,
and visibly presents advance, equipment retarget, attack, projectile, Guard/
intercept, hit and sustain states. Pause freezes event and sprite-frame motion;
1x/2x/4x changes presentation speed only.
The authoritative ignored local evidence is at
prototype/gallery/evidence/p8-3r1-candidate-169e387-attempt01/. Its 64-row
inventory verifies 64/64 with SHA-256
336a6e1757470648d269c2206834fc95df2bc67013315d50c1a185cf1fac5b06.
The P8.3R1 browser log SHA-256 is
d86fb7527efc89a9c764ce94a818e71696406c9f9c9c70e54dc0d8ac18d0ea63;
the self-contained bundle SHA-256 is
c8d57710162a928dea583b54786afc58e61ec2d80aa8a546d01259a06d4cd717.
Supporting motion evidence is the 8.76-second 1280x720 WebM at
prototype/gallery/evidence/p8-3r1-motion-review-169e387-attempt02/ with
SHA-256 55f7389afb08efa3a7e7b61b38618a1ffa6f4f850a533d8107bfba27944cdb3a.
Owner review rejected P8.3R1 because the units animated in fixed positions but did not visibly advance to collision, stop at contact, preserve a rear healer and ranged attacker, or replace a fallen frontline footprint. P8.3R2 is the only active repair. It must bind visible geometry and HP changes to one state chain: two-sided entry, collision stop, post-contact melee, Kindhand healing an injured ally, Farstring attacking from the rear, a separately labeled PF-B06 spell-language demonstration that does not add a fifth Company member, and one no-respawn frontline replacement. Victory/defeat, formal casualty, reward, recovery and P8.4 remain frozen.
Fixed clean/upstream source 02eb1e64ad54978b0c04dd9da59c7ed7eb941a87
passes the P8.3R2 browser chain from an isolated Git archive. Both formations
enter from opposite sides; one explicit contact line stops melee translation;
Wayrunner/Hearthguard act after contact; Kindhand raises Mael from 72 -> 88
HP from the rear; Farstring lowers a legal rear target from 100 -> 72 HP; an
enemy-side PF-B06 demonstration uses distinct charge/bolt/impact language;
and a zero-HP front stays down while the next living enemy advances to the same
contact footprint without respawn or Reserve entry. Pause freezes position,
event, frame and projectile time; 1x/2x/4x changes presentation speed only.
Attempt 01 is retained append-only as INVALID_AUDIT_COMMAND because its
inventory verifier ran from the wrong directory after all product commands.
Fresh attempt 02 is authoritative at
prototype/gallery/evidence/p8-3r2-candidate-02eb1e6-attempt02/. Its 68-row
inventory SHA-256 is
179b4ed720ac9d6e1da8e9955096572572c44528909fa4a38c280dc901b62d79;
the P8.3R2 browser log SHA-256 is
730a07358c1353ab80ab0509fee1e2694efae68d14f5cfe31b629e5ec2950ff4;
and the self-contained bundle SHA-256 is
bd73e97c48fb967ce638d252ae2eecf6f3d5342afaef7e5c2640074fb1882e81.
The continuous 10.96-second 1280x720 motion review is at
prototype/gallery/evidence/p8-3r2-motion-review-02eb1e6-attempt01/, WebM
SHA-256 69fb297fc3f0b3d6d0cc77439382c1f785eb17897122daf57ac280f4aa39b5d6.
P8.1/P8.2, the complete 50-screen atlas, design counts, anti-dominance,
single-equipment/individual-level and 96-asset provenance regressions pass.
On 2026-08-12 the Owner reviewed the published P8.3R2 experience and replied
好可以了. This accepts the visible frontline behavior and comprehension
boundary for progression to P8.4. It does not grant final animation, audio,
authoritative combat, Godot/runtime, device, packaging or release acceptance.
P8.4 Result and Recovery is now unlocked but has not started. It owns only the visible victory/defeat diagnosis, permanent casualty, reward, replacement and next-Market handoff defined by Phase 8. P8.5 and all production/runtime/release work remain frozen.
P8.4 fixed source f1488655ac677fc8260779a27f0628347e4d6920
is pushed clean/upstream and passes fresh fixed-source attempt 02. The
interactive package now proves diagnosis-first result reading, one permanent
Ilya casualty, exact 14 Credit and returned EQ-014, a stable independent
reward choice, three independent recovery responses and a choice-derived next-
Market ledger. P8.1-P8.3R2, the 50-screen atlas and all current design/economy/
loadout/provenance regressions pass.
The authoritative ignored evidence is at
prototype/gallery/evidence/p8-4-candidate-f148865-attempt02/. Its 75-row
inventory SHA-256 is
cd11540e6ea76cb5882d8318e8a4f79dbd899b8c25fcd1ee512742efbc95ff34
and verifies 75/75. The P8.4 browser log SHA-256 is
af5ef09e3e97d57f386eb8608dbe0f91d685589710613d2c821a00d6054f4d62;
the self-contained bundle SHA-256 is
19a1431b46152d90f08361bcc56b9c14099a3bcbfe429ea716780ba1a2c15eb2.
Fixed-source attempt 01 remains INVALID_AUDIT_COMMAND and is not reused.
On 2026-08-12 the Owner reviewed the published P8.4 experience and replied
OK了. P8.4 comprehension, visual direction and choice flow are accepted for
progression. This does not grant human fun, authoritative combat/save, final
media/audio, Godot/runtime, device, packaging, store or release acceptance.
Stage: P8_4_OWNER_ACCEPTED_P8_5_ACTIVE
P8.5 fixed source f1e93aa453406c6826b4758dc72d9c5520324ae9 is
pushed clean/upstream and passes fresh isolated-archive attempt 02. The
?package=p8-5 prototype joins the accepted opening, Market, risk, dynamic
battle, result and recovery across two consequential cycles. Ilya's casualty,
returned EQ-014, AR-043 and Credit-funded Vela are inherited; the Owner then
decides whether Vela equips EQ-014 before choosing between Open Span and
Needle Rain and observing a distinct second dynamic battle.
The authoritative ignored evidence is at
prototype/gallery/evidence/p8-5-candidate-f1e93aa-attempt02/. Its 21-row
inventory verifies 21/21 with SHA-256
d7786c48b1b83b56cbc13f2d51970122307e19aeaf0a9a7b137bb4aa4de7a6a2;
the P8.5 browser log SHA-256 is
97e1b6b33677684754c599cb94bc8871f14bd7102c2e107be9cb1e6025420b67;
the self-contained bundle SHA-256 is
20d66e39270b51d82716629b8affc48c0edb6064ee1c8c6c8d87c54b0fe81aaa.
Attempt 01 is INVALID_HARNESS_TERMINAL and is not reused.
Stage: P9_0_BOOT_TITLE_CANDIDATE_READY
On 2026-08-12 the Owner reviewed the published integrated loop and replied
这个OK了. Phase 8 comprehension, visual direction, choice flow and the
second-cycle continuation handoff are Owner-accepted. Prototype Web Audio cues
remain temporary and human listening is not claimed. Authoritative combat/save,
final media/audio, Godot/runtime, device, packaging, store and release remain
frozen and require their own evidence.
Owner authorization on 2026-08-12 opens Phase 9 as four separately accepted
runtime increments. P9.1 alone is active: implement the accepted opening
Company and first-Market preparation in a landscape Godot 4.6 project under
runtime/. P9.2 battle, P9.3 result/recovery/persistence, P9.4 device delivery,
final media, packaging, stores and release remain frozen.
P9.1 fixed product source
e7eb408e0e07200dd8e65f7226478c0383036371 is pushed clean/upstream. It
implements Contract/difficulty, four stable Recruit offers, an exactly-two
opening Company, separate Mael/Ilya hires, EQ-012 purchase/equip, one visible
Party-order swap and a final readiness receipt. It stops before battle.
Fresh isolated Git-archive evidence passes:
ABG_P9_1_DOMAIN_OK cases=40 final_coin=12 company=4 commits=6;ABG_P9_1_TOUCH_OK touch=25 fallback=0 direct=0 locale=en text_130=true reduced_motion=true mute=true final_coin=12 company=4;ABG_P9_1_LAYOUT_OK fixtures=18 viewports=3 states=6 locales=2 text_130=true;ABG_P9_1_RUNTIME_CAPTURE_OK frames=6 touch=19 fallback=0 direct=0.
The fixed-source bundle is retained at
runtime/evidence/p9-1-e7eb408-attempt01/. It contains six normal-render
states at each exact native size 1280x720, 844x390 and 390x844; the latter
two are explicitly domain-fixture render evidence and make no touch claim.
The 28-row evidence inventory SHA-256 is
7ff16f1a231e6c76dba0ec0545ea112f0afcc87f611b2ceb7ea953bbe7d22384.
Strict script/parse/resource/import/ObjectDB/RID diagnostic scan is clean.
Existing design validation, five-seed anti-dominance, 320-equipment one-slot
contract and 96-asset provenance regressions also pass. Agent visual review
found the six required states readable at all three sizes after repairing the
initial hidden heading, orphan HUD node and Party-card layout defects.
Human comprehension, choice quality, visual acceptance, fun and listening are still Owner gates. Physical-device, P9.2 battle, P9.3 persistence/recovery, packaging and release remain open/frozen.
Owner sequencing decision: the prior P9.1 candidate is preserved but not
Owner-accepted. Real implementation must now proceed one screen boundary at a
time, starting before run setup. Current P9.0 owns only SYS-001 cold boot and
the no-run SYS-003 Title. Start New Game may enter the preserved Contract
page but cannot alter its authority. P9.1 Owner review and P9.2 remain frozen.
P9.0 fixed product source
f881920b1be29933169950429d4e55d8cac825d8 is pushed clean/upstream. Fresh
isolated Git-archive attempt runtime/evidence/p9-0-f881920-attempt01/ passes
the ordered nine-resource Boot, visible 9/9 verified terminal, no-run Title,
five parsed ScreenTouch path with fallback/direct zero, keyboard/controller
initial focus, six layout fixtures and six normal-render frames at exact
1280x720, 844x390 and 390x844. P9.1 domain/touch/layout regressions and
the current design, anti-dominance, single-equipment/individual-level and
96-asset provenance authorities also pass with zero strict diagnostic markers.
The evidence content inventory verifies 27/27 with SHA-256
3c34f1742357d0cc57e8c4c59124133b8fb92de0a2dec01a90b2bbcf4ffb8318;
the structured audit SHA-256 is
5f2951c9f488760913a6fe7c67f96909fbce45bbaf3f6277f2346847428854f7.
Automated, runtime and agent visual gates pass. Owner understanding, visual
acceptance, fun, listening and willingness to continue remain open. Physical
device, packaging, store, release and every later page remain open/frozen.
Shortest next action: Owner plays the fixed P9.0 Boot and Title, then accepts it or reports the earliest confusing or weak entry boundary. Do not start the New Game setup page automatically.