Namespace administration and the Namespace Editor in Genera

Evidence and rights boundary

The implementation source, installed Help, release notes, world image, VLM, and raw runtime captures used here come from licensed Open Genera media. They remain untracked. This article records short interface labels, factual inventories, checksums, and original analysis; it does not reproduce the source, database contents, or Help prose.

Login identity is a Namespace object

Genera login normally resolves its first argument as a Namespace User object. That object supplies the Lisp Machine display name and home host; its class also contains file-server login names and the mail address. If a host is specified explicitly, login can construct an uninterned user identity for that host rather than using the user's normal home-host view.

The inspected Lisp entry points are:

Login and the Namespace Editor are related but distinct. Editing a User object does not itself log anyone in, and a local-only User edit is not a durable account change. The login path may query a namespace server and the file host, so its error/retry behavior is part of network and site state rather than a purely local password dialog.

Namespace database architecture

Complete object-class and field inventory

An asterisk below marks source-required data. Name is internal to every class. Fields can be repeated where their template says element or set.

File System is declared as introduced in Namespace protocol version 5. It is not described in the inspected site10–site12 class chapters, which cover the other six classes. This is a source-only feature finding, not grounds to retrofit the older manual silently.

Namespace Editor frame and entry points

The program framework has no fixed Select key by default. Its supported entry surfaces are:

• Select Activity Namespace Editor, verified in the Genera 8.5 runtime;
• activity selection through the loaded system menu;
• a site-selected Select-key assignment; and
• Edit Namespace Object or Create Namespace Object, which select the activity and inject the corresponding editor command.

The last two CP commands reject remote terminals: object editing and creation must occur on the local display. Show Namespace Object remains a textual CP operation.

The frame has a title pane, one Accept Values object pane, a current-object title, a two-column command menu, and a command interactor whose prompt is Namespace:. The source enables a system-menu entry and inherits the Help Program, Accept Values keyboard commands, full-command syntax, standard arguments, and input-editor compatibility. Inherited facilities are not mistaken here for custom Namespace bindings.

Complete Namespace Editor command inventory

Complete editor-specific keys and gestures

No additional Namespace-specific mouse button table was found. Editing field values uses the inherited Accept Values and presentation-type interaction: a typed object name, service, address, keyword, or set is parsed and completed by its semantic type, and mouse-sensitive presented choices can supply those values. This page does not relabel all generic Dynamic Windows editing gestures as Namespace Editor commands.

Defaults and validation

Insert Defaults does nothing for Network and Namespace objects. For the other classes it can derive:

Before Save, the source checks every required field and invokes registered validators. It checks network addresses; names, nicknames, and short names; service/medium/protocol triples; and structured field types. It rejects an incomplete Peripheral entry. For embedded Unix machine types it warns if an EMBEDDED-IN user property is absent. Genera 8 release notes also warn that adding TCP/UDP Namespace services can make pre-8.0 systems choose protocols they cannot boot with.

The primary server checks references before a global deletion and reports referrers. The release notes identify this as a post-7.2 safety improvement; older behavior could leave server errors after deleting a referenced object.

Complete Namespace CP command table

Namespace is a child of the broader Site Administration command table, alongside Access Control, Spelling, and World Building. The following eight commands are the complete Namespace administration surface defined by the two inspected implementation files; commands in sibling tables are not included.

Genera 8 changed Add/Remove from one service to a sequence and pluralized their names. It also completely rewrote the Set Site and Define Site dialogs and introduced Insert Defaults.

Persistence and safety model

The editor's confirmation flag can suppress routine Save/Delete questions, but the second confirmation for creating globally named Namespace or Site objects is deliberately not bypassed. LINK-NAMESPACES is a source-only Lisp function, not one of the eight CP commands: it runs only on the primary server, and its optional network merge is permanent and carries a strong confirmation. Use of the same global name is preferred where applicable, but the source comment calls it GLOBAL-NAMESPACE-NAME while the inspected Network class actually defines GLOBAL-NETWORK-NAME. This page does not silently choose which spelling the comment intended.

Compatibility entry points retained by source include TV:EDIT-NAMESPACE-OBJECT, SI:COM-SET-SITE, and NET:SET-SITE. Their presence supports old scripts; it does not make the old dialogs the Genera 8 interface.

Runtime observation in the isolated Genera 8.5 world

The Xvfb harness opened the Namespace Editor without selecting an object or contacting a namespace server. The world reported Genera 8.5 / Open Genera 2.0 and also reported that it was not configured for a local site and that servers were disabled. The observation therefore verifies frame behavior and menu surface, not a configured site's database contents or global update protocol.

The exact input sequence was:

1. type Select Activity Namespace Editor and Return;
2. observe the empty frame titled Namespace Editor, current state (No Object), Namespace: prompt, and all thirteen menu labels; and
3. press Help once.

The Help key was delivered successfully but produced no visible change in the empty, unconfigured frame. That does not establish a broken Help system: no field or topic was selected, and the source's context-help path requires an installed matching record.

No object was selected, created, edited, saved, reverted, or deleted. Set Site, Define Site, service changes, server validation, login, and network discovery were not invoked. The base and private world hashes still matched at shutdown; the private world did not change. The harness invoked neither Save World nor a process checkpoint. Shutdown reached its prompt, accepted confirmation, and showed cleanup progress, then encountered the known VLM cleanup stall and was forcibly terminated. Accordingly forced_stop and state_may_be_incomplete are true, and the run is not called orderly.

Reviewed runtime screenshot

Runtime observation: Namespace Editor on Genera 8.5 immediately after Select Activity Namespace Editor, captured 2026-07-18. The frame is intentionally empty: no object or site data was selected, and no mutation was attempted. Underlying software and display material remain the property of their respective rightsholders; reproduced here for criticism, scholarship, and historical documentation under 17 U.S.C. section 107. No affiliation or endorsement is implied.

This one frame is published because the title, (No Object) state, prompt, pane division, and complete short menu are necessary to verify the source/manual interface analysis. It is a sparse functional display, contains no configured namespace record or Help prose, cannot substitute for Genera, and is the minimum image needed for that purpose. The image-specific review and exact raw-to-curated mapping are recorded in the screenshot rights review and Genera screenshot catalog. The PNG is an exact 2,921-byte copy, 1200×900 pixels, SHA-256 258afd1127848af24d2c3cc91ae6c369b5fa8febbda7b5e79742baace765582c; the normalized-pixel SHA-256 is 3b0b4de8249126f4e790474c13498edcd9e10f195b23ea0944204dcdcce3f7b7.

The initial Listener capture and the visually identical post-Help capture remain ignored because they add no necessary editor evidence. A later configured-site run would require a separate safety and rights review and should use a synthetic, nonprivate Namespace object.

Manual, source, and runtime differences

• Installed site10 presents the principal editor commands but the live/source menu also makes Quit and Insert Defaults plainly visible; Not Modified and Refresh are keyboard-only.
• The manuals document six object-oriented Namespace CP commands in the editor chapter. Set Site and Define Site are documented elsewhere and are still in the same source command table; omitting them would understate the table's destructive end.
• File System, introduced in Namespace protocol version 5, is present in the 8.5 source class list but absent from the inspected class chapters.
• Source establishes top-level no-op keys, Space's typeout dual role, the infinity behavior of scrolling, the global-object second confirmation, the dangling-peripheral rejection, and the embedded-host warning; these details are not all apparent in the high-level editor overview.
• Runtime confirms the exact empty-frame menu and activity command in this unconfigured world. It does not validate object-specific fields, server propagation, or mutation commands.

Open questions

• TODO: identify which installed manual volume first documents the protocol-5 File System class and compare its exact fields with the 8.5 source.
• TODO: use a synthetic local-only object in an expendable private world to verify Accept Values field completion, validation errors, history selection, Revert, Not Modified, and Insert Defaults without contacting a server.
• TODO: test a synthetic primary/secondary namespace laboratory before making timing claims about lazy cache propagation.
• TODO: compare the source's LINK-NAMESPACES behavior with any administrator manual that documents the preferred global-name workflow and resolves the GLOBAL-NAMESPACE-NAME versus GLOBAL-NETWORK-NAME discrepancy.
• TODO: do not exercise Set Site or Define Site in the purchased base world; construct a disposable synthetic file host and explicit rollback procedure first.

Sources

• Symbolics Genera 8.5 licensed source artifacts identified in the evidence tables above, inspected locally 2026-07-18; proprietary files remain untracked.
• Symbolics installed Namespace Editor, Site Operations, and Command Processor Help, original Sage Binary artifacts identified above, decoded locally with the repository's inert Help extractor and inspected 2026-07-18.
• Symbolics Genera 8.0 Site Operations release notes, rn8-0/site.sab.~22~, SHA-256 1ffe437ef33b050fee52a14a1300db09cb75de35ce852fad4ebb9d1404144aef, inspected 2026-07-18.
• Local runtime observation d20-namespace-editor, generation 1, performed 2026-07-18 through the isolated Genera computer-use harness.