Software areas and programs of the MIT CADR and Symbolics Genera
The two systems are complete programming environments rather than operating systems with a small, sharply separated application layer. A listener, editor, mail reader, debugger, compiler, file browser, window manager, server, and hardware diagnostic can all coexist in one Lisp world and call one another directly. For that reason, a useful "application list" must include more than the icons or menu entries that would define an application list on a later workstation.
This page is the cross-system map. The release-bounded detailed catalogs are:
- MIT CADR and LM-3 software areas and applications, covering the public System 46 tape snapshot and the maintained System 303 source and load band used by the museum;
- Symbolics Genera software areas and applications, covering the inspected Genera 8.5/Open Genera 2.0 world and its installed source and system declarations.
The application dossier coverage matrix turns these exhaustive release catalogs into a finite 60-topic research queue and links each completed editor-depth study. Its companion CLIM-use audit identifies the actual interface substrate and any CLIM relationship for every one of those sixty topics, including explicit negative findings where the software instead uses TV, EINE/ZWEI, Dynamic Windows, streams, or a noninteractive service boundary.
The CADR System 46 evidence is public. The Genera archive, world, source, compiled systems, and extracted documentation are licensed local inputs; only evidence-only names, counts, hashes, and original analysis from them are tracked here.
Those pages carry the exhaustive name lists, evidence status, and release-specific qualifications. This comparison deliberately does not turn a source directory, Lisp package, library, test case, or individual command into an "application" merely because it has a name.
The visible center of each environment
These are the principal interactive roles a new user encounters. A dash means that the inspected evidence did not establish a close counterpart, not that no one could write one.
This is a role map, not a lineage claim. Similar labels can hide substantial implementation changes. The detailed pages identify when Genera retained an MIT concept, replaced it, or added a new subsystem.
Software-domain map
What "complete" means here
The catalog is complete for the identified preserved evidence, not for every program ever written for either machine family. It records the following evidence layers separately:
| Evidence layer | What it establishes |
|---|---|
| Distribution or artifact present | The named material occurs on the inspected release media or load-band support tree. |
| Source present | Source contains a distinct user program, server, tool, diagnostic, or demonstration with an identifiable entry point. |
| Declared or known | The system registry has a declaration for it. This does not mean it is loaded. |
| Loaded | The exact inspected world reports the system resident. This does not necessarily make it interactive. |
| Registered activity | The window/activity machinery knows how to select or create it. |
| Select key | The exact world or source binds it in the system-key/SELECT table. |
| System or Create menu | It appears in one deliberately curated menu subset. |
| Command or function entry | It is an interactive tool entered from the Listener, Command Processor, editor, or a Lisp call rather than a top-level menu. |
| Embedded mode or subapplication | It is a separately usable facility inside a larger program, such as Dired within the editor. |
| Runtime observed | The museum directly exercised or displayed it with the identified load band/world and emulator/VLM. |
| Documented product | A contemporary manual or installed documentation set describes it, although the inspected code or runtime state might be optional or absent. |
The detailed lists do not collapse these layers into "available." In particular, source presence does not prove that a program is loaded, configured, working, or supported in the inspected world. An installed Genera .system record does not prove that its product is resident. A menu entry proves an entry point, not every feature behind it. Conversely, menu enumeration undercounts by design: both systems provide interactive programs that do not occupy their short Programs columns.
Aliases are retained but counted as one user-facing concept when they identify the same implementation: for example, Edit, Editor, and Zmacs, or Mail and Zmail. Distinct implementation generations such as EINE and Zmacs remain distinct.
The census excludes individual Lisp functions, Command Processor commands, editor commands, packages, flavors/classes, low-level source modules, data files, fonts, tests, and incidental examples embedded in documentation. Those have their own inventories where useful. It includes libraries and infrastructure only when they define a historically meaningful software area needed to understand what the environment could do.
Runtime cross-checks
The museum's isolated harnesses provide two narrow runtime anchors:
- A fresh System 303 session's System-Help table displayed five bindings: Top-L for
LISP(Edit), E for Editor, I for Inspector, L for Lisp, and P for Peek. Its Programs menu separately displayed Lisp, Edit, Inspect, Trace, Peek, Mail, and Emergency Break. The difference demonstrates why neither registry is sufficient alone. The earlier menu capture and hashes are recorded in the CADR harness report. - A direct evaluation of the Select-key table in a fresh copy of the inspected Genera 8.5 world returned twelve bindings:
=Select Key Selector, C Converse, D Document Examiner, E Editor, I Inspector, L Lisp, M Zmail, N Notifications, P Peek, Q Frame-Up, T Terminal, and X Flavor Examiner. The F binding for File System Maintenance printed in the Genera User's Guide was absent from this exact world. Its System Menu separately displayed Distribute Systems, Document Examiner, Editor, Emergency Break, Frame-Up, Hardcopy, Inspect, Lisp, Namespace Editor, Trace, and Zmail. - The same world's live activity registry contained nineteen names: Converse, Distribute Systems, Document Examiner, Editor, File Server, Flavor Examiner, Frame-Up, Inspector, Keyboard Control, Lisp, Mail, Namespace Editor, Notifications, Peek, Restore Distribution, Select Key Selector, Terminal, Zmacs, and Zmail. Its Create registry contained Terminal, Lisp, Peek, Inspect, Edit, Frame-Up, Distribute Systems, Document Examiner, Namespace Editor, and the generic
Anychoice. These tables again disagree in useful ways with both the short menu and the documentation-derived union. - A second fresh, read-only runtime query found 98 System Construction Tool records with a non-null loaded version in this world: 26 had numbered versions and 72 used
:NEWEST. Their complete exact-name roster is retained in the Genera detailed catalog. - The same Genera world's top-level
Help Commandsresponse displayed command areas ranging from activities, editing, files, and Lisp through networking, printing, site administration, tape administration, and world building. This is a command taxonomy, not an application registry.
The exact-table query captures remain local. Separate later runtime studies selected one sparse menu state from each system for capture-specific publication review and the corresponding application dossiers. Their portable identities and shutdown evidence are recorded in the curated screenshot catalogs. The earlier Genera System Menu and command-category capture is described in the Genera harness report.
Neither menu is the whole software catalog. Both systems also contain facilities entered by commands, Select keys, functions, subsystem menus, server processes, or explicit system loading.
Sources and verification
- Symbolics, Genera User's Guide, especially "Selecting and Creating Activities" and "Standard Activities".
- Symbolics, Genera Handbook, especially the
SELECT HELPdescription andSelect Activitycommand. - MIT CADR System 46 public source snapshot, including its release README and license.
- LM-3 System 303 system declaration and System Menu implementation.
Last verified: 2026-07-18.