anchor.diff:    5. Producing the corresponding FTYPE declaration and the intrinsic
        DEFUN form for evaluation, in the macroexpansion.
   
  -  It is expected that this generalized application pattern will be
  -  retained, across the DEFUN* redesign.
  +  It is expected that this generalized application pattern will have
  +  been retained, across the DEFUN* redesign.
   
     While DEFUN* may provide a manner of convenience, for definitions of
     strongly typed, named functions in the null lexical environment, the
  
positive.code:   discrete concerns.
  
    - It should be portable, in its implementation, for supporting a
      similar semantics for definition of a similar, portable. strongly
      typed "Wrapper Macro" for LABELS forms
  
    - A portable implementation of DEFUN* should also be reusable for
      implementation of a methodology for strong typing of arbitrary
      anononymous lambda functions, _vis a vis_ the LAMBDA* macro as
      defined in this source system. It may be assumed that an FTYPE
      declaration may be usable for forms similar to
        (funcall (the <FTYPE> <FN>) <ARGS...>)
      in some Common Lisp implementations.
  
    - A portable definition of DEFUN* may furthermore be reusable for
  
negative.code:     accessors and funcallable standard objects, _vis a vis_ extensions
      onto CLOS and MOP.
  
    In its original implementation, DEFUN* produced a small number of
    ephemeral CONS objects, namely as pursuant of the construction of an
    effective, declared types table for lambda list parameters, and
    otherwise as for storage of lambda list parameter names, pursuant to
    producing an FTYPE form of the lambda list provided to DEFUN*. It was
    subsequently redesigned to use, in a manner, _callback functions_
    with discrete function signatures, in lieu of arbitrary list
    construction in the parser functions, themselves.
  
  
    During the redesign of the the DEFUN* implementation, a generalized
    approach was developed as follows:
  
    1. Move and optionally rename the set of lexically scoped functions,
    such as to be defined at the lexical _top level_, in the defining
  