Files
chimera-gfx-Public/docs/retroarch/phase-1.0ac-offline-dormant-adapter.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

56 lines
2.4 KiB
Markdown

# Phase 1.0AC: offline dormant adapter
Status: `OFFLINE_DORMANT_FAKE_SYSCALL_ADAPTER_COMPLETE_LIVE_ADAPTER_BLOCKED`
Date: 2026-07-22
Chimera GFX is a graphics/homebrew project. This phase adds host-side test
infrastructure for a possible future one-shot launcher observation; it is not
a security feature and it changes no RetroArch, SDL, VideoOut or target code.
## Closed capability boundary
`phase10ac_dormant_adapter.py` composes the Phase-1.0Z passive batch parser
with an exact built-in fake syscall facade. The facade consumes caller-created
synthetic outcomes. It cannot accept a live implementation and stores no
target. The module imports no socket, selector, DNS, real clock or filesystem
output interface and exposes no CLI.
The adapter requires a precommitted-receipt marker before the first synthetic
create step. It then models:
1. one create and immediate nonblocking setup;
2. immediate or pending connect completion;
3. readiness plus `SO_ERROR == 0` for a pending result;
4. an explicit partial-write loop for exactly one Phase-1.0Z batch;
5. bounded read readiness and at most 65,536 supplied bytes;
6. deadline-only result sealing;
7. one local close on success or any failure after successful create.
Timeout and interrupted-wait events stay inside the same synthetic attempt.
They never create a retry, reconnect or resume. When readiness coincides with
the deadline, the deadline wins and no subsequent fake read or write occurs.
EOF, zero progress, excess progress, malformed data and cleanup failure all
invalidate the run.
## Evidence boundary
The 32 host tests cover immediate and pending connect paths, partial writes,
interrupted and timeout waits, exact deadline races, EOF, receive limits,
malformed results, cleanup and closed fake types. They prove only the Python
model's behavior. They do not prove:
- a deployed shsrv identity or port-2323 behavior;
- Windows scheduler or real socket timing;
- a live connect, send, receive or remote-process cleanup;
- firmware-9.60 behavior;
- RetroArch launch context, SDL, VideoOut or rendering.
## Decision
The dormant fake-syscall adapter is complete. A live adapter remains blocked
and absent. The next permissible step is an offline-only Phase 1.0AD design
for numeric target validation and an inactive activation record. That phase
must still contain no socket creation, connection, device request or enabled
authorization.