Files
chimera-gfx-Public/docs/retroarch/phase-1.0e-device-observations.md
T
Chimera GFX release export fee37cd9b5
phase0-ci / build-and-audit (push) Failing after 1m41s
Publish Chimera GFX source
2026-09-03 02:53:36 +02:00

28 lines
2.3 KiB
Markdown

# Phase 1.0C/D/E device observations
Evidence class: **operator-observed, artifact-bound hardware evidence**.
Three separately authorized one-shot runs have occurred. Every authorization
is consumed and none authorizes another connection, transfer or execution.
| Run | Exact artifact | Host action | Operator observation | Proven boundary |
|---|---|---|---|---|
| A | `chimera_ps5_crt_entry_canary.elf`, 106,344 bytes, `c84c0fb43392ce17abc1e7e6be38b522f1b32a681fd516d684c3dbbf7b34b743` | one connection and one complete send; no retry | `CHIMERA C1 — CRT MAIN REACHED` visibly appeared | elfldr reached SDK `_start`, CRT completed, `main` and the notification ABI executed on firmware 9.60 |
| B | `retroarch_ps5_early_diag.elf`, 1,844,664 bytes, `092bcabc0f8717a648030c592aa0dc900f878952fb14ee453851a29f298ea7ee` | one connection and one complete send; no retry | one notification appeared too briefly to identify its D-code; console remained responsive | some notification-producing payload code ran, but the exact D-stage is **UNCLASSIFIED** |
| C | `retroarch_ps5_result_diag.elf`, 1,844,880 bytes, `1049c78099a60b472a3fb0e2999e3393b6ad76337a28532a7e53872e7772dedf` | one connection, complete send, write-half-close and bounded receive; no retry/reconnect | three binary frames validated, then remote EOF | D00 `main`, D01 platform-init begin and D02 platform-init result `0`; inherited stdout worked; incomplete before D03 |
The ignored local host traces bind each send to its artifact and show no retry.
They contain the session address and are deliberately not committed. RUN C's
trace is 1,795 bytes with SHA-256
`4ff27a0eac48283cdc4c7ff964226def2689e808e3adea6594d0e77674a676f0`.
It records one connect, one `sendall`, one `shutdown(SHUT_WR)`, five receives,
3,413 received bytes, 3,221 discarded non-frame stdout bytes, remote EOF, zero
parser errors, zero retries and zero reconnects.
The three valid frames had sequences 1-3 and CRC-32 values `93f81433`,
`f2b975e4` and `69173d14`. All reported notification result `0`; D02 carried
`raw0=0`. In source, D03 is emitted at entry to `sdl2_gfx_init()`. Its absence
means SDL-init begin, SDL/VideoOut, first flip, rendering, terminal status,
cleanup and safe exit remain **UNPROVEN**. The unretained stdout bytes cannot
be used to infer why execution ended before D03.