Screen Editor and Frame-Up layout design reimplementation specification

Release profiles

SE-C303 source and runtime are triangulated evidence, not a proven build chain. The same distinction applies to G85-S452.22 and the base world. A requirement names the witness that supports it rather than silently treating those artifacts as identical.

Screen Editor is a TV/native live-window tool in every profile. Frame-Up is a native Dynamic Windows program framework. Neither is CLIM, and CLIM's use of terms such as frame, pane, presentation, or command does not transfer CLIM semantics into these profiles.

Conformance levels

This specification normatively defines SE-C46/L2, SE-C303/L2, SE-G85/L2, and FU-G85/L2 at the semantic grain stated here. SE-C46 is source-only; SE-C303, SE-G85, and FU-G85 include only the bounded runtime observations listed below. L3 is reserved.

Here, L1 closes every application-owned binding and incorporates the complete selected-source Dynamic Windows, Command Processor, Input Editor, and Zmacs trees named below. Source-initialized maps and live installed maps remain distinct: a site remap or patch is a separately dumped overlay, not an omitted base binding and not an application-owned command. Runtime obligations test the specified source trees and record overlays; they do not weaken this inventory by hiding an unspecified chord.

Exact source artifacts

The installed Help record reports compilation in System 451.0 and Sage 439.0. The ignored decoded text used only for local inspection is 21,280 bytes with SHA-256 ecf64a74115e0cf3d305e2ade3276934b50b50280dc303d76aeaa9c206436b55; neither that text nor a machine-specific build path is linked or tracked.

Normative source and observation map

Selected-module coverage

Screen Editor session

Screen Editor window record

The clean-room semantic record is:

WindowRecord = {
  window: live direct-inferior identity,
  exposure: true | false | bury-request,
  left: integer,
  top: integer,
  right: integer,
  bottom: integer
}

bury-request corresponds to the historical special marker used to request a bury during application; it is not a third persistent TV exposure state. Coordinates are in the edited superior's coordinate space and use left/top inclusive and right/bottom exclusive containment. A snapshot includes a direct inferior only when it is exposed or reports that it remains visible while deexposed.

Frame-Up state

Frame-Up LayoutPane

LayoutPane = {
  box: optional simulated rectangle,
  name: symbol,
  type: registered leaf type | internal-row | internal-column,
  options: property list filtered to the type's allowed keys,
  stacking-direction: horizontal | vertical,
  superior: LayoutPane | null,
  inferiors: ordered list<LayoutPane>
}

Leaves represent emitted program panes. Internal row and column nodes exist only to encode layout. They MUST NOT appear in the emitted pane catalog. A newly made pane merges the selected type's defaults before removing options not allowed by that type. The registry is mutable: adding an existing type name replaces its definition, and enumeration order is the current registry order rather than a fixed seven-item ABI.

Invariants

1. A Screen Editor record names a live direct inferior of the fixed top sheet when captured. Historical code does not make that reference safe against concurrent destruction; a safety profile MAY reject stale references only if labeled INF.
2. In SE-C303 and SE-G85, every changed rectangle MUST receive an affirmative result from the target window's geometry verifier before its edges change; the central apply pass has no independent positive-extent predicate. Strict SE-C46 forwards a command's proposal directly to the target window. In either case an inverted proposal is accepted or rejected according to the target's underlying verification/edge-setting behavior.
3. The historical Screen Editor commit is not atomic. Geometry/exposure effects that precede an error remain unless the underlying window operation itself rolls them back.
4. Undo swaps/reapplies model snapshots; it is not a durable command journal. It has no resurrection or object-destruction operation. The exact outcome after Create or Kill is an oracle gap, and hidden ordering can be reconstructed only approximately.
5. A Frame-Up model is a rooted, ordered tree. Every nonroot pane has exactly one superior, and every superior lists that pane exactly once in the normal state.
6. Frame-Up leaf names SHOULD be unique. The historical numeric-suffix allocator scans all names and chooses one greater than the maximum parseable suffix, but a source comment identifies a duplicate-type standard-layout naming defect.
7. A split creates exactly one new display leaf and either appends it beside the selected leaf under a matching parent or inserts exactly one hidden parent.
8. A normal delete never leaves a hidden parent with one child; the survivor is promoted. The only root leaf cannot be deleted interactively.
9. Generated pane descriptions contain leaves only and contain only the options allowed by each leaf's registered type at generation time.
10. Frame-Up's simulated boxes are advisory display state. The generated framework and Preview, not the boxes, determine real Dynamic Windows layout behavior.

Screen Editor menu order

The order below is normative and profile-specific. Each row is one menu item; there are no hidden Screen Editor keyboard commands.

The Genera menu is labeled Screen Edit Operation. Exit and Undo use the bold-italic Swiss style; Kill and Undo are underlined. System 303 gives Exit the :MENU-STANDOUT style and supplies operation-specific pointer documentation on all 15 items; the preserved runtime visibly showed the Reshape documentation. System 46 has no per-item font or documentation override in this menu. Genera likewise showed Undo-specific bottom-line documentation.

In every profile the menu resource points at a mutable item-list variable and reads its current value when choosing. The tables above define the selected base-release fixture, not an immutable registration ABI. A runtime binding dump MUST record any mutation and invalidate a cached exhaustive-input tree. No separate supported Screen Editor command-registration API was found.

Frame-Up command menu

Frame-Up's command-menu pane has exactly two columns in this order:

All ten are also typed named commands in the local Command Processor. The declaration that makes them menu accelerators marks menu membership; it does not assign a character key.

Screen Editor entry tree

D02 System Menu -> Edit Screen
├─ SE-C46 ordinary single item
│  └─ frozen target -> release-specific screen finder -> edit selected top sheet
├─ SE-C303 button triple
│  ├─ Left   -> edit current mouse sheet directly
│  ├─ Middle -> edit current mouse sheet directly
│  └─ Right  -> frozen target -> release-specific screen finder
└─ SE-G85 button triple
   ├─ Left   -> edit menu mouse/default superior directly
   ├─ Middle -> edit menu mouse/default superior directly
   └─ Right  -> frozen target -> release-specific screen finder

The D02 specification is incorporated normatively for frozen-target timing and button dispatch. Screen Editor has no application-owned character key, prefix key, numeric argument, repeat syntax, or Help prefix. Characters delivered while its temporary menu or mouse tracking waits follow the exact tree below; none names a Screen Editor operation.

Screen Editor effective keyboard and fallthrough tree

The temporary operation menu and all pointing trackers seize or poll mouse state only; they never read characters and the menu is not selected for keyboard input. Screen Editor runs in the System Menu process while the keyboard dispatcher and the currently selected I/O owner remain separate.

hardware code while Screen Editor menu or tracker waits
├─ selected I/O buffer is in raw mode
│  └─ enqueue raw code directly in that private buffer when capacity permits;
│     bypass conversion and every Terminal/System/global/asynchronous branch below
└─ selected I/O buffer is not raw -> convert to Lisp Machine character
   ├─ SE-C46 encoded Terminal/Escape prefix -> global mutable Escape tree
│  ├─ unmodified 0..9/minus/repeated prefix -> base-eight accumulation and reset
│  │  rules; literal 8 and 9 are accepted by the historical accumulator
│  ├─ unmodified Help/? -> global Terminal Help, never Screen Editor Help
│  ├─ registered suffix -> registered global action
│  ├─ Terminal-A/Arrest -> may target Screen Editor because WHO-LINE-PROCESS is
│  │  dynamically bound to its process
│  └─ unknown suffix -> no operation
   ├─ SE-C303 Terminal prefix -> global mutable Terminal tree
│  ├─ digits/minus -> base-ten numeric state
│  ├─ Help/? -> global Terminal Help, never Screen Editor Help
│  ├─ registered suffix -> registered global action
│  ├─ eligible asynchronous/global unknown -> quote into selected I/O buffer
│  ├─ unresolved Rubout -> no operation
│  └─ every other unknown -> beep
   ├─ SE-C46/SE-C303 System prefix -> profile global mutable System tree
│  ├─ Help/? -> global System Help
│  ├─ registered suffix -> select/cycle/create action; current selection may change
│  ├─ unresolved Rubout -> no operation
│  └─ unresolved non-Rubout -> beep
   ├─ SE-G85 Select prefix -> D02 exact global Select tree
   ├─ SE-G85 Function prefix -> D02 exact global Function/numeric tree
   ├─ profile global asynchronous interception
│  ├─ C46 Call or Abort, unless selected buffer requests super-image mode
│  ├─ C303 Terminal/System/Control-Clear, then the selected buffer's asynchronous
│  │  table (base defaults include Control-Abort, Control-Meta-Abort,
│  │  Control-Break, and Control-Meta-Break); super-image makes that table NIL but
│  │  does not disable the preceding global keys
│  └─ G85 -> selected-world TV/Function asynchronous route incorporated from D02
   └─ every other character, including bare Help and any selected-app prefix,
      numeric/repeat key, or unbound chord
      └─ enqueue in TV's bounded global intermediate keyboard queue
         ├─ a later read transfers it to the I/O buffer selected at read time; that
         │  owner's keymap determines its meaning
         └─ no selected I/O-buffer read -> retain it in the intermediate queue

The CADR branches above directly resolve the release difference that the generic TV routing prose formerly obscured. Queue mechanics come from TV keyboard routing, while the selected base-release global prefix trees, including Genera Select and Function, come from D02 complete input binding trees. The mutable registries MUST be dumped at test time; a site-added leaf keeps its recorded owner and is not misattributed to Screen Editor. A global selector or Create can change the selected I/O owner between hardware enqueue and consumption unless a prefix path explicitly preserves typeahead for the old owner. Selection change alone does not wake a mouse-only tracker; the operation chooser returns NIL only when an external effect deexposes or dismisses its menu.

Initial direct-inferior selection common core

choose-window(model, point, button-mask)
├─ find first model record containing point
│  ├─ mask contains Left -> return that record
│  └─ mask has no Left -> abort selection
└─ no containing record
   └─ any button mask -> no target; command-specific abort/no-op result

Containment is left/top inclusive and right/bottom exclusive, and ordered model position breaks overlap ties. In SE-C303 and SE-G85, most initial aborts return the explicit abort sentinel and preserve the prior Undo slot. In SE-C46, there is no sentinel: the unchanged model is treated as a completed result and replaces the prior Undo slot. Later-stage helpers can return unchanged geometry without the sentinel even in later profiles; those exceptions are called out below. A represented deexposed-visible record remains point-selectable because the finder does not filter on its exposure field.

The CADR finder first waits for every button to be up, then samples X, Y, and the raw mask at the first nonzero down transition. Masks 1, 3, 5, and 7 select because they contain Left; masks 2, 4, and 6 cancel. Modifier state is irrelevant, and the helper returns without waiting for release. The System 303 Create-expand point finder uses the same down-time raw-Left-bit rule and the same lack of a final-release wait.

The ordinary operation menu itself accepts any of the seven nonzero three-button masks on an item; blank interior does not select. Except for live Shift state in the Genera Reshape tracker, keyboard modifiers do not alter a Screen Editor-owned menu or geometric pointing leaf: every main-operation button-mask leaf below therefore also covers its modifier combinations. This rule does not extend into the System 303 variable-value editor or Genera Accepting Values, whose encoded modifier, multiple-click, and nested input trees are stated separately. Button identity matters only after dispatch to an operation's nested pointing or choice stage. The main Screen Editor trackers have no double-click branch.

Ordinary operation tree

operation menu
├─ chooser returns NIL because the menu was externally deexposed/dismissed
│  └─ invoke no command; do not snapshot, rotate history, or apply; re-expose menu
├─ Bury -> choose-window
│  ├─ any Left-containing mask -> move record to model end; mark bury-request; apply
│  └─ no Left -> profile abort rule
├─ Expose -> choose-window
│  ├─ any Left-containing mask -> move record to model front; mark exposed; apply
│  └─ no Left -> profile abort rule
├─ Expose (menu)
│  ├─ choose hidden direct inferior -> add/modify exposed record; apply
│  ├─ dismiss menu -> abort/no change according to helper
│  └─ empty list -> C46 no explicit diagnostic; C303/G85 beep, error popup, abort
├─ Create -> D02 System Menu creation helper
│  ├─ success -> retain resulting model and resnapshot later
│  └─ cancel/failure -> C46 returns unchanged model; C303/G85 abort sentinel
├─ Create (expand) [C303/G85 only]
│  └─ same tree with expand flag enabled
├─ Kill -> choose-window
│  ├─ C46 Left-containing mask -> kill immediately; remove record
│  ├─ C303 Left-containing mask -> one-item positive confirmation
│  │  ├─ positive item -> kill; remove record
│  │  └─ dismissal -> abort sentinel
│  ├─ G85 Left-containing mask -> Yes/No confirmation
│  │  ├─ Yes -> kill; remove record
│  │  └─ No/dismiss -> abort sentinel
│  └─ no Left -> profile abort rule
├─ Expand window -> choose-window
│  ├─ Left-containing mask -> compute horizontal then vertical expansion; apply
│  └─ no Left -> profile abort rule
├─ Expand all -> compute horizontal pass then vertical pass; apply
├─ Attributes [C303/G85 only] -> choose-window
│  ├─ Left-containing mask -> profile attribute editor
│  └─ no Left -> abort sentinel
├─ Undo -> return previous model for application
└─ Exit -> terminate session and run restoration

No operation label has an accelerator character. Menu pointer Help/documentation is metadata on menu items and MUST NOT be treated as another activation route.

Move Window staged trees

SE-C46 Move window
├─ choose target: any Left-containing mask selects; no Left cancels but consumes Undo
└─ outline placement loop
   ├─ any nonzero mask -> wait for release, then sample the release-time position
   │  ├─ position verifier accepts -> return edge proposal to central direct apply
   │  └─ position verifier rejects -> beep and continue placement
   └─ no button -> continue tracking

SE-C303 Move window
├─ choose target: any Left-containing mask selects; no Left -> abort sentinel
└─ outline placement loop
   ├─ sample mask and cursor coordinates at button-down; return while held
   ├─ sampled mask containing Middle -> abort
   ├─ any remaining sampled mask containing Left or Right -> propose placement
   │  ├─ position verifier accepts -> return proposal for central edge re-verification
   │  └─ position verifier rejects -> beep and continue placement
   └─ no button -> continue tracking

SE-G85 Move window
├─ choose target: any Left-containing mask selects; no Left -> abort sentinel
└─ outline placement loop
   ├─ any mask containing Middle or Right -> abort
   ├─ Left alone -> propose placement
   │  ├─ position verifier accepts -> return proposal for central edge re-verification
   │  └─ invalid -> beep and continue placement
   └─ no button -> continue tracking

System 46 deliberately does not inspect the final button identity. System 303 Right is acceptance, not a snapping gesture. Those source rules override broader manual wording that says Middle or Right aborts.

Reshape staged trees

SE-C46 Reshape
├─ choose target: any Left-containing mask selects; no Left cancels but consumes Undo
└─ two-corner acquisition
   ├─ first corner: any nonzero mask; wait for release and use release-time point
   ├─ second/lower-right corner: wait for any nonzero mask without storing its
   │  identity, perform blinker cleanup, then sample still-live coordinates without
   │  release; add one to x and y for exclusive right/bottom edges; no abort leaf
   ├─ nonpositive rectangle -> replace with full inside rectangle
   ├─ helper verifier accepts -> return proposal to central direct apply
   └─ helper verifier rejects -> beep and repeat acquisition

SE-C303 Reshape
├─ choose target: any Left-containing mask selects; no Left -> abort sentinel
└─ two-corner acquisition
   ├─ at each corner preserve the button-down mask
   ├─ first corner coordinate -> sampled only after that button is released
   ├─ second/lower-right coordinate -> sampled after down-time mask capture and
   │  cleanup while no release is awaited; then add one to x and y for exclusive edges
   ├─ any mask containing Middle -> beep; return original edges as a normal result
   │  and therefore consume Undo
   ├─ any remaining mask containing Right -> smart corner
   │  ├─ traverse every exposed descendant and the edited sheet itself in depth-first
   │  │  postorder, following each exposed-inferior list in order
   │  ├─ per visited sheet test x-low, x-high, y-low, then y-high independently
   │  ├─ every qualifying directional delta 0 < d < 32 overwrites the prior axis value
   │  └─ after all overwrites clamp x to the closed coordinate bounds
   │     `[inside-left, inside-right]` and y to `[inside-top, inside-bottom]`
   ├─ Left alone -> ordinary corner
   ├─ helper verifier accepts -> return proposal for central edge re-verification
   └─ helper verifier rejects -> beep, error popup, and retry

SE-G85 Reshape
├─ choose target: any Left-containing mask selects; no Left -> abort sentinel
└─ one-corner window-editor reshaper
   ├─ initial active corner -> saved global default, initially lower-right
   ├─ pointer -> warped to active corner
   ├─ any mask containing Middle -> return original edges as a normal result;
   │  consume Undo
   ├─ any remaining mask containing Right -> smart-snap active corner
   ├─ Left alone -> place without smart snapping
   ├─ Shift held during tracking -> move the opposite corner dynamically too
   ├─ negative width/height -> beep and continue
   └─ proposal -> clamp to bounding box, then central window validation

The Genera Shift rule changes tracking mode while held; it is not a prefix and does not require a second key. The one-corner default is mutable global state and MUST be read at operation entry rather than compiled into the implementation.

Edge and corner classification

For Move Multiple and Move Single, select the first containing record. Within its rectangle:

1. For an extent, the low corner zone uses the strict test coordinate < low + truncate(extent / 3) and the high corner zone uses the strict test coordinate > high - truncate(extent / 3). Equality at either third boundary is not a corner-zone hit.
2. A point in both a horizontal and vertical terminal third denotes the corresponding corner.
3. Otherwise normalize distance to the nearest horizontal and vertical boundary on a 0-to-100 scale and choose the nearer edge.
4. The following-arrow blinker origin and rotation identify the selected edge or corner.
5. Genera's finder releases any button outside every record and continues. The older finders return an explicit :OUT classification. C46 passes that invalid descriptor to its add-moving-window path; C46 and C303 Move Single likewise pass it to their feature path and signal rather than silently ignoring it. C303 Move Multiple alone has a source-visible outside branch described below.

C46's source literal for a displayed corner segment is octal 100, decimal 64, and its edge strip is 4 pixels. C303 and Genera use 64-pixel displayed corner segments and 8-pixel edge strips. A conformer MAY scale them only in a separately labeled accessibility profile; strict visual/interaction mode uses those device-pixel values.

Move Multiple association rule

A selected record carries four independent booleans for left, top, right, and bottom. Selecting an edge toggles one; selecting a corner toggles two as a unit. Turning a feature on also turns on every eligible exactly coincident opposite feature:

• a vertical edge association requires equal x coordinates and the selected vertical span to contain the other opposite edge's span;
• a horizontal edge association requires equal y coordinates and the selected horizontal span to contain the other opposite edge's span; and
• corner association requires both shared coordinates and the geometrically opposite corner pairing.

Turning a feature off removes only the selected record's feature pair; it does not recursively clear associated records. The highlighted rectangle list is reconstructed after each toggle.

Move Multiple staged trees

SE-C46 Move multiple: selection phase
├─ any mask containing Middle or Right -> abort whole command
├─ Left inside, released at elapsed <= 60 ticks -> toggle feature; continue
├─ Left inside, still held when elapsed > 60 ticks -> toggle feature; begin movement
└─ Left outside -> pass source-produced :OUT descriptor to ADD-MOVING-WINDOW;
   signal from that invalid feature path

SE-C303 Move multiple: selection phase
├─ any mask containing Middle -> return unchanged normal model; consume Undo
├─ any remaining mask containing Left over a feature
│  ├─ release at elapsed <= 60 ticks -> toggle feature; continue
│  └─ still held when elapsed > 60 ticks -> toggle feature; begin movement
├─ Right alone over a feature
│  ├─ movement-list is non-NIL -> begin movement without toggling pointed feature;
│  │  this includes a retained record whose four feature flags are all false
│  └─ movement-list is NIL -> finish with no geometry change
└─ any non-Middle mask outside -> :OUT toggles nothing and the nonzero mask exits
   selection
   ├─ movement-list is non-NIL -> begin movement without adding the outside feature
   └─ movement-list is NIL -> return unchanged normal model; consume Undo

SE-G85 Move multiple: selection phase
├─ any button pressed outside every record -> release it and continue tracking
├─ any mask containing Middle over a feature -> cancel with unchanged model
├─ any remaining mask containing Left over a feature
│  ├─ release at elapsed <= 60 ticks -> toggle feature; continue
│  └─ still held when elapsed > 60 ticks -> toggle feature; begin movement
└─ Right alone over a feature
   ├─ nonempty move set -> begin movement without toggling pointed feature
   └─ empty move set -> finish with no geometry change

movement phase, SE-C46
├─ track delta and outline; out of bounds -> beep and continue
├─ Left alone -> commit
└─ any mask containing Middle or Right -> return original model normally; consume Undo

movement phase, SE-C303 and SE-G85
├─ track delta and outline; out of bounds -> beep and continue
├─ any mask containing Middle -> return original model normally; consume Undo
└─ any remaining nonzero mask -> commit

The 60-tick threshold is described in the source as one second. Release at elapsed time less than or equal to 60 ticks is the short/toggle branch; movement begins only when the held interval is strictly greater than 60. Strict compatibility MUST use the profile clock's comparison; a portable profile MAY define the wall-clock equivalent and disclose it.

Move Single staged trees

SE-C46 and SE-C303 selection phase
├─ any mask containing Middle or Right -> abort whole command
├─ Left alone on an edge/corner -> select only that feature and immediately move
└─ Left outside -> pass the source-produced :OUT descriptor to the feature path;
   signal rather than silently ignore

SE-G85 selection phase
├─ any button pressed outside every record -> release it and continue tracking
├─ any mask containing Middle or Right over a feature -> cancel unchanged model
└─ Left alone over a feature -> select it and immediately move

movement phase, SE-C46
├─ valid delta + Left alone -> commit
├─ any mask containing Middle or Right -> abort
└─ out of bounds -> beep and continue

movement phase, SE-C303 and SE-G85
├─ any mask containing Middle -> abort
├─ valid delta + any remaining nonzero mask -> commit
└─ out of bounds -> beep and continue

Move Single never adds coincident neighbors. Later profiles test only for Middle at final placement, so Right commits even though user documentation emphasizes Left.

Frame-Up application-owned and incorporated binding tree

global entry
├─ Select Q -> select or create Frame-Up activity
└─ System Menu -> Frame-Up -> select or create Frame-Up activity

Frame-Up local command table
├─ typed command name or command-menu cell -> Set Program Options
├─ typed command name or command-menu cell -> Select Configuration
├─ typed command name or command-menu cell -> Reset Configuration
├─ typed command name or command-menu cell -> Preview
├─ typed command name or command-menu cell -> Done
├─ typed command name or command-menu cell -> Set Pane Options
├─ typed command name or command-menu cell -> Set Pane Name
├─ typed command name or command-menu cell -> Split Pane
├─ typed command name or command-menu cell -> Swap Panes
├─ typed command name or command-menu cell -> Delete Pane
├─ application character accelerator or prefix -> none: accelerator reading is disabled
├─ inherited application command table -> none
└─ application numeric/repeat syntax -> none

layout-pane presentation in the outer idle command-input context
├─ exact unmodified Left / :select on a leaf
│  └─ activated Split Pane <leaf> Horizontally
├─ exact Shift-Left on a leaf, including the raw double-Left encoding
│  └─ activated Split Pane <leaf> Vertically
├─ exact unmodified Middle on any presented layout node
│  └─ Set Pane Options <node>
│     └─ an internal row/column can fail because it is not a registered pane type
├─ exact unmodified Right -> generic Dynamic Windows Operation menu
│  ├─ Split Horizontally and Split Vertically are candidates on leaves
│  ├─ Set Pane Options is a candidate on presented nodes
│  ├─ Set Pane Name is a menu-only candidate on presented nodes
│  └─ Delete Pane is a menu-only candidate on presented nodes
├─ handler-menu-only Set Pane Name <node> <unread name>
│  └─ produce a nonactivated command and acquire the name before execution
└─ handler-menu-only Delete Pane <node> -> produce an activated command

layout-pane presentation while CP is acquiring a layout-pane argument
├─ exact Left -> innermost identity/Select handler supplies the pane argument
├─ exact Shift-Left -> innermost Select-and-Activate handler supplies the pane
│  argument and activates when the reader permits it
└─ outer idle Split translators do not outrank that inner acquisition context

Zmacs standard command table
├─ M-X Extended Command -> name completion/activation
│  ├─ Create Program Definition
│  ├─ Insert Program Definition
│  ├─ Edit Program Definition
│  └─ Edit Program Redisplay Function
└─ C-M-X Any Extended Command -> name completion/activation
   ├─ Create Program Definition
   ├─ Insert Program Definition
   ├─ Edit Program Definition
   └─ Edit Program Redisplay Function

Every Frame-Up keyboard subtree below begins only after Genera console ingress. A hardware code first follows the exact raw-mode, Select-prefix, Function/numeric, asynchronous, and selected-buffer routing tree incorporated from D02 complete input binding trees. A globally consumed Select/Function/asynchronous character never becomes Command Processor or Input Editor text. A selector can also move keyboard focus away from Frame-Up while its program process remains alive.

The Frame-Up command table explicitly disables character accelerators and inherits from no command table. The three command-table names stored in the work area are defaults for the program being generated, not Frame-Up parents. Consequently the framework calls the ordinary Command Processor command reader rather than the accelerated reader. The Input Editor is still active while the command name and arguments are acquired, but its keys edit or navigate that input; they do not repeat a Frame-Up command.

The selected-source Input Editor registry and its dispatch precedence are incorporated normatively from the complete Dynamic Windows Input Editor map. That companion inventory includes every base chord, the C-Q and scroll-register second-stage reads, numeric argument construction, standard intercepted characters, ordinary self-insertion, unknown-control beep behavior, and mutable-overlay rule. Frame-Up adds the following per-call Command Processor option layer ahead of that global editor registry:

Frame-Up interactor character
├─ asynchronous console interception before delivery
│  ├─ C-Abort or C-M-Abort -> selected process abort route
│  └─ C-Suspend or C-M-Suspend -> selected process suspension route
├─ Command Processor command-name option map
│  ├─ graphic text -> self-insert into a command name
│  │  ├─ optional initial colon -> consumed by the command parser
│  │  └─ comma -> ordinary name text here, never a form-reader prefix
│  ├─ Space or Line -> partial-complete/name-token delimiter
│  ├─ Complete -> complete the name, then become its argument-space delimiter
│  ├─ Meta-Complete -> complete/preview and acquire arguments
│  ├─ Tab -> complete and validate, then become Space
│  ├─ Super-Complete -> maximal completion
│  ├─ Help, C-?, or C-/ -> contextual help or current possibilities
│  ├─ Right on a completion presentation -> semantic completion menu
│  └─ Return, C-Return, or End -> activate/terminate only if the command is valid
├─ per-call Input Editor option binding -> run it before the global editor map
├─ exact global Input Editor chord -> run the incorporated editor command
├─ Abort or M-Abort -> normal keyboard interception and top-level command abort
├─ Suspend or M-Suspend with framework typeout
│  └─ expose/use/remove the typeout window, then abort this command read
├─ any modified digit or modified minus -> build an Input Editor numeric argument
├─ C-U -> multiply that editor argument by four
├─ other unbound control/format character -> beep and clear the editor argument
└─ other graphic, Return, Tab, Backspace, or diacritic
   └─ self-insert according to the active CP option/parser boundary

The exact source-initialized command-name stages are:

Each typed route is command-name -> delimiter/completion -> arguments in declared order -> Return/C-Return/End activation. Meta-Complete after the name enters the argument-preview path, which uses Accepting Values when more than one argument remains. Help and completion are recomputed at the current stage; Abort unwinds the current read rather than executing a partial command. There is no Command Processor numeric prefix grammar at the idle Frame-Up prompt because accelerated reading is disabled. Any Input Editor numeric state instead applies to the next editor command or self-insertion and is then cleared.

A translator declared with no gesture is menu-only in this source: it appears in a presentation handler/Operation menu when its tester and input context permit it and MUST NOT be invented as a direct pointer chord. The exact live Right-menu contents were dismissed before reading and remain TODO-RUNTIME-FU-HANDLER-MENU. A Left click in pane whitespace produced no visible split in the preserved run, while a typed Split Pane command succeeded; TODO-RUNTIME-FU-LEAF-HITBOX must establish whether the source translator's presentation region excludes that whitespace or the loaded world differs.

The fixed command-menu pane has the following button dispatch:

command-menu cell
├─ exact unmodified Left
│  ├─ every missing positional argument has a usable default and no confirmation
│  │  is required -> supply defaults and execute directly
│  └─ any missing argument lacks a usable default, or confirmation is required
│     -> acquire/confirm through the Command Processor
├─ exact unmodified Right
   ├─ zero remaining arguments -> execute
   ├─ more than one remaining argument -> acquire with Accepting Values
   └─ exactly one remaining argument
      ├─ presentation type has a non-printer menu displayer -> menu acquisition
      └─ otherwise -> keyboard Command Processor acquisition
├─ exact unmodified Middle -> no Frame-Up command-menu action
└─ every modified Left/Middle/Right raw character -> no fixed-menu handler;
   continue through generic Dynamic Windows resolution, then dead-blip/beep if none

Consequently, Split Pane, Swap Panes, and Set Pane Name use Accepting Values when chosen with Right from the fixed menu; the one-argument layout-pane commands use keyboard acquisition because that type defines only parser/printer behavior; and Select Configuration's menu-choice argument is acquired by menu. These are standard program-framework command-menu handler semantics exercised by Frame-Up's declared commands and therefore part of the effective tree, although the handler mechanism is Dynamic Windows-owned.

The raw mouse encoder constructs a distinct character for each of the 32 combinations of Shift, Control, Meta, Super, and Hyper bits on each of Left, Middle, and Right. Frame-Up therefore has 96 distinguishable raw pointer characters; modifier-bearing characters do not fall back to the unmodified fixed-menu or layout translator. Simultaneous newly-down buttons choose the highest newly-down bit: Left+Middle becomes Middle, while every simultaneous mask containing Right becomes Right. Sequential chords resolve each newly-down transition separately. After a press, the physical encoder waits its configurable interval for release and repress of that same highest button; a NIL interval disables double-click construction entirely. It suppresses double-click construction when keyboard input is already pending, ORs Shift into a recognized second click, and stops after that second click; there is no distinct triple-click encoding. Thus double-Left is indistinguishable from Shift-Left, double-Middle from Shift-Middle, and double-Right from Shift-Right at the logical-gesture boundary. Conformance MUST test direct injection of all 96 logical characters separately from this physical transition/timing path.

Every one of those 96 characters first has a unique primary gesture named from its modifier state and button. The selected source adds only these aliases; every raw state absent from this table retains only its unique primary gesture:

Primary symbol spelling is historical, not a modern canonical modifier order. Numeric bit state 3 is specially printed CONTROL-META; every other combined state uses long-name order Hyper, Super, Meta, Control, then Shift. Thus bit state 19's primary symbols are META-CONTROL-SHIFT-LEFT/MIDDLE/RIGHT, even though the aliases declared with c-m-sh-mouse-* are Monitor/Unmonitor as shown below. A clone that serializes gesture names MUST preserve this distinction.

This is the exhaustive primary-state inventory. Each row expands to the three raw characters <prefix>LEFT, <prefix>MIDDLE, and <prefix>RIGHT, yielding exactly 96 cells; the empty prefix in state 0 yields LEFT, MIDDLE, and RIGHT.

Hyper-only states and unlisted multi-modifier combinations deliberately have no additional alias in this initialization. A handler still needs a compatible presentation/context/tester to make an alias actionable. The map is mutable: set-mouse-char-for-gesture can move or delete an alias and clears the relevant caches. A site-profile dump MUST therefore record all 96 mouse-char-gestures cells and the reverse gesture-to-character pairs.

Before Dynamic Windows sees a physical event, the Essential Mouse layer consumes an exact CHAR-MOUSE-EQUAL match to MOUSE-R-2. It opens System Menu on a console-enabled stream and otherwise beeps; there is no fallback into Dynamic Windows. That character can arise from either a physical Shift+single Right or a natural unmodified Right double click; the two are indistinguishable. Meta-Shift-Right is a different mouse character and reaches the Window Operation Menu path. This ingress rule does not prevent a test harness from injecting the raw character directly below the Essential Mouse layer, so both levels MUST be tested and identified.

Click routing also depends on selection. If the selected window implements the presentation-input-blip handler, hit-testing and coordinates come from the clicked window but the blip travels through the console system-I/O buffer, so the selected window's active input context and command table govern translation. Otherwise the event is forced into the clicked window. A click on an unselected Frame-Up display is therefore not automatically interpreted in Frame-Up's context. On blank area, exact unmodified Left has the generic Select This Window candidate only when the clicked window alias differs from the selected alias; the tester rejects an already-selected window.

For every raw character without a Frame-Up leaf, the complete outcome is:

unclaimed Frame-Up raw pointer character
├─ choose the highlighted innermost presentation using all three button characters
│  that share the event's modifier bits, not only the button actually pressed
│  └─ a sibling-button handler can therefore determine this outer presentation/context
├─ try that highlighted presentation in its highlighted context
├─ retry that presentation across active contexts, innermost to outermost
│  └─ suppress duplicate presentation-type context objects by identity
├─ reselect/retry using only the actual character while ignoring suppress-highlighting
├─ first applicable direct handler -> invoke it
│  └─ handler returns NIL without an explicit non-NIL type, or semantic dead result
│     -> return (dead-blip) without the no-match condition/beep path
├─ applicable menu alias -> construct the context-filtered generic menu
└─ no matching handler
   ├─ signal dead-blip with "<mouse char> is not defined in this context"
   ├─ condition unhandled -> beep
   └─ return the semantic (dead-blip) result

Definite generic candidates still have capability/tester gates. Below physical ingress, Shift-Right has a System Menu handler only on a console-enabled stream. Meta-Shift-Right starts the asynchronous TV Window Editor path. Super-Right opens Presentation Debugging only when its named menu has at least one applicable member; loading the Presentation Inspector component makes that menu nonempty for ordinary nonanonymous presentations when its debugging tester succeeds. While an si:input-editor context is active, Control-Left can hold/mark displayed strings; Control-Middle and Control-Shift-Middle require synthesized raw text; and Control-Right opens its Marking/Yanking menu only when that menu is nonempty. Super-Left and the remaining aliases likewise require a compatible type/tester; otherwise they reach dead-blip. This is generic substrate behavior, not an undocumented Frame-Up command. A conforming profile MUST dump the mutable gesture and handler registries and enumerate all 96 characters in each active context rather than extrapolating from unmodified buttons. Same-priority handler ordering cannot safely be inferred from the selected source's apparent name-comparison typo; the live effective order must be recorded where a tie actually occurs.

The fixed base contract comprises the 96 primary cells, initialization aliases and order, highest-newly-down-button rule, Shift-OR double encoding, lookup/context/dead algorithm, and selected built-in handler definitions. Profile inputs are the mutable gesture map, loaded handler registry and command tables, active context and selected window, tester/capability/object state, physical keyboard-to-internal modifier map, double-click timeout including NIL-off, and local-versus-remote debounce behavior. Every conformance result MUST state those profile inputs rather than treating the source initialization as an immutable global keymap.

Exact unmodified Right on a Frame-Up leaf's layout-pane presentation opens an Operation menu. Its application-owned unstyled members are Split Horizontally, Split Vertically, Set Pane Options, Set Pane Name, and Delete for a leaf; an internal node omits the two Split entries. Generic styled groups add Window Operation Menu always, System Menu when console-enabled, and Presentation Debugging Menu when loaded and nonempty, plus Marking and Yanking Menu when the outer Input Editor context makes that named menu nonempty. All unstyled entries sort alphabetically before all styled entries, which also sort alphabetically; the last choice is remembered separately per menu type. On blank Right there is always Window Operation Menu, optionally System Menu and Select This Window, and—because command reading establishes an outer si:input-editor presentation context—Marking and Yanking Menu when that named menu has an applicable member. There is no Presentation Debugging blank-area member.

Frame-Up confirmation and Preview nested trees

Select Configuration and Reset Configuration use a readline FQUERY, not a single-character Y/N reader:

readline Yes/No confirmation
├─ edit text -> full incorporated Input Editor map
├─ Space/Line/Complete/Tab/Super-Complete -> completion/delimiter behavior
├─ Help/C-?/C-/ -> show the Yes and No possibilities
├─ Return/C-Return/End on a complete Yes or No -> return that Boolean choice
├─ invalid or incomplete text -> retain editable input and request correction
├─ applicable pointer presentation -> return the same semantic choice
└─ Abort/intercept route -> unwind without confirming

Preview uses the generic character reader after drawing the candidate layout:

Preview wait
├─ Refresh -> repaint/reprompt, continue waiting
├─ any returned ordinary character, including Help without an installed help callback
│  └─ leave Preview and restore the designer
├─ Abort/M-Abort -> ordinary intercept/abort
├─ Suspend/M-Suspend -> ordinary suspend/typeout interception
└─ noncharacter blip -> generic TYI blip handler
   ├─ plain Mouse-Left -> ignore and continue
   ├─ other mouse button -> consider global System Menu dispatch, then continue
   ├─ Menu or Typeout-Execute blip -> beep, continue
   ├─ registered blip kind -> invoke its handler
   └─ unknown blip -> ignore, continue

The four Zmacs commands are reached through M-X or C-M-X, but their prompt is Mini-IE rather than the ordinary Dynamic Windows interactor. Its local table binds C-Q, C-G, Abort, the ordinary and shifted M-Y/C-M-Y variants, completion, Help, and conditional Return; explicitly shadows C-Z, M-Z, C-M-Z, and M-; as undefined; and inherits the full Standard Zwei map, including its C-X prefix tree. C-M-X during an active M-X prompt converts it to Any Extended Command while preserving entered text. The exact inherited tree is incorporated from Zmacs Mini-IE and recursive contexts; numeric arguments are displayed/preserved by that editor but do not repeat a Frame-Up integration command.

System 303 Attributes nested input tree

SE-C303 uses the older variable-value editor. Its application-owned row and margin gesture tree is complete below:

The form selects an ordinary TV stream, so hardware ingress still passes through the complete SE-C303 nonraw global layer in the Screen Editor effective keyboard tree before any event below. Terminal and System prefixes, Control-Clear, and the selected buffer's asynchronous table (base Control-Abort, Control-Meta-Abort, Control-Break, and Control-Meta-Break) can therefore act before enqueue; super-image disables only that selected-buffer table. Only an event delivered after those branches enters the idle chooser or alternate rubout handler. The mutable exact Terminal/System suffix trees remain normatively incorporated from D02 and TV; their keys MUST NOT be misreported as RH self-insert or unbound commands.

attribute form
├─ byte-exact MOUSE-3-2 with Control/Meta/Super/Hyper absent, anywhere
│  ├─ physical Shift+single Right and natural unmodified Right double click both encode it
│  └─ essential-mouse layer opens global System Menu before form hit-testing
├─ association-choice row (font, More, Reverse, input action, output action,
│  draw ALU, erase ALU, save bits)
│  ├─ exact unmodified single Left encoding -> assign that choice; no typed input
│  ├─ exact unmodified single Right encoding -> assign that choice; no typed input
│  ├─ unmodified Middle encoding -> no row action
│  └─ any other modifier-bearing or multiple-click encoding -> no row action
├─ typed row (vertical spacing, Other value, priority, name/label, border width,
│  border-margin width)
│  ├─ exact unmodified single Left encoding -> edit an empty input buffer
│  ├─ exact unmodified single Right encoding -> edit the printed old value
│  ├─ unmodified Middle, any other modifier, or multiple click -> no row action
│  ├─ any edit that empties the buffer -> full-rubout handshake below
│  ├─ once editing -> native System 303 alternate-rubout-handler tree below
│  └─ accepted text -> row-specific NUMBER, S-expression, or STRING reader
├─ idle chooser event
│  ├─ Variable-Choice blip -> run the selected row path above
│  ├─ Choice-Box blip -> run the selected Done/Abort path below
│  ├─ Mouse-Button blip -> consume/ignore
│  ├─ every other cons/blip -> signal FERROR
│  ├─ exact unmodified Form atom -> refresh the form
│  └─ every other atom/character -> consume without row action
├─ current bottom margin-choice region established by mouse motion
│  ├─ x falls in the gap/outside both small boxes -> beep and handle; never fall through
│  └─ x hits Done or Abort with any other encoded button
│     ├─ start separate Choice process; enqueue a Choice-Box blip asynchronously
│     ├─ rubout handler consumes it before typed edit returns -> ignored; no choice
│     └─ idle form chooser consumes it -> Done commits, or Abort catches, beeps,
│        applies no setter, returns unchanged normal model, and consumes Undo
└─ no row and the whole-bottom-margin method declined or was not current
   ├─ exact unmodified Left while chooser is deselected
   │  └─ essential-mouse may select the chooser instead of enqueueing a blip
   └─ otherwise -> no form action

For an unmodified physical mask the TV encoder chooses the highest set button: mask 1 becomes Left; 2 and 3 become Middle; and 4, 5, 6, and 7 become Right. Consequently a Left+Right, Middle+Right, or three-button chord takes the exact Right row path, while Left+Middle takes the no-action Middle path. Control, Meta, Super, and Hyper bits remain in the encoded character and prevent an exact row match. Shift increments the click count, so it likewise prevents a single-click row match. This mask rule applies to buttons newly down in one transition. Sequential presses dispatch separately: after Left enters a typed row, a later Right is handled inside the rubout handler rather than retroactively selecting the Right-prefill row path. For a margin choice, only otherwise-unmodified Shift plus a Right-containing mask (or an equivalent natural Right double click) becomes byte-exact MOUSE-3-2 and diverts to System Menu; adding Control, Meta, Super, or Hyper makes it a different character that the margin box dispatcher accepts and schedules. The tracked CURRENT-REGION covers the whole bottom margin; click-time x, not region identity, distinguishes Done, Abort, and the beeping gap.

CHOOSE-VARIABLE-VALUES acquires a temporary form resource, saves the selected window, exposes and selects the form, and runs this event loop. Its unwind cleanup deactivates the form and unconditionally reselects the saved non-NIL object, with no liveness test. Consequently, selecting another window from System Menu while the Attributes form is active can be overridden when the form exits, and a destroyed saved selection is passed back to :SELECT without a defensive guard. This nested selection restoration is independent of Screen Editor's own outer restoration.

The typed replacement stage is native TV, not Dynamic Windows. The selected System 303 load enables ALTERNATE-RUBOUT-HANDLER globally through RH-ON; its mutable binding tree is specified below and MUST be dumped before a site-specific test.

typed-row event inside the alternate rubout handler
├─ cons/blip
│  ├─ Redisplay Rubout Handler -> clear and reprint edited input
│  ├─ configured blip handler -> absent for Attributes
│  ├─ configured preemption -> absent for Attributes
│  ├─ exact unmodified single Right encoding
│  │  └─ open System Menu; keep editing
│  └─ Left, Middle, any modifier, or multiple click -> ignore; keep editing
└─ character
   ├─ configured command/activation/editing/pass-through rule -> absent here
   ├─ exact key in mutable RH-COMMAND-ALIST -> invoke with signed argument
   │  └─ command leaves buffer empty -> return through :FULL-RUBOUT
   ├─ digit 0..9 whose remaining `CHAR-BITS` are nonzero after exact-command lookup
   │  └─ decimal numeric accumulator; normal keyboard bits are Control/Meta/Super/Hyper,
   │     and a synthetically forced Mouse-bit character also satisfies this predicate
   │     (physical Shift instead changes the converted code; Shift-only letters can remain
   │     zero-bit self-insert, while C-Shift-A/D can hit exact registered commands)
   ├─ C-U -> numeric := (numeric if present, else 1) * 4
   ├─ modified minus with no numeric value yet -> toggle negative sign
   ├─ modified minus after a numeric value -> beep; preserve prefix state
   ├─ any other unbound modified character -> beep; clear numeric/sign
   └─ otherwise unmodified -> insert numeric-or-one copies unless sign is negative;
      clear numeric/sign

The handler passes (numeric-or-1 * sign) to a registered command and resets the prefix only after that command returns normally. A command-raised error escapes into the enclosing chooser before that explicit reset, but the argument/sign bindings are LET-bound and local to the unwound handler invocation, so a retry starts with no prefix. Cons/blip handling—including System Menu and ignored blips—preserves the numeric/sign state, so C-3, Right/System Menu, C-F still moves three characters. Insertion batches are capped by the historical 64-element resource buffer; movement clamps at the buffer endpoints and beeps only when asked to move farther from an endpoint already reached. Delete ranges clamp and a zero-width delete is silent. Right-edit inserts the old printed text but supplies no initial-pointer option, so point starts at the beginning of that prefilled text, not its end.

The complete source-initialized RH-COMMAND-ALIST, in registration order, is:

Unless a table row or the paragraph below explicitly names N, zero, sign, or a special argument value, the registered command receives but does not consult the prefix; normal return still consumes and resets it.

Numeric behavior is deliberately nonuniform and MUST NOT be normalized into a generic repeat rule. Default N is +1. C-F/C-B reverse naturally for negative N and no-op at zero; C-P/C-N no-op for every N <= 0. C-D/Rubout silently no-op at zero, but negative N reaches the historical reversed-interval path rather than a reverse-delete feature, so the exact condition or mutation is a required strict oracle. M-F/M-B with negative N do not reverse: their increasing loop proceeds until its boundary/no-next-word exit; the Meta delete commands delete to that result. Meta word commands no-op at zero except M-T, whose zero case explicitly uses mark and whose negative case explicitly repeats backward. C-Q and C-O with zero insert no elements but mark/enter the rescan path: at buffer end the throw is immediate, whereas in the middle the zero-width insertion can return and rescan occurs later. A negative count reaches the historical negative-width insertion path and requires a strict failure oracle. A C-O rescan also skips the command's later reposition step, so its end-of-buffer and middle-of-buffer point results differ. The insertion helper caps the copied batch at 64, but the middle-path subtraction uses original uncapped N; for N > 64 it can overshoot/clamp toward buffer start instead of simply stopping before the 64 inserted newlines. A zero-prefixed ordinary self-insert is more defective: at a fresh Left-start end with no prior rubout it copies nothing but advances scan and can return a stale resource-buffer character, whereas an already edited or Right-prefilled context forces rescan. A strict clone MUST preserve/profile this resource-state distinction, not treat zero as a universal no-op. C-! accepts only a positive match index; zero or negative eventually beeps. M-! supports negative direction and uses the current yank position at zero. M-Y/M-C at zero after a compatible yank delete the prior yank, insert nothing, set mark, and retain the compatible history-command type; without compatible yank state they perform no replacement. History-index signs and wrapping also depend on the selected mutable history policy and MUST be dumped with the registry.

C-Q is the only registered multi-stage prefix in this handler:

C-Q -> read one next event with alternate rubout handling bypassed
├─ exact unmodified single Right mouse blip -> open System Menu; keep reading
├─ any other noncharacter blip -> ignore; keep reading for a character
├─ unmodified character -> insert it N times
├─ modified alphabetic A..Z -> convert to control code 1..26; insert N times
└─ every other modified character -> beep; insert nothing

The Attributes wrapper adds one stage after :FULL-RUBOUT; emptying the buffer does not itself restore the old value:

alternate handler returns full-rubout
└─ stream TYI loop
   ├─ exact unmodified single Right mouse blip -> open System Menu; keep reading
   ├─ any other noncharacter blip -> ignore; keep reading
   ├─ returned character is Rubout -> choose NO-CHANGE and restore old value
   └─ any other returned character -> untyi it; restart from an empty edit buffer

Thus Rubout at the initial Right-start point zero is a silent zero-width delete and cannot empty the prefilled text by repetition alone. The user must first move point right/end and rub out, or use Clear Input; after actual emptying, one additional Rubout restores. A Left-start edit begins empty, so even Help or a motion command that leaves it empty enters this handshake. The active parenthesis-motion definitions in the selected file are the later S-expression commands listed above; the older parenthesis forms are commented out and never register. ADD-RH-COMMAND replaces an existing association or appends a new one, so a loaded-world dump remains mandatory for patches or site additions. At normal physical ingress the essential-mouse layer diverts byte-exact MOUSE-3-2, regardless of whether physical Shift+single Right or natural unmodified double-Right produced it, before it can become a rubout-handler blip. Only an already queued or synthetically forced MOUSE-3-2 blip reaches the handler's generic ignore branch.

After editing, NUMBER rows read one Lisp object and reject it unless it satisfies NUMBERP; S-expression rows use the ordinary Lisp reader; STRING rows use line input. These reader protocols, rather than an Attributes activation-key override, decide when delimiters or Return terminate input. A SYS:PARSE-ERROR is caught inside the stream rubout handler: it prints the error marker, requests re-echo, and stays in the alternate editor so the user can correct or rub out the text. An error that escapes that inner clause—such as NUMBER post-validation rejecting a non-number—uses the variable-value form's outer handler. That handler prints the condition and reads one dismissal character through the stream TYI filter: exact unmodified single Right can open System Menu first and other blips are ignored. Space is consumed. Every other returned character is put back and the form redisplays with FULL-RUBOUT still true: an untyied Rubout is consumed by the next loop's old-value handshake and restores the old value, while any other character is put back again and becomes the first input of the next empty retry.

Genera Attributes nested input tree

SE-G85 Attributes opens an owned Dynamic Windows Accepting Values interaction. Its keyboard events first pass through the Genera console raw-mode, Select, Function, asynchronous, and selected-buffer tree incorporated from D02, exactly as for Frame-Up; only a delivered event enters the accelerated form map below. The complete selected-source idle accelerator tree is:

Accepting Values
├─ local exact accelerator
│  ├─ Refresh -> force redisplay
│  ├─ Help -> Accepting Values help and effective accelerator documentation
│  ├─ End -> Done/validate
│  ├─ Abort -> signal Abort
│  ├─ Space
│  │  ├─ highlighted value/query -> replace it
│  │  ├─ highlighted enumerated choice -> choose it
│  │  └─ nothing highlighted -> accelerator error
│  ├─ C-E
│  │  ├─ highlighted value/query -> edit from old value
│  │  ├─ highlighted enumerated choice -> choose it
│  │  └─ nothing highlighted -> accelerator error
│  ├─ C-D
│  │  ├─ highlighted value/query -> remove/reset it
│  │  ├─ highlighted enumerated choice -> "Can't remove this field" error
│  │  └─ nothing highlighted -> accelerator error
│  ├─ C-N [argument] -> next query
│  ├─ C-P [argument] -> previous query
│  ├─ C-F [argument] -> next enumerated choice
│  └─ C-B [argument] -> previous enumerated choice
├─ inherited Standard Scrolling accelerator
│  ├─ Scroll -> vertical forward
│  ├─ M-Scroll or Back-Scroll -> vertical backward
│  ├─ M-< or Home -> vertical beginning
│  ├─ M-> -> vertical end
│  ├─ Super-Scroll -> horizontal forward
│  ├─ M-Super-Scroll or Super-Back-Scroll -> horizontal backward
│  ├─ C-Scroll -> typeout forward
│  ├─ C-M-Scroll or C-Back-Scroll -> typeout backward
│  ├─ C-M-S then one character -> save position in that register
│  ├─ C-M-R then one character -> restore position from that register
│  ├─ C-S or Super-S -> search forward
│  └─ C-R or Super-R -> search backward
├─ inherited Standard Arguments prefix
│  ├─ C-U [repeatable] -> argument starts at four and multiplies by four
│  ├─ Control-, Meta-, or Control-Meta digit/minus sequence -> signed decimal
│  ├─ dedicated infinity character -> infinite argument
│  ├─ then C-N/C-P/C-F/C-B or argument-aware scrolling -> consume argument
│  └─ then another local accelerator -> accelerator error, beep, clear input
├─ colon -> no full-command route in this table; accelerator error
├─ every other unknown idle character -> accelerator error, beep, clear input
└─ replace/edit opens a field reader
   └─ context-shadowed Input Editor, ACCEPT parser, completion, Help, and activation

Query/choice motion does not wrap. Positive motion from no highlight selects the first candidate; negative motion from no highlight beeps. Reaching an end beeps and preserves the current candidate. Negative arguments reverse direction. A zero query argument preserves the current query; the source's zero-choice branch can lose the choice highlight and MUST be reproduced/tested rather than normalized into a no-op.

The direct presentation and exit-box pointer tree is:

Accepting Values presentation
├─ value/query
│  ├─ exact unmodified Left -> replace
│  ├─ exact unmodified Middle -> edit old value
│  ├─ exact Shift-Middle or encoded double-Middle -> remove/reset
│  └─ exact unmodified Right -> generic Operation menu with applicable
│     replace/edit/remove candidates
├─ enumerated choice
│  ├─ exact unmodified Left -> choose
│  └─ exact unmodified Right -> generic Operation menu with choose candidate
├─ Done or Abort program-framework cell/inline exit presentation
│  ├─ exact unmodified Left -> execute zero-argument Done/Abort
│  ├─ exact unmodified Right -> execute zero-argument Done/Abort
│  └─ Middle or any modified raw gesture -> no cell handler
└─ every other raw modifier/button state
   └─ generic presentation handler if applicable, else dead-blip/beep

Field entry transfers to the full context-shadowed Input Editor and completion tree specified in Dynamic Windows; the idle accelerator table does not remain in control of editing characters. Screen Editor does not catch the form's Abort locally; its eventual preserved-world destination remains TODO-RUNTIME-SE-G85-ATTRIBUTES-ABORT. The source-initialized map is complete here, while live gesture, accelerator, and handler registries remain mandatory comparison dumps for patches and site remapping.

The four Zmacs commands add no command-specific direct chord. In the selected Genera 8.5 standard table, both M-X (Extended Command) and C-M-X (Any Extended Command) reach name completion and activation for all four names, as specified by the exact Zmacs standard command map. Its Standard Zwei, C-X prefix, Mini-IE, Help, completion, and unbound behavior is incorporated at that document's stated scope. Site remappings remain outside this base profile.

Entry-target and nested choice button precedence

The SE-C303 and SE-G85 D02 Edit Screen entries are three-button items. For a multi-button chord the highest set button selects the branch: Right takes precedence over Middle, which takes precedence over Left. Ordinary Screen Editor items and ordinary momentary choices instead execute on any pointer button without inspecting its identity.

The Right-entry target finder is release-specific:

• SE-C46 walks ancestors and retains every BASIC-FRAME, without an explicit exposure filter. With no frame it returns the mouse sheet. Otherwise it ensures a mouse-sheet choice and asks which object to edit.
• SE-C303 retains exposed BASIC-FRAME ancestors and clears the accumulated list after a deexposed ancestor. It stores label/window pairs, then mistakenly tests the raw mouse sheet against those pair objects with the source's MEMQ condition. Whenever the candidate list is non-NIL that test misses, so the code always prepends a (label . mouse-sheet) row. It is a duplicate only when the mouse sheet was already represented among the Basic Frame candidates. The prompt asks which screen or frame's inferiors to edit.
• SE-G85 retains exposed ancestors that affirm :INFERIORS-EDITABLE-P, clears the list at a deexposed ancestor, deduplicates raw sheet identities correctly, and labels them only after collection. Its prompt identifies editing subwindows.

Expose (menu) and confirmation menus accept any pointer button on a row. SE-C303 and SE-G85 beep and display a dismissible diagnostic when there is no hidden direct inferior, but their input contracts differ. C303's complete nested pop-up tree is:

C303 POP-UP-MESSAGE / POP-UP-FORMAT
├─ WINDOW-CALL selects the pop-up and saves the old selection
├─ global nonraw keyboard ingress -> D02 Terminal/System/Clear/async tree
├─ byte-exact MOUSE-3-2 before enqueue, from Shift+single Right or Right double click
│  └─ Essential Mouse consumes it and opens System Menu; keep waiting
├─ if the pop-up became deselected, exact MOUSE-1-1 may reselect it instead of enqueueing
└─ event delivered to the pop-up's keyboard-filtering :TYI
   ├─ any character -> dismiss
   ├─ exact queued MOUSE-3-1 -> open System Menu; continue waiting
   ├─ every other mouse or noncharacter blip -> discard; continue waiting
   └─ WINDOW-CALL cleanup
      ├─ current selection is still pop-up/descendant -> restore saved selection
      └─ another selection remains current -> do not override it

No C303 pointer click dismisses the diagnostic. The same tree governs its invalid-edge POP-UP-FORMAT call sites. The G85 pop-up instead prompts “Click here or type any character” and calls raw :ANY-TYI, so the first keyboard character or pointer blip actually delivered to the pop-up dismisses it; globally intercepted pointer encodings never reach that call, and the exact physical-delivery matrix remains a runtime oracle. SE-C46 has no explicit empty-list diagnostic. A selected inferior omitted from the snapshot is inserted using its live edges.

Create incorporates the selected profile's D02 creation registry and constructor transaction. Its window-type and subordinate choice menus are ordinary any-button menus: all seven nonzero masks select a row. C46's already-allocated window enters a nonabortable two-corner initializer: every nonzero mask fixes each corner. At either C303 corner, any Middle-containing mask aborts, Right alone or Left+Right requests smart placement, and Left alone places normally. Each C303 smart corner uses the exact depth-first postorder, per-sheet low/high overwrite, strict 32-pixel delta, and inclusive final clamp specified in the C303 Reshape tree; this common helper contract applies independently to both Create corners. Genera uses the same button precedence but its separate newer geometry helper: Middle-containing aborts, a Right-containing mask without Middle requests smart placement, and the remaining Left mask places normally. Nonpositive rectangles become the superior's full inside rectangle; minimum-size or outside failures beep and restart acquisition. Construction occurs only after successful geometry in C303/G85. C46's older path allocates before its initializer, as specified in D02. Create (expand) uses a point picker on which every Left-containing mask accepts the point and every mask without Left (Middle, Right, or Middle+Right) aborts. It expands a rectangle about the chosen point while ignoring the exposed inferior already containing it, then constructs and mouse-selects. Cancel and failure return the later abort sentinel; C46 Create returns an unchanged normal model.

Session entry

Preconditions:

• D02 has selected a top sheet;
• the top sheet supplies the required mouse/screen-management substrate; and
• the temporary Screen Editor menu resource can be acquired.

Required order:

1. Save the previously selected window and pointer sheet as entry values.
2. Acquire the temporary Screen Editor menu resource before moving the pointer context. An acquisition failure therefore occurs before pointer-restoration cleanup is established, while the pointer is still unmoved.
3. SE-C46 captures its initial direct-inferior snapshot after menu acquisition and before entering the pointer-restoration unwind scope. SE-C303 and SE-G85 defer their first snapshot until after the first non-NIL operation choice has deactivated the menu.
4. Establish the unwind cleanup, then move the pointer context to the edited top sheet. SE-C46 and SE-C303 dynamically bind the CADR WHO-LINE-PROCESS to the current process for the whole menu loop. SE-G85 instead saves and replaces the edited console who-line's forced-process slot within the protected setup.
5. Expose the operation menu near the pointer and repeat the profile-specific choose, resnapshot, command, and apply transactions until Exit or a nonlocal transfer. If choice returns NIL because the menu was externally deexposed or dismissed, re-expose it without invoking a command, snapshotting, rotating history, or applying state.
6. In unwind cleanup, restore the saved pointer sheet; unwind the CADR dynamic who-line-process binding or, for Genera, restore the exact old console forced-process value.
7. On normal exit only, reselect the old window if it and every ancestor remain exposed; otherwise ask the edited top sheet to autoexpose inferiors.

An error or external abort still runs unwind cleanup but bypasses the normal post-unwind reselection branch. A dead saved pointer or selection has no explicit historical liveness guard and remains TODO-RUNTIME-SE-CLEANUP-DEAD-OBJECT.

SE-C46 loop

current := snapshot(top-sheet)       // once, at entry
previous := current
loop:
  choice := choose-operation()
  if choice == NIL: re-expose menu; continue
  deactivate-menu()
  result := invoke(choice, top-sheet, current)
  if choice is Exit: leave
  apply(result, old=current)
  previous := current                // unchanged results still advance Undo
  current := snapshot(top-sheet)     // after application

The stored model is not every command's sole input. Target hit-testing, Bury, Expose, Move Multiple, Move Single, and Expand All use its stale rows/edges. Move Window initializes from the live sheet position and dimensions and writes live dimensions into its result. Reshape initializes from live offsets/dimensions and calls the live verifier. Expand Window rereads the live superior, exposed siblings, and target geometry. Expose-menu, Create, and Kill also enumerate or mutate live objects. An external geometry change while the menu is exposed can therefore be ignored, read, or mixed with stale selection/order according to the chosen command; a clone MUST not substitute either one blanket stale snapshot or one blanket fresh snapshot. There is no abort sentinel. Cancellation normally returns current, so it consumes the preceding Undo slot.

SE-C303 and SE-G85 loop

The historical loop rotates history based on the preceding result and resamples immediately before the next command. The equivalent observable contract is:

previous := undefined
command-start := undefined
prior-result := abort-sentinel
first-command := true
loop:
  choice := choose-operation()
  if choice == NIL: re-expose menu; continue
  deactivate-menu()
  under delayed-screen-management with unwind flush:
    if not first-command and prior-result != abort-sentinel:
      previous := command-start
    command-start := snapshot(top-sheet)
    if first-command:
      previous := command-start
      first-command := false
    result := invoke(choice, top-sheet, command-start)
    if result != abort-sentinel:
      apply(result, old=command-start)
  prior-result := result

Delayed screen management queues and later flushes management work. It is not a lock and does not make the command or apply pass atomic. Other processes can mutate live sheets; callbacks and conditions can escape after partial effects.

Literal abort preserves the older Undo snapshot. A normal return advances history even if it is NIL, has identical rows, or encodes original edges. In particular:

• initial target cancellation for ordinary later commands normally returns abort;
• C303/G85 Reshape Middle returns original edges and consumes Undo;
• C303/G85 Move Multiple and Move Single cancellation return an unchanged model and consume Undo;
• C303 Attributes Abort is caught and returns an unchanged model, consuming Undo;
• G85 Attributes completion with no changes returns an unchanged model and consumes Undo; the form's Abort propagation remains an oracle; and
• a C303/G85 Right-start of Move Multiple with a truly NIL movement list is a successful no-op and consumes Undo. In C303, a non-NIL retained movement record whose four flags are false instead enters movement and can expose the 65,535 maximum-coordinate sentinel path.

Snapshot and apply contract

Snapshot traverses direct inferiors in their live order. It includes each exposed inferior and each deexposed inferior that reports deexposed visibility; it excludes invisible deexposed inferiors and every nested descendant. The exposure field is the live exposed predicate result.

Application iterates desired records in order:

1. Find the matching command-start record by live object identity.
2. If its edges differ, C46 sends the new edges directly. C303/G85 first asks the window to verify the proposed rectangle.
3. On later-profile verification success, set the edges. On rejection, beep, display the returned diagnostic, skip only this record's geometry, and continue.
4. If desired exposure is true and old exposure was false, expose the window. If it is bury-request, bury it immediately.
5. After all records, make a second pass and bury every desired false record that is still exposed.

Objects absent from the desired result are not explicitly killed, deexposed, or buried by this pass. A rejected geometry does not suppress its exposure action or later records. An error retains the successfully applied prefix. A portable all-or-nothing transaction is allowed only as a labeled INF safety profile and is not strict compatibility.

Undo contract

Undo returns the single previous shallow snapshot and uses the ordinary apply pass. The command-start state of Undo then becomes the next previous state, so a second Undo often toggles back. It is not guaranteed to do so because:

• deexposed relative ordering is not exactly represented;
• burying a previously hidden window cannot restore its precise hidden position;
• records retain live object references but not arbitrary object state;
• attributes are outside the model;
• a killed object cannot be resurrected; and
• an object created since the old snapshot is absent, while apply does not explicitly bury or destroy absent objects.

Source comments/manual material expect an undone Create to leave the new object buried, while the apply algorithm has no direct absent-record action and the Genera menu documentation says Create and Kill cannot be undone. Strict conformance MUST retain TODO-RUNTIME-SE-CREATE-KILL-UNDO rather than selecting a convenient result.

Bury, Expose, Expose by menu, Create, and Kill

• Bury copies the chosen record, moves it to the model end, and writes the special bury request. Application performs the live bury during its first pass.
• Expose copies the chosen record, moves it to the model front, and marks it true.
• Expose (menu) enumerates live deexposed direct inferiors. C46 modifies only a candidate already found in its snapshot; later profiles can construct a fresh row for an omitted invisible inferior. Names prefer selection name and then sheet name where those protocols exist.
• Create and Create (expand) delegate to D02 as described in the binding section. Screen Editor does not roll back a partially constructed object.
• Kill is immediate and unconfirmed in C46. C303/G85 ask for confirmation before synchronous destruction. C303's source uses a one-item positive confirmation; Genera normally uses a Yes/No menu but can select an older compatibility UI. Cancellation does not kill. Once killing begins, deexposure, inferior destruction, and dead-state effects are not undone by Screen Editor.

Move Window

The chosen window's width and height remain constant. Tracking proposes a new upper-left coordinate and displays an outline; live mutation occurs only through the profile's eventual validation/application path. C46 clamps only maximum x/y in the inspected helper, while C303/G85 use a stay-inside positioning box. The tracker first sends a position-verification request. Rejection beeps and retries. Acceptance merely returns a model proposal: C46 central apply then sends edges directly, whereas C303/G85 central apply separately verifies the derived edge rectangle before setting it. A stateful verifier can therefore accept position but reject or signal on the later edge operation; in C303/G85 that is a normal command result with skipped geometry and advanced history. The exact button and coordinate-sampling trees above are normative.

Reshape

C46 and C303 acquire two corners. A nonpositive rectangle becomes the entire inside rectangle. C46 has no pointer cancel in the corner helper. C303 Middle cancellation beeps and yields the old edges as success. Its smart placement considers exposed edges with directional distance strictly greater than zero and less than 32 pixels; it walks exposed inferiors recursively in list order and postorder, including nested descendants and the edited sheet itself. Within each visited sheet it tests low then high x edges and low then high y edges; successive eligible edges overwrite earlier axis values, then x and y are clamped inclusively to inside-left..inside-right and inside-top..inside-bottom; the high coordinate itself is allowed. It therefore MUST NOT be described as a global nearest-edge search. In both older profiles the lower-right coordinate sampled shortly after button-down, while release is not awaited, is inside the requested rectangle: the helper adds one to its x and y coordinates to produce half-open right and bottom edges. Omitting this conversion makes a clone one pixel too small in each dimension.

The older reshape helper performs its own geometry verification before it returns a proposal. Central application is a second stage: C46 directly sends the returned edges and can signal, while C303 asks the verifier again and can reject the same edges, skip geometry, continue exposure/later rows, and still advance history. A stateful verifier therefore makes helper-accept/central-reject observable.

Genera's newer one-corner helper uses the configured active corner, live Shift state, superior bounding box, and optional smart target. Screen Editor requests calculation without immediate live movement; central application validates later. The documented NIL default-corner mode appears able to reach an invalid case because Screen Editor does not supply a click-derived corner; this is TODO-RUNTIME-SE-G85-NIL-RESHAPE-CORNER.

Edge movement legality and source defects

The movement precheck requires every changed coordinate to be at least the inside minimum and strictly less than the inside maximum. Equality with right/bottom maximum is rejected. It does not independently enforce left less than right or top less than bottom. C303/G85 central verification can reject an inverted rectangle after other records have changed; C46 forwards each proposal directly, so the target's edge-setting behavior decides whether an inverted rectangle is accepted or signals.

Normalized classification ties choose the horizontal boundary because the historical comparison selects the vertical edge only on a strict lesser x-distance. Exact midpoints therefore resolve to Right or Bottom after nearest-side selection. A zero- or negative-extent record cannot satisfy the containing-record guard and is therefore classified as outside; the later division is unreachable through the selected application interface absent concurrent or malicious mutation between the guard and arithmetic. C46 Multiple and C46/C303 Single pass the :OUT classification into an invalid feature path and can signal; Genera ignores outside clicks in the audited paths. Clearing a final move feature can leave an empty movement record; starting thereafter can expose a maximum-coordinate sentinel in relative rectangle construction. These are strict-profile defects, not opportunities to invent silent repair.

Expand Window

Expansion is calculated without live mutation:

1. Start with the superior's inside bounds.
2. Scan exposed siblings for nearest left and right blockers that overlap the original vertical interval.
3. Adopt the horizontal expansion.
4. Scan exposed siblings for top and bottom blockers using the newly widened horizontal interval.
5. Return the resulting edges for central application.

Touching half-open edges do not overlap. Horizontal-before-vertical order is normative and can differ from a globally maximal empty rectangle. The Genera helper can return NIL for a window without a superior; the exact Screen Editor downstream failure is TODO-RUNTIME-SE-G85-EXPAND-ROOT.

Expand All

Only exposed records enter the solver. Deexposed records are appended from the first false-exposure entry onward, relying on an exposed-prefix ordering assumption.

For each dimension, in horizontal-then-vertical order:

1. Build nearest overlapping blocker sets on each side, retaining ties. Orthogonal boundary equality counts as overlap: only strict separation with > or < excludes a candidate.
2. Propose integer midpoint sharing for each gap. A low-side midpoint is low + truncate(gap / 2); a high-side midpoint is high - truncate(gap / 2). Odd gaps therefore do not use one symmetric formula.
3. Ask affected windows whether candidate edges verify.
4. If both sides can move, share at the midpoint.
5. If the current target cannot move, try growing eligible winners; if a winner cannot move, the target may take the whole gap according to the release branch.
6. Propagate accepted winner bounds into cached scratch records so later decisions observe earlier ones.

The result depends on snapshot order and verifier responses; it is not an optimizer and does not promise a unique or globally maximum tiling. C46 and C303 differ when there is no winner. C303 still verifies the midpoint and performs no scratch change when it rejects. C46 skips midpoint verification in that branch and tries the full boundary; even if that rejects, it writes the unverified midpoint into its scratch proposal, which the later direct apply sends to the target. C303 central apply verifies again and can still produce a partial result.

SE-C303 Attributes

The fixed form first probes optional capabilities in the exact order border, label, then name. It then sends ten unconditional base getters, in order, for current font, More, reverse-video, vertical spacing, deexposed input action, deexposed output action, character ALU, erase ALU, priority, and save bits. Next it sends the applicable conditional getter for name or label, then border specification, then border-margin width; normalizes the staged values; and, while constructing the form, obtains the font map. It presents the following exact displayed rows and value mappings:

Only the name/label and border getter groups are capability-gated. The Other row is not fetched: it starts as local NIL and receives the original object during normalization when an old output action is not one of the standard choices. In that case the displayed action becomes Other, so leaving both untouched sends nothing. Editing the Other row has setter effect only while output action is Other; changing away from Other clears it and refreshes the form. Reverse-video editing also stages coherent character and erase ALUs.

Normalization preserves the original getter object in each OLD-* slot. If the border specification is a cons whose CAR is NIL or :ZERO, the staged width is 0; otherwise it is (FOURTH (FIRST old-spec)) - (SECOND (FIRST old-spec)). Because the old slot remains the cons, an untouched cons border normally compares NEQ with that number and deterministically sends :SET-BORDERS. If a Name or Label getter returns a cons, the displayed/staged string is its SIXTH. An untouched Name cons therefore compares NEQ and sends :SET-NAME with the extracted value. An untouched Label cons also compares NEQ; commit mutates the old cons's SIXTH and sends that same cons via :SET-LABEL.

Done detects change with object identity (NEQ), not value equality, then sends only changed setters sequentially in the listed order; failure leaves the setter prefix. Attributes are outside Screen Editor Undo.

SE-G85 Attributes

Genera asks the target for attribute queries under Dynamic Windows Accepting Values. Applicable methods combine most-specific-last and append message/value pairs. Base families cover more processing, reverse video, spacing, deexposed input/output actions, draw/erase ALUs, priority, and save bits; border, label, name, graphics, and other mixins extend the list. This is an extensible target protocol, not a fixed catalog.

After Done, Screen Editor sends each message/value pair in returned order. An odd list supplies NIL for the final missing value. An error in a later setter retains all earlier sends. No attribute send is represented in the geometry snapshot and Undo cannot reverse it.

Program framework and persistence

The selected program is internally layout-designer and visibly named Frame-Up. It registers Select Q and the System Menu/activity name Frame-Up, supplies a command definer, and disables local keyboard accelerators. Its local command table inherits from no other command table. Its top level binds the stored package only when non-NIL, resolves it before entering the default command top level, and can therefore fail before the command loop on a stale package name.

Its real framework panes are:

Instance initialization creates one private :DISPLAY leaf. Done deselects rather than killing or resetting the program, so direct reselection retains model and program settings. Reset Configuration resets only the pane tree.

Pane construction and naming

Creating a normal leaf:

1. Look up the exact registered type identity.
2. Merge its default initialization property list with supplied options.
3. Remove options not present in that type's editable allowed list.
4. Generate a name from a root and a decimal suffix.
5. Initialize an empty inferior list, superior link, and vertical stacking direction.

The helper always appends -N, even when the caller supplies a name root. Unique naming traverses the current top tree in preorder, parses decimal suffixes sharing the root, and returns one greater than the maximum. Set Pane Name does not enforce uniqueness. Detached standard-layout construction can therefore generate duplicate names because the incomplete siblings are not yet reachable from top-pane.

The typed layout-pane parser suggests leaves only, permits no arbitrary input, and prints the pane name. That parser restriction is not an invariant on programmatic calls or presentation translators: Middle can supply an internal node, and Delete can receive one through a nonstandard call.

Top box and coordinates

The renderer computes a top model rectangle whose width is two thirds of the display pane's inside width. Its height preserves the current screen aspect ratio, and the rectangle is centered using display viewport coordinates. Each node receives a half-open box. Rendering decrements right and bottom for the visible hollow border.

Every node is emitted as a nested layout-pane presentation and hollow rectangle. Leaves center the text NAME :TYPE. Pane options are not drawn. Thus internal border-only regions can expose an internal presentation while leaf interiors usually select the innermost leaf; exact Dynamic Windows nested-presentation tie breaking is incorporated from D28 and remains a runtime dump obligation for this app.

Partition algorithm

For each internal node:

1. Use its stacking direction to select horizontal or vertical extent.
2. Compute a simulated fixed extent only for children whose type has a registered simulation size function.
3. Subtract fixed extents from the parent's available extent.
4. If there is at least one unconstrained child, divide the remainder equally among those children using integer floor.
5. Give the reverse-accumulated/source-last unconstrained child the ceiling/remainder so the final edge reaches the parent's terminal edge.
6. Assign child boxes in source order and recurse.

The fixed scale is 20 pixels per simulated character unit. Command-menu vertical size uses explicit rows, then list length, then a two-row default; horizontal size estimates ten average characters per column. Interactor and Display use vertical height-in-lines; Title defaults to one line. Listener, Accept Values, and Tree Browser have no special simulation size function in this source.

There is no general overconstraint rejection or clipping rule. When every child is fixed, no division occurs: children are laid out in order using their computed sizes, even when their final edges escape the parent. When fixed children leave a negative remainder and unconstrained children exist, their computed shares can likewise be negative; no clipping or rejection repairs the result. The renderer is a simulation, not the real constraint-frame layout engine and not a WYSIWYG compatibility claim.

Split Pane

Inputs are a leaf pane and Horizontally or Vertically. Human Horizontally means a horizontal divider and a vertical stack/private column; Vertically means a vertical divider and a horizontal row.

Required order:

1. Reject a pane that already has inferiors.
2. Allocate a new :DISPLAY sibling with a NIL superior.
3. Set the selected pane's stacking-direction field to the inverse of the requested parent direction.
4. If the current parent already has the requested private orientation, set the new sibling's superior backlink to that parent before checking membership, then find the selected child and insert the sibling immediately after it.
5. Otherwise allocate an empty hidden parent, set its superior to the selected pane's old parent, set the selected and sibling backlinks to that new parent, set the new parent's inferiors to [selected, new], then substitute the new parent into the old parent or make it the root.

The stored stacking-direction is used when that node lays out inferiors and during promotion; the Split command never reads it to choose a later split. The dossier's former suggestion of automatic next-split alternation is not part of this contract.

If a corrupt matching parent does not contain the selected child, failure occurs after the new pane was allocated, the selected stacking-direction field changed, and the sibling backlink was set to that parent. In the nonmatching-orientation branch, substitution does not signal when the old parent omits selected: its inferior list remains unchanged while the already-linked new subtree is detached and the new parent still points back to that old parent. There is no rollback.

Swap Panes

Swap requires two distinct siblings under the same non-NIL parent. The same object, the top pane, or different parents causes a beep and explanatory message with no intended mutation. Valid swap replaces through a temporary marker so object names, types, options, and descendants move with their identities. The historical function does not first prove that each object occurs exactly once in the parent list; corrupt or duplicate state remains an oracle/safety-profile boundary.

Delete Pane

Deleting the only/root pane prints a refusal without beeping. Otherwise:

1. Destructively remove the pane from its parent's inferior list.
2. If zero or two-or-more siblings remain, stop.
3. If exactly one remains, promote it through the hidden parent.
4. With a grandparent, substitute the survivor and set its superior backlink; set its stacking direction to the inverse of the grandparent's stored direction.
5. Without a grandparent, make the survivor the new top pane.

The deleted pane's old superior link and the collapsed parent's backlinks are not cleared. For a stale/nonmember pane, destructive deletion leaves the parent's inferior members unchanged. The code nevertheless continues by list length: an unchanged one-member list promotes its sole member, while zero or two-or-more stops. If the target really was the sole member, deletion leaves zero and therefore stops without collapsing. These malformed-state outcomes are strict source-profile behavior; proactive membership rejection is allowed only in a labeled INF safety variant.

Set Pane Options and Set Pane Name

Set Pane Options edits a copied options list inside resynchronizing Accepting Values. It commits the pane's name, type, and options only after successful form exit.

• Changing type replaces options with that type's defaults; switching back during the same form restores the original options.
• Redisplay mode is None, String, or Function. Each removes incompatible keys; Function additionally exposes incremental redisplay. Title may temporarily gain incremental state in the form, but generation filters it out because the type does not allow that key.
• Command-menu geometry is Default, Rows, or Columns. Rows wins if a corrupt input contains both. Numeric entry defaults to 1; content mode edits existing strings and exposes one append slot.
• An allowed option without specialized metadata falls back to expression input. Flavor is stored raw; most nonconstant expressions are quoted.
• Rename has no uniqueness check.
• An internal row/column reaches a missing registry entry and can fail before commit.

Set Pane Name directly assigns the supplied symbol and redisplays. The menu-only translator returns an inactive partial command so name acquisition precedes that assignment.

Set Program Options

The form edits only:

• generated program name;
• optional generated Select key;
• whether to generate a command-defining macro;
• generated command-table keyboard-accelerator policy; and
• inherited generated command tables.

It does not expose the stored package, configuration name, or program state variables. The attempted state-variable editor is commented out as unsatisfactory.

Select Configuration and Reset Configuration

The standard-layout registry replaces matching names case-insensitively in place and pushes new names to the front. The two built-ins are:

The first name and its actual source child order disagree; a conformer MUST preserve the exact order rather than infer it from the label.

Both commands beep before destructive confirmation. No retains the tree. Yes sets top-pane to NIL before expansion or replacement; allocation, naming, or registry failure thereafter leaves NIL or a partial detached structure. Reset builds one Display leaf and does not reset program options. Select expands the selected dynamic registry description and is exposed to the duplicate-name defect described above.

Generated form

Generation first scans all nodes. If any node is :ACCEPT-VALUES, it adds the string accept-values-pane to the stored inherited-command-table list. This is a sticky model mutation: deleting all Accept Values panes later does not remove it.

It then returns one DEFINE-PROGRAM-FRAMEWORK form containing:

1. the program symbol;
2. optional generated Select key;
3. command-definer policy;
4. inherited table names, converting table objects to names while retaining strings;
5. generated command-table accelerator policy;
6. state variables;
7. leaf pane descriptions only, filtered against current allowed options; and
8. exactly one quoted configuration.

It omits Frame-Up's own pretty name, System Menu registration, top level, and stored package. Multiple generated configurations are unsupported. Private row/column nodes appear only in recursive layout. The top internal node is named with the configuration name. An unsplit leaf uses the release-7 fallback of a one-column layout and one even-sized member.

Size selection precedence is explicit height-in-lines, then size-from-output as an ask-window constraint, then even. Within each generated size clause, all explicit sizes are emitted before the separator and all even panes after it, while the layout child order itself remains unchanged.

Preview

Preview is not a sandbox:

1. Generate the form, including any sticky inheritance mutation.
2. Evaluate it with definition and framework redefinition enabled, changing the real named program in the current Lisp world.
3. Acquire or reuse a temporary processless program frame beneath Frame-Up's superior.
4. Enter protected window-call cleanup that deactivates the temporary frame on exit.
5. Bind terminal, query, and standard streams, clear query input, and print each parsed pane name into its pane.
6. Read one arbitrary character. The prompt requests Space, but Space is not enforced.

Preview does not run the generated program's top level. Generation, evaluation, construction, redisplay, or stream errors can retain the real definition and sticky model mutation. Resource cleanup deactivates the temporary frame but supplies no semantic rollback.

Done

Done commits in this order:

1. Generate the form.
2. Replace the matching program-symbol result in place or push a new result first.
3. Increment the global result tick.
4. Deselect Frame-Up.

It performs no file or world save. A generation/storage failure prevents tick and deselection, although sticky Accept Values inheritance may already have happened. A deselection failure leaves result and tick committed, so editor waiters can wake. There is no lock or rollback.

Shared insertion behavior

Insertion prints one form through a presentation-recording interval stream under the current package/readtable, downcases for a lowercase buffer, pushes the old point, and leaves point after the form. It does not explicitly append a newline.

Each calling command selects Frame-Up before invoking the wait helper. After that selection returns, the helper displays a Control-Abort continuation message, snapshots the global result tick, waits for a greater tick, and inserts the first global result. The helper itself never selects Frame-Up. This creates three normative source-visible races:

• a fast Done before the tick snapshot can be missed, causing a wait for another Done;
• multiple waiters share one tick and can all wake together; and
• there is no caller/program correlation, so the first result can belong to another program.

Create Program Definition

This command requires an existing Frame-Up window, reads a program name through general typein, creates a new Display pane before replacing top-pane, resets only program name, package, and root pane, asynchronously clears the frame, resets its process, selects it, waits, and inserts. Configuration name, command settings, state variables, and other stored options persist. Because naming scans the old tree, a reused designer can start the new model at a suffix greater than 1.

Insert Program Definition

This command errors when the result list is empty. Otherwise it chooses a retained program, defaulting to the first, finds it by symbol identity, and inserts its stored form.

Edit Program Definition

The command reads the enclosing definition interval and requires a DEFINE-PROGRAM-FRAMEWORK head, but compares against only the first retained result and the same program identity. It does not parse the buffer form back into a model. It warns that source-added options will be lost, edits will revert, and deletions will reappear; refusal aborts the Zmacs command. On acceptance it selects retained designer state, waits globally, deletes the old interval, then inserts the newest first result. Insertion failure can therefore leave the original code deleted.

Edit Program Redisplay Function

This command accepts any symbol that names a program; it does not choose from or require a retained Frame-Up result. It calls the program-instantiation operation, chooses among panes that have an explicit redisplay function, and invokes the editor on that function. Absence of such a pane/function is an error. Instantiation can itself have side effects or fail.

Replacement of a result preserves its old list position while new names are pushed first. Therefore “latest per program name” MUST NOT be conflated with “first result” in the wait/edit paths.

Failure and recovery rules

• Unknown/stale live windows are not proactively validated by the historical Screen Editor. An INF safety profile MAY reject them before mutation but MUST disclose the changed race behavior.
• C303/G85 invalid geometry produces a beep and diagnostic and continues where the relevant helper or central apply says to continue. It is not a transaction abort.
• Menu dismissal, literal Abort, successful unchanged result, and escaping condition are distinct outcomes and MUST NOT be normalized.
• Frame-Up commands mutate ordinary in-world model objects without a transaction log. No command supplies Undo.
• Accepting Values form exit can be transactional for its copied local option list while subsequent target setters or Frame-Up tree mutation remain nontransactional.
• Every abnormal exit MUST perform only the cleanup established for its dynamic resource scope; it MUST NOT invent semantic rollback.

SE-C303 operation menu

Runtime observation: the complete System 303 Screen Editor operation menu after Edit Screen, captured 2026-07-18 without a geometry command. MIT and other underlying interests remain with their rightsholders; reproduced for criticism, scholarship, and historical documentation under 17 U.S.C. section 107. No affiliation or endorsement is implied.

The strict visible profile MUST be capable of displaying one temporary 15-item menu in the captured order over the selected screen, with the highlighted item and its bottom pointer documentation. The image does not define a general CADR font or pixel-perfect desktop profile.

SE-G85 operation menu

Runtime observation: the complete Genera 8.5 Screen Editor menu after Edit Screen, captured 2026-07-18 before exiting without mutation. Symbolics and other underlying interests remain with their rightsholders; reproduced for criticism, scholarship, and historical documentation under 17 U.S.C. section 107. No affiliation or endorsement is implied.

The strict visible profile MUST provide the Screen Edit Operation label, exact 15-item order, visible grouping and emphasis, current-item feedback, and bottom operation documentation. Surrounding Listener/debugger text is incidental session context and is not a Screen Editor requirement.

FU-G85 two-pane model

Runtime observation: Genera 8.5 Frame-Up after a researcher-requested horizontal split of the default pane, captured 2026-07-18. Symbolics and other underlying interests remain with their rightsholders; reproduced for criticism, scholarship, and historical documentation under 17 U.S.C. section 107. No affiliation or endorsement is implied.

The strict visible profile MUST provide a title region, graphical layout region, interactor, and ten-cell two-column menu. After the typed command shown, it MUST render two labeled :DISPLAY leaves, PANE-1 above PANE-2, separated by a horizontal divider. The image constrains this unconstrained two-leaf case only; it does not make the simulator a pixel-exact constraint engine.

The action prefix also records a Left click in apparent pane whitespace with no visible split and a Right click that opened a generic Operation menu. Because the presentation hit region and menu contents were not captured completely, those are oracle obligations rather than contradictory requirements.

Screen Editor core and bindings

Screen Editor commands and geometry

Frame-Up model, commands, bindings, and generation

Runtime closure probes