Files
chimera-gfx-Public/docs/retroarch/phase-1.0d-next-device-test-ladder.md
Chimera GFX release export a6037502d7
phase0-ci / build-and-audit (push) Successful in 2m14s
Publish Chimera GFX source
2026-09-03 03:27:14 +02:00

1.6 KiB

Phase 1.0D future device-test ladder

Current state:

ps5_connection_authorized=false
device_transfer_authorized=false
device_execution_authorized=false
installation_authorized=false
autoload_authorized=false
device_write_authorized=false
automatic_retry=false

There is no transfer or execution package. The following is only a contract for a later task.

RUN A

A later authorization must name exactly chimera_ps5_crt_entry_canary.elf, size 106,344 bytes, SHA-256 c84c0fb43392ce17abc1e7e6be38b522f1b32a681fd516d684c3dbbf7b34b743, the destination address supplied in that later task, one connection, one direct in-memory transfer, one execution, and a bounded observation window. It must continue to forbid install, autoload, staging, device files, live replacement, cleanup, retry, reconnect, reboot, and any other payload.

Visible CHIMERA C1 — CRT MAIN REACHED is the only RUN-A success marker. A completed host send is not success. RUN A is never automatically repeated.

RUN B

RUN B cannot be authorized merely because Phase 1.0D passed offline. It requires visible RUN-A success, a separately recorded result, and a new artifact-specific authorization naming retroarch_ps5_early_diag.elf, size 1,844,664 bytes, SHA-256 092bcabc0f8717a648030c592aa0dc900f878952fb14ee453851a29f298ea7ee. It permits at most one connection, transfer, execution, and bounded observation. The operator records the last visible D-code or the magenta-frame state.

RUN B has no retry, reconnect, second execution, third artifact, autoload, installation, persistent staging, device write, or Phase-1.0B smoke rerun. RUN A authority does not carry to RUN B.