EINE, ZWEI, and Zmacs editor-family reimplementation specification

Release profiles

ED-Z46 is intentionally asymmetric. Standard ZWEI source and the generated named-command artifact are normative where identified; a full System 46 Zmacs application conformance claim is unavailable until the missing artifact is recovered. No later table may be substituted.

The application boundary is:

• EINE itself for ED-E77;
• ZWEI editing and the evidence-bounded Zmacs layer for the later profiles;
• core language/text modes and editor-stream integration owned by those editors;
• only the transition edges to task editors and other applications.

D06 owns Dired, BDIRED and Edit Buffers application closure. D01 owns Lisp Listeners and ZTOP; D08 owns mail reading and composition; D12 owns Debuggers; D18 owns patch editors; D25 owns source comparison. Their local tables remain listed in the normative binding companions so the global tree is not hidden, but they do not gate D05 conformance.

Conformance levels

This specification defines ED-E77/L2, ED-Z303/L2, and ED-G85/L2 at the semantic and behavioral grain stated here. It defines a separately named ED-Z46-STANDARD/L1 target only for preserved Standard ZWEI and the built listing; it makes no full ED-Z46/L1 claim because the Zmacs artifact is missing. L3 is reserved.

An L1 implementation MUST emit a machine-readable effective binding graph with ordered table provenance and explicit unbound leaves. A patch, optional product, site form or user remap MUST be an identified overlay on a selected base graph.

Exact public EINE artifacts

The recipe is eine/9004365/dlw/eine.8, 1,129 bytes, SHA-256 1ae9bed8b613e4bf1997b8a232e66de20c525f399c1cd15964c75f56282f4976. Its resolved 19-module corpus totals 276,909 bytes; the ordered manifest SHA-256 is 7aefec316b32dac5ec42db1721655c010a14c394ecb2c9b7f03b42a7261ed8f5.

Exact public ZWEI/Zmacs artifacts

The pinned System 303 tree contains 42 selected ZWEI files totaling 1,706,505 bytes; their ordered manifest SHA-256 is 87af558ea62e894f8f279f73365b1dee69786f09fb657928a90cd76c61d19a1a.

Exact licensed Genera artifacts

The 54-module base Zwei corpus totals 2,405,992 bytes; its declaration-order manifest SHA-256 is d32d09305b38f8636d689cf89161a2e97fba254ea5890fd448bef3b984eed6eb. The declaration witness is sys.sct/zwei/sysdcl.lisp.~3~, 5,581 bytes, SHA-256 69a0dc2c0709cabcf1d3b14c35e745fbcb0b6414efc800057473c1d93545d0c3. The purchased archive is 206,213,430 bytes with SHA-256 89fb3e76b91d612834f565834dea950b603acf8f9dbacacdd0b1c3c284a2d36e. Those inputs remain local and ignored.

All three corpus-manifest hashes use the same byte format: each record is the UTF-8 portable pathname, one NUL byte, and the 32-byte binary SHA-256 digest of the file; records are concatenated without a terminator and hashed again. E77 and C303 records are ordered by portable pathname. G85 records follow sysdcl.lisp.~3~ declaration order and use archive-relative, versioned sys.sct/zwei/ pathnames.

Exact runtime artifacts

Source profiles and runtime witnesses remain separate even when they have the same release label.

Neither runtime identity proves that the maintained/public or licensed source tree is the exact source used to build that disk or world.

Normative evidence map

EINE records

EINE invariants:

1. A permanent pointer occurs in its line's pointer registry exactly once.
2. Inserting at a pointer's exact position advances a MOVES pointer and leaves a NORMAL pointer before the inserted text.
3. Inserting before a pointer shifts it right; deleting over it collapses it to the deletion start; deleting before it shifts it left.
4. Multi-line deletion joins the surviving prefix and suffix, relocates all affected pointers, and removes the consumed line records.
5. Insertion beyond end of line pads intervening columns with blanks.
6. The active mark delimits one region and is cleared after a completed command unless that command explicitly requests preservation.
7. A temporary pointer is caller-owned and MUST NOT survive as a line-registered anchor.

ZWEI and Zmacs records

ZWEI invariants:

1. A line's next pointer and its successor's previous pointer agree.
2. Every permanent buffer pointer belongs to its line registry and uses a valid index; temporary working pointers are not leaked into that registry.
3. The first and last boundary pointers of a node remain reachable in document order after every mutation.
4. Text mutation advances the owning node's modification state and invalidates every display/parser cache whose dependency intersects the mutation.
5. Read tick, save tick, current modification tick and external file identity remain independently representable.
6. Window selection changes the active editing context; it MUST NOT copy the underlying text merely to provide another view.
7. A mode-local table may shadow, inherit or hard-disable a base leaf; flattening must retain that provenance.

Normative companion incorporation

The following files are normative, not explanatory appendices:

If this specification and a companion disagree about an individual leaf at the same repository revision, that is a documentation and conformance defect; a timestamp does not select a winner. Neither document may turn an explicit TODO into a binding.

The D05 boundary includes every EINE/ZWEI/Zmacs-owned fixed key, pointer cell, translator, action, menu, mode, and context. It incorporates D28's complete selected-source three-module catalog and its exact ordinary-Zmacs inherited 47-definition/59-record subset. The other seven Presentation Inspector translators remain typed delegation edges that require a compatible nested Command Processor context. TV global ingress and live-world registry identity, patches, remaps, equal-score order, optional products, and site/user definitions remain explicit runtime overlays; they MUST NOT be reported as base application bindings or silently classified as unbound.

Common effective-tree schema

Every L1 implementation MUST expose this representation for every input:

The required abstract lookup result is one of:

command(name)
prefix(child-table)
alias(target-character)
menu(menu-id)
sentinel(value)
undefined-hard
unbound
intercept(owner, operation)

EINE tree and lookup

EINE input
├─ mouse/tablet bit set
│  └─ region(text | line | paragraph)
│     └─ click-count(1 | 2 | 3+)
│        └─ physical button(0 | 1 | 2) -> command or unbound
└─ keyboard
   └─ modifier row(plain | Control | Meta | Control-Meta)
      └─ character code
         ├─ alias(row, code) -> repeat lookup in same table
         ├─ C-X prefix -> read exactly one further input through prefix array
         ├─ M-X -> complete over named-command alist
         ├─ command -> execute
         └─ NIL or unfbound symbol -> editor error

The initial main array has 576 cells: 263 direct commands, 78 lowercase aliases, one Control-X prefix and 234 unbound cells. The prefix array has 19 direct commands, 104 aliases and 453 unbound cells. The pointer array has 27 cells: 23 commands and four unbound. The companion lists all 53 named commands.

The effective tree MUST then apply dynamic shallow shadows:

• EDT changes exactly six main cells, including activation, clear and exit, and hard-unbinds ordinary M-Z and C-M-Z;
• a string minibuffer temporarily binds raw modifier-row-0 code 033 octal and plain Return to string exit, changes C-G to minibuffer cancel/beep, and hard-unbinds C-Z, M-Z, and C-M-Z;
• a Lisp-reading minibuffer changes C-G to minibuffer cancel/beep, binds C-Return to read/exit, and hard-unbinds C-Z, M-Z, and C-M-Z.

These dynamic bindings unwind with the recursive edit. They are not permanent mutations of the initial table.

Aliases MUST be cycle-detected in a clean-room implementation. Historical source does not provide a cycle guard; strict mode MAY reproduce nontermination for a user-created cycle only in an isolated test, while the default safe profile MUST report an alias-cycle error without editing text.

ZWEI/Zmacs precedence tree

For ED-Z303, effective input depends first on the active reader. Genera MUST retain its own source-profile reader/interceptor distinction rather than inherit this System 303 detail merely because its table composition is similar:

TV input ingress
└─ active input reader
   ├─ ordinary command or prefix read under WITHOUT-IO-BUFFER-OUTPUT-FUNCTION
   │  ├─ special window event -> editor object's special-event handler
   │  └─ keyboard or mouse character, including Abort/Break family
   │     └─ transient or task context, if active
   │        └─ minor-mode overlay(s), in installed precedence order
   │           └─ major-mode comtab
   │              └─ Zmacs application comtab
   │                 └─ Standard ZWEI comtab
   │                    └─ unbound
   └─ input read outside that dynamic suppression
      ├─ Abort / Meta-Abort / Break / Meta-Break -> installed TV intercept tree
      └─ other input -> reader-specific handling

Control-X is a staged child tree:

C-X
└─ Zmacs Control-X table
   └─ Standard Control-X parent
      ├─ local or inherited command
      ├─ Help -> describe containing prefix
      ├─ Abort -> prefix abort
      └─ absent -> not-defined error

Minibuffer, completing-reader, pathname, FQUERY, extended-search, editor-stream, recursive-edit and standalone tables have the distinct parent chains drawn in the normative companions. They MUST NOT be collapsed into one “minibuffer map.” In particular, a local explicit undefined cell stops lookup; an absent cell inherits.

System 303 command lookup evaluates a cell in the current table, follows the parent only for a missing cell, and restarts alias resolution from the original top table. A top-level override can therefore shadow the destination reached by an inherited alias. An explicit undefined sentinel is observably different from absence. Genera MUST retain the equivalent result even if represented differently.

Reader-context TV interception

System 303 installs an editor TV interception list around the command loop, but that outer installation does not determine every input path. The WITHOUT-IO-BUFFER-OUTPUT-FUNCTION macro dynamically binds TV:KBD-INTERCEPTED-CHARACTERS to NIL; its source says this inhibits synchronous intercepted characters such as Break and Abort but does not affect asynchronous characters such as Control-Abort. Both the ordinary command read and the child prefix read use that wrapper.

The installed intercept operations retain their distinct consequences: Abort and Meta-Abort enter the corresponding abort paths; Break clears scheduler inhibition and enters the ordinary break path with editor-idle false; Meta-Break enters the error-break path. A returning Break completes typeout and redisplays editor windows except in the source-defined recursive/typeout cases.

The Standard and local Break or Abort cells are therefore effective table facts for wrapped ordinary and prefix reads, not dead documentation. Unwrapped readers retain the interception branch. A conforming input graph MUST record which reader context produced a leaf. ED-Z46 and ED-G85 interception remain bounded to what their selected sources establish; this System 303 mechanism is not backported or forward-ported by assumption.

Numeric arguments

EINE starts a command with value 1 and presence false. C-U multiplies the value by four and sets presence true. Digits form a signed decimal value. Minus forces the value negative rather than toggling it; a lone minus leaves EINE's presence flag false while the value is −1. Argument commands return an internal “continue reading” sentinel and do not complete a real command.

System 303 starts with value 1, presence false, digit count zero. Minus establishes negative/sign state; digits accumulate decimal input. The exact configured minus family is the literal family in the normative companion. It includes a duplicated C-- constructor cell and does not contain H-C--, even though the digit ranges do contain the corresponding Hyper-Control digits. An implementation MUST preserve the selected source tree rather than regularize this asymmetry.

Genera uses its configured argument commands and modifier families as listed in its companion. A conformance dump MUST enumerate the actual expanded cells; prose such as “all modifier combinations” is insufficient.

A special window event received during a System 303 numeric argument MUST preserve the argument and continue reading. After a real command, argument state resets even if the numeric value happened to be one.

Help, pointer and dynamic-presentation leaves

Self-documentation receives the active context, not a frozen wall chart. It MUST be able to:

• describe a direct key and follow a prefix into its child table;
• report the effective command and the table that supplied it;
• distinguish unbound, hard undefined, missing implementation and intercepted input;
• enumerate named commands visible through the current table chain; and
• show context-specific completion or minibuffer Help.

EINE pointer dispatch is completely fixed by region, saturated click count and button. Its two allocated paragraph operations that only beep remain beep-only stubs. Later ZWEI fixed mouse cells coexist with TV/System gestures. Genera also creates context-sensitive presentation translators, bottom-line pointer documentation and right-button menus. Those dynamic objects MUST be exported as a separate overlay with presentation type, gesture, priority, applicability predicate and owner; they MUST NOT be invented as fixed comtab cells.

The Genera Zmacs captures prove that bottom-line pointer documentation and an Operation menu exist in the exercised List Buffers window. They show only generic window/menu documentation, not that a typed buffer-row presentation won lookup. The source establishes the presentation machinery; an exact-glyph hit probe and live translator dump remain TODO-RUNTIME.

Exhaustive enumeration requirement

For each selected context, the conformance runner MUST enumerate the finite physical character domain used by the release, all supported modifier combinations, every pointer cell or registered presentation gesture, and recursively every prefix. It MUST record:

1. candidate tables in lookup order;
2. alias expansion and generated normalization;
3. the selected leaf and owner;
4. whether the leaf is reachable, shadowed, hard undefined or unbound;
5. Help's reported result; and
6. the source companion row and effect-contract section used as the oracle.

Every reachable D05-owned fixed leaf in an L2 profile MUST resolve to a normative effect contract in the core editing, register/macro/replacement, undo/search, mode, file, window, or lifecycle sections. A dependency-owned leaf MUST name its dossier/specification boundary. A graph that merely maps a bound key to an otherwise unspecified command symbol is L1 dispatch evidence, not an L2 behavioral implementation.

Enumeration MUST terminate on cycles, repeated prefix/table pairs and dynamically generated menus. Site or user overlays are compared separately against a pristine base graph.

EINE command loop

At editor entry, EINE initializes or reuses its editor state, makes the appropriate screen records current, clears the screen, performs complete redisplay and enters the command loop. Each completed command transaction follows this order:

1. Reset numeric and per-command dynamic state.
2. Deactivate stale echo output and repair lost mode-line/blinker state.
3. Reclaim the temporary editor allocation area.
4. Read a character, lookup a command and execute it.
5. If the result is the argument sentinel, preserve argument/mark state and repeat step 4 without completing a command.
6. If the command killed the current buffer, require selection of another buffer.
7. Move current command type to last command type.
8. Clear the active mark unless the command requested that it stay.
9. Reset per-command state.
10. Validate that the command result is a numeric redisplay degree.
11. Accumulate that degree and perform minimal, pointer/buffer, or full-screen redisplay as required.
12. If a temporary special screen was shown, wait for acknowledgement, invalidate the normal display and redraw it.

End of input exits through the editor's EOF path. A normal top-level exit runs recovery, clears the console cursor record and calls the selected exit continuation. Recursive minibuffer exit instead restores the enclosing window, redisplay degree, blinker and screen outline.

An undefined cell, unfbound target, illegal command result or explicit editor BARF:

• clears current command type and argument state;
• can print the diagnostic on the debug/echo stream;
• rings the display bell, with optional separately loaded visual effects;
• marks redisplay lost and, outside debug mode, marks a special screen active; and
• nonlocally returns to the command loop.

Text mutated before BARF remains mutated unless the particular command supplied its own inverse. A clone MUST NOT promise automatic rollback.

ZWEI command loop

The later loop is entered with a current editor closure, window, interval, active comtab and mode-line state. It:

1. processes queued window-selection, configuration and redisplay events;
2. begins delayed selection so the frame is not exposed in a half-redrawn state;
3. derives the exposed window list and draws the mode line;
4. flushes covering typeout where appropriate;
5. installs the four outer editor TV intercepts;
6. resets command type, numeric state, mark-retention state and minibuffer-command state before a real command;
7. clears prompts, redisplays all editor windows and refreshes the typein window;
8. reads any keyboard, mouse or special event while dynamically suppressing the synchronous intercept list for this ordinary command read;
9. sends special events to the editor object; a handled event during a numeric argument returns to input without consuming that argument;
10. looks up and executes an ordinary character with command hooks;
11. records minibuffer commands in their ring, updates typeout completion and runs post-command behavior; and
12. flushes delayed selection on every normal or abnormal exit.

The loop surrounds command execution with an error restart whose top-level wording differs from recursive editing. An editor error returns to the appropriate loop, marks text redisplay because mutation may have occurred, terminates a keyboard macro being defined or replayed, reports/beeps, and preserves a usable editor context.

The command result is a redisplay degree or the argument sentinel. A command hook may skip the target by throwing to the command executor. Hooks run in defined priority order before the command. A port MUST expose that skip as a completed dispatch with no command body, not as an unbound key.

Redisplay degrees

Both lineages permit commands to return the least display repair required. A portable implementation MAY use different numeric constants, but MUST preserve this ordering:

none < point/blinker < changed lines or buffer < mode line/window < complete screen

Redisplay invalidation is monotonic within one transaction. A later request cannot downgrade an earlier full redraw. Logical text, point, mark and history are authoritative; line/pixel caches are disposable.

Insert characters

Preconditions:

• point belongs to the selected writable interval;
• the character is representable in the selected profile; and
• numeric repetition is nonnegative for ordinary insertion.

Required order:

1. Check read-only state before text mutation.
2. Normalize the insertion character only as the active command/mode requires.
3. If EINE point is beyond the line fill pointer, insert blanks to point.
4. Insert at point.
5. Relocate permanent pointers: pointers after point advance; at point, MOVES advances and NORMAL remains before the new text.
6. Advance the active point according to the command.
7. Update node/buffer ticks and undo/history state where the profile supports it.
8. Invalidate syntax and redisplay caches intersecting the changed span.

For a repeated insertion, strict mode performs the historical sequence rather than one opaque host-string replacement whenever pointer relocation or hooks can observe intermediate positions. Failure after some repetitions retains the completed prefix.

Split or insert line boundary

Inserting a line boundary creates a successor line, moves the suffix at point to it, and places point at the selected command's resulting position. Permanent pointers in the suffix move to the successor with adjusted indexes; pointers exactly at the split respect insertion affinity. Linked-line profiles update reciprocal links and node ownership. EINE updates its line array and line ordinals.

Indent-new-line additionally computes indentation after the split. A failure in indentation does not retroactively remove a line boundary already inserted unless the selected release command explicitly recorded it as one undo batch.

Delete a range

Preconditions:

• both endpoints belong to the same writable top-level text object; and
• the range is converted to ordered start/end positions.

Required effects:

• an empty range changes no text;
• pointers strictly inside collapse to the start;
• pointers after the end shift by the deleted length/topology;
• a same-line delete closes the character gap;
• a multi-line delete retains the start-line prefix and end-line suffix, joins them, relocates affected pointers and removes intervening line objects;
• point becomes the selected command's required boundary;
• kill commands append/prepend or create a kill-history entry according to last command type, while plain deletion does not masquerade as a kill; and
• modification, undo and redisplay state are updated after the text change.

If the command discovers read-only state before mutation, text and history remain unchanged. If a lower-level failure occurs after mutation, the profile-specific partial state remains and the command-loop recovery redraws it.

Movement and structural navigation

Movement commands accept point, direction, unit and signed repetition. Units include character, real/display line, screen, edge, buffer, word, sentence, paragraph, S-expression, list, definition and profile-specific field or section. They MUST:

1. preserve text;
2. either arrive at the furthest legal boundary or report the selected profile's boundary/search error;
3. retain the goal column across compatible vertical commands;
4. use active syntax/mode rules for word and Lisp-structure units; and
5. request only the redisplay needed to show point and any changed region feedback.

A negative argument reverses direction where the historical command supports it; it is not universally equivalent to calling the opposite named command. Unknown per-command negative behavior is a test obligation, not an inferred convenience.

Point, mark and region

Point is the active insertion/command position. Mark is a saved pointer plus an active/present predicate. Setting mark pushes or rotates the point stack according to command state. A region is the ordered span between point and active mark.

Region-consuming commands MUST reject an inactive or foreign-buffer mark before mutation. After a completed command, EINE and later ZWEI clear/deactivate mark unless the command sets mark-retention state. Movement, documentation and redisplay commands that historically preserve mark MUST do so. Swapping point and mark changes the active endpoints without changing text.

Each editor window can preserve its own point/mark/view state when buffers or windows are switched. A buffer also retains saved editing state for later selection. The implementation MUST define which layer is currently authoritative and round-trip it without silently merging positions from two windows.

Kill, save and yank histories

A kill entry contains an ordered text interval copy with the profile's character style/font information. Consecutive compatible kill commands coalesce in command direction; Save Region creates history without deleting; Append Next Kill changes the coalescing state for the following kill.

Yank inserts the current entry and records the exact inserted span. Yank Pop is legal only after a yank/yank-pop-compatible command; it replaces that span with the next history entry and updates the recorded span. Matching-yank variants filter candidates without corrupting the underlying order. If no candidate exists, text remains in the last coherent state and the editor reports the miss.

Transposition, case, fill and indentation

Transposition commands exchange the selected adjacent characters, words, sexps, lines or regions and relocate point/pointers as ordinary delete/insert semantics require. They reject missing neighbors before mutation where possible.

Case conversion preserves the number and topology of characters unless the selected character repertoire has a profile-specific non-one-to-one rule. Fill and indent commands use current mode variables: fill column/prefix, tab stops, comment syntax, package/readtable and Lisp indentation metadata as applicable. A mode-specific implementation wins over the base command at the same binding.

EINE font commands change raster-font character state. System 303 font commands change the editor's character font representation. Genera style commands operate on character styles and typein style, which can include family, face and size. A clone MUST NOT substitute vector-font claims for the earlier raster profiles.

Registers

A register name is one case-insensitive, unmodified character. Text and saved position are independent register properties. Help describes this naming context and resumes acquisition. Abort, a modified name, and—under System 303—a code outside its supported range fail before register or buffer mutation. Genera accepts an unmodified printing character.

The fixed leaves are C-X G Get, C-X X Put, C-X S Save Position and C-X J Jump:

• System 303 Get inserts the saved interval exactly. Genera's leaf is Open Get: after inserting, it consumes the corresponding blank-line span by performing Return semantics and deleting the overwritten span. Missing text fails before insertion. Both preserve font/style data and set yank command state.
• With no numeric argument, the executable Get branches swap point and mark. Their prose labels the final endpoints in the opposite order; executable behavior controls, while exact BP-affinity endpoint naming remains a runtime oracle.
• Put copies the ordered region first; any numeric argument then deletes the source. Failure during deletion leaves the new register property installed. Genera permits an empty region; System 303 applies its ordinary region rule.
• System 303 saves a moving BP and top-level node. Jump first pushes old point, selects the saved node, then moves point; a later failure can leave partial navigation. Genera saves a moving BP and physical display line and restores both through point-history movement. Missing position fails before movement.
• System 303 Kill Register removes text and list membership but can leave an independently saved position; a point-only register cannot be killed by that command. Genera removes text, point and membership together.

Keyboard-macro state machine

A keyboard-macro stream owns the active definition/replay stack, current and previous arrays, inclusive recorded length, current position, repeat/default counts, and one-character pushback. C-X (, C-X ), C-X E, and C-X Q check stream capability before changing that state.

C-X ( removes its own key sequence from any enclosing definition and starts a nested array. With a numeric argument it appends to a previous macro when one exists; otherwise it starts a new definition. C-X ) removes its own sequence, finalizes inclusive length and makes the result previous. Its numeric count includes the definition run: a value greater than one performs N-1 additional runs, zero repeats indefinitely, and the ordinary no-argument close does not replay. Closing with no active definition beeps/exits without text mutation.

While an outer macro is being recorded, C-X E executes the previous array. System 303 records that invocation as a nested macro item; Genera executes it with do-not-store semantics. System 303 also runs its configured pop hook after definition, prompts for a name, generates an internal name on Return and confirms replacement. Genera has no such pop-hook naming step; naming is a separate command.

C-X Q records a query sentinel. During replay it reads this exact subtree:

A later invocation restores every no-query sentinel to a query sentinel. Genera also discards redisplay/window blips around the prompt and accepts only typed mouse-click blips at mouse entries. A macro error stops macro state but does not roll back completed editor commands. Clear Input clears macro pushback and the underlying stream.

Replace and query-replace

Replace String acquires both strings before mutation and rejects an empty search string. It searches the active region when present, otherwise point through the selected interval end. A System 303 numeric value bounds the replacement count. Genera requires one-buffer bounds, holds the write lock during mutation and rejects an empty active region.

Case preservation applies only when the search contains no uppercase character; matched capitalization transforms the replacement. Genera additionally disables that conversion when search and replacement are already equal ignoring case, and either retains explicitly styled replacement text or uniformly restyles it from the first non-whitespace matched character according to *STYLE-REPLACE-P*.

For every Query Replace candidate, the response tree is:

System 303 pushes each offered candidate on point history and has no explicit first-candidate guard for ^; underflow remains a runtime oracle. Genera tracks local history depth and beeps/stays when there is no predecessor, and passes intercepted TV characters to the editor intercept handler.

Each accepted System 303 query replacement is a separate undo save. Genera uses one sparse undo batch by default, selectable to per-replacement records with *UNDO-EACH-REPLACE-SEPARATELY*. Abort never rolls accepted mutations back.

Font/style, comments, and fill

System 303 font mutation stores a raster-font index per selected character; a nonzero index upgrades a thin line to a font-bearing representation. Change One Font touches only the requested old index. Selection accepts A through Z, full-name entry, sampling a pointed character, a menu, Help and Abort; repeated font commands may reuse the last choice. Default Font changes future input only. The source's apparent 26-font overflow check is internally ambiguous, so exact overflow behavior is TODO-RUNTIME.

Genera style replacement discards old style, while merge retains components the new style does not supply. Quick choices include bold, italic, bold-italic, null, smaller and larger. Undefined ordinary characters can define accelerators; modified invalid characters fail. Consecutive character/word style commands can reuse the prior style. C-X C-J directly changes the definition region without an argument and merges with any numeric argument. C-M-J changes future typein style.

Comment commands use the major mode's syntax. Genera calls exit-comment hooks before terminators and enter-comment hooks before starters. With a numeric argument, Comment Out Region removes wrappers only from the consecutive fully wrapped prefix; it stops at the first mismatch and retains the unprocessed suffix as the active region. Complete success clears it.

A fill column below 200 is measured in default-space widths; 200 or greater is a pixel coordinate. Fill retains the prefix, normalizes whitespace, inserts two spaces after sentence punctuation and breaks by rendered width. A positive numeric argument requests adjustment. System 303 fills under one undo save. Genera requires a single-section interval, records sparse filling, then records adjustment as a second undoable operation.

Genera Fill Differently starts from the buffer fill column unless immediately repeated, inherits adjustment only from the adjacent fill family, applies one less than the numeric argument in space widths before filling, and advances retained state by one afterward. Auto Fill runs only after an activation character, without a numeric argument and outside a minibuffer. Genera also requires major-mode support and persists buffer :NOFILL state.

Spelling and hardcopy overlays

System 303 M-$ chooses the current word and uses a loaded local speller or the Chaos ISPELL service. No available server fails without mutation. A correction is one undo save. Its optional whole-buffer query-replace path is questioned by the maintained source itself and remains a runtime oracle.

Genera spelling is optional. Its word alphabet is letters plus apostrophe. It spells the active region, otherwise the containing/current word, or the preceding word when point is on whitespace; no prior word fails before scanning. Corrections preserve case and original style and keep point relative to the nearer endpoint after a length change. Abort leaves earlier accepted corrections. Dictionary choices include accept once, accept for this command, and persistent writable dictionaries.

Hardcopy is external and never text-undoable. System 303 buffer/region printing is synchronous. Print All gathers every choice first and submits sequentially, so failure on item N leaves earlier jobs submitted. Genera hardcopy is an optional named-command overlay without a fixed base key. Buffer and region jobs are synchronous. File hardcopy may query whether to save a modified matching buffer: failed/aborted save submits nothing, declining uses the disk file, and successful preflight launches a background job whose later failures are asynchronous. Missing default printer fails before stream open; spool/device failure can follow external side effects.

Literal and incremental search

Search state contains direction, current pattern, origin, current match and the previous search history. Each character extends or edits the pattern through the active search-input table. A successful step selects the next match and exposes it; a failing extension preserves the last successful position/pattern state needed for rubout or direction reversal.

Forward and reverse search use the selected profile's case and syntax rules. Repeating the search at a boundary either wraps, prompts or reports failure exactly as selected by the command; a clone MUST NOT add implicit wrap globally.

Extended search

The System 303 and Genera companions normatively define the complete C-H operator prefix trees. A parser MUST preserve grouping and the Boolean operators AND, OR and NOT, plus the release-specific character predicates and string-search position operators. Invalid operator input follows that context's unbound/help path and does not become literal search text.

Completion and minibuffer activation

A completion context consists of:

• editable input;
• a candidate source and predicate;
• exact/prefix/substring or apropos policy supported by that context;
• default and history values;
• activation characters; and
• the active child/parent comtab chain.

Completion MAY extend input only to the common valid continuation promised by the selected operation. Complete-and-exit validates the result before returning. Complete-and-exit-if-unique refuses ambiguity. List-completions and Help display results without mutating the candidate registry.

Genera mini-input “special character” cells delegate to the exact gateway and generic-ACCEPT/COMPLETE-INPUT matrices in the Genera binding companion. Those source-profile terminal branches are normative: predicate priority, strict barf, Return insertion fallback, out-of-band rescan, completion, forced return, empty input, Help and invalid/ambiguous behavior MUST all be represented. A live dump is still required to identify caller-supplied predicate sets and patches, not to fill a missing base-source leaf.

Possibility sets

A possibility set records ordered locations such as alternate definitions, callers or warnings plus a current member. Next/previous operations select the corresponding location, update editor/buffer state and retain the list for repetition. Stale or unavailable locations are reported and MAY be skipped only where the selected source does so. Full callers/warnings/debugger application behavior belongs to its dossier; D05 specifies the editor navigation container and transition only.

Create, select, rename and kill buffer

Creating a buffer validates or resolves its requested name, allocates an empty text object, initializes point/mark/view/mode state, and adds it to the release's registries in source order. The later source mutates list, name-index, history, and selection state incrementally; it does not establish an all-or-nothing creation transaction. A duplicate name follows the selected profile's reuse, rename, or query rule. An INF port MAY stage registration and roll it back on failure, but MUST expose that strengthening separately from strict injected failure behavior.

Selecting a buffer:

1. saves the outgoing window's point, mark, start and local environment into the appropriate window/buffer records;
2. makes the incoming buffer/interval current;
3. restores its saved point, mark, modes, package and view;
4. updates buffer history; and
5. invalidates the mode line and affected display.

Killing rejects protected buffers and handles modified/file-associated buffers with the profile's query. After killing the current buffer, the command transaction MUST select a live replacement before ordinary input resumes. References from windows, histories and completion caches must not retain a usable pointer to killed text.

Rename behavior is profile-specific and nontransactional:

• System 303 changes the buffer's name slot, then finds the old name-alist cell and changes that cell to the new name. An interruption or injected failure between those steps can expose a renamed object under the old index; no rollback or interrupt exclusion is inferred.
• Genera's Rename Buffer command first validates the requested name, converts a file buffer to a non-file buffer, then invokes name change. The name-change :BEFORE method removes the old hash entry and installs the new one before the primary method stores the new slot value. Thus successful rename deliberately detaches the visited-file association, and an injected failure can expose registry/object disagreement.

If validation rejects the target before either sequence starts, the old state remains. An atomic clean-room registry transaction is permitted only as labeled INF behavior with strict phase-failure tests retained.

Visit, find, view, insert and revert

Find/visit canonicalizes a pathname through the selected file system, reuses an already associated file buffer where required, reads bytes/characters, constructs lines, records file identity and ticks, applies file attributes/mode, then selects or displays the buffer. A view/read-only operation marks the resulting editing context read-only without conflating that state with external file permissions.

Insert File inserts decoded content at point as an editor mutation and participates in undo where the selected profile records it. Failure after a partial stream read MUST be reported as partial unless a temporary staging buffer prevented visible mutation.

Revert first checks or queries about editor modifications, reads the selected file version, replaces the buffer text, resets association/ticks and invalidates undo or view state as the profile requires. A read failure before replacement preserves the old buffer. A failure after destructive replacement is not described as rollback without evidence.

Save and write

Before saving, the editor distinguishes:

• editor modified state;
• file read-only state;
• buffer read-only state;
• held file lock;
• saved file identity; and
• current external file identity.

An external-change or lock conflict is detected before opening the destination when possible and enters the selected query/error path. The historical System 303 save path writes and closes a stream before updating pathname/file identity/ticks and may discard undo afterward. It is not an atomic modern replace transaction. A conforming strict profile MUST preserve observable ordering:

validate/query -> open/write -> close -> update association and file identity
               -> update read/save ticks -> release or retain lock as specified
               -> optional undo/history cleanup -> mode-line redisplay

If write or close fails, dirty state remains true, the old saved identity is not advanced, and any partial external file effect is reported. A safety-corrected port MAY stage and atomically replace a host file, but MUST label that as INF and offer strict failure simulation for comparison.

Write File differs from Save File where it changes the associated pathname. Copy, append and prepend operations do not change association unless the selected command explicitly does so.

EINE definition sections

In EINE section style, scanning recognizes the selected top-level defining forms and explicit BEGF/ENDF boundaries. It creates sorted section records with original source ranges and separate HEAD/TAIL roles. Editing a section changes its buffer/tick while retaining the defining-file association.

Update File reconstructs one file from its ordered current section set, writes the modified definitions, then refreshes file/section identities only after successful I/O. Forget File removes editor associations without deleting the external file. Load Whole File realizes every section despite the design's preference for demand loading.

If the current file identity differs from the recorded version/date/time/size identity, update MUST report or query about the conflict; it MUST NOT silently overwrite on the assumption that section buffers are authoritative.

Later definition and tag workflows

Zmacs associates definition names and types with buffers, files, sections and tag tables. Edit Definition can produce multiple possible locations; the Genera binding explicitly names “and other definitions.” Compile/evaluate operations accept a definition, region, buffer, file, changed-definition set or tag-table set according to the selected command.

For each operation, the editor:

1. resolves an exact text range and package/readtable environment;
2. records source-location/locator metadata where supported;
3. calls the external reader, evaluator or compiler;
4. routes output/typeout and warnings to the associated editor facilities; and
5. preserves text and dirty state unless the command explicitly replaces text.

Compiler, evaluator, source-comparison, warning, patch and debugger semantics are dependency contracts. D05 owns selection of the source range, environment, output edge and return navigation.

Window layouts

The editor supports one-window and profile-specific two-window layouts, other-window selection, window growth and two views over one region. Zmacs adds layouts selected by its Control-X child such as ordinary two windows, view two windows, modified two windows and two windows showing a region.

A layout transition MUST:

1. save current window/buffer view state;
2. validate that the frame can contain the requested panes;
3. create/reuse pane records and assign intervals;
4. choose the new current pane;
5. repair mode-line, minibuffer and typeout associations; and
6. perform a full affected-frame redisplay.

If pane construction fails before commit, the old layout remains selected. If the historical mutation is incremental and failure can leave a partial layout, strict mode exposes that state and a recovery command restores a legal one.

Noncurrent-window pointer dispatch

For the later editors, pointer input over another editor window may temporarily bind that window, interval, point, mark and active table for the command. Selecting an unselected frame happens before editing. The first-button selection exception and minibuffer Standard-table fallback are specified in the binding companions.

The temporary context unwinds after dispatch even on error. Text mutations remain in the clicked interval; dynamic selection variables do not leak into the formerly current pane.

Typein, minibuffer and typeout

The minibuffer/typein area is a recursive editor context with its own active table chain, prompt and history. Entry saves the enclosing context; normal activation returns a typed or textual result; Abort restores the enclosing context and display. An unbound key clears pending input only where the selected ZWEI command executor does so.

Typeout can cover editor windows and paginate. The command loop waits for or completes unread typeout according to the input received, then redraws newly exposed editor regions. A special event during a numeric argument does not consume the argument.

Display caches

EINE's selected normal non-debug raster regions are:

Its two-window layout uses main regions 002–182 and 187–367, 15 text lines each. The debug layout reserves an additional seven-line debug area and reduces the main window to 25 lines or two 12-line windows. These are selected-source constants; a scaled accessibility port MAY transform them but MUST preserve region order and relationships.

Later editors cache physical lines, continuation state, character widths/styles and the correspondence between logical pointers and screen positions. Text mutation invalidates every intersecting cached line and following line whose wrapping can change. Redisplay may reuse unaffected prefix/suffix rows but MUST derive them from current logical text and selected window state.

Mode lines expose at least application/editor identity, mode, buffer name, modified state and profile-specific position/file indicators. The bottom who/pointer documentation line belongs to the TV/Dynamic Windows substrate but must remain visible where the reviewed profile shows it.

EINE entry

An EINE entry operation receives an editing target or constructs an initial buffer, initializes editor globals on first use, acquires the display/input stream and enters the screen/command-loop transaction. ED, value editing and property editing resolve different target buffers but converge on that transaction.

Normal exit:

1. leaves recursive editing if present;
2. saves current buffer/window point and view;
3. releases or restores editor-owned display/input state;
4. runs EINE recovery;
5. clears the console cursor record; and
6. invokes the exit continuation with the exit reason/result.

Error exit MUST run the recoverable subset of steps 2–5. The editor's temporary allocation reset cannot reclaim persistent lines, buffers or pointers.

Zmacs entry and reuse

Zmacs is a reusable application/process, not a fresh editor object per ED call. Entry resolves a target and then:

1. checks whether an eligible editor activity/process already exists;
2. if idle, selects/reuses it and sends the target editing request;
3. if busy, follows the selected release's wait, use another, skip or query branch;
4. if none is usable, follows the selected release's frame/window construction branch and enters its command loop;
5. initializes the current buffer, tables, mode environment and display; and
6. selects the editor through the D02 activity/window-management contract.

The Genera entry rejects an unsupported remote-terminal configuration where the selected source does so. A port MUST report this before creating a stranded editor process.

The inspected Genera Zmacs new-frame branch sends :COMMAND-LOOP to the result of constructing a ZMACS-FRAME. The nearby unwind protection resets or disables an already obtained process around selection; it does not establish Zmacs-owned cleanup of every partial new window/process/activity construction stage. Strict historical cleanup and registration order are therefore TODO-RUNTIME. A safe INF port SHOULD remove only its partial new objects and MUST identify that behavior as a strengthening rather than attributing it to the historical source.

Quit, abort and dirty-buffer queries

Quit means leave the current editor invocation or select another activity according to profile/context. It is not necessarily process destruction. Standalone and recursive-edit tables have their own exits. In System 303, the wrapped prefix read lets a prefix-table Abort cancel the prefix and any keyboard macro in progress; an unwrapped synchronous read with the editor intercept installed takes the TV Abort path instead. Asynchronous Control-Abort remains outside that suppression.

Before destructive exit with modified buffers, Zmacs enters the selected save/kill query. Canceling that query leaves the editor, buffers, locks and current selection active. Saving commits each file independently; a failure on one file does not justify claiming that earlier successful saves were rolled back. Discarding changes must be an explicit choice.

System 303 Zmacs

Runtime observation — Experimental System 303.0, load band System 303-0, session eine-zwei-20260718 generation 1; (ED T); captured 2026-07-18 and verified for D05 on 2026-07-19.

Runtime observation: (ED T) selected a fresh buffer whose mode line identifies ZMACS (LISP). A conforming ED-Z303/L2 display MUST preserve the dominant editing pane, a distinct bottom mode line, visible point and application/mode/buffer identity. The image does not prove the source-to-band build chain.

Runtime observation — Experimental System 303.0, load band System 303-0, session eine-zwei-20260718 generation 1; Help Help; captured 2026-07-18 and verified for D05 on 2026-07-19.

Runtime observation: Help followed by Help displayed the live staged self-documentation choices. A conforming display MUST make Help visibly modal or typeout-distinct, retain the editor relationship and expose the active dispatcher tree. It MUST NOT copy the screenshot's prose as its implementation oracle; the source-defined tree is normative.

Runtime observation — Experimental System 303.0, load band System 303-0, session eine-zwei-20260718 generation 1; M-X Text Mode; captured 2026-07-18 and verified for D05 on 2026-07-19.

Runtime observation — Experimental System 303.0, load band System 303-0, session eine-zwei-20260718 generation 1; M-X Lisp Mode; captured 2026-07-18 and verified for D05 on 2026-07-19.

These two observations constrain a mode transition: the buffer remains the editing subject while the mode-line mode changes from Text back to Lisp. They do not prove that the buffer's entire local-variable set is identical before and after.

Genera 8.5 Zmacs

Runtime observation — Genera 8.5 base world, session zmacs-research generation 1; Select E then right-button Editor menu; captured 2026-07-18 and verified for D05 on 2026-07-19.

Runtime observation: Select E entered Zmacs and unmodified right button opened the configured fifteen-action Editor menu. A conforming ED-G85 base display MUST preserve a menu clearly associated with the editor and the surrounding editing pane. Menu entries and order are governed by the normative binding companion; the image is not a generic Genera menu template.

Runtime observation — Genera 8.5 base world, session zmacs-research generation 1; mapped Help; captured 2026-07-18 and verified for D05 on 2026-07-19.

Runtime observation: the mapped Help character reached the editor's active dispatcher. The distinct Help/typeout state and its relationship to the editor are required; exact glyphs and copied Help prose are not.

Runtime observation — Genera 8.5 base world, session zmacs-research generation 1; C-X 3; captured 2026-07-18 and verified for D05 on 2026-07-19.

Runtime observation: C-X 3 produced two stacked editor windows and selected a new buffer in the lower pane. A conforming layout MUST retain two independent point/view records, clear pane separation, per-pane mode-line association and one current pane.

The companion Genera screenshots of the List Buffers report, generic bottom-line pointer documentation, and opened Operation menu remain cataloged D06 dependency evidence and are not needed to repeat D05's visual constraints. They do not prove a typed buffer-row presentation hit. D06 now includes a reviewed true Edit Buffers capture with a visible pending delete mark; an exact List Buffers row hit, Dired, and the Kill Or Save Buffers chooser remain D06 runtime obligations. D05 does not repeat the application-specific image.

EINE and System 46 visual oracle

No compatible public EINE or System 46 band has been exercised. The EINE source geometry above is normative, but a reconstruction MUST be labeled source-profile visual conformance until this oracle is closed:

TODO-RUNTIME: locate or construct a rights-clear compatible band; enter an empty editor; insert a synthetic definition; exercise point/mark and one/two-window states; open Self Document and both minibuffer variants; exercise each pointer region with non-destructive actions; capture exact client geometry and shutdown state; compare the fixed raster regions and record every discrepancy.

Profile and evidence tests

Text and pointer property tests

For ED-T01 through ED-T08, generate randomized line text, permanent NORMAL/MOVES pointers at every boundary, temporary pointers and an independent flat-string reference model.

The runner repeats random edit sequences and compares after every step, not merely at the end. It checks line links, owner, interval boundaries, pointer registry membership, indexes, ticks and rendered logical rows.

Exhaustive binding-tree tests

For C303, enumerate all 160 character codes (octal 000 through 237) by all 16 modifier-bit states and two click buckets by three buttons by all modifier states. For G85, enumerate the complete release character-array dimensions rather than assuming the C303 denominator. Every reachable prefix/table pair is visited once and its complete finite child domain recorded.

Numeric and command-loop tests

Editing, history and mode tests

Register, macro, replacement, and production tests

Search, file and section tests

Window, lifecycle and failure tests

Visual tests

Visual comparison is semantic, not a raw pixel-difference gate:

Pixel hashes identify the evidence images but do not impose pixel identity on a reimplementation.

Public CADR/LM-3

1. Verify the public source revision, private copy hash, emulator, disk/load band, microcode and toolchain identities.
2. Clone the public base disk into a disposable private session.
3. Start Xvfb and the CADR harness with exact window targeting.
4. Decline or record boot-time site prompts without adding configured-site state.
5. Use synthetic buffers and definitions only.
6. Dump tables and semantic state without executing destructive leaves.
7. Exercise the smallest representative command in each semantic family.
8. Capture only a state needed for a named visual claim.
9. Exit the guest/session cleanly; record forced_stop and state-completeness flags.
10. Verify the public base disk is unchanged and hash every retained private report.

No compatible EINE/System 46 band is currently known. Their procedure begins only after a rights-clear artifact is identified; System 303 is not a substitute.

Licensed Genera

1. Verify archive, world, VLM, debugger, harness and toolchain hashes.
2. Clone the base world and run under isolated user, mount, network, PID, IPC and hostname namespaces.
3. Keep the source tree, world, raw actions, dumps and screenshots under ignored build paths.
4. Record loaded systems, patches, site/user forms and active mode order before table enumeration.
5. Dump the pristine base/effective comtab and presentation graph without copying source bodies or Help prose into tracked output.
6. Exercise synthetic buffers and harmless fixed/input-context leaves.
7. Record the exact action/result prefix for every candidate screenshot.
8. Publish an image only after capture-specific rights review and catalog update.
9. Attempt an orderly guest exit; if the known cold-load mutex stall forces host termination, label guest persistence unknown and verify the immutable base world.
10. Publish only original analysis, counts, checksums and bounded interface facts.

The existing zmacs-research session had 37 intents and 37 linked outcomes. It verified representative paths, not the exhaustive graph required by ED-K12 through ED-K16.