Current 8088/8086 conversion: English 6.3.0.12 / German 6.3.0.13
22 October 2026

START HERE
acceptance.json is the combined current-release gate. It binds each accepted
report to a checksum and binds both edition hashes. ui-build-freeze.json is
only the earlier STATIC freeze, not a substitute for completed acceptance.
native/native-report.json is the dedicated 8086-core functional acceptance.
strict8086-report.json combines the strict instruction/semantic execution
checks, geometry, 95-frame repaint/game tests, production bridge ABI and smoke.
DEVELOPMENT/source-rebuild-report.json binds the exact corresponding source.

CPU EVIDENCE
static-nasm-8086-report.json classifies all emitted listing bytes and checks
all 1691 UI/runtime/bridge instructions per edition against the linked files.
Static engine instruction coverage is recorded separately.
The UI/runtime/bridge assemble as CPU 8086. Independent raw decoding also
rejects later CPU encodings: NASM CPU 8086 alone silently accepts three tested
later forms, so the assembler flag is not relied on by itself. The finite
opcode oracle/semantic/cache reviews cover 207 cases; see their reports and
OPCODE-GATE-INDEPENDENT-REVIEW.md. Dynamic guards reject known 8086/later CPU
semantic differences in the exercised paths, plus unsupported prefixes,
segment/20-bit wraps and stale-code-cache reuse. This is a constrained
instruction execution check, not a full 8086 electrical/timing emulator.

Engine-semantics-review.json separately checks the retained Watcom -0 object
listings. Original engine instructions/data and 272 bridge operand targets
per edition are checked against releases 10/11. engine-and-memory-audit.json
verifies changed call operands still name the same engine resource/entry;
every other compared engine byte, size and load flag is preserved.
engine-and-memory-independent-audit.json independently normalizes targets.

thunk-abi-8086-report.json executes the linked production bridge: 434 cases per
edition, all 119 stubs, FLAGS patterns, RETF N, arguments, nesting and failure
guards. nested-bridge-independent-review.json adds depths through 128 under
an independent harness. bridge-abi/report.json is a separate 120-case generator
check. Portable current tests and CPU gate live in SOURCE/tests.

TRUE 8086 NATIVE SCOPE
DOSBox-X uses its dedicated 8086 normal CPU core. The same strict 8086 DOS
probe produces different PUSHSP, CL32 and FLAGS results on 8086 versus 386,
preventing a normal 386 core from being mislabeled 8086 evidence. BIOS reports
640 KiB conventional memory; XMS, EMS and UMB are disabled; GEOS uses disk.geo
only. Both languages pass launch, moves/depth 4, controls, resizing, repaint
and lifecycle checks on the supplied English Ensemble 1.2 installation.
Native board RGB pixels after incremental Undo and genuine covered/full
Expose match exactly. The native report records exact configurations and
limits, including the lack of direct heap/kernel CPU-byte observation.

No physical 8088/8086 hardware, bus-cycle timing or minimum whole-system RAM
claim is made. DOSBox-X's 8086 core is experimental; it is used together with
static/raw instruction audits and functional regression, not as the sole
proof. No commercial runtime, fonts, raw guest memory or helper DSOs ship.
The small CPU probe is our source; observed output is decoded scalar JSON.

MEMORY SCOPE
Fixed initialized resources plus 49152-byte stack: 127616 bytes both editions.
All resource reservations plus stack: 214848 EN / 214832 DE bytes. Compared with
releases 10/11, fixed resources decrease 960 EN / 992 DE bytes. DGROUP 8400,
arena 34336 (34260 initialized-used), stack 49152, histories, capacities and
search limits are preserved. A bridge entry temporarily uses two extra
stack bytes; no new reservation/framebuffer is added. These file-derived
figures exclude actual heap, handles, loader, shared libraries and UI data.
The current native run does not measure per-geode heap peaks.

REPRODUCTION AND HISTORY
SOURCE/README-REBUILD.txt gives the supported SDK-free rebuild and optional
portable tests. The evidence/tools scripts preserve original workspace paths
and may need adaptation; the runtime audit needs the user's matching runtime.
Engine listing scripts refer to retained original compilation objects, which
can be reproduced by the separately documented full engine build route.
Earlier source, timing and graphics evidence remains historical under
EVIDENCE/ui-history10-11, ui-history8-9 and slim-history. Old 386/frame captures
are not relabeled 8086 runs. No old timing is an 8088 performance benchmark.
