Interacting with the DCP

( domain control program )
As referenced here, DCP is an aspect of system software that attempts conversational support for the construction and operation of domain spaces. ¹ DCP provides discursive assistance to the three main classes of domain agents, consumers, developers and operators all of whom are first class AKPERSONs. For other users it provides guided navigation to static help text . For all users it communicates system level messages. Agents with less than token tx-authentication are not differentiated other than as possibly distinct individuals at a station or device.
What is a Domain?
There are two distinct but related senses in which this word is relevant here. Firstly, it refers to a so-called domain of discourse, what some thing is broadly about. Secondly, it refers to the name system of the internet and what are called domain names. DCP connects these two senses by providing knowledge engineering support for the first and operations beyond the base OS (MCP) level for the second.

Paths to the DCP and DCE (domain controlled english)

From the wild, there are desktop, tablet, and smart phone landings on the single page interface4 which the help link in sameboats, a tab in the commons app, as well as the default front page for logged in sameboat users link or embed some form. DCP doesn't attempt discourse with small form factor devices, providing console support only. Use tablet or desktop.

Domain Space KEE 1.0


Content suppressed in the wild

Groups AI

DCP works with group admins to construct group IT infrastructure and build knowledge structures for the group which can range from simple taxonomies for flat data processing to ontology baseing for full knowledge engineering.

In particular, the DCP actively participates in the construction of Sameboat Portable Groups, their taxonomies, knowledge bases (KB), and supporting computing elements.


If you are logged in you can select a path from the prior heading for maintained context across your different devices. DCP will not discuss existing private domains (or groups) with anonymous users unless a responsible AKPERSON has authorized it. ³

When will the DCP be in a production state?

Never, although it might become relatively unchanging outside the subject KBs at times. First, I don't intend any particular implementation of the cog arch to be fixed so long as it's a pure software system. Second on several levels this is a system of continuous learning and improvement. It would not be appropriate for it to be considered to be anything other than development unstable, in analogy to a living being rather than a dead codeset.

The opposite is the case for the KBs² it produces. These will move thru normal cycles of change and stability and we are committed to forward compatibility with any future DCP, subject to a possible required migration procedure, of archived knowlegebases.

Even KBs should be thought of as product lines subject to change and growth as a rule with at most forward compatibility albeit with conserved cores, again by analogy to a living intelligence.
¹ Traditionally, a real time Expert System, other terms such as Knowledge Representation and Reasoning System are appropriate and a mix of different paradigms is used.
² As files in standard formats such as RDF. These may be worked in other tool frameworks and are supported relative to a well defined platform (i.e. a LSB, compilers and libs release manifest, DCP version)
³ The buttons with lang logos or Chinese labels are for dev ops use , normal users will only use the pink Say and red Abort conversation buttons and all buttons are removed when DCP connect is initiated and reappear when fully connected. Note that while all buttons are enabled for all first class users, full use of the KEE presumes a knowledge engineering user.
4 The ancient AutoConsult interface with skin level legacy elements. The IRC pane provides basic text chat with IRC and other text networks and can be used with the video services.