RawringTwenties: Difference between revisions
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
<td width=1%></td><td valign=top style="font-family: UWS;font-size: 14px;font-weight: 600;width: 65%;color: white; background-color: black; margin: 5px; text-indent: 5px;"> | <td width=1%></td><td valign=top style="font-family: UWS;font-size: 14px;font-weight: 600;width: 65%;color: white; background-color: black; margin: 5px; text-indent: 5px;"> | ||
<blockquote style="text-align: justify;"> | <blockquote style="text-align: justify;"> | ||
By 4719/20 cog and machine arch conceptual design was settled. Next comes a RAD Urknall of a working baseline of that as driven by the sameboat and tl:dr lines. Michelangelo spent 5 years on the Sistine Chapel, static content.<ref> 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.</ref> DCP/MCP will reach maturity by the end of this period. | By 4719/20 cog and machine arch conceptual design was settled. Next comes a RAD Urknall of a working baseline of that as driven by the sameboat and tl:dr lines. Michelangelo spent 5 years on the Sistine Chapel, static content.<ref> 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.</ref> DCP/MCP will reach maturity by the end of this period.<br><br> GT2 and YAS3 had inception in the teens and will have completions early in this period as drivers for MCP/DCP with change limited to maintenance after product baselines achieved. | ||
<ref>Sources of GT2, YAS3, and the tl;dr product line are available at graded entitlement levels.</ref> Social networked without entitlement has access to C-六/DCMS and FOSS projects not on github. Development of a bespoke app, or developer use of the KEE, requires a devops account. | <ref>Sources of GT2, YAS3, and the tl;dr product line are available at graded entitlement levels.</ref> Social networked without entitlement has access to C-六/DCMS and FOSS projects not on github. Development of a bespoke app, or developer use of the KEE, requires a devops account. | ||
</blockquote ></td><td width=1%></td></tr> | </blockquote ></td><td width=1%></td></tr> | ||
<tr><td colspan=5 style="background-color: black;"><blockquote style="color:firebrick;font-size:8px;"><br><hr><references/></blockquote></td></tr></table> | <tr><td colspan=5 style="background-color: black;"><blockquote style="color:firebrick;font-size:8px;"><br><hr><references/></blockquote></td></tr></table> | ||
</div> | </div> | ||
Revision as of 21:53, 12 December 2022
4720-30 (2022-2032 Era Vulgaris)
修身 — Zero-th precedence. Failing it moots projects, if it succeeds failure in them tolerable / temporary.
In chrono order of completion; DCP/MCP perennial, others reach maintenance only fairly early in this period ...
- .dom — Domain Space (DS) [2]
- C-六 — Domains CMS
- GT2 carbon domain (android iOS)
- TASKPM tl;dr™ — Bindings for MS Project, task/timewarrior, etc.
- YAS3 — S3 client and manager for MCP
- MCP/DCP — OS concept with homage [3]
AutoConsult, doorbell/Ft: legacy labels, tl;dr™, sameboat current ones for agent, videoteleophony, consumer and group networking product lines, respectively. [4]
As a human being, I share with you the challenge of thriving in these thrilling times.
As a sole trader, I am bound by laws of local jurisdictions and will disable access from those where I cannot comply as they become known.
As Founder of the Equity Class I move from seriality to fusion via 工 王 with the reserve army of labor/FOSS commons.
By 4719/20 cog and machine arch conceptual design was settled. Next comes a RAD Urknall of a working baseline of that as driven by the sameboat and tl:dr lines. Michelangelo spent 5 years on the Sistine Chapel, static content.[5] DCP/MCP will reach maturity by the end of this period.
GT2 and YAS3 had inception in the teens and will have completions early in this period as drivers for MCP/DCP with change limited to maintenance after product baselines achieved. [6] Social networked without entitlement has access to C-六/DCMS and FOSS projects not on github. Development of a bespoke app, or developer use of the KEE, requires a devops account.
- ↑ Domain Operations and Planning Expert.
- ↑ The .dom TLD in operation for most of the prior decade, support for it deepening in this one. As far as routing the name, that's trivial and complete.
- ↑ Mainly Burroughs, VM/CMS from IBM. MCP the base OS, DCP the cog arch.
- ↑ Redvant(is)/dcms< (dcms-bra), and dcms> (dcms-ket), designate stack layers.
- ↑ 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 GT2, YAS3, and the tl;dr product line are available at graded entitlement levels.
