Directory, difference, and buffer editors reimplementation specification

Release profiles

The editor members are native ZWEI applications, not CLIM application frames; Genera Compare Directories is instead a Command Processor command with Dynamic Windows output. DB-C46 and DB-C303 use TV and predate CLIM. DB-G85 uses Dynamic Windows presentations for typed List Buffers output and source comparison, and uses a TV multiple-choice interface for Kill Or Save Buffers. It defines no CLIM frame, pane, command table, port, or application dependency in the selected sources. A clean-room implementation MAY use CLIM internally only if its externally observable profile behavior remains the same.

Where a rule names DB-C46 without a suffix, it applies to the shared System 46 Dired body. Only DB-C46-DIRED-STANDALONE is a closed effective profile.

Conformance levels

This document normatively defines DB-C46-DIRED-STANDALONE/L2, DB-C303/L2, and DB-G85/L2 at the semantic grain. DB-C46-HOSTED has a complete Dired-local body but cannot reach L1 because the selected public snapshot lacks the parent Zmacs tree and referenced buffer-manager bodies. The runtime verification axis is independent:

L3 remains reserved. A test suite MUST report semantic/source conformance separately from preserved-runtime closure.

Exact source and compiled artifacts

The C46 QFASL is artifact evidence, not decompiled source. The public System 46 snapshot's package declaration refers to a separate Zmacs QFASL, but that payload and its source are absent from the selected tree. Names in tags, load declarations, or historical correspondence therefore do not close its buffer-manager bodies.

Normative evidence map

The exact line numbers above identify the local licensed copy only by portable artifact name and hash. No licensed source body is reproduced here.

Common editor view

SpecialEditorView {
  profile
  owning_command_loop
  interval_or_node
  read_only_to_ordinary_editing
  mode
  rows_in_display_order
  point
  numeric_argument_state
  pending_action_state
  selected_or_exposed_state
  rebuild_generation
}

Read-only means ordinary text editing is rejected. Application commands MAY mutate mark columns, regenerate rows, or replace the interval inside their protected update scope. The display is derived state; the release-specific parsed row metadata or attached object is authoritative.

DB-C46 directory view and row

C46DirectoryView {
  singleton_buffer_name = "*DIRED*"
  device
  directory
  parsed_rows
  sort_order
}

C46DirectoryRow {
  rendered_DIR_line
  parsed_name_and_version
  size
  creation_date_and_time
  reference_date
  status_flags
  pending_mark: blank | D | P
  newest_version_flag
}

DB-C46 MUST read a DIR device stream into the one special buffer and parse the fixed columns established by the profile. It MUST retain the device and directory as the implicit identity used by later operations. It MUST compute newest-version marks only under the source assumption that rows are ordered by file name and numeric version. It MUST NOT claim pathname-object identity or multiple simultaneous Dired buffers for this profile. (C46-SRC)

DB-C303 directory view and row

C303DirectoryView {
  unique_zmacs_buffer
  top_level_pathname_list
  open_subdirectory_pathnames
  sort_state
  rows_with_nesting_levels
}

C303DirectoryRow {
  pathname_object
  translated_pathname_identity
  level
  directory_and_contents_present_flags
  file_property_plist
  pending_mark: blank | D | U | P | F | A
}

Each invocation MUST create a unique read-only Zmacs buffer, mark it with special type :DIRED, save Dired as its major mode, activate it, optionally select it, and retain the exact pathname list. A row MUST carry the pathname and nesting level. Multiple top-level directories and opened subdirectories MAY coexist. (C303-SRC)

The profile's local-host equivalence rule MUST canonicalize the special host named LOCAL to the actual local host before comparing directory identity. Rebuild MUST remember open subdirectory pathnames and attempt to reopen them after the base listing has been reconstructed. (C303-SRC)

DB-G85 directory node and row

G85DirectoryNode {
  pathname
  read_only_node_state
  old_interval_snapshot_during_protected_update
  sorted_up_by_name_property
}

G85DirectoryRow {
  pathname_or_switch_identity
  file_property_plist
  current_display_string
  pending_mark: blank | D | P | F | A
  deleted_state
  newest_and_status_flags
}

The Genera node MUST rebuild from FS:DIRECTORY-LIST with sorted and deleted-file options, compute newest-version flags, attach pathname identity to each actionable file row and switch identity to each switch row, insert the disk-space summary after header lines, and move point to the first pathname row. Headers and the summary remain nonrows. A failed protected rebuild MUST restore the old interval and its sorted-up-by-name property when an old display existed. (G85-SRC)

The rollback protects the editor view; it does not undo external file operations already committed before another failure.

Undelete has no U pending glyph. The U command writes a blank into the action column; at execution time, a blank row whose independent file state is :DELETED means undelete. A clone MUST preserve that distinction between the displayed mark and the underlying deleted-state flag. (G85-SRC)

BDired compiled-directory model

BalanceView {
  primary_cdirectory
  alternate_cdirectory
  read_only_buffer
  two_rendered_directory_sections
}

BalanceRow {
  cfile
  truename_pathname
  alternate_cdirectory
  transfer_destinations
  pending_mark: blank | T
}

DB-C303 BDired MUST build one compiled-directory graph for each pathname, compare them, store each graph on the first line, attach the actual compiled-file object and truename to every file row, and attach the alternate directory to each compiled file. Initial nonempty transfer destinations MUST appear as T marks. The model's transfer destinations, not the glyph alone, are authoritative. (C303-SRC)

The I/i Resolve Inconsistency implementation occurs inside a source COMMENT form and its table entries are commented out. It MUST remain unavailable in the strict profile.

System 303 Edit Buffers row

C303BufferActionRow {
  buffer_object
  staged_pathname_or_nil
  kill_column_0: blank | K
  file_io_column_1: blank | S | W | R | ~
  print_column_2: blank | P
  select_column_3: blank | .
  modification_and_identity_display
}

The four columns are independent. A conforming strict implementation MUST preserve that independence, including the historical partial-unmark defect specified below. The visible buffer name is not its identity. (C303-SRC, C303-RUN)

Genera Edit Buffers row

G85BufferActionRow {
  buffer_object_in_line_property
  action_or_current_column_0: blank | . | D | S | ~
  listing_status_and_description
}

The Genera editor uses one main pending action per row. The period identifies the current buffer when the listing is rebuilt; it is not a deferred operation, and a later D, S, or ~ mark overwrites it. Its read-only special node retains a filter that is NIL, one case-insensitive substring, or a list interpreted as the OR of its strings. The report heading is a ZMACS-BUFFER-LISTING presentation, but editable rows are line-property records; they MUST NOT be represented as List Buffers row presentations merely because the heading can translate into the editor. (G85-SRC)

List Buffers report

BufferReportRow {
  buffer_object
  status_character
  displayed_name
  file_version_or_description
  major_mode
  presentation_or_typeout_item_record
}

List Buffers is a report, not an Edit Buffers mode. DB-C303 emits TV typeout items of type ZMACS-BUFFER; DB-G85 emits Dynamic Windows presentations whose type is the runtime class of the buffer. DB-G85 sorts by recency unless its sort variable is false; a supplied filter limits rows without rewriting the authoritative global buffer registry. (C303-SRC, G85-SRC)

Kill Or Save Buffers choice model

BufferChoiceRow {
  buffer_object
  status_and_name
  available_choices
  selected_choices
}

This surface is a TV multiple-choice transaction. Selection state is temporary until the generic chooser completes. Abort returns an aborted result and MUST cause no application-owned buffer operation. A successful result is processed in the profile-specific order below. (C303-SRC, G85-SRC)

Normative incorporation and finite domains

This section incorporates the following companions by reference as normative parts of the D06 effective tree:

• MIT ZWEI and Zmacs keybindings for every System 46 and System 303 inherited direct leaf, alias, prefix, minibuffer, mode, pointer, Help, numeric-argument, undefined, and error path;
• Genera Zmacs keybindings for every Genera inherited keyboard, pointer, prefix, minibuffer, Help, presentation, and menu path;
• the editor-family specification for command-loop and editor-context semantics; and
• the TV and Dynamic Windows specifications for generic menu, choice, typeout, scrolling, recognition, and presentation behavior.

This incorporation is exact, not shorthand for an unspecified modern editor. Applications override only the cells and staged surfaces enumerated below.

A missing cell falls through; an explicit hard-undefined cell terminates lookup. Aliases restart resolution at the original top table. Exhaustion invokes the profile's not-defined behavior; a selected command symbol without an implementation invokes the distinct not-implemented path. No implementation may invent modifier stripping.

System 303 has a read-context switch that is essential to effective compatibility. The ordinary command and prefix readers temporarily inhibit synchronous TV intercepted characters, so local and parent Abort or Break comtab cells are reachable. Other raw or staged reads that do not use that wrapper retain TV's synchronous Break/Abort interception; asynchronous Control-Abort remains separate. The active read context MUST therefore be part of a binding dump. (C303-SRC)

Entry tree

DB-C46
├─ named Dired -> prompt, enter System 46 Dired
├─ current-file Dired command
│  ├─ no argument -> whole current directory
│  ├─ exact 1 -> retain current FN1; wildcard remaining components
│  └─ every other explicit value -> prompting Dired
├─ built C-X C-B -> List Buffers metadata-only boundary
└─ absent selected Zmacs body -> other exact host bindings remain TODO-C46-ZMACS

DB-C303 Zmacs
├─ C-X D -> Dired for current file
├─ C-X C-B -> List Buffers
├─ Meta-X Dired / BDired / Edit Buffers / Buffer Edit / Kill Or Save Buffers
│  -> inherited completing-reader tree
└─ Mouse-3-1 generic Zmacs menu
   ├─ List Buffers
   ├─ Kill Or Save Buffers
   └─ Edit Buffers

DB-G85 Zmacs
├─ C-X D -> Dired for current file
├─ C-X C-B -> List Buffers
├─ C-X C-Shift-B -> Edit Buffers
├─ C-X C-Meta-B -> Kill Or Save Buffers
├─ Meta-X Dired / Edit Directory / Edit Buffers / List Buffers /
│  Kill Or Save Buffers -> inherited completing-reader tree
└─ Mouse-3-1 generic Zmacs menu
   ├─ List Buffers
   └─ Kill Or Save Buffers

DB-G85 Command Processor
└─ typed command name Compare Directories
   ├─ first pathname
   ├─ second pathname and confirmation
   └─ optional explicitly mentioned Ignore Versions Boolean

System 303's generic Zmacs right menu has these 16 ordered command leaves:

Mouse-3-1
├─ Arglist
├─ Edit Definition
├─ List Callers
├─ List Sections
├─ List Buffers
├─ Kill Or Save Buffers
├─ Edit Buffers
├─ Split Screen
├─ Compile Region
├─ Indent Region
├─ Change Default Font
├─ Change Font Region
├─ Uppercase Region
├─ Lowercase Region
├─ Mouse Indent Rigidly
└─ Mouse Indent Under

Genera's full 15-leaf generic Zmacs right menu remains normative in the Genera binding companion. Dired locally shadows that fixed pointer cell; System 303 BDired and both Edit Buffers modes do not and therefore inherit their applicable Zmacs menu. (C303-SRC, G85-SRC)

For Genera C-X D:

• no numeric argument selects the directory of the current file;
• exact numeric value 1 retains the current name and wildcards type/version; and
• any other explicit argument invokes the ordinary prompting Dired command.

The System 303 source has the same three-way current-file entry shape. Entry through standalone Lisp Dired composes Dired mode directly over Standard rather than Zmacs.

Complete System 46 Dired local table

The constructor has exactly 30 cells: 20 direct cells and ten lowercase aliases.

System 46 Dired has no local Abort cell. No selected Standard/standalone cell supplies one, so an ordinary Dired command read reports Abort as undefined. This is not an exit command. (C46-SRC)

The fixed pointer menu is this exact ordered tree:

Mouse-3-1
├─ Sort Increasing Reference Date
├─ Sort Decreasing Reference Date
├─ Sort Increasing Creation Date
├─ Sort Decreasing Creation Date
├─ Sort Increasing File Name
├─ Sort Decreasing File Name
├─ Sort Increasing Size
├─ Sort Decreasing Size
├─ Automatic
└─ Automatic All

Cancel invokes no command. Unlisted cells inherit the selected parent. Because the public System 46 snapshot lacks the Zmacs body, standalone Dired has the closed effective parent while Zmacs-hosted parent deltas remain TODO-C46-ZMACS.

Complete System 303 Dired local table

The constructor has exactly 62 cells: 46 direct cells and 16 lowercase aliases.

The named mode menu has exactly ten leaves: Automatic, Automatic All, then the increasing/decreasing pairs for reference date, creation date, file name, and size.

The row pointer tree has exactly twelve operations. The source first validates and labels the clicked row, then opens the menu. It moves point to that row only after a command has been selected:

Mouse-3-1 over a file row
├─ Delete
├─ Rename
├─ Copy
├─ Subdirectory
├─ Undelete / Cancel
├─ Change Properties
├─ Edit File
├─ View File
├─ Compare
├─ Find File on Exit
├─ Load File
└─ Hardcopy

Cancel leaves point unchanged and invokes no command. A click not identifying an actionable row follows the source error/cancellation path rather than manufacturing a pathname.

Complete System 303 BDired local table

The constructor has exactly 21 cells: 14 direct cells and seven lowercase aliases.

There is no local pointer/menu cell. I/i Resolve Inconsistency is commented-out source and MUST be unbound. The installed Help's claim that P sends hardcopy is wrong for this source profile: the body prints the transfer-destination object.

Complete System 303 Edit Buffers local table

The constructor has exactly 27 cells: 18 direct cells and nine lowercase aliases.

? is not local and falls through. No local pointer/menu cell or prefix exists. The visible initial state MAY already contain S and . marks because rebuild premarks buffers needing save and the most recently selected non-editor buffer.

System 303 Help subtree used by Dired and BDired

The first ? or Help is a local application leaf that enters the common documentation dispatcher with an added M operation for that mode:

Dired/BDired ? or Help
├─ M -> Dired Help or BDired Help
├─ C -> read a key; recurse prefixes; `*` enumerates a selected prefix
├─ D -> Describe Command
├─ L -> What Lossage, only when playback exists
├─ A -> Apropos
├─ U -> Undo Help
├─ V -> Variable Apropos
├─ W -> Where Is
├─ Space -> repeat stored request; fresh stored B silently reprompts
├─ Help -> describe this dispatcher
├─ Control-G / Rubout -> abort
└─ every other input, including `?` -> beep and reprompt

The body contains a dead later test for ?, but the valid-input reader cannot pass ? to it. This unreachable branch MUST NOT be made reachable in strict mode.

Complete Genera Dired local table

The constructor has 51 specifications expanding to exactly 60 cells: 59 keyboard cells and one pointer cell.

The local named-only command is Show File Properties. Dired has no local C-X child. ? and Help shadow the global staged Help dispatcher with direct local typeout. X enters the inherited completing reader.

The fixed menu has exactly fourteen leaves and no application-declared keyboard accelerators:

Mouse-3-1
├─ reference date: increasing / decreasing
├─ creation date: increasing / decreasing
├─ file name: increasing / decreasing
├─ size: increasing / decreasing
├─ partition: increasing / decreasing
├─ Automatic
├─ Automatic All
├─ Change File Properties
└─ Describe Attribute List

It is a cached TV momentary menu, remembers its last selection per screen, and returns no command on cancel. Ordinary Dired rows are line-property records, not typed presentations. Pathnames in confirmation output are presentations; applicable Zmacs pathname translators and Dynamic Windows handlers then participate.

Complete Genera Edit Buffers local table

The constructor has 27 specifications expanding to exactly 36 keyboard cells and no local pointer cells.

There is no local named array, prefix, pointer binding, or menu accelerator. Every other keyboard and pointer cell uses the incorporated inherited trees.

List Buffers effective trees

List Buffers is transient output and owns no modal keyboard comtab, local prefix, local Help key, or menu accelerator. Once it has returned, ordinary editor keys use the active Zmacs tree. System 303 ignores numeric-argument state. Genera prompts for a name substring when any numeric argument is supplied and otherwise ignores its magnitude.

DB-C303 rows are TV typeout items. Their exact app-relevant pointer tree is:

ZMACS-BUFFER row
├─ Mouse-1-1 -> queue default Select
├─ Mouse-3-1 -> operation menu, source-registration reverse order
│  ├─ Compile File
│  ├─ Kill
│  ├─ Print
│  ├─ Unmod
│  ├─ Save
│  ├─ Write
│  └─ Select
├─ Mouse-3-2 -> System Menu
└─ other click -> no D06 action / inherited invalid feedback

Only Select is the default. The seven menu actions are immediate and independently fallible; no report-level transaction exists.

The effective DB-G85 application-relevant presentation subtree is composed from several owners:

ZMACS-BUFFER-LISTING heading
└─ Select -> Edit Buffer Listing -> enter Edit Buffers with same filter;
             hide typeout after switching

concrete buffer row presentation
├─ Select gesture -> Select Buffer, if buffer remains live
├─ menu-only Save Buffer
├─ menu-only Not Modified
└─ menu-only Kill Buffer

The buffer-editor module owns the heading translator. The general Zmacs buffer module owns row selection. The general Zmacs buffer/file support modules register Save Buffer, Not Modified, and Kill Buffer. Dynamic Windows owns recognition, applicability filtering, selection, and menu construction. These registrations are therefore effective inside List Buffers but are not all owned by the D06 report.

These are application-relevant registrations, not a replacement for the full fixed and presentation trees. Fixed comtab matches win. Otherwise the recognized candidate set includes the incorporated 64 ZWEI translators plus two actions and the applicable Dynamic Windows handler set. Type applicability, testers, gesture mapping, context, and equal-score registration order determine the winner. A specific live row hit and final candidate menu remain TODO-G85-LIST-HIT.

Kill Or Save Buffers effective trees

This application owns no keyboard comtab, prefix, keyboard Help leaf, or menu accelerator after entry. It MUST NOT acquire invented Return, Space, End, Abort, or mnemonic keys. Keyboard-event fate in the exact chooser is an inherited TV/runtime oracle.

The DB-C303 TV multiple-choice pointer surface is:

choice row
├─ Mouse-1-1 or Mouse-3-1 on a box -> toggle choice and apply implications
├─ Mouse-1-1 or Mouse-3-1 in an item-row gap -> beep
├─ same outside a displayed item -> inherited mixin path
└─ every other pointer gesture -> inherited mixin path
bottom margin
├─ any pointer gesture except exact Mouse-3-2 on Do It -> return selected choices
├─ same on Abort -> return aborted result
├─ same in a margin gap -> beep
└─ exact Mouse-3-2 -> inherited mixin path
deexposure -> force abort
scrollbar -> inherited TV scrolling

The strict System 303 implementation accepts exactly Mouse-1-1 and Mouse-3-1 on row boxes, despite its who-line documentation saying “Any button.” The source dispatch wins over that displayed generalization. Turning a box with another pointer gesture on is not a compatibility extension.

The DB-G85 TV multiple-choice pointer surface is broader:

choice row
├─ any pointer button/modifier except exact Mouse-3-2 on a box -> toggle
├─ same over row gap -> beep
├─ exact Mouse-3-2 -> deliberately unhandled here
└─ outside row -> inherited mixin path
bottom margin
├─ any pointer button/modifier except exact Mouse-3-2 on Do It -> commit result
├─ same on Abort -> aborted result
└─ same on gap -> beep
deexposure -> force abort
scrollbar / hover / who-line -> inherited TV behavior

Choice implications are order-sensitive:

Turning a choice off has no implication. In DB-G85, Kill followed by UnMod can leave both selected, while UnMod followed by Kill clears UnMod. This asymmetry is a required profile behavior.

Genera Compare Directories input boundary

Genera has no active BDired or Balance Directories editor in the selected source corpus. Its D06 directory-difference surface is the typed Command Processor command Compare Directories. It owns no raw key, local prefix, local Help leaf, pointer gesture, translator, or menu accelerator. The complete Command Processor name/input editing tree, typed-command flow, FQUERY behavior, and Dynamic Windows presentation tree are inherited and MUST be incorporated by a conforming implementation through the companion complete Input Editor base map, Command Processor integration, and FQUERY compatibility. Loaded-world and site-table conflicts remain a runtime-registry oracle.

The source registers COM-COMPARE-DIRECTORIES in the Command Processor's Directory command table.

Its argument grammar is exact:

Compare Directories
├─ first pathname: wildcard name/type/version; default rebuilds the first
│  pathname-history object with all three components wildcarded
├─ second pathname: default first pathname; confirmation required
└─ Ignore Versions: Boolean, default No, explicitly mentionable

Its resortable output offers exactly Name, Type, Smallest First, Largest First, Oldest First, and Newest First. Edit Viewspecs is a generic Dynamic Windows action, not an application-owned binding.

The six view comparators are exact. Name applies FS:PATHNAME-LESSP to the pathname at the head of each entry. Type applies STRING-LESSP to pathname types, but equal types under STRING-EQUAL are broken by FS:PATHNAME-LESSP on the full pathnames. Smallest First and Largest First compare :LENGTH-IN-BLOCKS with missing values replaced by 1,000,000, using < and > respectively. Oldest First and Newest First compare :CREATION-DATE, then :FILE-CREATION-DATE, then 1_40, using < and > respectively.

Unbound, mode composition, and exhaustive enumeration

Each sparse mode mutates the shared active mode table. Later minor-mode activation wins collisions. Disabling an older System 303 mode unwinds newer modes, removes the target, then reapplies newer modes in original order. A binding census MUST therefore record activation order, comtab identity, aliases, hard undefined cells, named arrays, pointer registries, presentation registries, and active read context.

The exhaustive test MUST enumerate every finite keyboard cell and raw pointer cell, recurse through each reachable prefix or staged reader, resolve every alias from the original top table, enumerate each menu and presentation candidate, and inject one genuinely unbound value. Constructor counts alone are necessary checks, not proof of the effective tree.

Special-view lifecycle

ENTER
  -> resolve or allocate special view
  -> establish semantic backing objects
  -> rebuild derived interval
  -> install mode and read-only boundary
  -> select/expose
  -> mark, inspect, or perform immediate actions
  -> confirm and execute, or abort
  -> exit, retain, reuse, revert, or kill special view

The phases are not atomic unless a profile explicitly says so. The implementation MUST expose the selected release's allocation/reuse policy and failure point:

An implementation MUST NOT call the Genera protected rebuild generally transactional. It explicitly restores a copied nonempty interval and one sort property on abort; it does not establish restoration of point, tick, every buffer property, an initially empty buffer, or prior filesystem effects.

Mark transaction

Marking is an editor-view mutation, not the external operation itself:

1. resolve the row object;
2. validate any source-defined precondition;
3. write the mark or semantic queue in the source-defined order;
4. move point according to signed count; and
5. retain all earlier marks if a later repeated row fails.

Zero repeat count performs no row operation where the shared walker receives zero. A positive count operates then moves down; a negative count moves up before each operation. Commands that use only numeric-argument presence or ignore the numeric value are named separately below.

Confirmation and execution

Execution is a sequence, not a database commit:

scan derived rows
  -> build profile operation lists
  -> display pending work
  -> read profile confirmation
  -> perform categories in exact profile order
  -> report per-item failures or unwind unexpected conditions
  -> exit or rebuild according to caller

Earlier successful external or buffer effects survive a later error unless an individual backend operation supplies its own rollback. A clean-room SAFETY-CORRECTED mode MAY stage or journal operations, but it MUST be separately selected and MUST report where its observable result differs from strict history.

System 46 entry, parsing, and rebuild

Entry selects the global *DIRED* buffer, makes it writable, deletes its old interval, reads the requested DIR stream, parses each fixed-column row, computes newest-version status, and then makes the interval read-only. (C46-SRC)

The current-file entry has an exact three-way argument rule: no numeric argument uses the whole current directory; explicit value 1 retains the current first name while wildcarding the remaining components; every other explicit value delegates to the prompting Dired command. The standalone Lisp entry composes Dired directly over Standard and TV.

There is no display rollback. An open, read, or parse failure after deletion leaves the buffer empty or partly filled. A conforming strict implementation MUST preserve that failure boundary. A safety-corrected implementation MAY build offscreen and swap only after success, but MUST label the difference. (C46-SRC, INF)

The parser retains first name, version, size, creation date/time, reference date, and status flags. Automatic cleanup assumes rows of one first-name family are contiguous and numeric versions ascend. Sorting by date, size, or decreasing name before Automatic can violate that assumption; strict mode MUST retain the resulting source-visible grouping/marking risk rather than silently re-sort by name. (C46-SRC)

System 46 row commands and numeric semantics

• D/aliases and P apply over abs(argument) rows. Earlier marks survive a later header/error.
• U without an explicit argument targets the preceding row when the current first character is neither D nor P; otherwise it targets current. An explicit argument supplies signed count.
• Rubout negates the current numeric value and delegates to U.
• N uses an explicit numeric value as its excess-version threshold and otherwise uses mutable *FILE-VERSIONS-KEPT*, whose selected-source default is 2. It counts only rows whose second name/version field is numeric.
• H distinguishes only numeric-argument presence: any explicit argument selects Automatic All and the magnitude is ignored.
• !, E, V, Q, X, sorting, and menu operations ignore numeric value.
• $ resolves to its named command symbol, but that symbol has no definition in the pinned public tree and is absent from the built command listing. Strict selected- source behavior is not-implemented, not a guessed protection toggle.

Automatic uses the same retention count. Its exact configured second-name (FN2) list is MEMO, XGP, @XGP, UNFASL, OUTPUT, and OLREC; Automatic All extends processing beyond that list. Rows whose parsed flags contain $ are protected from automatic marking. Grouping still follows the current display order.

System 46 two-class exit state machine

Exit scans rows, then processes the Print class before the Delete class:

pending prints?
├─ no  -> deletion phase
└─ yes -> show prints; query
         ├─ Y -> print sequentially; then deletion phase
         ├─ N -> return to Dired
         └─ Q or X -> finish this class; then deletion phase

pending deletes?
├─ no  -> exit
└─ yes -> show deletes; query
         ├─ Y -> delete sequentially; exit
         ├─ N -> return to Dired
         └─ Q or X -> exit without deleting

Q or X at the Print query does not necessarily abort the whole exit; it can advance to the Delete query. Per-file string errors are printed and later files continue. Earlier prints or deletes survive later failure or a later N. There is no cross-class or cross-file rollback. (C46-SRC)

System 303 Dired rebuild and nesting

Initial entry creates a unique read-only buffer and records its pathname list. Revert records expanded subdirectory pathnames, deletes the entire interval, reads each top-level directory in sequence, restores point where possible, and attempts to reopen remembered subdirectories. An error can leave an empty, partial, or only partly reopened view. (C303-SRC)

Subdirectory S with no numeric argument inserts or removes the selected subtree. Any explicit argument prompts for a wildcard subset and ignores the numeric magnitude. Closing an old subtree before a new read fails can leave it closed; no rollback is specified. (C303-SRC)

The named prompting Dired command treats numeric-argument presence as a request for :DIRECTORIES-ONLY; its magnitude is ignored. The separate current-file entry uses the three-way no-argument/exact-1/other-explicit rule stated in the entry tree.

System 303 Dired marking defects and numeric semantics

• D, A, F, P, and U use signed count. Non-file lines are skipped where the shared walker specifies it.
• D checks :DONT-DELETE only on the starting row before counted traversal. Later protected rows can therefore receive D marks. Strict mode MUST preserve this defect.
• P validates each row in order; if a later row is unprintable, earlier P marks remain.
• U without an explicit argument goes to the previous row when current is a non-file or blank row. It writes U for an already-deleted file and blank for an ordinary pending mark.
• N uses an explicit numeric value as threshold and otherwise uses mutable *FILE-VERSIONS-KEPT*, whose selected-source default is 2. H uses numeric presence for Automatic All. Unlike C46, this Next Hog counts every matching directory/name/type pathname row without requiring a numeric version, so symbolic or special versions can affect the threshold. S uses presence to request a wildcard. C, R, flags, load, edit, view, compare, and process ignore the value unless their own reader says otherwise.
• Automatic still assumes contiguous filename/type groups after an arbitrary sort, although it sorts version numbers inside a discovered group. Its selected temporary-type set adds PRESS to the early family; it skips :DONT-REAP rows and truncates a discovered version family at the first nonconsecutive version gap.
• > validates that the current line has a plist and is not a directory, then scans the contiguous same-name/same-type group forward. On the first differing successor it reports the current pathname and moves point to that row; it does not compare numeric version values and therefore relies on listing order. The installed patch binds the next line's pathname/name/type before evaluating its intended end test. A nil, nonfile, or terminal successor can therefore signal before the explicit “end of display” branch. Strict mode MUST preserve this evaluation order; only source-to-band confirmation remains TODO-C303-NEWEST-EDGE.

System 303 immediate file mutations and partial display state

The strict profile MUST retain these observable orderings:

These are not permission to corrupt host files in tests. Use disposable guest fixtures and injected backends.

System 303 Dired confirmation and execution

The scanner displays categories in this order: Delete, Undelete, Find, Print, Apply. After one confirmation it executes in a different exact order:

1. Apply Function;
2. Delete;
3. Undelete;
4. Find into editor;
5. Print; and
6. optional Expunge.

The confirmation accepts these effective gestures:

This FQUERY uses its own unwrapped READ-CHAR while the outer editor intercept list is installed. Synchronous Abort, Meta-Abort, Break, and Meta-Break therefore take the corresponding TV/editor intercept path rather than becoming FQUERY choices. Asynchronous Control-Abort remains a substrate path. Application-level cancellation from this query is Q or X; an implementation MUST NOT invent an Abort choice.

The Q caller exits when processing returns true; the X caller remains. The source's :ABORT confirmation result maps to no operations, but the processing function ultimately returns true, which preserves that caller distinction.

Per-file failures are reported and later items continue on the ordinary path. Multiple-file backend failure callbacks and sequential failure paths update marks differently and MUST be tested separately. An unexpected condition stops later work while retaining earlier effects. When multiple top-level directories share one view, undelete/expunge capability is derived from the first header in this source; cross-directory behavior MUST remain a profile test rather than a normalized rule.

Genera Dired entry, reuse, and rebuild

Dired and Edit Directory are synonyms. Zmacs entry uses the three-way C-X D argument rule above; standalone Lisp entry composes Dired over Standard and rejects E because its interval is not an editable Zmacs buffer. (G85-SRC)

A Dired special buffer is reusable exactly when the requested pathname is EQ to the stored pathname. Pathname equality without object identity is insufficient. Selecting it as new causes revert. Revert's bounded old-display recovery is the only rollback specified. (G85-SRC)

Genera Dired numeric and command semantics

• D, P, F, and A use signed count; earlier marks remain on a later failure.
• U without an explicit argument inspects column zero: it targets the preceding row unless that action is D, P, or A; notably F defaults to the previous row. Explicit count supplies direction. Rubout negates and delegates.
• H with any explicit argument selects Automatic All and ignores magnitude.
• N uses explicit numeric value as the version threshold; otherwise the configured File Versions Kept value, whose source default is 2.
• E with any explicit argument attempts other-window selection. Control-U passes the historical special default instead of an ordinary numeric window index.
• = with any explicit argument prompts for the comparison pathname. Bit 2 ignores case and character style; bit 4 ignores whitespace.
• C accepts explicit bit masks 1 through 15. Bits 1 and 2 select 16-bit binary and text; both select 8-bit binary. Bits 4 and 8 suppress author and creation-date copying. Explicit 0, negative, or greater than 15 barfs. No argument resolves to internal mask zero after the source's validity path.
• G without an argument accepts :ALL or a nonnegative integer, with :ALL converted to zero. An explicit numeric argument is passed onward without a local negative check; downstream negative behavior is TODO-G85-GENERATION-NEGATIVE.
• Abort with an argument beeps and remains; without one exits without applying pending marks.

The Dired signed walker has the same asymmetric boundary shape as the Genera buffer editor: negative count moves first, positive count acts before moving, zero performs no row action but moves point to column zero, and pathname resolution precedes the positive terminal check. Crossing a header or terminal nonrow can therefore signal after earlier marks. It never wraps. Marking D on an already :DELETED row is ignored at execution; blank plus :DELETED schedules undelete.

Automatic requires the sorted-up-by-name property, retains configured generations, and skips Don't Reap/Don't Delete rows. The configured source default for disposable types is :UNBIN and :OUTPUT; Dired docstrings that additionally name Press do not match that default. A mutable live-world value remains TODO-G85-DIRED-DEFAULTS.

Genera Dired sort contract

Increasing name order uses FS:PATHNAME-LESSP; every decreasing order swaps the comparator operands. Reference date and partition ID use -1 when metadata is absent. Creation date uses :CREATION-DATE, then :FILE-CREATION-DATE, then -1. File size is -1 for links; otherwise it is nonzero byte size times length in bytes, else block size times length in blocks, else -2.

Sorting removes switch rows, sorts pathname rows, and recreates switches at each device or directory change only if at least one switch existed before sorting. Only increasing-name sort sets :SORTED-UP-BY-NAME true; every other sort writes NIL. These state changes govern whether later multiple-version operations are accepted.

Genera Dired immediate actions and execution

Completed immediate property, copy, rename, generation, view, load, compare, and sort operations are not undone by Abort. Rename can complete externally before a later property-refresh failure, leaving the row stale. The @ and $ flag commands likewise commit FS:CHANGE-FILE-PROPERTIES before updating row metadata and text; generic . commits selected property changes before merging the returned pairs and regenerating. A later row-update failure therefore leaves external success with a stale or partial view. (G85-SRC)

Copy performs the external copy and does not insert, update, or revert a Dired row; a destination inside the displayed directory remains invisible until refresh. Generation retention commits the FS property before updating the row plist and adjusting multi-version marks, so later failure preserves that external change and any earlier display marks.

Deferred action categories execute in this exact order:

1. Delete;
2. Undelete;
3. Hardcopy;
4. Format and hardcopy;
5. prompt for Apply Function, then apply; and
6. optional Expunge.

Confirmation is:

FQUERY also records each displayed choice as an FQUERY-CHOICE presentation. Selecting the rendered Y, conditional E, N, Q, or X choice with the pointer returns the same semantic :YES, :EXPUNGE, :NO, or :ABORT result as its raw-character route. The presentation object is the complete choice entry; FQUERY reduces it to the semantic result before Dired dispatch. Exact recognition, gesture resolution, and menu feedback follow the incorporated Dynamic Windows FQUERY contract.

If there are no pending marks, exit leaves without asking and Immediate simply reverts. Apply Function acceptance occurs after preceding operation categories, so abort/error there cannot roll them back. Per-file returned FS errors are reported and later files continue; an unexpected condition unwinds with earlier effects.

The E/Expunge choice is offered only when the scan found at least one delete mark and either *ALWAYS-OFFER-TO-EXPUNGE* is true or the pathname host advertises the :UNDELETE attribute. Its configured source default is NIL. Expunge derives the directory of each deleted row and deduplicates that list with MEMQ, so two equal-but-not-EQ directory objects can both be processed.

After successful exit processing, *DIRED-KILL-BUFFER-ON-EXIT* controls the special view: NIL selects another buffer and retains Dired, T kills it, and :ASK prompts. The configured source default is NIL. Selection, kill, and history purge use the special-buffer lifecycle implementation; they are distinct from whether file operations succeeded. The :ASK prompt occurs after confirmed file operations and optional expunge but before Dired exit; abort or error there cannot undo those file effects and can leave Dired active. (G85-SRC)

When no default printer exists, both hardcopy paths return a diagnostic string. The generic file-list executor tests only the historical error predicate, so that string is treated as a nonerror. A conforming strict implementation MUST preserve this distinction pending TODO-G85-NO-PRINTER runtime output.

Construction and comparison

BDired reads two directory pathnames, creates both compiled-directory graphs, updates the special buffer's pathname metadata, compares the graphs, then deletes and rebuilds the interval. Read/compare errors before deletion preserve old pixels but can leave metadata updated. Insertion errors after deletion leave a partial display. (C303-SRC)

Each compiled file's nonempty initial transfer destinations MUST render T. Both directory sections share the compared graph state. The view is not a content diff: its comparison and transfer decisions come from FS compiled-directory semantics.

Mark and transfer order

Only T, U, P, and Space consume signed count; Rubout negates. With no explicit argument, U targets the preceding row when the current line is not a file row or its column-zero mark is blank; otherwise it starts on the current row. Copy, Rename, Compare, View, and exit ignore numeric value despite the broad Help wording.

Q/End does not ask for one overall confirmation. It sets transfer mode for the first graph, then the second, transfers the first, then the second, and exits only after success. Unknown file types can invoke per-file FQUERY. Earlier setup, copies, or consumed queues survive a later prompt abort or failure. Abort exits without performing queued transfers but does not undo Copy/Rename already performed.

System 303 Edit Buffers rebuild and marks

Rebuild excludes the Edit Buffers interval itself, emits four action columns, marks S for each buffer already needing save, and marks . for the most recently used non-editor buffer. Therefore immediate End is not necessarily a no-op: it can save premarked buffers. (C303-SRC)

The signed walker applies to Save, Write, Revert, Unmodify, Kill/Delete, Unmark, No File I/O, and Print. Space is inherited Down Real Line rather than this mark walker, and . ignores the numeric argument. The walker silently skips nonbuffer lines, reverses for a negative count, stops at interval bounds, and with count zero performs no action but moves point to column zero. A later prompt or error retains changes made to earlier repeated rows.

The mark commands have these additional observable rules:

• Kill writes K. If that row held the selection period, it removes the period and marks the most-recent eligible non-K buffer for selection; if the killed buffer needs saving, it also writes S in column 1.
• Selection beeps on a nonbuffer or K row; otherwise it makes that row's period unique.
• Save writes S for a buffer with a pathname. For a buffer without one, it prompts for a pathname and writes W. Write prompts for every affected row. Revert silently marks only rows whose buffers have pathnames.
• Staging a pathname rewrites the visible row to name the destination, stores that pathname in the line plist, then writes the column-1 action. Save on an existing pathname, Revert, Unmodify, and No File I/O remove any staged pathname and restore the ordinary row rendering before setting their action character. Thus N changes only the file-I/O action column among the four action columns, but it also clears staged pathname/display state.
• With no explicit argument, U targets the preceding row only when columns 0, 1, and 2 of the current row are all blank. With no explicit argument, N targets the preceding row only when column 1 is blank. Explicit signed counts use their stated direction.

The strict profile MUST preserve the U defect: it clears column 0 three times instead of clearing columns 0, 1, and 2. Thus a row marked Kill and Print loses Kill but retains Print. The preserved runtime reproduced this exact visible result. N correctly clears only action column 1 while performing the staged-pathname and row-rendering cleanup above. (C303-SRC, C303-RUN)

System 303 Edit Buffers exit

Exit visits rows top-to-bottom. For each row it performs:

1. column 1 Save, Write, Revert, or Unmodify;
2. column 2 Print;
3. remember column 3 selection; and
4. column 0 Kill.

It then exits the special buffer clean and selects the remembered target. A failure stops later columns/rows and preserves earlier effects. Write changes the buffer pathname and clears its file identity before performing output, so failed output can leave a retargeted/detached buffer. (C303-SRC)

The selected Zmacs KILL-BUFFER accepts a no-save parameter but ignores it in its body. Killing a modified buffer can therefore prompt to save even when Edit Buffers passes true; N followed by K does not reliably suppress that prompt. The same defect affects new-buffer cleanup helpers. Strict mode MUST preserve it.

Genera Edit Buffers rebuild and marks

Any explicit numeric argument at entry prompts for a buffer-name substring and ignores its magnitude. Rebuild lists matching buffers, stores each buffer object on the line, writes . for the current buffer and blank for others in action column 0, and retains status in column 1. A later action overwrites the period. (G85-SRC)

Delete, Save, Not Modified, and Unmark use the signed row walker. With no explicit argument, Edit Buffers U tests the character under point: any literal Space selects the previous row, while any non-Space selects the current row. Thus the default depends on point's column, not merely the row's column-zero action. H ignores numeric magnitude and writes S only for editing-file rows whose status is new-file or modified-file; it does not mark ordinary non-file + rows. = requires a file buffer and pathname; bits 2 and 4 control case/style and whitespace comparison.

The signed walker has asymmetric source order: for a negative count it moves upward before resolving and acting; for a positive count it resolves and acts before moving down; zero performs no row action but normalizes point to column zero of its current line. The row resolver runs before the positive terminal check, so a count that crosses a terminal or header line can signal after preserving marks made by earlier iterations. It does not wrap.

E immediately selects the row's buffer, leaves other marks and the special view available for later return, and errors if asked to select its own interval.

Genera Edit Buffers exit

Exit scans rows top-to-bottom but pushes each category, giving bottom-to-top order within categories. It MUST:

1. resolve the buffer under point without error and select it only if one exists;
2. save all S buffers bottom-to-top;
3. set all ~ buffers not modified bottom-to-top;
4. kill all D buffers bottom-to-top with no-save true; and
5. exit the original special buffer.

If point is on a heading, legend, or terminal nonrow, selection remains unchanged, but marked actions still execute and the special buffer still exits. There is no confirmation or overall transaction. When a row buffer resolved, selection already occurred if the first save fails; earlier category effects survive later errors. The historical kill path is required not to prompt when no-save is true. Abort performs no marked action, but a retained/reused special buffer may keep visible marks until reverted or killed. (G85-SRC)

The fresh runtime proves true C-X C-Shift-B entry and lowercase d changing one action column to D. A later harness alias named abort did not leave the mode; that alias is not accepted as a probe of the Lisp Machine's actual Abort character and supports no runtime Abort claim. (G85-RUN)

System 303 List Buffers report

The report order uses the current window's history when the configured per-window history option is true, otherwise the global buffer list. Marker selection is a priority, not independent flags:

1. file identity T -> + new file;
2. else read-only -> raw 036 glyph;
3. else modified -> *;
4. else blank.

It displays name, file version or non-file line count, Dired/BDired pathname special case, and major-mode value. Long names truncate and set the source's raw 000 sentinel/legend. Every row is a TV typeout item carrying the buffer object. (C303-SRC)

Selecting an item action is immediate. A failed later menu action cannot roll back an earlier separately selected one. Typeout regions expire when the underlying output is cleared or reused as specified by TV.

The layout uses MAX-SIZE = min(40, output-width - 40) and VERSION-POS = min(max(max-visible-name-length + 3, 16), MAX-SIZE + 2). The heading places its mode label at VERSION-POS + 15; rows place major mode at VERSION-POS + 20. A name longer than MAX-SIZE becomes its first max(MAX-SIZE - 2, 0) characters followed by raw 000. Each status or truncation legend is emitted only if its glyph occurred. These formulas, including narrow output widths, are strict profile behavior rather than suggested columns.

Genera List Buffers report

With sorting enabled, the implementation performs a stable sort by position in the buffer history; buffers absent from history follow those present. An unfiltered sorted report writes this order back to the global buffer list. A filtered report does not. Sorting disabled preserves existing list order. (G85-SRC)

Status priority is read-only, then new/no-file +, then modified *, then blank. Major-mode errors render <<Error>>; available width controls name, description, and mode truncation. List Buffers passes no period flag and therefore MUST NOT show a current-buffer period or explain one. The period belongs to Edit Buffers. (G85-SRC)

The shared formatter budgets IWIDTH = width - 6 after the status field. Its heading minima are name 12 (the length of Buffer name:), description 13 (the length of File Version:), and mode 9 (two less than the length of Major mode:). On each remaining overflow it performs this exact sequence: unconditionally set mode width to 11; set description width to min(33, current); set name width to max(6, IWIDTH - description - mode); set description width to max(3, IWIDTH - name - mode); then set mode width to max(3, IWIDTH - name - description). The first step can therefore increase a 9- or 10-column mode field. EXTRA is exactly min(10, IWIDTH - name - description - mode) and can be negative at pathological narrow widths. The exact positions are VERSION-POS = 2 + name + (// EXTRA 2) and MODE-POS = VERSION-POS + description + (EXTRA - (// EXTRA 2)) + 1, using the profile's integer-quotient operator, which truncates toward zero. Thus negative odd EXTRA differs from floor division. It left-trims before output; an overlong field is shortened to maximum - 2 characters plus raw 000, and the truncation legend is conditional on that sentinel actually appearing. Edit Buffers calls this formatter at fixed width 94 with period display enabled. List Buffers uses the current typeout-window character width with period display disabled.

Direct numeric List/Edit Buffers entry prompts for one substring. A translated ZMACS-BUFFER-LISTING heading may carry either one string or a list; a list matches when any member substring matches.

System 303 Kill Or Save Buffers

Rows sort by status priority modified *, new +, ordinary blank, read-only raw 036, then alphabetically within a group. Compile is available only to a buffer with a pathname whose major mode reports Lisp syntax. (C303-SRC)

Default selection depends on the exact numeric value:

Thus a modified row can begin with both Save and Kill under value 16. On Do It, move the current buffer to the end, then for each row perform Save, Compile, UnMod, Kill. An abort/deexposure result performs nothing. Any error stops later work and retains earlier effects. Because this profile's kill implementation ignores its no-save argument, Kill-only on a modified buffer can still prompt to save. (C303-SRC)

The chooser row width is the maximum buffer-name length plus five. Padding places a dot at every fifth absolute character position. The chooser is centered at half the current Zmacs window width and height; its visible line count is min(row-count, floor(sheet-height / 14)), with TV scrolling when more rows exist. The hard-coded 14-pixel divisor is part of this source profile.

Genera Kill Or Save Buffers

Rows sort by display status *, +, blank, read-only, then alphabetically by their possibly truncated names. Equal-label order is not established by the source sort. Names longer than 100 characters are truncated to the first 99 characters.

With no numeric argument, Save starts on only when the buffer's :MODIFIED-P :FOR-SAVING result is true. This is not identical to the + display group:

Any numeric argument suppresses default Save selection and its magnitude is ignored. On Do It, move the current buffer to the end, then per row execute UnMod, Save, Kill, Hardcopy. This is the source-defined order, not necessarily a safe order: selecting Kill and Hardcopy calls hardcopy on a buffer object after removal. That exact runtime result remains TODO-G85-KILL-HARDCOPY. Any error stops later work and retains earlier effects. Abort returns no choices, performs no operation, and displays an aborted completion message; Do It with no choices still displays Done. (G85-SRC)

Genera Compare Directories

Compare Directories obtains both directory listings before emitting its difference records. It compares name and type with CL:EQUALP and, unless Ignore Versions is true, version as well. It does not compare contents, device, or directory components. With Ignore Versions, any matching name/type on the other side suppresses each matching version under the source set-difference algorithm. The internal helper returns the two resulting pathname lists as two values. (G85-SRC)

The output state machine is normative:

1. always print the comparison heading;
2. if either difference list is nonempty, handle side one then side two: emit a per-input no-match label when that input listing was empty, otherwise emit a “files in A but not B” heading and one resortable record when that side's difference list is nonempty;
3. if both inputs are nonempty and neither difference list has entries, emit the “no differences encountered” result; and
4. if both inputs are empty, emit the first no-match result and emit the second only when the two directory argument objects are not EQ.

There are therefore zero, one, or two resortable records, one per nonempty difference side, and each initially uses the Name view. Missing block counts sort using sentinel 1,000,000. Missing creation dates use source token 1_40, parsed by the selected reader as (ash 1 40) = 1,099,511,627,776. Directory elements are normal presentations. Strict mode MUST preserve the identity-sensitive both-empty branch.

The command performs no filesystem mutation. Directory-list errors propagate through the Command Processor boundary. Partial typeout can remain if later output or interactive resorting fails.

Shared visible contract

These applications present structured text rather than generic host file-picker widgets. A conforming L2 implementation MUST visibly distinguish:

• headings from actionable rows;
• status from pending action columns;
• read-only editor state from ordinary editable text;
• the current point/row from selected pending operations;
• exit and abort affordances in the mode line where the profile displays them;
• typeout reports from persistent special editor buffers; and
• momentary menus or multiple-choice state from the underlying editor.

Exact historic font rasters and pixel coordinates are not part of L2, but columns MUST remain aligned well enough that action/status meanings are unambiguous. A narrow window MUST use the profile's truncation behavior rather than allow one field to silently overwrite another.

System 303 Edit Buffers

Runtime observation — DB-C303, System 303-0, session d06-d07-20260718, generation 1, 2026-07-18: the named Edit Buffers command displayed two buffer rows, four action columns, a read-only Edit-Buffers mode line, and visible End/Abort guidance. The exact 768-by-963 PNG has SHA-256 bfb96fecd7fc0bac92cc795a687eb0b1e938756fab07ccd9a3a28635f4453a0b and normalized-pixel SHA-256 7e7e951204b44fe98b13b8c0d9e0bdc00fcbc25c4476e0ec74bf7650505a1be2. It proves this initial visible state only, not the later U defect, dispatch, destructive effects, or source-to-band identity. Published for reviewed fair-use scholarship; MIT, LM-3, and contributors do not endorse this museum.

Strict DB-C303 MUST preserve the recognizable four-column design. It MAY use different screen dimensions at nonvisual conformance levels, but it MUST NOT present the one-column Genera editor as this profile.

Genera Edit Buffers

Runtime observation — DB-G85, Genera 8.5, session d06-edit-buffers-genera-20260719, generation 1, 2026-07-19: explicit modifier down/up events delivered Control-X Control-Shift-B, the mode line identified Zmacs (Edit Buffers) *Edit-Buffers-1* (RO), and lowercase d placed D in the single action column. No marked action was executed. The exact 1200-by-900 PNG has SHA-256 72ab740da8adc1cbe6c1b784ece34679b5b21d12ad01a54a686d53badc1b1de0 and normalized-pixel SHA-256 61469b3f957c209b6860ef00c273393968fc0b735a49466ccce01b992b5ce133. It proves only the recorded entry and visible mark transition, not Abort, deletion, List Buffers, Dired, or source-to-world identity. Published for reviewed fair-use scholarship; Symbolics and other rightsholders do not endorse this museum.

Strict DB-G85 MUST preserve the one-action-column view, distinct status column, Buffers in Zmacs heading presentation, read-only mode line, and visible exit hint.

Screenshot boundaries for the remaining applications

No login prompt is a substitute for a populated Dired view. No Edit Buffers frame is a substitute for BDired, List Buffers' row menu, Kill Or Save Buffers' chooser, or Compare Directories. The current isolated harness exposes no disposable guest-visible host file service, and the preserved CADR Dired attempt stopped at an unconfigured ED-FILE login without credentials. Therefore:

• TODO-VIS-DIRED-C303 and TODO-VIS-DIRED-G85 require populated disposable listings, local Help, fixed menu, and non-destructive confirmation state;
• TODO-VIS-BDIRED requires two disposable directories and a visible transfer view;
• TODO-VIS-LIST-C303 requires a typeout row hit and seven-item menu;
• TODO-VIS-KOS-C303 and TODO-VIS-KOS-G85 require synthetic buffers and an aborted choice transaction;
• TODO-VIS-COMPARE-G85 requires two disposable guest directories and both resortable difference records; and
• TODO-G85-LIST-HIT requires a concrete presentation hit rather than the already reviewed generic pointer documentation.

Every future image MUST be captured through the appropriate Xvfb harness, retained raw under the ignored session tree, reviewed for its exact publication use, and cataloged with portable provenance before it is linked here.

Binding and entry tests

Dired and BDired tests

Buffer-manager tests

Visual, rights, and provenance tests

Recorded runtime witnesses

The System 303 session d06-d07-20260718, generation 1, used load band System 303-0; disk SHA-256 bb16e46ad81decfe1efe691d36b6aa4ce3fd4ffb82474365de3520989d397cb5; and usim SHA-256 707a77d23e28ea1c45ae0eb0145dc181fa7ba649b9defc30044d4f847ac2c5be at start and execution. It ended with forced_stop=false, state_may_be_incomplete=false, emulator/Xvfb status zero, and unchanged public base disk. This intermediate session predates the current structured action log; its screenshot sidecar does not itself contain the execution-time emulator hash, which is joined from run.json.

The Genera session d06-edit-buffers-genera-20260719, generation 1, used base and private Genera-8-5.vlod SHA-256 a8ee5e86cc7e322f7385af3e0cd579d7650d4dcfc3ce328acbf8b25515dd0672 at start and stop; VLM SHA-256 9f5e18d5770f973879716182b6856ef5a8ee9d3b2bb907476ea0cf35986aa4c7; 26 action records with SHA-256 a6e95256eb5f29113b39c6a95954246d4d63785c3a700d8591b31947eda89fe5; and final run-record SHA-256 cd12c4a5b93b628835df86af5eef3c511c93fbbb205a955a401d19134a61f48b. The stop observed a prompt, sent confirmation, and observed cleanup progress, but did not record confirmation acceptance. Bounded cleanup was forced with forced_after_confirmed_shutdown_stall=false, state_may_be_incomplete=true, and orderly_vlm_host_shutdown=false. The world was unchanged, no process remained, the harness invoked neither Save World nor a checkpoint, and both remain unknown.

Runtime closure probes