From Cibernética Americana
Revision as of 12:41, 27 May 2022 by Root (talk | contribs)

4720-30 Agenda (2022-2032 Era Vulgaris)

Self improvement takes precedence. Failing that success in projects moot, if it succeeds failures in them are tolerable / temporary.

     Domain engineering,   mecha intelligence,  and   sovereign praxis

  1. .dom — my TLD AKA Domain Space
  2. GT2 personal carbon accounting domain (android iOS)
  3. C-六 — php/python Domain CMS
  4. TASKPM tl;dr™ — taskwarrior, MS Project, etc. for DS users
  5. YAS3 — yet another S3 client
  6. MCP/DCP — intelligent OS with mannerisms in homage to mainframes¹

Chrono order of completion; .dom and DCP/MCP perennial, others in variously lower activity maintenance fairly early in this period.


AutoConsult, doorbell/Ft: legacy labels, tl;dr™, sameboat current ones for agent, videoteleophony, consumer and group networking product lines, respectively.
Redvant(is)/dcms< (dcms-bra), and dcms> (dcms-ket), designate stack layers.

As Founder of domain space, I am the paramount member of the Equity Class. Moving from seriality in the reserve army of labor/FOSS commons to fusion may occur in that group domain.

As a sole trader, I am bound by whatever stipulations various local jurisdictions make for same and will disable access from those where I cannot meet their requirements as they become known.

DCP/MCP will reach maturity by the end of this period. By 2022 cog and machine arch conceptual design debt was cleared setting up for a RAD Urknall. While 3rd party packages not currently maintained elsewhere are made available, I don't intend to publish complete sources for the central DCP, possibly ever, in part for security. Here the distinction between mechanism and content is significant, those portions of the DCP which are the culmination of the machine arch will be available early on. Even documentation will be deferred past the first KE cohort. Everything else (including MCP) is maintained in open source form and can be the basis of various development opportunities.

Sources of C-六, GT2, YAS3, and the tl;dr product line are available at the token entitlement level, and only MCP, YAS3 and TASKPM will require that. Social networked without entitlements have access to all other published sources. Development of a bespoke app, or developer use of the KEE, a developer entitlement is required. GT2 and YAS3 are completions for projects from the prior decade which have become presentation vehicles for bespoke apps/services using various supports but themselves are basically feature static after 4720/21 with change limited to utilization of our or 3rd party infrastructure changes.

¹ Mainly Burroughs, VM/CMS from IBM.