RawringTwenties: Difference between revisions
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
</td><td width=2%></td><td valign=top style="font-size: 10px;font-weight: 600;width: 63%;color: white; background-color: black; margin: 5px; text-indent: 5px;"> | </td><td width=2%></td><td valign=top style="font-size: 10px;font-weight: 600;width: 63%;color: white; background-color: black; margin: 5px; text-indent: 5px;"> | ||
<blockquote style="text-align: justify;"> | <blockquote style="text-align: justify;"> | ||
DCP/MCP will reach maturity by the end of this period. By 2022 a cog and implementation arch were established. While 3rd party packages not currently maintained elsewhere are made available, I don't intend to publish sources for the DCP , possibly ever, mainly for security. Even documentation will be deferred past for the first KE cohort. Everything else (including MCP) is maintained in open source form and can be the basis of various development opportunities. <br> | DCP/MCP will reach maturity by the end of this period. By 2022 a cog and implementation arch were established. While 3rd party packages not currently maintained elsewhere are made available, I don't intend to publish sources for the DCP , possibly ever, mainly for security. Even documentation will be deferred past for the first KE cohort. Everything else (including MCP) is maintained in open source form and can be the basis of various development opportunities. <br> <br> | ||
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. | 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. | ||
</blockquote ></td><td width=4%></td></tr><tr><td colspan=2 style="background-color: black;"><blockquote><hr>¹ <font size=1>Mainly Burroughs, VM/CMS from IBM. </font></blockquote></td> | </blockquote ></td><td width=4%></td></tr><tr><td colspan=2 style="background-color: black;"><blockquote><hr>¹ <font size=1>Mainly Burroughs, VM/CMS from IBM. </font></blockquote></td> | ||
Revision as of 08:56, 22 March 2022
4720-30 Agenda (2022-2032 Era Vulgaris)
Personal 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
- .dom — my TLD AKA Domain Space
- GT2 personal carbon accounting domain (android iOS)
- C-六 — php/python Domain CMS
- TASKPM tl;dr™ — taskwarrior, MS Project, etc. for DS users
- YAS3 — yet another S3 client
- MCP/DCP — intelligent OS with mannerisms in homage to mainframes¹
chrono order of completionAutoConsult, 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 a cog and implementation arch were established. While 3rd party packages not currently maintained elsewhere are made available, I don't intend to publish sources for the DCP , possibly ever, mainly for security. Even documentation will be deferred past for 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.
