Concordia, structured documentation, and book design

One corpus, two principal reading forms

Manual and source: a record is the independently retrievable unit. It has a unique topic/name and type, fields such as contents and keywords, an identity in the record registry, and links to other records. Authors can compose one physical book from records spread across several .sab files, while Document Examiner can retrieve an individual record without reconstructing that book's printed order.

This dual use changes the writing model:

The physical order of records in a .sab file does not define the book. Reordering or relinking records can change a document hierarchy without copying the underlying record text. Conversely, a record written for on-line lookup needs enough context to stand alone even when its printed parent and neighbors are absent.

The four configurations are one activity

Source: Concordia is one Dynamic Windows program with four configurations, not four unrelated processes. Each embedded program frame is created with no separate process. The persistent top title and selector pane switch the rest of the frame among these layouts:

The always-visible selector uses four application font glyphs. The editor is the initial configuration. Graphic Editor callbacks can return directly to it, and the Page Previewer Edit Record command switches back to it after queueing the edit. See Genera Graphic Editor and structured drawing for the illustration subsystem's own complete command and format analysis.

The public guide documents switching by the four icons and by a Super-Select sequence for Editor, Page Previewer, Graphic Editor, and Book Design Browser. The inspected Super-Select hook, however, recognizes only E, P, and G; it has no Book Design Browser entry. The source does include the Browser icon and the Change Configuration command. This is a source/manual discrepancy, not grounds to invent a fourth key.

Registry, record group, and multiple versions

Source: the registry groups records by topic, type, and unique identity. A record group can refer to published, installed, and one or more edited records rather than overwriting one undifferentiated value. Lookup mode selects among three policies:

Installing an edited record clones and canonicalizes it, updates index information, and marks both editor and installed copies. Published and edited link sets can therefore disagree temporarily; commands that show links distinguish which version contributes a relationship.

The editor tracks modification, installed, published, and checkpointed state. A coarse file lock protects writing a .sab buffer; it is not a per-field or per-link transaction. Set Buffer Disposition can lock a connected file or disconnect the buffer, while Break File Lock forcibly removes a lock and is explicitly a recovery operation, not normal collaboration.

Fields exposed by the structural editor

The active field construction is type-sensitive:

Contents, Oneliner, and Keywords are created by default. Source-Topic, Related, Notes, Arglist, and Source-Title are available but suppressed from automatic creation. Add Record Field exposes the optional fields appropriate to the current record type; Update Arglist Field derives an object record's argument list from the live definition when possible.

Structural Zmacs, not decorated flat text

The .sab file type selects Concordia major mode. The editor maps records, fields, formatter environments, formatter commands, links, pictures, and record markers to Zwei structure nodes. Text remains editable through Zmacs, but markup appears as diagram nodes with structural extent. Commands such as Beginning/End Environment, Remove Markup, Kill Environment, and Change Environment act on those objects rather than searching for visually similar punctuation.

This explains several otherwise surprising behaviors:

• deleting a record from a buffer and killing/undocumenting it are different operations;
• Remove Markup retains the environment's contents, while Kill Environment removes both wrapper and contents;
• links have editable views and targets rather than being mere text labels;
• moving records among buffers preserves registry identity;
• pictures can invoke an external editor and later regenerate their encoded display;
• Parse and Replace Region converts flat at-sign formatter syntax into structure, while its inverse operation is a separate unparse action.

Link views and document structure

The active source list contains four link views:

A Topic entry survives only behind an ignored reader conditional and is not part of the active list. Graph Links From Record is narrower than its name might imply: the source says it graphs structural links and does not display every crossreference or other view. Find Orphan Records also uses a pragmatic preservation definition: it finds records with no incoming links or with no contents, not a proof that a record is semantically unused.

Editor Commands and Collected Record Names panes

Source and manual: the right-side Editor Commands pane is a direct-manipulation index into the structural editor's command table. Clicking a category heading with the selection gesture expands or contracts it; the menu gesture opens that category's commands in a pop-up. Operating on the all-categories heading provides these exact setup operations:

The customization is live state unless the generated setup form is saved and later evaluated. The separately named Insert Concordia Menu Choices command instead opens a boolean form and inserts a setq form into the current buffer; it is not in the normal Writer Tools command table inventoried below.

The Collected Record Names pane stores convenient link targets. Creating records and explicit collection commands add names; clicking a name can supply it to a link operation, and a presentation command removes a collected name. Dragging the pane's title with the selection gesture resizes the pane. The implementation treats other gestures on that title as abort/no-operation paths rather than text editing.

Complete visible category menu

This is the complete normal category definition in comtab.lisp.~52~. A name in this table means it is exposed through that mouse pane; commands that exist only by name or keystroke appear in later inventories.

A Debugging category is created only when the private *debugging-sage* switch is enabled. It is excluded from the public user surface and from the counts here.

Complete direct key and mouse bindings

The mode inherits ordinary Zmacs motion, editing, search, window, macro, and file commands. The following table is complete for literal bindings added or changed by the inspected Concordia mode table:

Concordia deliberately undefines Control-;, Meta-;, Meta-N, Meta-P, Meta-Line, and Control-Meta-; in this mode because the inherited Lisp comment commands would damage the structural representation. The comment in the source recommends the structural Super-M route for comments instead.

Loading Concordia also changes tables outside its mode:

• the global Zmacs table receives Super-. for Edit Record and the named Concordia Mode command;
• the global Zmacs named-command set receives Align Table Tabs, which calculates common tab stops for marked table lines;
• the standard Zwei table receives Super-Space Again and Super-Backspace Reverse Again, replaying the last minibuffer command without reconfirming its arguments; Reverse Again negates its numeric argument.

Those are source-visible global side effects of loading Concordia, not intrinsic bindings in an unloaded Genera world. The 7.3/7.4 notes also warn that left-side Super+Shift combinations and Super-Select were unreliable on MacIvory keyboards; they recommend the right modifier keys or the on-screen icons for that environment.

Inclusion rule

The count is the 74 unique commands explicitly supplied to the active *wt-comtab* command alist in comtab.lisp.~52~. A second form repeats Convert Flat Text to Record; it is counted once. The ordinary inherited Zmacs set, menu aliases with a numeric argument, inactive commented commands, and debugging commands are excluded. The descriptions below combine implementation docstrings with direct control-flow inspection; they are not copied manual prose.

Buffer, syntax, record, and registry commands

Links, markup, pictures, examples, and generated matter

Conversion, change control, repair, and configuration commands

Create Markup, Find Markup String, and Reverse Find Markup String remain active direct-key/menu commands described above, but the inspected source does not supply them to the mode's named-command alist. They are therefore deliberately not part of the 74 count.

What “preview” means here

The Page Previewer is a formatter front end and page browser, not a passive bitmap viewer. Format Pages expands the chosen record hierarchy, evaluates formatter commands and environments under a document-device type, performs line and page breaking, constructs headings and collectors, resolves tags and case options, and stores page-box objects with semantic presentations. It can produce an index and table of contents and optionally send the result directly to a printer.

The manual warns that screen spacing and fonts need not exactly match printed output. Source inspection explains why: formatted pages are device-aware box trees, and display is a rendering of those trees, not a raster capture of printer bytes. Page border presentations navigate backward and forward; page numbers and index entries are presentations that can select a page; record presentations can switch back to the editor.

The frame keeps a hash table from record group to formatted-pages object. Each entry contains the page sequence plus final ambient values, final heading state, and any improperly referenced tags. Show Formatted Pages switches among these cached results during the boot. This cache is Lisp-world state; the source does not claim that it is a durable host-side page cache.

Format Pages options and validation

Each run increments a formatter timestamp, clears stale Case bindings and the list of unassigned selectors, and can reuse the prior formatted result's final ambient values. After building pages it annotates presentations that cross a page boundary, selects the first page, checks tag references, reports unassigned Case selectors, and clears transient Case bindings again. This last validation work is easy to miss if the Page Previewer is described only as “print preview.”

Set Widow Action has four exact policies:

Change Layout switches between Single-Page and Two-Page. Next/Previous move one page in single-page mode and two in two-page mode. Set Page searches by the page's rendered page-number string, starting after the current spread and wrapping around, rather than assuming page labels are consecutive integers.

Complete Page Previewer command inventory

The inclusion boundary contains 18 commands defined directly by the Page Previewer and BIX modules, three NSage variable commands explicitly installed into its table, and five ordinary Help/printer operations available through the inherited command environment. Disabled block-commented forms and the #+Franz experimental formatter are excluded. Two active definitions retain comments saying they are probably or only for debugging; they are included because the source still installs them.

The source contains but does not activate Show Page Containing, Check for Bogus Tags, and Discard Ambient Values; they sit in block comments. Format Experimental Record is guarded by #+Franz and explicitly debugging-only. None belongs in the active count.

Installed-help gaps

The recovered Concordia help set has ordinary topics for Format Pages and 13 command topics named as Page Previewer commands: Change Layout, Edit Record, Hardcopy Pages, Next Page, Previous Page, Restore Tags, Save Tags, Set Page, Set Widow Action, Show Documentation, Show Formatted Pages, Show Improperly Referenced Tags, and Show Overview. The active implementation surface is broader.

In particular, Reformat End Pages, Describe Page, Show Tags, Show Unassigned Case Selectors, Save Index, Format Merged Index, and the three Sage-variable commands are source-visible even though that named Page Previewer command-topic set does not cover them. The three printer-queue commands are system-wide facilities and need not have Concordia-specific help records. This comparison is structural; it does not claim the public guide never mentions an operation in explanatory prose.

.CTAGS is executable reconstruction data

Save Tags does not write a generic JSON-like table. It uses the Genera forms dumper to write forms in the Sage package that allocate counters, repair circular parent/child/alias relationships, and restore tag and citation values. Restore Tags invokes the binary loader inside a dynamically guarded continuation; loading the file outside the command's context is rejected.

For preservation, .CTAGS should therefore be treated as trusted Genera/Sage reconstruction input, not opened as an inert interchange archive. An external extractor may parse it, but executing an untrusted file would invoke a Lisp loader.

.BIX is a compact index interchange, not a world image

The active BIX format begins with the indexed topic and type, then a 32-bit entry count. Each entry contains a 32-bit page number, the page-number rendering contents, the index-entry contents, and a sort string or nil, using the SAB symbol and object encodings. It omits the original live counter graph and reconstructs stand-in page counters when read.

Format Merged Index takes a small text file whose nonblank lines name .BIX files; ! begins a line comment. Every source index must resolve to a registered book with a nonempty mnemonic, which prefixes its reconstructed page references. The source warns that multilevel-index support in this merge path still needs work. .BIX is therefore meaningful, narrow formatter interchange, not a resumable VM snapshot and not a lossless substitute for the source records.

Hardcopy and Scribe

Page hardcopy can target the configured printer or a file using that printer's format. The output pipeline is the Genera hardcopy device system; Postscript is an explicit Concordia dependency, and older book designs include LGP device paths. See hardcopy, Press, printing, and plot output for the wider cross-system printing substrate.

The 7.3/7.4 notes and the active toscribe.lisp.~216~ source also preserve an export route from a documentation topic to Scribe .mss source. That is a conversion from Concordia structure into another formatter language. It is not evidence that .sab itself is Scribe source or that the round trip preserves every Concordia-only presentation, picture, Case, and book-design behavior.

Document type, device type, and their pairing

Concordia separates what a document is from where it is rendered:

The current source's low-level device registry initializes Generic, LGP2, and LM, while its output flavors separately implement window/DEX and hardcopy device protocols. The guide's user-facing device names and the implementation's primitive device objects are therefore related layers, not a one-to-one enumeration. The article does not infer unsupported modern printer types from old LGP names.

Inheritance and effective specifications

Book designs are Lisp source files, principally under SYS:NSAGE;. A named element has definition forms and a source file. A use clause names parent elements; the child inherits their specifications and can add or override values. Top-level document-device entries compose several elements, so one apparent formatting rule can originate far from the final document type.

The active model includes at least these kinds of specification:

This is executable configuration in a live Lisp environment, not a CSS-like static style sheet. A book design can call functions and register commands. Concordia's DynamicText facility goes further: it can call a named Lisp function while a record is formatted, so output can depend on document options and machine state. That power makes source provenance and a controlled evaluation environment important when preserving or reviving a book design.

Source organization

The public book-design guide identifies specialized sources for Approach, Article, Lisp Dictionary, Installation, Letter, Memo, and Reference Cards alongside generic elements. The inspected media contains corresponding bd-*.lisp modules. The generic modules supply reusable document/device elements; specialized files compose or modify them rather than duplicating a complete formatter.

The Browser's internal registry retains each book-design element's name, definition forms, and defining source pathname. Edit Book Design Element opens that source in Zmacs at the defining form. This means the Browser is simultaneously:

• an inheritance and dependency inspector;
• a documentation front end for environment and attribute meanings; and
• a development navigator into editable Lisp book-design source.

It is not a WYSIWYG drag-and-drop page designer. Actual page results are verified in Page Previewer after definitions are compiled or loaded.

Pane and gesture model

The embedded Browser has a scrollable Display pane, a fixed top-level command menu, and a three-line Interactor. Command output in the Display pane is presentation sensitive. A selection or menu gesture on a document-device type, book-design element, environment, or attribute can describe it, show dependencies, edit its source, or retrieve its documentation according to type and gesture.

The source disables keyboard command accelerators. A comment explains that enabling the generic accelerator mode would make the command processor accept commands only through Meta-X or the colon command syntax. The two explicit Scroll Forward and Scroll Backward command definitions are consequently block-commented; the pane's left and bottom scroll bars provide navigation.

The fixed menu has these ten labels in four columns:

The manual generally offers Display, Printer, and Typeout as output destinations. The implementation routes Display output to the Browser pane, Printer output to a hardcopy stream, and Typeout to the current command output. Environment descriptions request landscape printer output; the other browser reports use portrait.

Complete Book Design Browser command inventory

The 11-command count includes every active define-book-design-browser-command form after removing top-level block comments. Ten commands are in the fixed menu. The eleventh, Describe Registered Book, is command-line only.

The source contains a substantial Define Document Device Type prototype, but the entire command and its helpers are inside a block comment. It is not a hidden active feature. New pairings are created in source using the documented book-design forms, then loaded/compiled; the Browser inspects and edits those definitions.

Manual and source discrepancies

Three differences are preservation-relevant:

1. The installed dictionary documents nine domain commands. It does not list the Browser's active Help wrapper or command-line-only Describe Registered Book.
2. The guide says every command except Clear Display and Edit Book Design Element accepts an output destination. The inspected Show All Document Device Types definition instead takes no argument and always sends its reports to Printer.
3. The manual's four-way Super-Select switching sequence includes the Browser; the active configuration hook includes only Editor, Page Previewer, and Graphic Editor. The icon and Change Configuration remain valid source-defined routes.

These are bounded disagreements at one media snapshot. They could reflect a manual revision mismatch or a later source change; neither side is silently declared wrong for all releases.

Create and structure a document

1. Load/select the optional Concordia system and create or read a .sab buffer in Concordia mode.
2. Create typed records, fill their structural fields, and keep each independently meaningful for on-line lookup.
3. Create Include/Contents links to establish a hierarchy; use Crossreference or Precis where inclusion is not wanted.
4. Add formatter environments and commands, pictures, examples, active text, Case options, index directives, tags, and citations.
5. Check spelling, link graphs, outlines, orphan reports, and modification history.
6. Format the root topic in Page Previewer, inspect page breaks and presentations, repair tag/Case diagnostics, and reformat.
7. Send selected pages to hardcopy or a printer-format file, or export a bounded topic to Scribe where that compatibility path is required.

The editor's preview command can format a record or send it to hardcopy, while Page Previewer formats a complete linked document with collectors and page state. Those operations are related but not interchangeable.

Develop or modify a book design

1. In Book Design Browser, describe the target document-device type and identify the element that supplies the effective environment attribute.
2. Show dependencies before changing a widely inherited generic element.
3. Edit the defining element in its Lisp source, preferably specializing a narrower child when the change should not affect every document type.
4. Compile/load the definition in a controlled development world.
5. Reformat representative books and inspect both Screen/DEX and intended hardcopy routes; the inheritance graph alone cannot prove page behavior.
6. Package site changes through the normal system/patch workflow so the source and loaded definitions remain reproducible.

The Browser makes inheritance visible, but it does not provide transactional rollback for arbitrary evaluated book-design code. Source control, system versions, and patches remain the durable change mechanism.

Install and distribute documentation

The documentation maintenance guide models a documentation corpus as a patchable Genera system whose ordinary modules are .sab inputs. Compilation installs the records and updates component directories, journals, and database/index state. The guide explicitly configures source distribution for .sab modules and disables ordinary binary-object distribution because there is no per-module .bin product.

The same .sab file can be loaded on 3600-family and Ivory machines. A second machine-type “compile” can therefore consist of updating system journals/component metadata rather than translating record code into a new instruction-set object. That is strong contemporary evidence that .sab is portable serialized document source, even though its representation is binary.

The 7.3/7.4 installation notes add operational context:

• loading Concordia was an optional, historically lengthy operation;
• writer use generally required decompressing the installed documentation database so full record-group relationships were available;
• Lock Simple coordinated shared .sab writes;
• sites with custom designs, commands, or environments needed to distribute and load both the definitions and their documentation.

Format character

Source: sab-file.lisp.~122~ describes its principal operations as writing and reading a compiled Sage record over a byte stream. The encoding is a tagged object language with separate symbol and string tables. Active type codes cover, among other things:

• records, types, function specifications, fields, and unique identifiers;
• strings, long strings, characters, lists, fixnums, and interned or uninterned symbols from several packages;
• contents lists, environments, environment modifications, commands, macro calls, and source locations;
• links/references, including the later extensible-reference representation;
• token lists, modification histories, indexes, callees, and file attributes;
• pictures, eight-bit byte arrays, and example-record markers.

Each record is independently addressable by a start pointer and length. A file also contains an index and attribute information, which lets the database locate records without materializing an entire world image. Package symbols and executable-looking formatter structures are serialized as data for the Sage loader; a generic parser must not assume that every field is plain Unicode text.

This answers several preservation questions directly:

Local recovered corpus boundary

The inert Genera help extractor selected 30 Concordia .sab inputs at the inspected media boundary. They total 3,896,264 source bytes, 689 decoded records, and 2,602,648 bytes of embedded byte arrays. A sorted evidence manifest of logical path, record count, source size, embedded byte count, and source SHA-256 hashes to 3bce1e6e43283a8b88c2a2cf554f4fabb6c3f72e4253d2c9f55d4cefd54c8cd7.

Representative components include:

These counts are evidence, not redistributable content. The decoded JSON, text, pictures, and byte arrays remain under ignored build/help/genera/. The repository tracks the inert extractor and this original analysis only.

What external extraction preserves and loses

The current decoder preserves enough structure to inventory record topics and types, fields, commands, environments, links, pictures, styled strings, character styles, function specs, reader-source forms, and embedded arrays. The full 801-file Genera run recovered 17,266 records; Concordia's 30-file subset is reported separately above so corpus-wide counts are not misrepresented as Concordia-only.

High-confidence extraction can retain the effects represented in data: linked hierarchy, formatter commands, text, field values, encoded pictures, and identifiers. It cannot by itself reproduce:

• arbitrary functions called by DynamicText or active examples;
• the effective book design unless the relevant Lisp definitions are also analyzed;
• live registry conflicts, site patches, fonts, printers, or presentation translators;
• an external Graphic Editor source drawing when the .sab retains only a compact replay encoding;
• author intent that was discarded when flat markup became compiled structure.

For that reason a museum export should expose a normalized record graph and mark unresolved executable or package-dependent objects, rather than pretending the result is either original prose source or a resumed Genera system.

MIT CADR System 46

A case-insensitive search of the complete pinned public src/ snapshot for Concordia, Basic Sage, Writer Tools, SAGE-BINARY, Page Previewer, and Book Design Browser returned no files. System 46 does provide the underlying historical categories—ZWEI/Zmacs editing, documentation strings and help, fonts, Press/XGP/Versatec/DPLT output, and Lisp data structures—but no evidence supports calling those pieces an early Concordia application.

This boundary matters. Similar goals such as editing text and producing hardcopy do not establish source lineage. The earliest public tree here should be described as providing ancestors of the platform facilities, not the Concordia record database, formatter, or book-design browser.

LM-3 System 303

The pinned LM-3 System manifest contains 4,917 file entries. Its path inventory has no Sage, Writer Tools, Concordia, Page Previewer, or Book Design Browser subsystem. A full-text search of the corresponding maintained checkout finds the selected terms only in 24 historical bug/release-record files (including duplicate evacuated versions), not implementation modules.

Those records nevertheless establish chronology that System 46 cannot. They name, among other combinations:

• Experimental Basic Sage 2.2 with a “New Sage” environment;
• Experimental Basic Sage 7.6 and Experimental Writer Tools 7.0;
• Basic Sage 15.9 and Experimental Writer Tools 12.23 in Release 6.0 records;
• later Basic Sage 42.x/52.0 and Writer Tools 37.0/41.0 contexts.

This is evidence that Sage and Writer Tools existed in the Symbolics-era software line represented by those archived reports before the later Concordia 444 snapshot. It does not prove that their source is open, that the LM-3 restoration distributes it, that their feature set matches Concordia, or that the current System 303 band loads them. Recovering that implementation would require a separately licensed or authoritatively public historical source corpus.

The exact public boundaries checked here are MIT CADR commit 8e978d7d1704096a63edd4386a3b8326a2e584af and LM-3 System check-in 4df393c68d7f083ce42d5c377039d26043cc18a9031ace28258dc97f4137eb91. The latter is a maintained restoration check-in, not the date of the historical bug reports it carries.

Exact probe and result

Session d36-concordia-20260718, generation 1, cold-booted the private Genera 8.5 world in the repository's isolated Xvfb harness. The selected main window was 1200 by 900 pixels and titled Genera on DIS-LOCAL-HOST. The ordered input intents were:

1. find the packages named NSAGE, SAGE, and CONCORDIA;
2. for CONCORDIA, *WT-COMTAB*, PAGE-PREVIEWER, and BOOK-DESIGN-BROWSER, report symbol accessibility plus function and variable binding state in the Sage package;
3. ask the System Construction Tool for Concordia and NSage without issuing a load command;
4. send Abort after the system lookup requested a site login.

The first form returned the same SAGE package object for NSAGE and SAGE, and nil for a separate CONCORDIA package. The second returned:

• an internal CONCORDIA symbol with neither function nor variable binding;
• an external *WT-COMTAB* symbol with no variable binding;
• no PAGE-PREVIEWER or BOOK-DESIGN-BROWSER symbols.

The system lookup reported Concordia unknown and tried to locate a Concordia system definition through the unconfigured site's DIS-SYS-HOST. It reached a Login prompt because the sandbox intentionally supplies neither an external route nor guest-visible host file service. The lookup was aborted; no optional system, source, help file, or book was loaded, compiled, installed, or written.

This proves that the base world contains resident NSage/Sage package substrate but not the inspected Concordia application definitions. It does not prove that all of NSage 440 is loaded, and absence from this world is not absence from the licensed media.

Why there is no published screenshot

Four raw screenshots and their sidecars remain in the ignored session tree. The three evidentiary captures were:

They show only a Dynamic Lisp Listener, not the application documented here. Under the repository's screenshot publication review, publishing one would add little application evidence and risk becoming decorative. No image was curated into docs/assets/. A future page revision should publish a specific, rights-reviewed Concordia frame only after the optional activity can be loaded safely and its visible state is actually exercised.

Harness and shutdown provenance

The harness ran in separate user, mount, network, PID, IPC, and hostname namespaces; the guest had no default/external route or host file service. Xvfb advertised no MIT-SHM, and both pinned X-protocol substitutions plus the local RFC 868 reply were observed before the session was considered running.

Shutdown reproduced the already documented VLM behavior: the prompt appeared, yes was sent and accepted, cleanup progress appeared, and the VLM then reached the confirmed stall that required the bounded forced stop. The result is not an orderly VLM shutdown. At handoff both VLM and Xvfb were dead, the base world was unchanged, the private world was unchanged, and no host process checkpoint was created. save_world_performed and guest_checkpoint_created remain unknown, and state_may_be_incomplete is true. No world hash change is being used to infer a guest Save World.

Principal Concordia inputs

All pathnames below are portable media-relative identities under sys.sct/; no machine-specific acquisition path is published.

Principal NSage inputs

Help extraction toolchain

The full source-input manifest recorded by the catalog hashes to ca5678d3e1ffc8650e28836d4a2daf4cea1a48ee594dcf406485d92717281b70. The source-help pass is non-evaluating: it identifies literal docstrings, command definitions, and explicit documentation registrations but does not macroexpand or load the licensed source. All figures in this page were verified on 2026-07-18.

Public manuals and exhibit

• Symbolics, Symbolics Concordia consolidated manual, especially “Using Symbolics Concordia,” “Concordia 3.1,” Page Previewer, Writer Tools commands, and documentation maintenance sections.
• Symbolics, User's Guide to Symbolics Concordia Book Design, especially the document-device model, inheritance, environments, and Book Design Browser chapters.
• Symbolics, Concordia 7.3 Ivory Release Notes.
• Symbolics, Concordia 7.4 Ivory Patch Notes.
• University of Hamburg, Symbolics documentation index and Concordia exhibit.

Public source boundaries

• MIT CADR System 46, pinned public source tree, commit 8e978d7d1704096a63edd4386a3b8326a2e584af.
• LM-3 System 303, pinned maintained restoration check-in, check-in 4df393c68d7f083ce42d5c377039d26043cc18a9031ace28258dc97f4137eb91; the public historical System 42 bug report is one of the records carrying Basic Sage and Writer Tools version evidence.

Related museum studies

• Genera Graphic Editor and structured drawing
• World loads and VLOD
• Help, self-documentation, and Document Examiner
• Lisp Machine text editors
• Hardcopy, Press, printing, and plot output
• Dynamic Windows and presentation-based interaction
• Publishing runtime screenshots for museum documentation

External public links and pinned source boundaries last verified 2026-07-18.