Zipchain details
|
A zip-transaction is an event involving a congruent change (i.e., a synchronized change by the same value with the reverse sign) in a pair of parameters of two model mfaces, including a change in a pair of parameters of one and the same mface.
On correct terminology practically applied
For the mutual mapping concept a special terminology is used.
However, since dia$par is intended for a wide range of business users, this terminology comprises well known notions like "documents", "results", "reports", etc.
Since the mfaces — i.e. hyperplane projections of a complete model — have an internal structure of a theoretically unlimited complexity, a pairwise change in two mfaces can produce (and normally does) a multitude of zip-transactions.
As we ascend to the next level of the abstraction, changes between mfaces in turn are caused by an event involving the emergence of a specific mpack instance in a particular mstep of a specific mchain.
Note that the logic behind the generation of transactions can be heavily dependent on the state of the random parameter from the repertoire of the complete model.
Start of a broad licensing of zipchain (tentatively) is scheduled for February 2021.
There's no fees, the only licensee's counterparty obligation is a guarantee of software compatibility with the Cyberspace infrastructure.
The resulting zipper of successively linked zip-transactions is an equivalent of machine code (the product of a compiler — the dia$par.Mirror mmizer), while high-level descriptions of business objects in the logic of the cybernetic model (the product of a dia$par.Matrix application developer) are an equivalent of business-specific object-oriented programming.
Note that while a blockchain application developer tasked with formulating the business logic has access (at best) to scant meta data of the previous transaction, whereas an ERP developer can use fundamentally incomplete information within the scope of a given "module", a dia$par application developer can access at all times a bottomless data container storing complete knowledge about the state of the managed enterprise at any random point along timescale.
The analogy with machine code should not be misleading in the sense that the final chain of zip-transactions exists in the form of physical entries in a file (similarly to the primitive general ledgers in common ERP systems).
On the contrary, the endless ray of the zipper of zip-transactions reflecting the complete history of the evolution of dia$par mfaces is also merely one of the possible projections of the cybernetic model.
Which is built by low-level tools of the mmizer using the analytical approach.
Therefore, zipchain transactions do not exist in the physical world at all — unlike the distributed database of a blockchain.
Meanwhile, that which does not exist physically cannot be stolen or corrupted.
