chimera-gfx-Public/docs/retroarch/phase-1.0aa-offline-fake-adapter-integration.md

Phase 1.0AA: offline fake-adapter integration

Status: OFFLINE_FAKE_BATCH_INTEGRATION_COMPLETE_LIVE_ADAPTER_BLOCKED

Date: 2026-07-22

Phase 1.0AA connects the Phase-1.0Z passive batch contract to the Phase-1.0X exclusive evidence model using only an exact built-in fake adapter and exact synthetic clock. It creates no live adapter, socket, address, CLI, target code or target artifact. No PS5 action occurred.

Closed fake boundary

run_offline_fake_batch rejects subclasses and arbitrary adapter objects. The only accepted components are:

• OfflineFakeClock, whose value changes only through explicit fake events;
• OfflineFakeBatchAdapter, which allows one fake open, one complete Z batch, a bounded scripted event sequence and one fake close;
• OfflineFakeEvidenceStore, which exclusively creates local test evidence.

There is deliberately no adapter protocol that a network implementation could quietly satisfy. The fake adapter records only the SHA-256 of sent bytes, not a target. Scripted event buffers are logically discarded during close; physical memory erasure remains unproven because caller-owned immutable bytes may still exist.

State and ordering

validate W plan -> build and revalidate Z batch
  -> exclusive consumed receipt
  -> fake open exactly once
  -> fake send exactly one complete batch
  -> zero or more bounded DATA events before deadline
  -> HARD_DEADLINE at or after the synthetic deadline
  -> Z completeness validation and sanitization
  -> fake close exactly once
  -> exclusive receipt-bound sanitized output

The consumed receipt includes run ID, window, batch size, batch SHA-256, deadline and the exact Z contract hash. It does not include a target or raw transcript. A failure after receipt creation leaves the receipt intact and creates no sanitized output; no cleanup deletes it.

Remote EOF, a blocked receive event, missing deadline, early deadline, data at or after the deadline, IAC, partial output, a second fake send, a second fake close and evidence collisions all fail closed. Prompt bytes remain ordinary data and cannot seal a result.

What the tests prove

The host tests prove internal ordering and rejection behavior of this exact Python model. They do not prove:

• a live listener or exact deployed shsrv binary;
• OS socket timeouts or preemption of a blocking call;
• live fragmentation, short sends/writes, disconnect or cleanup;
• firmware-9.60 behavior;
• absence of atime, cache, accounting, scheduler or shell-process effects;
• physical erasure or containing-directory durability.

Decision

The fake integration is complete and remains host-only. A live adapter is blocked and unauthorized. The next permitted step is an offline feasibility review for a future bounded live adapter: OS timeout/preemption semantics, short-send handling, exclusive evidence ordering and failure cleanup must be specified without adding a socket, address or device action.