MCP

A timeline of "MCP" in my life course.

MCP 4 Era

The first referent of the acronym is the operating system of the same name, which was at release 19 in 2019.

I was the systems programmer at Daytona Beach Community, now Daytona State college which was then a Burroughs shop as my second multi-year job out of college.

4715 Story

In a my domain space concept, it is the designation for nodes of a Domain Control Program (DCP).

«MCP» is the operating system abstraction on a single node of a cluster, or cloud of computers with fast interconnectivity, miniminally 1 gigabit per second. The MCPs operate as the nodes of the larger OS construct, the DCP. MCP itself has these components/layers:

• The top level which is a lisp image running a generic blackboard model of realtime operations control and knowledge base management.
• The workflow level which is implemented by the Work Flow Language, another Burroughs inspiration, reimagined as a context for literate programming and revival of the job control concept based on an adaptation of WFL to the DCP context.
• A base layer close to machine level using the c++ actor framework and optionally a custom debian kernel.
  

4716-18

α/β period:

In this period the elements of the DCP are prototyped, marshalled, deployed then productized:

1. Get working build of all packages in same form they will ultimately be used in the product.
2. Get working build of newly created elements such as the DGUI/SPO and WFL.
3. Apply the above to the proto domains.
4. Workout in service of the proto domains.
5. Do productization/packaging for mass deployment

CP 4721 roughly corresponds to what is produced by 1 and 2 and the AKDOMHST/SVC SKUs to 5.

Sometime between milestone 2 and 4, a MCP shell service will be made available to authenticated users.

CP 4721

Blank for formatting purpose.

See also

• Current docs

Footnote