CADR QSend, Converse, SHOUT, and NOTIFY bindings and semantics

Release profiles

These short names are exact aliases for the main D09 identifiers, not parallel profile systems:

The maintained Fossil branch was created in 2025 from historical material. Its check-in is a maintained restoration target, not evidence that the exact selected bytes were installed in an original 1980s band. [C303-SRC]

Conformance levels

This companion uses the main specification's levels unchanged:

C46-QSEND/L2 means exactly DM-C46-SRC/L2, and C303-CONVERSE/L2 means exactly DM-C303-SRC/L2. Both are source-profile goals. C303-WORLD-303-0 currently closes only the negative load-boundary observation, not L3.

C46-QSEND objects

SAVED-SENDS MUST retain messages in arrival order because the receiver appends at its active end. Mutation is incremental: the local heading, remote first line, and each body prefix copied before a stream failure remain in the active string. There is no transaction rollback or delimiter repair; because the two final returns are appended only after successful copy and close, a mid-copy failure leaves an unterminated partial tail that PRINT-SENDS exposes and the next receive extends. The source gives no persistence promise across world save or cold boot. PRINT-SENDS writes the entire active string and returns true. [C46-SRC]

C303-CONVERSE objects

The following invariants are normative for the strict source profile:

1. The first conversation is the headerless composer; ordinary conversations follow it in *CONVERSE-LIST*. [C303-SRC]
2. Each conversation's first line reaches its active To: delimiter, which reaches its last line; adjacent conversations share the expected line adjacency. The integrity predicates check those facts before structural commands. [C303-SRC]
3. OLDMSGS stores each recorded display string independently of visible unsent edits; regeneration can reconstruct recorded messages but cannot reconstruct unsent text. [C303-SRC]
4. A peer is grouped by case-insensitive EQUALP comparison of the exact canonical destination string returned by the parser. Multiple recipients are processed as separate peers and records. [C303-SRC]
5. Network processes MUST NOT directly edit the interval. They enqueue work; the frame's forced internal keyboard event, expose hook, or post-command hook drains it. [C303-SRC]
6. Compatibility saved-send history and per-conversation OLDMSGS are distinct. Updating the first does not prove that a delayed Converse request was drained. [C303-SRC]
7. TV notification history is distinct from both Converse histories. A display or careful-delivery failure does not roll back its already-pushed history entry. [C303-SUB]
8. The selected before-cold initializer does not assign the last-sender register. Invoking that operation MUST retain its exact prior value in strict mode. This is an operation-level guarantee only; it does not claim survival through every cold boot or world-loading mechanism. [C303-SRC]
9. The distinct TV before-cold initializer sets notification history to NIL but does not assign pending or deferred queues. Strict invocation MUST preserve exact sentinel identities in both queues; this does not assert their survival through every complete cold-boot mechanism. [C303-SUB]

The selected file registers four distinct operations. A cold-only action sets gag state NIL. One before-cold action sets saved sends NIL and leaves last sender and receive mode untouched. A separate before-cold action calls FIND-CONVERSE-WINDOW: it chooses a Converse ancestor, finds an existing frame, or creates one; ensures the frame process has a run reason; and then clears that frame's request queue. The :ONCE action initializes the comtab, creates and activates a frame, and gives its process a run reason. Strict mode MUST expose these independently and MUST NOT equate :ONCE with every cold operation. Receive mode is untouched by all four.

On the first receive after the saved-sends NIL reset, selected STRING-APPEND coerces the old symbol value to its name, so the new history ends in the literal characters NIL. A fresh source load that first binds the variable to its empty extensible string does not add that suffix unless the before-cold initializer runs. It contains no automatic transcript writer and no equally explicit cold-reset form for all conversation OLDMSGS; a reimplementation MUST NOT invent one under the strict profile. That initializer also leaves the last-sender reply register untouched; strict mode retains a sentinel value across this operation, while an explicitly labelled correction may clear it. [C303-SRC] [C303-SUB]

The separately registered TV before-cold operation clears only retained notification history. Pending and deferred queues remain untouched. A correction that clears all three is permissible only as an explicitly reported option. [C303-SUB]

Normative incorporation of D05 parent trees

For C303-CONVERSE, the complete effective clean-profile parent is incorporated, not summarized, from these exact in-repository D05 sections:

• System 303 standard ZWEI table;
• System 303 standard Control-X table;
• System 303 effective ingress and pointer overlays; and
• System 303 Help subtree.

Those mappings are normative here wherever the local sparse table falls through. The local table's indirection points directly to *STANDARD-COMTAB*; its clean editor closure selects Text mode. An implementation MUST compose the local cells below over the incorporated parent, retain D05's alias restart and explicit :UNDEFINED semantics, and attach reader context to TV interception. User/profile mutations and later mode activation form a separate mutable-tree profile and MUST be reported by a runtime dump rather than folded into this static denominator.

Terminal is a host-global TV asynchronous prefix above that D05 editor lookup, as the incorporated effective-ingress section already establishes. Converse installs zero Terminal-prefix cells. The TV-owned Terminal N leaf and notification windows are nevertheless enumerated below because the selected C303 receive modes enqueue and display through that facility.

For the C46-QSEND rubout-handler editor path, the applicable parent is incorporated from the complete preserved System 46 Standard table and System 46 Control-X and recursive contexts. Only the pass-through terminators below are application registrations.

Deterministic denominators

T-BIND-DENOMINATORS MUST reproduce every number and tuple above from the pinned forms. Counts are source-cell counts unless the row explicitly says effective case-folded values.

C46-QSEND body-reader tree

QSEND or SEND-MSG with no body
└─ SEND-MSG-GET-MESSAGE
   ├─ stream supports rubout handler and no handler is already active
   │  ├─ #/END       -> pass through -> finish body
   │  ├─ legacy Control-c literal -> pass through -> finish body
   │  ├─ legacy Control-C literal -> pass through -> finish body
   │  └─ every other editing input -> incorporated System 46 rubout editor
   └─ fallback character loop
      ├─ End, either encoded Control-c form, or EOF -> finish body
      └─ every other value -> append exactly that value

The source contains no local yank, edit-in-Converse, pointer, prefix, numeric, or repeat binding in this prompt. Abort is not an application-owned leaf. A global keyboard abort can still nonlocally leave the inherited stream interaction, but its semantics belong to the TV/editor substrate. [C46-SRC] [C46-SUB]

C46-QSEND incoming reply query

The receiver calls the selected System 46 Y-OR-N-P; these are effective inherited keys, not registrations in chsaux.113:

If reply sending returns an error string, the receiver prints it and consumes one arbitrary input value before continuing cleanup. There is no application pointer or menu table. Programmatic :MOUSE-SELECT exposes/selects the pop-up; it is not a user gesture binding. [C46-SRC] [C46-SUB]

C303-CONVERSE main direct table

The Control-Z spelling is not a typo in this page. io1/conver.lisp defines CONVERSE-SEND-WITH-EXIT but stores the different symbol COM-CONVERSE-SEND-WITH-EXIT in the comtab; a full-tree search found no definition for the latter. Because the local nonempty cell shadows D05's parent Control-Z, the strict result is the editor's distinct “not implemented” path, not inherited Quit and not a guessed send. TODO-RUNTIME-C303-CONTROL-Z tests whether an unrecorded resident alias changes the preserved world. [C303-SRC] [C303-SUB]

Every other direct input falls through to the incorporated D05 Standard/Text-mode tree. An absent cell continues to the parent; an explicit undefined parent cell stops; a final unbound input clears queued input and reports not-defined. A stored symbol without a function binding, such as the strict Control-Z target, reports not-implemented instead. [C303-SUB]

C303-CONVERSE exact Meta-X registry

Meta-X itself is inherited from D05. The application adds exactly these nine completion names:

The registry contains no aliases, menu accelerators, or hidden tenth entry. Aborting Meta-X completion before a name resolves is inherited D05 behavior and precedes an application command. [C303-SRC] [C303-SUB]

C303-CONVERSE Help tree

The editor closure prepends exactly one entry to the inherited Help dispatch alist:

Help (also inherited C-Help and C-M-? dispatcher entries)
├─ M -> COM-CONVERSE-HELP
├─ C, D, A, U, V, W, conditional L, Space, Help, C-G, Rubout
│     -> exact incorporated D05 Help leaves
├─ ? -> inherited invalid-input path (beep and retry)
└─ every other input -> inherited invalid-input path (beep and retry)

The local Help operation displays the Converse explanation and returns to the editor after any continuation input required by the ordinary typeout path. Its prose is not normative where it conflicts with executable cells: it reverses the default End and Control-End meanings and omits Control-Z. The handlers, mode-line strings, and System 94 release note agree on End/Control-End; the Control-Z table target is nevertheless unresolved as specified above. [C303-SRC] [C303-MAN]

Main-editor pointer, prefixes, presentations, and menus

Converse installs no application mouse comtab and no local Control-X subtable. Therefore:

• D05's Standard Mouse-1-1, Mouse-1-2, Mouse-2-1, and Mouse-2-2 cells and pane-selection precedence remain effective in the main editor;
• Control-X and every reachable child are exactly the incorporated D05 Standard prefix tree, subject only to separately reported active modes;
• no Converse-specific Control-X leaf exists;
• no presentation translator, command-button gesture, right-click menu, or menu accelerator exists in the selected main-editor source; and
• an unrecognized local direct key follows D05 parent lookup rather than a separate Converse beep rule.

These are zero-count conclusions from the selected construction, not omissions. [C303-SRC] [C303-SUB]

C303 QSend transient body reader

QSEND/REPLY with destination but no body
└─ QSEND-GET-MESSAGE
   ├─ active stream offers :RUBOUT-HANDLER and no handler is already active
   │  ├─ End              -> return current body
   │  ├─ Control-Z        -> return current body
   │  ├─ Control-Meta-Y   -> request insertion of last received body
   │  ├─ Control-Meta-E   -> return current body plus transfer=true
   │  └─ other input      -> stream/rubout editor, including inherited Abort
   └─ fallback loop
      ├─ End, Control-Z, or EOF -> return body
      ├─ Return and END-WITH-RETURN-OK=true -> return body
      ├─ Control-Meta-Y -> append last body (or empty string) and force those bytes as input
      ├─ Control-Meta-E -> return body plus transfer=true
      └─ other input -> append exactly that input value

The selected current file does not register or test Control-C, although the historical system-98-26 patch file did. Strict C303-CONVERSE follows the selected current file; a patch-resident world profile MUST disclose any restored Control-C leaf. Abort is promised by the prompt/manual but is inherited from the active stream/editor rather than listed as a local editing-command cell. [C303-SRC] [C303-SUB] [C303-MAN]

If transfer is false, QSend sends. If true, it sets the exposure-wait flag, enqueues an edit-and-send request, waits until the frame is exposed, waits for window exposure, and then clears the flag. The transferred text is inserted into only the first parsed recipient's composer; this edit path does not initialize one composer per listed destination despite the function's broader docstring. [C303-SRC]

C303 simple-reply pop-up tree

The application registers nine literal FQUERY choice inputs. FQUERY compares characters with CHAR-EQUAL, so five letters also accept their opposite case:

The pointer method adds exactly:

The who-line text's L: and M: are labels for left and middle pointer choices, not keyboard letters. There is no keyboard L or M choice in the FQUERY table. The pop-up is a TV window, not a CLIM dialog. [C303-SRC] [C303-SUB]

Ambiguous-host chooser

For a bare user with more than one discovered host, Converse creates one dynamic menu item per candidate, labeled USER@official-host-name and valued by that host. A single host bypasses the menu; no host reports a Converse problem. The application owns item construction and consumes the selected value; TV's MOMENTARY-MENU owns the interaction. It installs no local keyboard reader or comtab, hence has zero menu-local Help, prefix, numeric, repeat, and unbound-key leaves. Global TV asynchronous keys remain global rather than falling through a chooser keymap.

For a fixture containing N candidates, the selected pointer tree is:

pointer over current selectable row i
└─ :MOUSE-BUTTONS(BD), for any nonzero three-button down mask
   ├─ item is not a :BUTTONS item -> ignore BD completely
   ├─ chosen-item := row i; last-item := row i
   ├─ deactivate momentary menu before execution
   └─ execute (label . host) -> return host

pointer over blank interior
└─ no current item -> no choice

pointer leaves hysteretic menu / menu deactivates without a choice
└─ execute NIL -> abort the choice transaction -> return NIL

The current-row branch does not call MOUSE-BUTTON-ENCODE. Left, Middle, and Right therefore select the same row; held Shift, Control, Meta, Super, and Hyper states are never merged into a button character, and Shift does not become a double click on this path. Simultaneous newly-down masks also select because the normal-item branch tests only that a current item exists and ignores BD after dispatch.

Accordingly the exact denominators are:

• N semantic returned host values;
• 3N normalized single-primary row/button operations;
• 96N single-primary raw state tuples: N × 3 × 32 combinations of the five Shift/Control/Meta/Super/Hyper state bits; and
• 224N full raw physical tuples when the four additional nonzero multi-button masks are included: N × 7 × 32.

Every tuple in the latter two sets maps to its row's same host value. These are TV-owned effective gestures, not Converse-owned cells, but they are normative for the selected chooser. Strict source cancellation returns NIL; parsing then emits the <undetermined-host> destination plus a NIL host, so the caller follows its ordinary no-host failure/omission path. TODO-RUNTIME-C303-HOST-CANCEL is retained only to detect a resident-world divergence. [C303-SRC] [C303-SUB]

SHOUT and NOTIFY prompt surfaces

SHOUT supplies *QUERY-IO* to the C303 QSend reader and therefore reaches its exact transient tree. It has no optional message parameter in the selected function, despite the manual signature. NOTIFY and NOTIFY-ALL-LMS have no input surface when a message argument is supplied. If omitted, their default form calls NOTIFY-GET-MESSAGE, whose selected body passes its default NIL STREAM as an explicit first argument to QSEND-GET-MESSAGE; the callee's *STANDARD-INPUT* default is therefore bypassed. Strict source behavior is a stream-operation failure before the documented prompt unless an unverified runtime definition repairs it. TODO-RUNTIME-C303-NOTIFY-PROMPT distinguishes those outcomes. [C303-SRC] [C303-MAN]

C303 TV notification ingress and dismissal trees

Converse owns no cell in this surface. In hidden :NOTIFY and :NOTIFY-WITH-MESSAGE modes it calls TV:NOTIFY with the Converse frame as the window of interest, thereby entering this exact TV-owned tree:

global Terminal prefix
├─ zero or more decimal digits and optional `-` characters -> accumulate signed ARG
└─ N (case folded to uppercase) -> KBD-ESC-NOTIFICATIONS(ARG), with :TYPEAHEAD
   ├─ ARG = NIL -> detach pending+deferred; always open task window
   ├─ ARG = T   -> detach; open only when detached list is nonempty
   │               (programmatic handler class; physical parser cannot make T)
   ├─ ARG = 1   -> detach; open and include retained old history
   ├─ ARG = 2   -> detach; move detached list to deferred; do not open
   └─ any other integer/value -> detach and neither display nor requeue

The physical prefix parser passes NIL when no digits or minus were entered. Digits are decimal; a minus makes the accumulated number negative, defaulting to -1 when there were no digits. It uppercases the final command character, so n and N reach the same single leaf. Terminal Help and Terminal ? show global Terminal help, not notification-window Help. An unknown final Terminal key follows TV's global quote-or-beep rule; it never falls through to the Converse or D05 comtab. [C303-SUB]

The T handler class has another prose/source disagreement. Its docstring says pending notifications only, but once a nonempty pending set opens the window, the shared WHEN ARG branch also prints every retained history entry left after the detached entries are skipped. Strict TV-NOTIFY-C303 preserves that extra old-history section for T, just as it does for integer 1. [C303-SUB]

The Terminal-N task window detaches pending ++ deferred atomically and clears both globals before branching. When displayed, each iteration first puts newly pending items before its current list, clears pending, redraws newest first, and prompts Type a space to flush. The executable input loop is broader than that prompt:

Terminal-N task window (POP-UP-FINGER-WINDOW)
├─ a new pending notification -> redraw/restart; do not yet dismiss
├─ selected window changes -> return and deactivate
├─ any ordinary character reaching :TYI-NO-HANG
│  ├─ Space -> consume one value; return and deactivate
│  ├─ Help or any other nonintercepted character -> identical dismissal
│  └─ no command lookup, unbound-key error, prefix, numeric, or repeat behavior
└─ Abort/Meta-Abort/Break/Meta-Break -> standard TV stream intercept, not a local leaf

Only one queued character is consumed on the dismissal path. If new pending work is observed first, the loop redraws; a still-queued character can dismiss the next iteration. This window defines zero notification-specific pointer methods, so pointer behavior belongs to its generic temporary-window substrate and is not invented as a notification binding. The prompt's claim that Space flushes is thus help text, not an exclusivity rule. [C303-SUB]

When the global wait-for-notifications flag is false, or a selected notification stream cannot fit the message, TV uses the separate fallback window:

fallback POP-UP-NOTIFICATION-WINDOW
├─ before input -> beep; select blank window; wait until the 180-tick protection
│                  interval; move preexisting typeahead back to the old window;
│                  clear this window's input; print its prompt
├─ any ordinary value returned by :ANY-TYI, including Space or Help
│                  -> finish the wait and deactivate
├─ forced :DEEXPOSE input -> wake the wait; deactivate
├─ Mouse-1-1 -> MOUSE-SELECT self -> deexpose; if non-NIL, mouse-select the
│                  recorded window of interest
├─ every other pointer button/chord -> local :MOUSE-CLICK returns NIL
└─ Abort/Meta-Abort/Break/Meta-Break -> standard TV stream intercept, not local Help

The fallback window has no local Help replacement, no unbound-key state, no local prefix, and no numeric/repeat interpretation. Under the standard stream output function, Abort is intercepted before :ANY-TYI; the selected code has no local abort cleanup clause, so post-abort exposure/resource state remains TODO-RUNTIME-C303-NOTIFY-ABORT. Deexposure forces the synthetic value solely to wake the waiting process. [C303-SUB]

System 46

The server registration is named SEND and starts POP-UP-RECEIVE-SEND-MSG through the Chaos server alist. The pop-up is allocated on first accepted message and reused. [C46-SRC]

System 303

Source construction proceeds as follows:

1. INIT-CONVERSE-COMTAB creates the sparse table and installs direct indirection to Standard ZWEI.
2. one-time START-CONVERSE initialization creates an active CONVERSE-FRAME and gives its process a run reason;
3. frame initialization creates/selects one ZWEI-WINDOW-PANE, inserts the initial return, constructs the headerless composer, and moves point after To: ;
4. the frame process loops forever calling its editor;
5. System C is registered for CONVERSE-FRAME; and
6. CONVERSE is declared as a separately compile/loadable system and an OUTER-SYSTEM component after ZWEI and ZMail. [C303-SRC] [C303-SUB]

These frame properties are normative source state even though visible pixels remain blocked by TODO-RUNTIME-C303-VISIBLE:

The source-visible entry paths are:

The manual and global symbol declaration mention QREPLY as a synonym for REPLY, but no defining or alias form was found in the selected current source files. It is not part of strict source-level callable closure until TODO-RUNTIME-C303-QREPLY finds a resident definition or another pinned defining artifact. [C303-MAN] [C303-SRC]

Request serialization

ENTER-REQUEST copies arguments, appends a request under interrupt inhibition, and forces internal keyboard input (:EXECUTE CONVERSE-EXECUTE-QUEUE). A delayed request does the same append without waking the frame. Exposure forces a queue execution if anything is pending; the post-command hook also drains the queue at priority 64. The executor applies each request and removes it from the live queue only after its function returns. Therefore a failing request remains queued, and later requests may remain behind it; there is no rollback or per-request condition handler in this method. [C303-SRC]

The executor's DOLIST begins at the live FIFO head, and enqueue extends the same list tail with destructive NCONC. A request appended during a successful handler is therefore reachable in the same traversal. For initial [A,B], if A enqueues C, strict execution is A, B, C in one drain. Snapshotting the initial length and deferring C is not source-compatible. [C303-SRC]

Incoming hidden-mode :SIMPLE, :POP-UP, :NOTIFY, and :NOTIFY-WITH-MESSAGE work is delayed. Compatibility history and last-sender state change immediately, but the conversation interval changes only when a later wake or exposure drains the queue. :AUTO or already-exposed work uses the waking path. [C303-SRC]

C46-QSEND outbound transaction

1. If a nonnumeric destination contains @, split at the last at-sign, uppercase the person component, and use the suffix as host. Otherwise use person anyone and the destination as host.
2. Force a user login.
3. If body is NIL, run the C46 body reader.
4. connect to Chaos contact SEND <person>.
5. If connection returns an error string, return it without stream output.
6. Write one sender/time header, then body bytes, then stream EOF; close with an empty reason and return NIL. [C46-SRC]

The transaction does not record outbound messages in SAVED-SENDS and is not atomic after connection opens.

C46-QSEND inbound transaction

1. Record the current saved-string end as the display start.
2. Listen for SEND. If state is not RFC-RECEIVED-STATE, skip every RFC/history/ close/UI/reply operation, attempt REMOVE-CONN exactly once, and normally return NIL. If an RFC is present, derive recipient from contact suffix or use anyone, append a local display heading, accept, and read the remote first line into SAVED-SENDS.
3. Derive sender user from text before @, from text after from , or from the empty string; append the connected host name.
4. Copy remaining stream bytes incrementally into SAVED-SENDS.
5. After the copy reaches EOF successfully, close the connection and append two returns.
6. Lazily allocate the window; beep SEND-BELLCOUNT times before acquiring the pop-up lock.
7. Acquire the global lock. A waiter may notify the current screen once before sleeping.
8. Select the pop-up, clear it only if newly exposed, and show this message's slice.
9. Remove the already closed Chaos connection.
10. Run the inherited reply query; an affirmative answer calls SEND-MSG back to the captured sender.
11. Clear the lock, allow scheduling, then deselect/deactivate only if no successor already acquired the lock. [C46-SRC]

The local heading and remote first line are already committed before body copy, and the stream copier mutates the same string as bytes arrive. A failure during that copy therefore leaves the connection open and registered, preserves the copied prefix without the final two-return separator, performs no window allocation or beep, and does not roll back history. A later PRINT-SENDS exposes that partial tail, and a later receive appends directly after it. [C46-SRC]

After successful copy, CLOSE and the two-return history terminator occur before window allocation, beeping, locking, selection, and display, but REMOVE-CONN occurs only after the slice's :STRING-OUT returns and immediately before the reply query. Thus a failure after close but before completed display leaves a complete, terminated history record and a closed but registered connection; a query or reply failure observes it already removed. The unwind clause clears the lock if the current process still owns it, but does not close or remove the connection and never rolls back history. [C46-SRC]

A LISTEN or state-access/comparison failure exits before ordinary REMOVE-CONN. The unwind clause still performs only conditional owner-lock release; it does not close or remove the connection. [C46-SRC]

C303-CONVERSE destination and send transaction

Comma parsing trims each field and preserves order. An explicit user@host uses the first at-sign in PARSE-SINGLE-DEST, parses the host, and returns the official address form. A bare user searches logged-in Lisp Machines plus configured extra hosts; no match yields <undetermined-host>, one match selects directly, and several invoke the chooser. [C303-SRC]

The editor send path MUST preserve this order:

1. validate the whole structural buffer and locate the conversation at point;
2. require the selected text to begin with To: and contain a nonblank body;
3. parse every comma field far enough to reject a nonexistent explicit host;
4. restore/clear the composer before attempting any delivery;
5. for each recipient in order, resolve the bare user, send or mail if a host exists, and append one success/failure record to that recipient's conversation;
6. move point to the resulting conversation's active composer for an in-frame send;
7. return true only if no recipient set the sticky aggregate loss flag. [C303-SRC]

Thus validation failures preserve the draft, but a connection failure occurs after the unsent draft has been removed. Its text survives only in the inserted failed-send record. Earlier recipient records remain after a later failure; there is no group rollback. For interactive delivery, each SEND-MSG result replaces the current recipient's failure reason. In mail mode, a prior no-host failure reason is not cleared before a later mail call, so a later mailed recipient can be recorded with the stale failure reason. Strict compatibility preserves this ordering defect. [C303-SRC]

The in-frame loop attempts and records recipients in comma-input order. Each newly created peer block is inserted immediately after the headerless composer, however, so several all-new peer blocks finish in reverse creation order even though their network attempts occurred in input order. Existing peer blocks are not reordered. [C303-SRC]

End staying in Converse ignores the boolean send result. The exit variants bury only after an all-success result. Control-M uses the mail adapter but otherwise shares draft clearing and per-recipient recording. [C303-SRC]

C303 out-of-frame QSend ordering

QSEND-FORCE-MESSAGE parses candidates in comma-input order but PUSHes each resolved recipient, producing a reversed work list. QSEND-FORCE-MESSAGE-1 therefore attempts valid recipients and appends their delayed record requests in reverse input order. It also PUSHes each success, so its synchronous returned success list is back in the successful recipients' original relative input order. The request queue is FIFO. If all peer blocks are new, draining reverse-ordered record requests through front-inserting SETUP-CONVERSATION happens to restore their original block order; that does not change the reverse wire-attempt order. [C303-SRC]

C303 raw SEND-MSG

Raw SEND-MSG accepts one destination only. An integer in the selected Chaos address range is converted to a Chaos host. A string is split at the last at-sign; person case is preserved for Unix and Multics host types and uppercased otherwise. Without an at-sign, the person is anyone. It opens SEND <person>, writes user@local-host plus date/time, writes the body, closes, and returns NIL; an open error object is returned unchanged. It warns when this machine has locally gagged incoming messages but still attempts the outbound send. It does not create a Converse record by itself. [C303-SRC]

C303 receive transaction and policy

The server listens on SEND, rejects a connection classified as Symbolics by the selected compatibility predicate, and otherwise rejects while gagged. A string gag value is the rejection text; true synthesizes a user-not-accepting message. If accepted, it derives requested recipient from the RFC, reads the first line, derives sender user, resolves the remote Chaos host or formats its numeric address, and builds the display record. It includes a To: line only when the request recipient differs from the logged-in user. A caught connection drop appends an explicit trouble marker to the partial body. [C303-SRC]

CONVERSE-RECEIVE-FROM-NETWORK then:

1. prepends the record and two newlines to compatibility saved sends, coercing an old NIL value to the literal suffix NIL;
2. replaces last sender;
3. finds/creates the frame and samples its exposed state;
4. for hidden simple/notify modes, beeps, queues delayed insertion, and opens the pop-up or calls TV:NOTIFY;
5. otherwise queues waking insertion; and
6. insertion finds/creates the peer conversation, pushes OLDMSGS, adds the visible record according to append mode, moves point when appropriate, and redisplays. [C303-SRC]

Receive modes are :AUTO, :NOTIFY, :NOTIFY-WITH-MESSAGE, and :SIMPLE; the body also accepts undocumented alias :POP-UP. In :NOTIFY-WITH-MESSAGE, the selected format has one substitution labeled as the sender but supplies the trimmed message body instead. The strict profile therefore preserves the misleading notification. [C303-SRC] [C303-MAN]

Receiver

The NOTIFY server reads the request text after the seven-character contact prefix and compares it with one global LAST-NOTIFICATION string using STRING-EQUAL. If case-insensitively different, it stores the string, resolves the remote host, and calls TV:NOTIFY; if equal under that comparison, it suppresses the presentation and returns the duplicate string storage. Both branches answer Done. The guard compares only the immediately previous message text: it has no host or time field. Consequently consecutive A then a requests are duplicates even across different hosts, while A, B, A presents all three. The register begins NIL and changes only for a nonduplicate; suppression leaves it unchanged. No selected initializer resets it, so a reset extension MUST be labelled rather than folded into strict source behavior. [C303-SRC]

One host

With an explicit message, CHAOS:NOTIFY calls the simple request protocol using NOTIFY <message>. A string response is returned directly; a packet response is copied to a new string and the packet returned to its pool. There is no Converse record. [C303-SRC]

All Lisp Machines

With an explicit message, NOTIFY-ALL-LMS assures Chaos is enabled, opens one connection per parseable location-alist host, waits at most 300 ticks (five seconds) for every connection to leave RFC-sent state, then prints each host with its answer, timeout, or unexpected state. Host traversal and connection opening follow SI:MACHINE-LOCATION-ALIST order, but each returned connection is PUSHed onto CONNS. Waiting, reporting, and unwind cleanup therefore traverse the parseable connections in the reverse of source-host order. A host for which ADDRESS-PARSE returns NIL creates no connection, report row, or cleanup call. If reporting signals partway through, already printed reverse-order rows remain and unwind cleanup still removes every collected connection in that same reverse order. [C303-SRC]

The omitted-message source path is defective as specified in the prompt-surface section. A safety-corrected implementation may default NOTIFY-GET-MESSAGE's stream to *STANDARD-INPUT*, but MUST expose that it is not strict C303-CONVERSE.

Exhaustive effective-tree procedure

T-C303-PARENT-COMPOSE MUST enumerate the complete character domain and mouse-array domain represented by D05, then compute lookup from the local top table. It MUST also enumerate every prefix path, every Help leaf, all nine completion names, all dynamic host-menu items and all 224N raw row/button/modifier tuples in the fixture, the QSend task context, the simple-reply context, the five Terminal-N argument classes, and both TV notification-window contexts. For each tuple it records source owner (Converse, D05 parent, TV/FQUERY, or unbound), stored target, resolved function status, numeric state, and result. Comparing only the eight local cells is insufficient.

T-C46-BODY and T-C46-QUERY perform the equivalent exhaustive class check for the early stream contexts. Each test includes an invalid/complement value so an implementation cannot pass by recognizing only the successful leaves.