Help: This page shows how the referencing vocabulary definitions are maintained and interlinked for controlled consistency of documentation. Click on the hyperlinks to see how the terms are defined within the Askemos architecture. moreā€¦ Tip: Remember the back-button!

This page has three main sections. (Note that the listings could be empty.)

  1. The first item displays a term, URL, text or picture.
  2. Followed by a (still unordered) listing of statements about this subject. (for details follow ">"-link)
  3. Separated by a horizontal rule a "reverse" listing of statements referring to this item in object position.
703 container member >

Currently there are two implementations of the Askemos structure at

What we Pick from prior work

Askemos core structure is influenced by Erlang/OTP. This buys us proven concept, the "actor model", to create distributed systems which need to graceful degrade when the network is partitioned. From L3 we take the idea that processes can be persistent even over a system reboot. From functional programming we take immutable data and store this in immutable "booked memory" (a.k.a. "blockchains sans native crypto currency" these days - though these are not a prior work to Askemos). From Scheme we take a minimal initial language which we use to update shared state in booked memory. From state machines replication we take the concept byzantine consensus about shared facts. Finally we recognize the concepts "privity and privacy" and conclude to distribute shared facts precisely to parties relevant to the fact and possibly witnesses deliberately chooses by those parties.

Preview of here

693 is a > service
694 is a > sequence see also
Askemos relation