state of the world

Nicoletta,

 

As promised:

 

In the diagram below, in yellow is a state machine that transitions from T0 to T1 when a valid triple {actor, action, asset} is received by the evaluator. The rest of the boxes represent what is required to complete the scenario, the “evaluator” in purple is the clank.

 

As I explained during the call, the agreement is not part of the SoW, but it is required to bind the “state” with “how it transitions”.

 

So when triggered, the evaluator:
finds out what constraints and/or refinements it has to calculate based on the received triple,
“gets” those values out of the current state of the world,
performs the evaluation and for those  values that require it “sets” them and changes to the new state
 

In this simple example, there is 1 constraint, and:
if there is no match for the triple, activated = false, otherwise activated = true.  If activated = false, status = “unknown” (in ‘zero trust’ and being Boolean, should be “false”). State remains “current” (T0).
When activated = true then: if var < limit the status/result is true, else when var >= limit, then the status/result is false. State moves to T1.
 

Time flows from top to bottom.

 

 

This is a simplified view, as I explained during the call the process works as per the pseudocode in GitHub.

 

Regards,

___________________________________

Joshua Cornejo

marketdata

smart authorisation management for the AI-era