# Phase 1.0H one-shot device result

Status: **AUTHORIZATION CONSUMED; FIRST FLIP SUBMIT FAILED**.

One exact authorized attempt ran on firmware 9.60. The host used one
connection, one 1,845,152-byte transfer, one execution and bounded result
reception. It performed no retry or reconnect. Remote EOF arrived after 2.27
seconds.

## Result

Twenty-five valid `CHD10H01` frames and 2,353 bytes of ordinary stdout prove:

1. I04 was reached, so the Phase-1.0H `-v` correction fixed the deterministic
   no-argument/no-menu exit.
2. Core initialization and driver selection continued through I12.
3. I13, I14 and D03 reached internal video, SDL2 video and SDL initialization.
4. D05 returned positive VideoOut handle `1309671680`.
5. D06 returned `0` for VideoOut buffer registration.
6. Source order proves the diagnostic pattern was copied into mapped video
   memory before D07.
7. D07 returned `-1` from the first `sceVideoOutSubmitFlip` attempt.
8. D04 returned `-1` from SDL initialization.
9. Stdout reports `Cannot open video driver` and a fatal error in
   `video_driver_init_internal()`, followed by core unload messages.

D12 appeared earlier with shutdown reason `6` and error `118`: the write
firewall rejected a requested filesystem write during argument/config parsing.
The exact operation was not included in the frame. The shutdown request did
not immediately stop subsequent initialization.

No D08, D09 or D11 was received. A successful/visible flip, input/audio
initialization, runloop entry, complete VideoOut cleanup and safe exit remain
unproven. The console's visible display result has not been operator-attested.

## Evidence

- artifact SHA-256:
  `822f2cf1f4d33a514d2bdd88fde40ad580dda5d85f537362ef6dff2eafcb56b6`;
- ignored local trace SHA-256:
  `858a205afcf682a498d8bc11947b67d2446098883a61f6871e31df4d950d0a61`;
- attempt receipt SHA-256:
  `aa598838c2db9a03799ce69ed977ad1dbb4f9d0b92ad017c0e1f91c680f1e04a`;
- raw stream SHA-256:
  `6578869b15575c57a19dc0c0317f6b516a85bf6e246abaa85df76e8ae9d5cf67`;
- ordinary stdout SHA-256:
  `109e465582ae55354cb1f7b52c1b17d6741264735b41c59d6ecde565bf3cdc55`.

The permission and run ID are consumed. All current authorization and artifact
eligibility fields are false. No follow-up device action is authorized.