← Supporting evidence

Evidence record

research/services.md

From Windows Application to Portable Emulation Platform

3,711 bytes

Debugging and Development Service Inventory

Service Principal layer Mechanism Critical qualification
Authoritative machine operations Shared C++ session and native bridge Serialized lifecycle and commands Retained globals permit one loaded session per process
Consistent snapshots Core and bridge Owned registers, memory, mappings, counters, frames Caller serialization remains required
Safe memory observation Core MMU/session Logical/physical reads and availability masks Unavailable I/O is not an observed zero
Runtime attachment identity Core plus source-map verifier Generation, program revision, mapping, complete code guards Hashes and guards are consistency evidence, not authenticity proof
Instruction and source execution CPU hooks/session/native development Bounded normal execution and explicit stop reasons Source stepping and audio capture advance execution
Historical trace CPU/GIME/session Retained pre/post registers, instruction bytes, real events Finite capture is not an unbounded profiler
Graphics inspection Core plus native/helper UI Current/declared buffer rendering and pixel backing A preview does not advance the live beam
Executable/source map Native toolchain integration Source/object/listing/link/relocation verification Build success alone is insufficient
Compiler debug metadata Maintained compiler patch and native reader Types, scopes, functions, storage locations Unsupported/optimized storage stays unavailable
Call stacks and typed values Native development services Supported frame/call proof and immutable memory Unknown frames stop unwinding
Banked module identity Manifest verifier and core guard service Actual physical backing and complete executable bytes Equal logical address/opcode is insufficient
BASIC development Core tokenizer/interpreter integration Qualified dispatcher/source mapping and stack-aware stepping Unknown ROMs and OS-9 do not inherit BASIC support
Assembly development Bundled assembler/native/core Verified instruction/source attachment and binary launch Source mapping is distinct from C-frame interpretation
Bounded call context Native C service and MCP Fixed 64-byte S window; independently gated caller/arguments Full end-to-end publication qualification to be refreshed against final source
Build provenance Native build/input service Immutable inputs/artifacts and diagnostics Modified control scope requires review
Disposable playtests App/helper plus separate core process Owned guest, writable copy, bounded field input Personal session and media remain separate
MCP observations Scoped helper and native host Capability discovery, snapshot IDs, retry ledgers Existing grants do not gain capabilities implicitly
Compiler correctness Maintained CMOC optimizer patches Register/address, stack-effect and condition-code dependency guards Three fresh target-executed regression fixtures; no exhaustive language-conformance claim
Relocatable toolchain CMOC, LWTools, mcpp, Make, Perl integration Controlled preprocessing, dependency paths, pinned source and payload identities Source build and installed runtime have different prerequisites
Guest SDK Guest C libraries and bundled toolchain Hardware APIs and bounded compatibility subset Host tooling and guest libraries have separate contracts

The call-context extension is implemented. Selected source-content identities and public source links identify the described mechanism; publication qualification remains separate from this evidence view.

SHA-25639a085881e92da5a367246845bc270a22209f598fa977f589bce849754d41141

A closer look

Open original