View source for Redvant

<div class="nomobile">
<h6 style="position:relative;top:-15px;"><span class=plainlinks><b>[https://redvant.ai-integration.biz <span style="color:lime;">redvant.ai-integration.biz</span>]</b></span></h6>
<html><style> .mw-headline {color: gold !important;}</style></html>
<div style="position:relative;top:-15px;font-weight: 600;background-color: #fbfcf8; color: black;">
<blockquote>
__NOTOC__
<br>
<html><img style="position:relative;left:-20px;float:left;" width=175 src=https://eg.meansofproduction.biz/eg/images/c/c7/KASTALIEN.svg></html>  &nbsp; &nbsp;
<br>
= Pr&eacute;cis =
<span class=plainlinks>
'''Redvant''' , or ''''<dcms'''' (dcms-bra), is a collective term for software including react and [https://servant.dev<font color=lime>servant</font>] within a DCP context and packaged as a reusable resource demonstrated in various applications such as the tl:dr and by the KEE. 
<div style="position: relative;left: 50px;"><br>
<span style="position:relative;left:-30px;top:-5px;">"red" could be</span>
<blockquote>
 react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, lil riding hood, Malcom X, Simply, etc..
</blockquote> <br>
and "vant" could be similarly zweideutige. Thing with a node red face and haskell servant backside is another.
</div>
<blockquote style="position:relative;left:150px;">
 Redvant is defined to be a production line that begins with wireframed mocks applied to domain models and emitting Android and iOS binaries via turnkey MCP cells worked by DevOps users.<br>
 I mean the remit to be no more precise than that, informally just workflows DCP manages in app generation and runs in a DS context.
</blockquote>
== Transparency ==
Redvant will remain opaque except as is clear from exposed working artifacts until several iterations of production use when some technical detail will be exposed in a &sect; fanout in the DCMS volume in Books. The link under the article title is the storyboard domain. In practice, the Redvant tool chain in storyboard will in general require some expertise and is unlikely to be workable by the average domain owner or popular group member, or even a single IT professional. This is compensated for by the fact that domains are defined by their DCE (Domain Controlled English) definitions in natural language form which are workable by domain owners or PG members.

<div style="font-weight: 600;background-color: #fbfcf8; color: black;">
== The hs aspect of DCMS ==
<span style="position:relative;top:-5px;left:10px;font-size:10px;">and DS app lang</span>
<blockquote style="position:relative;top:-10px;">
I mean Haskell to be the DS application lang and for DCP to semi-automatically generate apps for it. Central to this is  my implementation of the [[Specious Present]]. I have created #haskell-nlp.libera.chat for discussion about it.
<br><br>
Various services are integrated by DCP in the process of domain content definition and maintenance. De novo domains and the unification of CMSes mentioned in the next &para;. In general, where possible integration means operation of the received CMS as is at the code level via its LDAP integration and running under MCP. At the detail level this is mediated by domain for codegen of models, beam for abstraction of the rdbmses, and compdata.
<br><br>
Acknowledging <html><a href=https://wiki.haskell.org/Web/Content_Management>clckwrks, et al.</a></html> as suggestions for hs CMS, have taken a different route based on generalization and pass thru of the function of PHP and python CMSes such as WP, mediawiki, Cliu/D7, and django-cms. The design intent is for recovery of the function of contained CMSes as an abstracted and separately maintained bulk with their original and subsequent live code absorbed as is.
</blockquote>
</blockquote>
</div>

== History ==
<html><blockquote><span class=plainlinks><p>
In the original remit use of Apache </html>[https://isis.apache.org <font color=lime>causeway (formerly ISIS)</font>]<html> or other fat DDD pkg was intended later in fulfillment of our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer a java basing of ISIS or an ERP core and this is still an option for GC projects.
Next, Clafer, a package I first ran into in the telematics work in '14/15 was chosen as a basis for the, as then conceived line. <a href=https://clafer.org>Clafer</a> is essentially forked for this purpose here, its repos forked within 6 mo of the Sept. '23 update, which was the first activity on it in some time. It is an archived project at its source, which simplifies my use here in applying to the product line engineering of the DSAP derivatives.
<p>Although I mean to keep local clafer tools close to the original on the common code intersection, there will be some rebranding to Redvant instead of Clafer to make clear the diff between just clafer the domain modeling lang and its use here.
</blockquote></html>
<html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=REDVANT></html>
</div>