This is the only entry point for current product documentation. Historical Goals, H5 delivery notes, test-attempt reports and rejected generation notes are not current design authority.

No implementation resumes until the Owner reviews every retained document in this index and explicitly approves the hand-drawn redevelopment plan. Review begins with Section 1; the later sections provide the detailed rule, content and production authority behind those summaries.

1. Review First

Read these six documents in order:

Game Product Contract - what the game is, who it is for, how long it lasts and what completion means.
Systems And Battle - recruiting, formation, automatic combat, professions, equipment and failure.
Page Development Plan - all 50 pages and the exact development order.
Japanese 2D Visual Direction - the only accepted art and UI style.
Hand-Drawn Repair Contract
- what is preserved, replaced and rejected.
Full-Game Roadmap - the route from the current midpoint to the complete local game.
Originality Boundary - what may be learned structurally and what must never be copied.

2. Rules And Persistence

3. Complete Content

4. Detailed Presentation

5. Development Control

These four documents control work after the Owner approves Sections 1-4:

Generated image prompts, task reports, hashes and JSON manifests remain retained as production provenance, but they are not additional product documents for Owner review.

Current Decision

The latest pixel H5 is rejected. Gameplay, content, Save and test work are preserved. The next implementation action, after plan approval, is one real BAT-002 Godot battle screen in the accepted Japanese 2D hand-drawn style.