RawringTwenties

From Cibernética Americana
Revision as of 06:06, 2 July 2023 by Root (talk | contribs)

70s CE (2020s Era Vulgaris)

DOPE, [1]   GOFAI,  &  工 王

As a member of your species, sharing the thrill of reaching the milestone of scientific situational awareness ( it's a process ).

As a sole trader, I operate in select jurisdictions, will sell to any at my discretion.

As Equity Class Founder, moving via 工 王 from seriality in to fusion with the reserve army of labor/FOSS commons.

By 73 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.
  The Sistine Chapel took 5 years, static content & Don Knuth started TAOCP in 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]


Impressum

  1. tl;dr[λ]™ — GT2 (android iOS), TASKPM, [5] YAS3 [6]
  2. .dom — Domain Space (DS) [7]
  3. C-六 — Domains CMS
  4. MCP/DCP — OS concept with homage [8]


In chrono order of completion; GT2 goes back to '11m 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]


  1. Domain Operations and Planning Expert.
  2. Our Knowledge Engineering Environment
  3. Sources of C-六 and the tl;dr products are available per entitlement.
  4. 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.
  5. Bindings for MS Project, task/timewarrior, etc.
  6. FUSE client and manager for MCP
  7. 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.
  8. Mainly Burroughs, VM/CMS from IBM. MCP the base OS, DCP the cog arch.
  9. Redvant(is)/dcms< (dcms-bra), and dcms> (dcms-ket), designate stack layers.