Redvant: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
← Older edit
No edit summary
 
(145 intermediate revisions by the same user not shown)
Line 1: Line 1:
<html><style> .mw-headline {color: black !important;}</style></html>
<div class="nomobile">
<div style="font-weight: 600;background-color: #fbfcf8; color: black;">
<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>
<blockquote><br>
<html><style> .mw-headline {color: gold !important;}</style></html>
{{TOCleft}}
<div style="position:relative;top:-15px;font-weight: 600;background-color: #fbfcf8; color: black;">
= Purpose =
<blockquote>
 
__NOTOC__
The primary purpose of the <b>Redvant</b> moniker is to name the separation of some product lines from their domain space aspects. Products developed under its rubric can be compiled for operation strictly on the basis of the FOSS or COTS software upon which they are based without any integration with DS though in some cases this can gut the app if presentation of as DS feature was it's original purpose. A non-DS application can then supply a new purpose. My <b>tl;dr</b> line and other apps sold on stores may thus have core function repurposed to such new apps without committing to DS ops.
<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;
However this separation is only in evidence at the time of it's application in such non DS development activity. Redvant exposition is largely or entirely in terms of its use in domain space and does not further comment on this separability .
<br>
 
= Pr&eacute;cis =
= Pr&eacute;cis =
<span class=plainlinks>
<span class=plainlinks>
'''Redvant''' , or ''''dcms<'''' (dcms-bra), is a collective term for software including react and [https://haskell-servant.readthedocs.io/en/stable/ <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.  
'''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.  
<br><div style="position: relative;left: 50px;">
<div style="position: relative;left: 50px;"><br>
"red" could be
<span style="position:relative;left:-30px;top:-5px;">"red" could be</span>
<blockquote>
<blockquote>
  react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, riding hood, Malcom X, Simply, etc..
  react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, lil riding hood, Malcom X, Simply, etc..
</blockquote>  
</blockquote> <br>
and "vant" is just from haskell-servant.
and "vant" could be similarly zweideutige. Thing with a node red face and haskell servant backside is another.
</div><br><span class=plainlinks>
</div>
Use of Apache [https://isis.apache.org <font color=lime>ISIS</font>] or other fat DDD pkg is intended later in our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer the java basing of ISIS or an ERP core and this is anticipated for later development.
<blockquote style="position:relative;left:150px;">
</span>
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.
= Requirements =
 
At this time, this &sect; is the sole exposition besides the code of any forks of constituent 3rd party packages in my public github or my original ones in my private git repo.
 
For pragmatic reasons, it is accounting oriented and doesn't address the full actual scope of use as implied by &sect; 2.2 below, which could be confusing.
 
Later, there will coverage in the Docs DCMS volume.
 
== Scope ==
 
Redvant carries our use of react and related node based stuff generally but here is discussed for the core purpose of transacting and accounting in domain space systems and apps. The transctional UI is actually django templating which could also be confusing.
 
As such it is deeply integrated with DCMS, DCP, etc. but these interfaces shall not be required in the product and its operation without them is a design requirement.
 
== Design by Doing ==
<span class=plainlinks>
The model use cases are the [https://ac.ai-integration.biz Web KEE SPA] and the [https://doorbell.meansofproduction.biz/?TCOLL=1 Ft doorbell], as well as GT2 2.1 and later and the tl:dr product line, in sofar as their front and middle are concerned.
</span>
 
== Transacting ==
==== django-oscar ====
 
<blockquote class=plainlinks>
I chose this back end pkg because of its claim of being domain driven. That claim, as it turns out is based on dynamic class loading. So without quibbling and as its sole focus on txing is convenient it turns out to be an early anchor in my DDD praxis.
 
Provides front end for tx'ing objects. We introduce the notion of an ephemeral tx ledger, oriented to a single, possibly complex tx which is connected to the others (&sect; 2.4.1.1). Like 'ledger', transaction 'tx' is defined to be an abstract change to a ledger. The process of application of a real instance of such change to persistent ledgers is called settlement.
 
Consequently, any transaction requirements are realized as constraints on the [https://django-oscar.readthedocs.io/en/3.1/ref/apps/index.html 16 Oscar Apps] or new classes in its framework.  
</blockquote>
</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 IV,VI,VII and VIII. The link under the article title is the storyboard domain. In practice, the storied Redvant tool chain 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.


== Accounting ==
<div style="font-weight: 600;background-color: #fbfcf8; color: black;">
<blockquote>
=== Design Principles ===
<blockquote>
 
==== Abstraction and Unity ====
<blockquote>
#Ledgers are abstract entities realized differently in different packages but from the perspective of a single accounting ontology.
#Unless qualified, 'ledger' means double entry accounting ledger, a fundamental concept conserved across all ledger implementations, the basis of their unification.
</blockquote>
 
==== Security and Transparency ====
<blockquote>
This is a requirement that requires a balancing of interests as transparency can conflict with security. Users. i.e. individuals and groups (including firms) may opt
for near complete opacity of their accounts which has been the general norm. The System, domain space, however is required to have open books and line items
against its books are why it's not complete opacity.
</blockquote>
</blockquote>
 
=== Back End Packages ===
<blockquote><blockquote>
The pkgs that provide the functional detail in different use cases generally repeat and duplicate functions. By virtue of &sect; 2.4.1.1.2 however, and system ops that implement it, they all operate against common ledgers. When function is duplicated, there is generally only one package that is contextually supported. For example, SQL/SMB has transaction interfaces but these are not used as django-oscar is selected for that and SQL/SMB is used as a back office system only.
</blockquote></blockquote>
<blockquote>
==== hledger ====
 
The users personal ledger. It may be convenient for the group administrators personal ledger to be used as the group ledger and this is the assumed default. hledger-web is not duplicated, nonetheless because of its accounting function and system integration, it is deemed a part of 'redvant'.
 
==== ledger ====
 
Basis of the System Journal, how the system views all ledgers. AKA ledger-cli, ledger c++, the original that was ported to hledger.
 
==== SQL-Ledger / LedgerSMB ====
 
The enterprise Chart of Accounts (COA), typical of an ERP pkgs ledger. Individuals don't normally view this package and its interface is mod perl based.
Every O class user has its own COA.
The System COA is visible to all AKPERSONs.


== 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>
</blockquote>
</blockquote>
</div>


= Sonstiges =
== History ==
=== Commonalities ===
<html><blockquote><span class=plainlinks><p>
<blockquote>
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.
The [https://devops1.sameboat.network/sb-app <span style="color: pink;">same boat small form factor</span>] common reusable base with ...
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.
#DS SSO, messaging, and DCMS API setup for product families.
<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.
#Videotelephony, defaults to Jitsi.
</blockquote></html>
</blockquote>
<html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=REDVANT></html>
 
=== Deliverables ===
<blockquote>
*[[tl;dr|<span style="color: pink;">tl;dr</span>]] product line engineering [https://desktop.thoughtcrime.biz <span style="color: lime;">cases</span>] for [https://play.google.com/store/apps/details?id=org.commoditysoftware.greentravel <span style="color: pink;">GT2</span>], [https://tl-drak.meansofproduction.biz/products/tl-drtask <span style="color: pink;">TASKPM</span>], and [https://yas3fs.ai-integration.biz <span style="color: pink;">YAS3FS].
*stable production level  [https://doorbell.meansofproduction.biz <span style="color: pink;">Ft</span>] and [https://ac.ai-integration.biz <span style="color: pink;">AC</span>] SPAs
<br><br>
</blockquote>  
</blockquote>
</div>
</div>
Retrieved from "https://eg.meansofproduction.biz/eg/index.php/Redvant"