RawringTwenties: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
<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="position:relative;left:30px;top:5px;"> 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></span></p> 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> | 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="position:relative;left:30px;top:5px;"> 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></span></p> All AKPersons have access to C-六/DCMS and FOSS projects not on github at minimum entitlement. Development of a bespoke app, or developer use of the KEE, requires devops entitlement. 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> | ||
</blockquote ></td><td width=1%></td></tr></table> | </blockquote ></td><td width=1%></td></tr></table> | ||