# Phase 1.0AQ: offline fixed worker result record

Status: `FIXED_RESULT_AND_GENERATION_IDENTITY_COMPLETE_TRANSPORT_BLOCKED`

Date: 2026-07-29

The bytes-only protocol is one exact 128-byte little-endian record. It binds an
attempt ID, worker nonce, worker and child PID, monotonic generation, requested
and copied byte counts, status and credential-restoration failure bits. The
first 96 bytes are protected by a trailing SHA-256 digest. Reserved and flag
fields must be zero.

PID alone is explicitly insufficient. A result is accepted only when every
identity field equals a precommit. Success additionally requires the exact
requested byte count and zero restoration failures. Failure records preserve
partial progress. Tests mutate every byte position and also reject rehashed
records with semantically invalid fields.

SHA-256 provides integrity here, not authentication; identity comes from the
precommitted attempt and nonce. The model has no random source, pipe, socket,
process, clock or target capability. Exclusive writer ownership, partial reads,
EOF/deadline behavior and PS5 pipe atomicity remain unproven, so no transport or
target implementation is allowed.