FLYGAME / PLAYER & ENGINEERING REFERENCE

Playable Slice 1.0 — Evidence Tracker

PLAYABLE SLICE 1.0 / LIVE ACCEPTANCE BOARD · Evidence snapshot November 15, 2026

What will count as a complete playable adventure?

A normal, source-matched game session must connect the planned sequence from the title screen through saving and continuing. Debug-only warp success, fixture simulations and disconnected screenshots cannot substitute for this route.

  • 01 — NEW GAME and ordinary early progression
  • 02 — Waypost reached through gameplay
  • 03 — Great Temple floors 1, 2 and 3 traversed normally
  • 04 — Tideheart milestone and weather interaction observed
  • 05 — SAVE, exit and CONTINUE using isolated, protected battery SRAM
  • 06 — Progress and weather state confirmed after Continue

Current gate status

  • ROM0 / HOME: FULL_ROM_LINK_PASS for one experimental candidate ending at 0x3FCB, 53 bytes within fixed ROM. That candidate's movement behavior is not yet an accepted gameplay pass.
  • F-024 / stack: OBJECT_COMPILE_PASS on local handler frame 41 → 31 bytes. Whole-path stack minimum and actual WARP-related memory safety UNVERIFIED.
  • F-025 / chest: SOURCE-IMPLEMENTED caller-memory result channel with STATIC_PASS regression checks; end-to-end chest session and Save/Continue UNVERIFIED.
  • Mesen isolation: private ROM/NOI identity checks passed offline; genuinely disposable battery SRAM and successful live loaded-ROM identity still UNVERIFIED.
  • BASELINE-PS1: UNVERIFIED. An accepted continuous playthrough remains the decisive milestone.

Why this distinction matters

GBDK compilation can verify that C and assembly link into a cartridge. It cannot prove that a quest interaction is reachable, a chest remains consistent through bank switches, or a player's save survives a complete return to the title screen. This board follows the strongest evidence actually available for each requirement.

What comes next

First protect every emulator session and identify its exact loaded ROM. Then observe real movement/collision, stack minimum and an isolated save-and-continue journey. Only after the complete sequence passes will this board use ORDINARY_GAMEPLAY_PASS for Playable Slice 1.0.

Current known limitations · Development Journal · Engineering Bench


Publication policy: this board is an editorial status snapshot, not an automated runtime test dashboard. The scheduled Editorial Desk must verify newer source evidence before revising its claims.