Systema: Manipulating Relationships

In the last post we looked at entity manipulations. Now let’s look at the next row in the Six Hats Six Coats Framework:

Relationships are all about communication and are subject to the same manipulations as a communication link. We also established earlier that there are six relationship types:

So how do we manipulate these relationships?

The first relationship manipulation is the SELECT:

The SELECT manipulation “snoops” or “eavesdrops” on the relationship between two instances. The relationship is untouched.

The second manipulation is the INSERT:

The INSERT manipulation “throws” or “interjects” into the relationship between two instances. Extra data is added to the relationship, but the original is untouched.

Next is the UPDATE manipulation:

The UPDATE manipulation “spoofs” or “imitates” the relationship between two instances. The original data is changed in value.

Finally we have the DELETE manipulation:

The DELETE manipulation “crashes” or “denies service” between two instances. The original data is completely corrupted or the relationship broken.

And there you have relationship manipulation in a nutshell.

Systema: Manipulating Entities

The Six Hats Six Coats Framework’s first row deals with entities.

Let’s remind ourselves more visually:

In an earlier post I laid out the rows and columns for an entity security table. I’ve now abstractly filled in the cells and will share it with you:

Forgive me for coining new terms to make a consistent vocabulary.

How can these security breaches be described? First, the SELECT manipulation recognizes the instance it is dealing with. Second, the INSERT manipulation adds instances. Third, the UPDATE manipulation corrupts the original instance. Fourth, the DELETE manipulation destroys the instance. Realize that an instance can be a physical goal, a physical person, a physical function, a physical datum, a physical event or a physical node.