Sylpheed/authored/flow.json

{
  "format": "sylpheed.flow/1",
  "_": [
    "The boot sequence. AUTHORED, and it has to be: HANDOFF Q6 closed this with a",
    "negative -- the order is in none of the four places it could have been. It is",
    "not in config.ini's empty [SYSTEM], not in the movie manifest (which carries",
    "assets, not transitions), not in a persistent GamePart field (the requested id",
    "lives only as a stack argument in flight), and `GP_ADVERTISE_DEMO` has zero",
    "xrefs of any kind. A transition is a call with a name argument, chosen by code.",
    "",
    "So this file REPRODUCES AN OBSERVATION. The sequence below is what the RE",
    "agent watched the game do, not what any file on the disc says it does. Nothing",
    "here may be presented as decoded."
  ],
  "boot": [
    {
      "screen": "publisher_logo",
      "why": "The SQUARE ENIX wordmark is the first thing the boot shows -- RE agent, 2026-08-29. Entry 10 of the pair; 13 is its region twin and the port shows one, not both."
    },
    {
      "screen": "developer_logos",
      "why": "GAME ARTS / SETA / studio anima, after the publisher wordmark. HANDOFF Q2."
    },
    {
      "video": "ADV",
      "why": "HANDOFF Q9, DECODED from the movie manifest: ADVERTISE_MOVIE -> ADV.wmv, and the boot intro and the attract movie are the SAME asset -- there is no separate boot slot. Its POSITION here (after the developer logos, before the title) is measured, not decoded: it is the order the RE agent watched the game boot in.",
      "skippable": true,
      "skippable_why": "HANDOFF Q9: one (A) press skips a movie -- measured, title reached at 57 s against a 193 s baseline."
    },
    {
      "screen": "title",
      "overlay": {
        "screen": "press_start",
        "after_settle_seconds": 2.13,
        "why": "MEASURED, 2026-08-29, docs/re/title-plate-delay-measured.md on branch auto/no-disc-and-menu-captures at fb536df (NOT yet on main when this was written). The boot title shows build 4 ALONE, and the `PRESS (A) BUTTON` plate -- build 2 -- is composited over it 2.13 s later. Two independent boots of the real game agree to 6 ms. This is the ONE case in the port where two builds are drawn at once.",
        "measured_from_why": "The 2.13 s is timed from the frame build 4's own build-in animation FINISHES, not from the frame the title art first appears. That distinction is the finding, not a detail: measured the other way the two runs differ by 0.48 s, because the build-in itself ran 1.64 s and 2.13 s and the emulator's frame pacing during an animation is not the game's clock. A number taken from the wrong instant here looks exactly like a measurement.",
        "not_a_fade_in_why": "The alternative -- that the plate was there all along, pulsing too dim to see -- was tested and refuted on two observables. The plate's declared alpha never exceeds 0x50, so a thresholded glyph counter could in principle miss a dim phase; it does not. The count sits at EXACTLY 154 with zero variation for 1.99 s / 2.13 s and then swings 714-1520, and the surface mean is flat to +/-0.03 across the plateau. A pulsing overlay moves the frame mean.",
        "scope_why": "Attached to the BOOT STEP, not to the `title` screen, and that is deliberate. What was measured is the boot title. Whether the title shows the plate when it is REACHED AGAIN -- by (B) from the main menu, or after the attract movie -- is not measured, and putting the overlay on the screen would quietly claim it is. See docs/port/BLOCKED.md.",
        "no_pulse_why": "The port draws the plate arriving and then HOLDING VISIBLE. It does not pulse it. The plate's own group encodes exactly one cycle -- alpha 0x00 at t=214, 0xff at t=238-244, 0x00 on the final untimed keyframe -- and the port holds at the settle (t=238, alpha 0xff) as it does on every other screen. The running game was measured pulsing continuously at peak intervals averaging 2.24 s, and NO reading of this group produces 2.24 s: looping the whole group gives 268 units = 4.47 s, looping from the first keyframe gives 54 units = 0.90 s. So repeating the group here would be inventing a period, and the port does not. Filed in BLOCKED.md."
      },
      "why": "HANDOFF Q2/Q6: the boot reaches the title after the intro movie. This is the LAST step, and a last step is where the sequence stops rather than fading out -- a boot that ends by fading to black looks like a boot that crashed. P5 gave the title somewhere to go, but that is a HANDOVER and not another boot step: `--boot` still stops here, and `--boot --play` hands the same held title to the menu flow, where (A) opens TITLE_MENU. Kept as a stop rather than folded into `screens` because what the boot does is authored from a measured sequence, and what (A) does is a separate measurement."
    }
  ],
  "dwell": {
    "_": [
      "DELIBERATELY EMPTY. Each screen's dwell is its own keyframe group -- the",
      "publisher wordmark reaches its hold at t=235 (3.92 s) and the developer",
      "logos at t=190 (3.17 s), both read from the disc. Holding beyond that would",
      "be a number nobody has measured, so the sequencer holds for zero extra time",
      "and the pacing is the disc's own.",
      "",
      "When a capture times the real boot, the extra hold per screen goes here."
    ]
  },
  "navigation": {
    "_": [
      "MEASURED off the running game, HANDOFF Q5 -- none of it is on the disc.",
      "It lives here rather than in GDScript so that a reader can see it is a",
      "measurement and delete it the day a field on the disc states it."
    ],
    "wrap": true,
    "wrap_why": "HANDOFF Q5: up/down move one item and WRAP at both ends. Measured on the 5-item main menu AND the 3-item EXTRAS, so it is a menu rule and not a per-screen one (docs/game/navigation.md, branch auto/no-disc-and-menu-captures 3a87a26).",
    "left_right": "nothing",
    "left_right_why": "HANDOFF Q5: left/right do nothing. Measured. Implemented as an explicit no-op rather than by omission, so that 'we never wired it' and 'the game ignores it' are distinguishable in the code.",
    "input_during_transition": "ignored",
    "input_during_transition_why": "AUTHORED, and NOT measured -- nobody has watched what the game does with a button pressed mid-fade. Ignoring is the choice that invents the least: it cannot queue a press the game might have dropped. Ask the RE agent before relying on it."
  },
  "screens": {
    "_": [
      "What each button does. The NAVIGATION ORDER is not here -- it is derived,",
      "in each screen file's `buttons` (button-role elements sorted by resting Y).",
      "Only the destinations, the initial focus and the cancel target are",
      "authored, because only those are measurements or decisions.",
      "",
      "`goto` is an EXPORTED SCREEN NAME or null. `goto_name` is the game's own",
      "screen vocabulary from the decoded transition lookup -- carried so the",
      "binding is not lost, and marked below as the NAME MATCH it is, never as a",
      "measurement (HANDOFF: the strings are what the call sites reference, not",
      "proven arguments, and the same list mixes in TEXT_FONT and GAMMA_RGB).",
      "",
      "`goto: null` with a `blocked` note means the destination screen is real and",
      "measured but is NOT IN THIS EXPORT -- it lives in another archive. That is a",
      "milestone boundary, not an unknown."
    ],
    "title": {
      "on_accept": {
        "goto": "main_menu",
        "goto_name": "TITLE_MENU",
        "goto_name_kind": "name match, not measured",
        "why": "MEASURED, HANDOFF: (A) on the title opens the main menu, with (A) on the boot title as the control in the same run."
      },
      "on_cancel": null,
      "on_cancel_why": "MEASURED, HANDOFF Q5: (B) on the title does nothing."
    },
    "main_menu": {
      "initial_focus": "ptbtn01",
      "initial_focus_kind": "authored",
      "initial_focus_why": "AUTHORED, standing in for HANDOFF Q5, which measured that initial focus is NOT STABLE: four boots of the same harness opened on TUTORIAL, TUTORIAL, NEW GAME, NEW GAME. A port has to open on something. ptbtn01 (NEW GAME) is picked because it is one of the two states actually observed and it is the top item, so a reader can predict it. It is a CHOICE. Delete this the day the RE agent finds what selects it.",
      "on_cancel": {
        "goto": "title",
        "goto_name": "TITLE_SCREEN",
        "goto_name_kind": "name match, not measured",
        "kind": "authored -- likely but UNPROVEN",
        "why": "HANDOFF Q5 states (B) on the main menu returns to the title. That is the ONE navigation rule on this screen with no capture behind it: it was seen once, without a capture, and the title also returns on its own after ~8-10 s idle, so an observer could not have told the two apart (docs/re/menu-navigation-semantics.md). Independently, the main menu is the ONLY screen whose footer does not advertise (B) -- confirmed here from the disc art, see docs/port/DECISIONS.md. The port implements it because a menu with no way out is worse than a menu with a plausible one, and records that it is authored."
      },
      "buttons": {
        "ptbtn01": {
          "label": "NEW GAME",
          "goto": null,
          "goto_name": "DIFFICULTY",
          "goto_name_kind": "name match, not measured",
          "blocked": "DIFFICULTY is not in this export. MEASURED destination (EASY/NORMAL/HARD/BACK, opening on NORMAL, then SELECT DATA) but it is not a GP_TITLE build, so there is no screen file to go to yet."
        },
        "ptbtn02": {
          "label": "LOAD GAME",
          "goto": null,
          "goto_name": null,
          "blocked": "The save-slot list is GP_SAVE_LOAD, not in this export. Destination MEASURED."
        },
        "ptbtn03": {
          "label": "TUTORIAL",
          "goto": null,
          "goto_name": "TUTORIAL_MENU",
          "goto_name_kind": "name match, not measured",
          "blocked": "The lesson list is not a GP_TITLE build. Destination MEASURED."
        },
        "ptbtn04": {
          "label": "OPTIONS",
          "goto": null,
          "goto_name": null,
          "blocked": "The settings menu is GP_OPTIONS, not in this export. Destination MEASURED."
        },
        "ptbtn05": {
          "label": "EXTRAS",
          "goto": "extras",
          "goto_name": "EXTRA_MENU",
          "goto_name_kind": "name match, not measured",
          "why": "MEASURED, HANDOFF Q4: EXTRAS opens GP_TITLE build 6. It is the ONLY main-menu destination inside this archive, and therefore the only (A)-into-a-submenu the P5 gate can actually walk."
        }
      },
      "labels_why": "The five labels are read off live-main-menu.png, a capture of the running game (docs/game/navigation.md, branch auto/no-disc-and-menu-captures 3a87a26). They are carried for logs and for a human reading this file; nothing draws them -- the button sprite already has its own text."
    },
    "extras": {
      "initial_focus": "ptbtn11",
      "initial_focus_kind": "measured",
      "initial_focus_why": "MEASURED, unlike the main menu's: EXTRAS opens focused on MISSION SELECT (live-extras.png). It is authored here only because there is nowhere else to put a measurement -- it is not a choice.",
      "on_cancel": {
        "goto": "main_menu",
        "goto_name": "TITLE_MENU",
        "goto_name_kind": "name match, not measured",
        "why": "MEASURED, HANDOFF Q5: (B) goes up one level and RESTORES FOCUS to the item you came from. EXTRAS advertises (B) in its own footer -- the red glyph is in ptmsg2.png and absent from the main menu's ptmsg.png."
      },
      "buttons": {
        "ptbtn11": {
          "label": "MISSION SELECT",
          "goto": null,
          "goto_name": null,
          "blocked": "The stage list is GP_MISSION_SELECT, not in this export. Destination MEASURED."
        },
        "ptbtn12": {
          "label": "MOVIE THEATER",
          "goto": null,
          "goto_name": null,
          "blocked": "NEVER OPENED. docs/game/navigation.md marks this one unknown -- not merely unexported. Do not assume it opens GP_MOVIE_THEATER; that would be a name match dressed as a destination."
        },
        "ptbtn13": {
          "label": "BACK",
          "goto": "main_menu",
          "goto_name": "TITLE_MENU",
          "goto_name_kind": "name match, not measured",
          "same_as_cancel": true,
          "why": "MEASURED: EXTRAS' third item is BACK (live-extras.png). Treated as (B): it pops the stack, so focus is restored on the main menu exactly as (B) does. Whether the game distinguishes them is untested and there is no reason here to invent a difference."
        }
      }
    }
  }
}