Publish Chimera GFX source

docs/retroarch/phase-1.0dc-inactive-bigapp-comparison-gate.md

@@ -0,0 +1,26 @@
+# Phase 1.0DC: inactive BigApp comparison gate
+
+Status: `INACTIVE_DUAL_ARTIFACT_BIGAPP_GATE_COMPLETE_TARGET_IMPLEMENTATION_BLOCKED`
+
+Phase 1.0DC turns the post-CZ gaps into one data-only admission contract. It
+does not create target source, a launcher ELF, a network client, a socket, a
+CLI or an active approval, and performs no device action.
+
+Any hypothetical candidate must bind two artifacts independently: a bounded
+launcher no larger than 1 MiB and the unchanged CZ canary of 1,845,240 bytes
+with SHA-256 `8dadce9d...a9bf95`. Firmware is exactly 9.60, the only title is
+the existing v0.7 reference `PPSA01659`, and the result protocol remains
+`CHD10AV1` with sole cleanup terminal D14.
+
+The contract additionally requires a fresh approval hash, a five-minute
+window, an attestation that no BigApp is running, explicit acceptance of the
+temporary kernel/ptrace effects, and static proof of bounded parent detach,
+child cleanup and result-channel completion. It rejects terminating an
+existing BigApp, persistent writes, `/system_ex` remount, installation,
+autoload, retry, reconnect and fallback titles.
+
+The tracked instance is entirely inactive and target-free. No current
+candidate can pass because there is no bounded launcher artifact and the live
+result-channel composition remains unproven. Passing the pure validator in a
+future phase would validate record shape only; it would not authorize or
+perform execution.