Files
chimera-gfx-Public/docs/phase1/APPROVAL_PACKAGE.md
T
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

54 lines
2.7 KiB
Markdown

# Hardware approval package
Status: **not authorized; offline review artifacts only**.
## Current offline review artifacts
| Artifact | Firmware | SHA-256 | Transfer/execution |
|---|---|---|---|
| `chimera-gfx-capability-probe.elf` | `NONE` | `f0f74978ac62490ff2482386e9c4efa3ad6d6cc46e10d54c41cb8669b4449f36` | false / false |
| `chimera-gfx-phase1-videoout-clear.elf` | `NONE` | `2e826ac4ea2bffb626d82e370f98909bb508417d92b1ac3796e9f5a902e975c9` | false / false |
| `chimera-gfx-capability-probe-0.1.0-fw-9.60-offline-audit-only.elf` | `9.60` | `4be1c17b4964f2b68c39b5145bc4af4619c32512d60269ecf5c39728b390fa63` | false / false; permanently denylisted |
The two `NONE` artifacts are tied to source commit
`72292f2d5788ad643e9d1816ce28ab754ef739b5`. The offline test and import
evidence is in `docs/evidence/phase0-build-2026-07-17.md`. These exact artifacts
cannot enter the project-requested GNM module open or SDL initialization because
their firmware gate is `NONE`. The SDK payload CRT still initializes before
`main`.
## First hardware gate
The first console action, if it ever becomes safe and receives new permission,
must be the non-rendering capability probe, not the VideoOut experiment.
Project code would call only `dlopen`, `dlsym`, `dlclose`, and standard output
functions. It would resolve the 21 manifest names, record only booleans, invoke
no resolved pointer, and request no submit, draw, dispatch, flip, or GPU-memory
operation.
Jens reported exact firmware `9.60` and authorized only its offline build and
audit. The pinned SDK v0.41 payload CRT performs prohibited kernel process-state
writes before `main`, so the resulting ELF is not execution-eligible even
though the project gate precedes `dlopen`. A kernelwrite-free startup route and
a newly built digest are required before execution can be considered.
## VideoOut gate after successful discovery
The later experiment would execute the exact SDL sequence and indirect API
inventory in `VIDEOOUT_CLEAR_EXPERIMENT.md`. Likely failures are a clean error,
payload crash, stuck payload, lost display ownership, or required controlled
console restart. Automatic retry is prohibited. The unbounded SDL flip wait is
an unresolved blocker even after symbol discovery.
## Authorization state
The 9.60 offline build authorization has been received. No transfer or execution
authorization has been received. No execution-permission wording is offered
while the SDK CRT blocker remains. The firmware-specific evidence and blocked
approval package must record the filename, SHA-256, exact source commit, all
imports, startup/loader/cleanup call chain, and offline tests. Approval never
carries forward to the VideoOut test.
The completed firmware-specific package is
`docs/approvals/probe-9.60-transfer-execution.md`.