Curated Genera runtime screenshots

Zmacs session

Character-style prompt session

The ordered interaction selected Zmacs, inserted the researcher-authored line Plain text, then styled text, recorded one semantic key probe that Zmacs reported as undefined, and then dispatched Control plus the X mod2 path and J. The selected capture is the resulting style prompt. This proves that visible prompt in this world; it does not prove that the host chord is a portable physical-keyboard recipe or that later exploratory input changed a style successfully.

Edit Buffers session

The ordered input was deliberately explicit. Select E entered Zmacs. The harness then recorded keydown Control_L, keydown x, keyup x, keyup Control_L, followed by keydown Control_L, keydown Shift_L, keydown b, keyup b, keyup Shift_L, and keyup Control_L. The resulting screen identified Zmacs (Edit Buffers) *Edit-Buffers-1* (RO), which distinguishes this true Control-X Control-Shift-B application from the earlier List Buffers capture. Lowercase d then put D in the row's action column. A later dispatch of the harness's abort alias did not leave this mode and therefore supports no claim about Edit Buffers' Abort command; that later frame remains local.

Core applications session

Frame-Up session

The ordered interaction was: invoke Frame-Up with Select Q; capture its default one-pane model; make one exploratory Left click in the pane with no resulting layout change; open the generic right-button Operation menu, then dismiss it without a selection; choose Split Pane from Frame-Up's command menu; select the printed PANE-1 presentation; complete Horizontally; capture the resulting two-pane model; choose Done; verify return to the prior Listener; and stop the private session. The selected image is the one successful layout result, not the exploratory sequence.

Debugger and Screen Editor session

The ordered interaction deliberately signaled project-owned errors, exercised the ordinary Debugger and Display Debugger, evaluated and navigated only synthetic stack content, recovered to the Listener, opened the live System Menu, entered Screen Editor, inspected its fixed operation menu, exited without changing geometry, and initiated shutdown. Only the three minimal functional states selected below are published.

Document Examiner session

The ordered interaction invoked Document Examiner with Select D, captured its initial command-oriented frame, invoked computed Help and a completion prompt for analysis, dismissed them, and initiated shutdown. The richer Help and candidate-list screens remain ignored; only the sparse initial application frame is published.

Flavor Examiner and CLOS session

The ordered interaction selected the Flavor Examiner; displayed components, instance variables, and functions for DW:PROGRAM-FRAME; observed its three-result history rotation; returned to a Listener; and used the command processor's distinct CLOS superclass command on CLOS:STANDARD-OBJECT. No definition was edited or dumped.

Trace, Stepper, and call-analysis session

The ordered interaction inspected the initially empty breakpoint and mode-trace tables; defined small project-owned caller/callee functions; traced and called them; entered the Stepper; inspected its live one-line operation summary; exited; exercised call analysis and breakpoint setup/removal; removed the trace; and initiated shutdown. The selected frame shows the synthetic trace/Stepper state rather than installed prose.

Zmail and Zwei Mail-mode session

The ordered interaction selected Zmail; completed a local LISP-MACHINE login without entering mail credentials or reading mail; inspected the empty reader and its functional menus; attempted integrated composition until the unavailable DIS-SYS-HOST file service established the site boundary; returned to Zmail; entered the distinct Zmacs Text Mail mode; left the blank draft without a recipient or body; and initiated shutdown. Only the empty reader and blank composition template are published.

Presentation Inspector session

The ordered interaction evaluated the researcher-entered values 42 and :MUSEUM-PROBE; opened the Presentation Debugging menu over the integer; invoked the Presentation Inspector; exercised context, hierarchy, handler, applicability, and Detailed reports; switched to and recovered the processless frame through the System Menu; exited to verify buffered Listener input; and initiated shutdown. The selected images show the initial synthetic-object inspection and one functional handler-analysis page, not installed Help or a general handler database extract.

Converse and Notifications session

The ordered interaction logged in locally; selected the empty Converse activity; opened its local Help for analysis; selected the initially empty Notifications activity; returned to a Listener; disabled only fallback notification pop-ups in unsaved state; submitted the researcher-authored record Museum runtime probe D09 through TV:NOTIFY; returned to Notifications; and initiated shutdown. The Help, login, Listener, and duplicate empty-state captures remain ignored. A generation-1 preflight invoked the Python entrypoint outside the pinned Guix environment and failed before the VLM started; it produced no guest input and is not part of the runtime evidence.

Namespace Editor session

The ordered interaction typed Select Activity Namespace Editor, observed the empty frame, pressed Help once, and initiated shutdown. It did not select, create, edit, save, revert, or delete an object; set or define a site; change services; log in to a server; or perform network discovery. Help produced no visible change in this empty context. Only the pre-Help frame is published.

Runtime and compiler session

The ordered interaction defined, compiled, invoked, macroexpanded, and disassembled only a researcher-written squaring function; displayed the read-only Lisp context and garbage-collector status; and tested the default Show Expanded Lisp Code behavior. A later unsupported raw-keyword attempt entered input correction, so the article does not call the in-guest cleanup verified. No Save World occurred, and the unchanged private world discarded all unsaved state. Only the two minimal screens selected below are published; correction-mode and cleanup candidates remain ignored.

Accepting Values and CLIM-presence session

The ordered interaction opened Set GC Options, moved through its live Accepting Values form, and deliberately changed no option. A read-only CLIM-status expression was mistakenly entered while a Boolean field still owned input; the type checker rejected it, and the input was removed before the selected capture. The pointer then rested on the printed Abort presentation, causing the bottom documentation line to identify its left- and right-button action. A left click aborted the form and returned to the Listener. Two subsequent read-only queries established that this fresh world had neither a registered system name containing CLIM nor a CLIM package or :CLIM feature. Those Listener screens remain ignored because they add no distinctive CLIM interface evidence. Generation 1 stopped before launch because another VLM was still active; generation 2 failed before a guest started because its experimental launcher named a nonexistent sandbox shell. Neither preflight produced guest input.

Hardcopy forms session

The ordered interaction queried the two default-printer variables, enumerated the six live hardcopy formats, and queried the loaded versions of Hardcopy, Press, GPrint, Print, and PostScript. An exploratory attempt to treat the screen-option template helpers as conses entered the Debugger and was aborted. The session then opened the Hardcopy File form and the numeric-argument Screen hardcopy form and aborted each through its printed Abort presentation. It never chose Done, captured a requested screen, loaded another system, opened an output file, contacted a printer, or submitted a request. The selected crops retain only the two forms; the raw frames, Listener transcript, and debugger remain ignored.

Network-service registry session

The ordered interaction entered one researcher-authored, read-only expression that reported server policy, the registry count, and selected registered/enabled pairs; captured the result; and initiated shutdown. It enabled no service, contacted no peer, opened no output file, and displayed no installed Help. A generation-1 preflight failed before the VLM ran because it was invoked outside the required Guix wrapper; it produced no guest input and is not runtime evidence.

Emergency Break publication session

The ordered interaction targeted the main client; opened the System Menu with the Shift/right-button gesture while retaining the complete exploratory attempts in the action log; highlighted and selected Emergency Break; targeted the separately identified cold-load client; typed the researcher-authored form (+ 40 2); sent its End activation as host KP_End; captured the resulting 42; sent host F5 to the cold-load client for the mapped Resume gesture; verified the main Listener was restored in a separate ignored capture; and initiated shutdown. Every recorded input intent has a linked successful XTEST-dispatch outcome. The screenshot proves the displayed breakpoint state and evaluation; source and the ordered record, rather than the still alone, ground entry and return semantics.

D10 Terminal disconnected-state session

The ordered interaction completed the local non-network login, invoked Select T, captured the untouched Terminal frame, and later pressed Network-Help solely to verify the live command surface. The Help frame contains licensed prose and remains ignored. The capture proves the prompt, initial label, blank surface, scrollbar, who-line and geometry only. The isolated namespace exposed no peer or external route.

Each screenshot sidecar captured the prefix of the action log that existed when the PNG was installed. Counts below include both the recorded intent and its linked outcome, so six records represent three attempted actions. The sidecar's prefix hash makes preceding exploratory input visible rather than silently reducing provenance to the final keystroke.

Zmacs session

The shutdown prompt was observed, yes was sent and accepted, and cleanup progress was observed. The VLM then encountered the reproduced Cold Load channel mutex stall and required bounded host termination. The final record is therefore forced-stopped, with forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false.

The base and private world hashes remained identical. The harness did not invoke Genera's Save World and created no host-process checkpoint. Whether an independent in-guest save or checkpoint occurred remains unknown; no persistence claim is inferred from the screenshots.

Character-style prompt session

The shutdown prompt was observed, yes was sent and accepted, and cleanup progress was visible before the known Cold Load channel mutex stall required bounded host termination. The final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false.

The private world remained byte-identical to the base world. The harness invoked neither Save World nor a process checkpoint; save_world_performed and guest_checkpoint_created remain unknown, the unsaved editor state was discarded, and no session process remained.

Edit Buffers session

The stop path observed the VLM prompt, sent confirmation, and observed cleanup progress, but did not record confirmation acceptance before the supervisor timeout. The bounded fallback then stopped the remaining processes. The final record is therefore forced-stopped, with forced_stop=true, forced_after_confirmed_shutdown_stall=false, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false. It must not be described as the separately confirmed Cold Load mutex stall seen in other runs.

The private and base worlds remained byte-identical, and the private world did not change during the run. The harness invoked neither Save World nor a host-process checkpoint; save_world_performed and guest_checkpoint_created remain unknown. No marked buffer action was executed before shutdown, and no session process remained.

Core applications session

This session reached the same bounded shutdown condition after the shutdown prompt was observed, yes was accepted, and cleanup progress appeared. The known cold-load channel mutex stall then required host termination. Its final record says forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false. The private world remained byte-identical to the base, no Save World or host-process checkpoint was requested, and no session process remained after cleanup.

Frame-Up session

After the documented split, Done returned Frame-Up to the preceding Dynamic Lisp Listener. The harness then reached the same confirmed shutdown and cleanup stall as the other Genera sessions and performed bounded host termination. The final record says forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false. The unsaved Frame-Up model was discarded, the private and base world hashes remained identical, no Save World or process checkpoint was requested, and no session process remained.

Debugger, Document Examiner, Flavor Examiner, and trace sessions

Each of the four later sessions reached the same known Cold Load channel mutex stall after the shutdown prompt was observed, yes was accepted, and cleanup progress was visible. Bounded host termination followed. Their final records therefore set forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false.

In every case the private world remained byte-identical to the base world, the harness requested neither Save World nor a process checkpoint, and cleanup left no session process running. This establishes isolation of the observation; it does not turn the forced stop into an orderly guest shutdown.

Zmail and Presentation Inspector sessions

Both sessions reached the same known Cold Load channel mutex stall after the shutdown prompt was observed, yes was accepted, and cleanup progress was visible. Bounded host termination followed. Their final records set forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false.

For both runs the private world remained byte-identical to the base world, the harness invoked neither Save World nor a process checkpoint, unsaved Lisp state was discarded, and no session process remained. The unchanged world files establish the isolation result; they do not imply that the bounded forced stop was an orderly guest shutdown.

Converse and Notifications session

The shutdown prompt was observed, yes was accepted, and cleanup progress was visible before the known Cold Load channel mutex stall required bounded host termination. The final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false.

The private world remained byte-identical to the base world. The harness invoked neither Save World nor a process checkpoint, the researcher-created notification and option change were discarded with unsaved Lisp state, and no session process remained.

Namespace Editor session

The shutdown prompt was observed, yes was accepted, and cleanup progress was visible before the known Cold Load channel mutex stall required bounded host termination. The final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false.

The private world remained byte-identical to the base world. The harness invoked neither Save World nor a process checkpoint, no namespace mutation was attempted, and no session process remained. This establishes observation isolation, not an orderly VLM host exit.

Runtime and compiler session

This session reached the same confirmed shutdown and cleanup stall after the prompt was observed and confirmation accepted. Its final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false; bounded host termination left no VLM or Xvfb process. The base and private worlds remained byte-identical, the harness invoked no Save World or process checkpoint, and the synthetic function and all other unsaved Lisp state were discarded.

Accepting Values and CLIM-presence session

This session reached the same confirmed shutdown and cleanup stall after the prompt was observed and confirmation accepted. Its final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false; bounded host termination left no VLM or Xvfb process. The private world never diverged from the base-world hash, the harness invoked no Save World or process checkpoint, and all unsaved interaction state was discarded. The unchanged world establishes observation isolation; it does not make the bounded forced stop an orderly guest shutdown.

Hardcopy forms session

The shutdown prompt was observed, yes was accepted, and cleanup progress was visible before the known Cold Load channel mutex stall required bounded host termination. The final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false; no session process remained afterward.

The private world remained byte-identical to the base world. The harness invoked neither Save World nor a process checkpoint, both forms were explicitly aborted, no print request was submitted, and all unsaved interaction state was discarded.

Network-service registry session

The shutdown prompt was observed, confirmation was sent and accepted, and cleanup progress was visible before the known stall required bounded host termination. The record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, and unsaved_lisp_state_discarded=true. The private world remained byte-identical to the base world, and the harness invoked neither Save World nor a checkpoint. The unchanged world establishes observation isolation, not an orderly VLM exit.

Emergency Break publication session

The shutdown prompt was observed, yes was sent and accepted, and cleanup progress was visible before the reproduced Cold Load channel mutex stall required bounded host termination. The final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, orderly_vlm_host_shutdown=false, vlm_forced_stop=true, and xvfb_returncode=0; the launcher return code is 137. This was not an orderly VLM host shutdown.

The private world stayed byte-identical to the base world for the entire run. The harness did not invoke Save World or create a host-process checkpoint; save_world_performed and guest_checkpoint_created remain unknown, and the final record marks the unsaved Lisp state discarded. These facts establish the bounded publication observation and lack of world-file mutation, not a general persistence claim.

D10 Terminal session

The shutdown prompt was observed, yes was sent and accepted, and cleanup progress was observed before the reproduced Cold Load channel mutex stall required bounded host termination. The final record sets forced_stop=true, forced_after_confirmed_shutdown_stall=true, state_may_be_incomplete=true, orderly_vlm_host_shutdown=false, and unsaved_lisp_state_discarded=true; the launcher return code is 137. This was not an orderly VLM host shutdown.

The private world remained byte-identical to the base world. The harness did not invoke Save World or create a host-process checkpoint. save_world_performed and guest_checkpoint_created remain unknown except for those negative harness facts. The selected screenshot precedes the later raw Help probe and establishes only the initial disconnected state.

See Zmacs in Symbolics Genera for the behavior these images support and the Genera computer-use harness for the capture and isolation model.

The character-style prompt supports Inks, faces, and character styles in Symbolics Genera.

The core-session captures support the Dynamic Lisp Listener, the D01 Listener specification, activities and the System Menu, the D02 program-selection specification, and Inspector and Peek.

The Frame-Up and Screen Editor captures support Screen Editor and Frame-Up and the D03 Screen Editor and Frame-Up specification.

The Emergency Break capture supports Emergency Break and the cold-load stream and the D04 Emergency Break and degraded interaction paths specification.

The Edit Buffers capture supports Directory, difference, and buffer editors and the D06 reimplementation specification.

The later captures support the Genera Debugger and Display Debugger, Help and Document Examiner, Flavors, CLOS, and the Flavor Examiner, and Trace, Stepper, breakpoints, and call analysis.

The Zmail and Presentation Inspector captures support Zmail and mail composition, the D08 ZMail and mail composition reimplementation specification, and the Presentation Inspector.

The Converse and Notifications captures support Converse, direct messages, and notifications and the D09 reimplementation specification.

The Terminal capture supports the network terminal dossier and D10 reimplementation specification, including its normative Genera Terminal companion.

The Namespace Editor capture supports Genera Namespace administration and editor.

The compiler and status captures support Lisp runtime, compiler, and development environment.

The Accepting Values capture supports Dynamic Windows and presentation-based interaction.

The Hardcopy crops support Hardcopy, Press, printing, and plot output.