RawringTwenties: Difference between revisions
No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
<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;"><p style="position:relative;top:-5px;"> | <blockquote style="text-align: justify;"><p style="position:relative;top:-5px;"> | ||
By 4720 cog and machine arch conceptual design was settled. Then, a RAD Urknall of a working baseline of that as driven by the sameboat and tl:dr lines.<br> <span style="font-size:10px;position:relative;left:5px;top:5px;color: | By 4720 cog and machine arch conceptual design was settled. Then, a RAD Urknall of a working baseline of that as driven by the sameboat and tl:dr lines.<br> <span style="font-size:10px;position:relative;left:5px;top:5px;color:lightsalmon;"> Michelangelo spent 5 years on the Sistine Chapel, static content and Don Knuth has been working TAOCP since 1962.</span></p> All AKPersons have access to C-六/DCMS and FOSS projects not on github at S class entitlement. Development of a bespoke app, or developer use of the KEE<ref>Our Knowledge Engineering Environment</ref>, requires devops entitlement. GT2 originating in the early teens will, with the rest of the tl:dr line have completions early in this period as drivers for DCP/MCP with change limited to maintenance after product baselines achieved.<ref>Sources of C-六 and the tl;dr products are available per entitlement.</ref><ref>Mechanism vs. content: DCP will remain binary dist, while it's knowledge bases will be in standard file formats. Even documentation will be deferred past the first cohort of knowledge engineers other than myself. Everything else (including MCP) is maintained here in source form and can be the basis of various development opportunities.</ref></blockquote ></td><td width=1%></td></tr></table><br> | ||
<span style="position:relative;left:7px;text-align:center;" class=plainlinks>[https://meansofproduction.biz/rawr <span style="color: lime;">Impressum</span>]</span><br><br> | <span style="position:relative;left:7px;text-align:center;" class=plainlinks>[https://meansofproduction.biz/rawr <span style="color: lime;">Impressum</span>]</span><br><br> | ||
<ol style="position:relative;left:-7px;list-style-type: cjk-ideographic;"> | <ol style="position:relative;left:-7px;list-style-type: cjk-ideographic;"> | ||
Revision as of 13:21, 31 January 2023
4720-30 (2022-2032 Era Vulgaris)
As a member of your species, sharing the thrill of reaching the milestone of scientific situational awareness ( it's a process ).
As sole trader, will only operate in certain jurisdictions, but will sell to any.
As Equity Class Founder, moving via 工 王 from seriality in to fusion with the reserve army of labor/FOSS commons.
By 4720 cog and machine arch conceptual design was settled. Then, 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 and Don Knuth has been working TAOCP since 1962.All AKPersons have access to C-六/DCMS and FOSS projects not on github at S class entitlement. Development of a bespoke app, or developer use of the KEE[2], requires devops entitlement. GT2 originating in the early teens will, with the rest of the tl:dr line have completions early in this period as drivers for DCP/MCP with change limited to maintenance after product baselines achieved.[3][4]
- .dom — Domain Space (DS) [5]
- tl;dr[λ]™ — GT2 (android iOS), TASKPM, [6] YAS3 [7]
- C-六 — Domains CMS
- MCP/DCP — OS concept with homage [8]
In chrono order of completion; DCP/MCP perennial, DCMS follows it, others maintenance after mature baseline ...
修身 — Zero-th precedence. Failing it moots projects, if it succeeds failure in them tolerable / temporary.
AutoConsult, doorbell/Ft: legacy labels, tl;dr™, sameboat current ones for agent, videoteleophony, consumer and group networking product lines, respectively. [9]
- ↑ Domain Operations and Planning Expert.
- ↑ Our Knowledge Engineering Environment
- ↑ Sources of C-六 and the tl;dr products are available per entitlement.
- ↑ Mechanism vs. content: DCP will remain binary dist, while it's knowledge bases will be in standard file formats. Even documentation will be deferred past the first cohort of knowledge engineers other than myself. Everything else (including MCP) is maintained here in source form and can be the basis of various development opportunities.
- ↑ 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.
- ↑ Bindings for MS Project, task/timewarrior, etc.
- ↑ S3 client and manager for MCP
- ↑ 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.
