RawringTwenties: Difference between revisions
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
<tr><td valign=top style="font-size: 10px;font-weight: 600;width: 67%;color: white; background-color: black; margin: 5px; text-indent: 5px;"> | <tr><td valign=top style="font-size: 10px;font-weight: 600;width: 67%;color: white; background-color: black; margin: 5px; text-indent: 5px;"> | ||
<blockquote style="text-align: justify;"> | <blockquote style="text-align: justify;"> | ||
MCP/DCP is the central project to be finalized at the end of this period. By 2022 a base cognitive and implementation architecture were established. While every 3rd party package I use in its construction is made available here in the form I've found it, I don't intend to release | MCP/DCP is the central project to be finalized at the end of this period. By 2022 a base cognitive and implementation architecture were established. While every 3rd party package I use in its construction is made available here in the form I've found it, I don't intend to release for the DCP in this decade. Everything else (including MCP) is maintained in open source form and can be the basis of various development opportunities. Open source here (as opposed to my github) means available at some level of entitlement either simple capitation (AKPERSON) or devops levels.<br> | ||
Source code of C-六, GT2, YAS3, and all supporting code for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are 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 4719/20 with change limited to utilization of our or or 3rd party new infrastructure. | Source code of C-六, GT2, YAS3, and all supporting code for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are 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 4719/20 with change limited to utilization of our or or 3rd party new infrastructure. | ||
Revision as of 14:43, 25 January 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™ and sameboat current ones for conversational agent, videoconf, and consumer, group networking, product lines, respectively.
Redvant(is)/dcms< (dcms-bra), and dcms> (dcms-ket), designate stack layers.
MCP/DCP is the central project to be finalized at the end of this period. By 2022 a base cognitive and implementation architecture were established. While every 3rd party package I use in its construction is made available here in the form I've found it, I don't intend to release for the DCP in this decade. Everything else (including MCP) is maintained in open source form and can be the basis of various development opportunities. Open source here (as opposed to my github) means available at some level of entitlement either simple capitation (AKPERSON) or devops levels.
Source code of C-六, GT2, YAS3, and all supporting code for the tl;dr product line is available at the minimum entitlement level, actually known (tx-authenticated or invited). At least one developer entitlement for bespoke app support, including any use of the OS/KEE are 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 4719/20 with change limited to utilization of our or or 3rd party new infrastructure.
For the value of the interaction, I remain open to joining a group, optionally deferring my projects for an agreed period, or in joint development agreements. Moving from seriality in the reserve army of labor/FOSS commons to fusion with a smaller group has a presumed low but unknown expected value in this period. 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.
¹ Mainly Burroughs, with a nod to VM/CMS.
