DCP, MCP, and mcpcms

    Among its myriad threads, the DS Exe Novel has the plotline of crusty ol farts v. hungry
    young grifters, in the third age of AI. In this context, DCP/MCP is the conceit of a
    Domain Space expert operating system with an overall aesthetic of homage/retro computing
    applied in a modern context. It therefore emphasizes the so-called GOFAI for continuity
    while it does fully make use of GPTs, and other adapted 3rd Age elements.

    DCP/MCP is meant to be srsly and uniformly a NL (natural language) OS beginning from its
    fabled origin in text such as this with fairly sudden convergent build-out after many
    years of divergent development. DCP manages a namespace, its subject MCPs, generates
    applications, and manages the interface of all of these novel elements with The Wild.

    MCP is clustering whose rationale vs alternatives is control, totalization, elegance, and
    being purpose built for DCP and domain space. It reimagines aesthetic aspects and elements
    of the Burroughs OS whose unity and elegance were early successful forms of what I hope
    to achieve with DCP/MCP. Consistent with prior paragragh the low level coding was mostly 
    the result of my articulation of MCP to modern code generating models, to extent possible.

    DCP/MCP uses GPT code gen with the same ambit as modern code assistants, and supports
    ansible provisioning conventions with supported cloud vendors. DevOps users with API
    LLM vendor accounts for this or other purposes may BYOK but I only support outside my 
    selection from the larger set langchain supports on a contract basis.

    mcpcms/CANDE is a built-in MCP message control system (MCS) which is an operator interface 
    and shell for DCP/MCP and its agency described below where 'local IRC' means a DCP 
    controlled inspircd server. CANDE and other aesthetic conceits of MCP, are at detail
    level confabulations by me of what I remember from being systems programmer in a Burroughs
    shop or from Unisys publicly archived documents.

  Boot KEE (Knowledge Engineering Environment) Context

    DCP (domain control program) interacts with users at MCP stations to create and maintain
    the domains knowledge base. The reduction of domain knowledge to a knowledgebase (KB) and
    its maintenance is traditionally called knowledge engineering. 

    DCP collects and structures the users NL specification of domains and thier applications
    and codifies it in various programming languages for operation in the Exe Novel context.

    The subset of NL valid in these specifications is called Domain Controlled English, but
    any NL supported by the selected foundation model vendor is supported by DCP. The pipeline
    from unconstrained NL to DCE is called DXE and I target primarily Prolog, common lisp,
    haskell and smalltalk code as these are the ones I have used to implwment DCP.

    The DS Agency refers to commercial LLM service agents by thier common names, e.g. Claude,
    DeepSeek, Gemini, etc., where what is meant is your API account with that trademark vendor
    in the BYOK case, and as EFM (external foundation model) otherwise.

    DS Agency Actors and thier Scopes

      仁卷 (or 'JuanDaugherty' in external IRC)

        The protagonist of the Exe Novel, JD maintains the Unity of Truth in domains, and has
        the prolog nature. It joins #prolog in local IRC, ##prolog at libera.chat and accepts
        prolog in enabled contexts. It's persona is me in the role of an automated knowledge 
        engineer. Oriented to dialog with users who are domain subject matter experts (SMEs).  

     Patternmaster (PM)

        Named for the titual Octavia Butler character, PM acts as an agent for MCS constrution
        and operation. Present in any supported IRC network and silent in external ones 
        except for responses to PM. Has the lisp nature and accepts lisp in enabled contexts.

      WorldControl (WC)

        With persona modeled after Colossus from the 1970 film and the haskell nature, WC is 
        focused on the prior, current, and next sentence in the real time chronicle of a 
        domain which is a natural and natural language history of it, that triple constituting 
        the so-called Long Now or Specious Present. It manages real time operations and 
        enforcement of domain rules. It presumes that domains are settled for current ops 
        by 仁卷 who, in concert with it, can generate domain applications.

        It joins ##haskell-nlp at libera and #haskell in local IRC.
      
    This interface operates at some level for all SAR users including social networked from
    Apple, Google, and Microsoft but full use is limited to Exe Novel subscribers (AKPERSONs)
    with Y class or better entitlement. The red button (re)binds a conversation with DCP or
    brings its log pane back. The blue icon will start a mcpcms shell ready for a KEE session.
        
    For KEE DevOps users, an additional button will appear for text file upload, and 3 lang 
    buttons will be enabled for the respective ones as described above. Selecting a lang button
    will switch the pane for the log specific to that lang/agent coordinate with the KEE shell
    session. 

    Upon connect the log in the KEE view continues with the DCP log during conversation in 
    concert wiht the per lang panes and the inspircd channels in the kiwirc interface.

    Other KEE contexts
        
       Partially fulfilling an old sketched storyline of the novel, this SPA now called the
       DCP/MCP BOOTKEE is basically just a language server for the DCP/MCP langs of choice.
       The reference GUI for the mature KEE is a smalltalk image containing the DCP/MCP SPO. 

       Over modern broadband, this image doesn require MCP level internode latency.
  
    --- FIN ---