The Brain: ZenUniverse: Seven Senses


  1. GREEN: EYE: OCCIPITAL LOBE: visual center of the brain
  2. YELLOW: EAR: TEMPORAL LOBE: sensory center of hearing in the brain.
  3. SKY: NOSE: BRAINSTEM: control of reflexes and such essential internal mechanisms as respiration and heartbeat.
  4. BLUE: TONGUE: PARIETAL LOBE: Complex sensory information from the body is processed in the parietal lobe, which also controls the ability to understand language.
  5. RED:  JAW: FRONTAL LOBE: control of skilled motor activity, including speech, mood and the ability to think.
  6. ORANGE: BODY:  CEREBELLUM: regulation and coordination of complex voluntary muscular movement as well as the maintenance of posture and balance.
  7. GREY: SELF: CORPUS CALLOSUM: The arched bridge of nervous tissue that connects the two cerebral hemispheres, allowing communication between the right and left sides of the brain.


If you look at my first ZenUniverse post, you will see a six column model.  However, the System International Units require seven columns.

Here is a table of two hemisphere intersections.  I am using Latin roots, but you will recognize many of the terms:


Here is a blank table you can print out and experiment with correlations and intersections of your own:





The Brain: ZenUniverse 1.0


“Tao can Tao not Tao”

Lao Tzu

Since reading the work of Clare W. Graves of Spiral Dynamics fame, reflecting on the work of all the people mentioned in my Blogroll as well as my recent foray into Zen I attempted to review and revise my work on the assortment of frameworks I had come up with. As I was making revisions it dawned on me that nature had done all the work already.

“Outside this office, Business as Usual;

Inside this office, Thunder and Lightning.”

Colonel John Boyd

I decided to take another angle of attack.  I realized I was dealing with entities, hierarchies, attributes and relationships and one thing Boyd overlooked, results, in two dimensions not one.  You may remember this graphic:


I realized I would have to take the Boyd Pyramid a bit more seriously.  And I have.  I compared Boyd’s work to Einstein’s, saw the correlations and what I think is a flaw.


“The only real valuable thing is intuition.”

Albert Einstein


The first thing I want to address is a misconception regarding solids.  It was one Plato made as well as R. Buckminster Fuller.  There are not five stable solids.  There are six.

The mistake Plato and R. Buckminster Fuller made was to demonstrate the stability of a triangle composed of three rods to their students while saying that the simplest solid in three dimensional space is the tetrahedron.  He didn’t realize the triangle in his hand was the simplest solid.  The triangle is a two sided three vertex solid that is the simplest enclosure of space.  Our eyes use two of them to locate an object and calculate distance.

Considering the above solid and the Platonic Solids we have six three dimensional closed network structures as illustrated below:


Take note of the stability of each of the solids.  What this means is that the triangulated solids are able to support themselves structurally, while the non-triangulated solids collapse.

What I realized regarding the work of Einstein and other physicists is they did not regard the various phases of matter as important.  However the states of matter are important.  Each state from the triangle up to the icosahedron as illustrated above are higher states of order.  Yet, each state of order is fundamental to the universe in which we live.  And all are simply phases of what I call the “ZenEntity”.


I decided after looking at what I had found regarding the solids to reject contemporary empirical conventions and simply address one thing.  We have six fundamental ordered states.  After several billion years of evolution would not all organisms have what they require to function in response to all of the six states in their niche?

My next question was, “How do I represent the phenomena I had encountered as a network?”

In my profession there are data architects, database designers, data modelers, database administrators, data entrists, data analysts, database developers, database programmers database analysts, data warehouse architects, data warehouse analysts, data warehouse developers, Extract-Transform-Load architects, ETL analysts, ETL designers, ETL developers, ETL programmers, Business Intelligence architects, BI analysts, BI designers, BI developers and so on.  However, I was never satisfied with any of these position titles.  So, I coined one myself: data designer.  I was of the opinion no matter how much data was out there, it was finite.  Zero and Infinity were very useful, but they violated the laws of thermodynamics.  I saw seven distinct phases of order in the universe and only saw transitions from one state to another.  I could design according to those states.

This led me to explore how I could represent the six states.  I studied and applied a variety of project lifecycles such as System Development Lifecycle, Extreme Programming and Rapid Application Development, joint application development.  I had learned various enterprise frameworks such as Zachman and TOGAF, modeling techniques like UML, the various generations of programming languages, data structures, network topologies, organizational concepts, rule based systems, event based systems, data based systems, user centered design, goal directed design, location based services, pattern languages, service oriented architecture, hardware architectures and many more.  I studied English, Greek, Latin, Anglo-Saxon, German and French to see how I could develop a consistent taxonomy as well.

Ultimately I concluded that a majority of the people out there working on these problems had abandoned the basics for pet concepts.  They had no idea how many entities there were.  They had no idea how those entities should be related.  So I took it upon myself to identify all the relations that were applicable and came up with the following:


The associations are as follows:

  1. Pattribute: a triangle entity
  2. Battribute: a one to many relationship describing the association between a triangle and an tetrahedron
  3. Attribute: a one to one relationship describing the association between a triangle and a hexahedron
  4. Nattribute: a many to one relationship describing the association between a triangle and a octahedron
  5. Lattribute: a recursive many to one relationship describing the association between two icosahedrons and one icosahedron
  6. Mattribute: a recursive one to one relationship describing the association between two dodecahedrons

As you can see, the network is asymmetrical and allows for Node, Lattice, Tabular, Lattice, Linear; Lattice arrangements.  Note that since all of the entities are simply states of a single “ZenEntity” none of the states are independent from each other in the network.


Now, that we have established the solids and how they are interconnected we can look at what the actual phases of the ZenEntity are.  Each of these phases are recognized in physics, however I have not come across any discussion of the possibility that they are together a set of fundamental phases.


Usually, we see Space, Time, Energy and Mass described in Einsteinian classical physics.  We also have discussions of Ions, Gases, Liquids and Solids as states of matter.  But we don’t see them together.

  1. Energy: a three dimensional coordinate system
  2. Time: a connection between one three dimensional coordinate system and two four dimensional coordinate systems
  3. Ion: a connection between one three dimensional coordinate system and one six dimensional coordinate system
  4. Gas: a connection between two three dimensional coordinate systems and one eight dimensional coordinate system
  5. Liquid: a connection between two twelve dimensional coordinate system and one twelve dimensional coordinate system
  6. Solid: a connection between two twenty dimensional coordinate systems

Next, we will see how these states are all very important to our sensory systems.


As well as the phases there is another way to look at the six solids.  This is in the Latinate language of the six states.  The states differ from  the phases in that they deal with the essence or source of each of the states.


The essence of each of the states is as follows:

  1. Pattern: Father
  2. Battern:  Hold
  3. Attern: Give
  4. Nattern: Birth
  5. Lattern: Milk
  6. Mattern: Mother


Now, I am going to introduce you to some friends of mine.  I call them “Zen Sensors”


As you can see each ZenEntity State has a coresponding human sensory organ:

  1. Eye: detect events
  2. Ear: detect pressures
  3. Nose: detect plasmas
  4. Throat: detect molecules
  5. Jaw: detect organics
  6. Body: detect inorganics


Next, we have for your viewing pleasure the standard interrogatives and how they correlate:


I found this interesting, because I spent a great deal of time resisting the order of these interrogatives.  Finally, I just went along and found ultimately the order does make perfect sense.  It is an acquired taste.

  1. Eye: Who: Identification
  2. Ear: What: Objectification
  3. Nose: Where: Location
  4. Throat: When: Chronation
  5. Jaw: Why: Rationation
  6. Body: How: Function

If you read enough Anglo-Saxon it makes sense.


Having considered the Entities, Associations, States and Sensory Organs, let us now look at how this relates to a hemisphere of the brain:


The above illustration shows the left hemisphere of the brain and the major regions.  They are color coded to correspond to the fundamental states I have described.  You can also see the corresponding sensory organ as well as the corresponding network structure in the region:

  1. GREEN: EYE: OCCIPITAL LOBE: visual center of the brain
  2. YELLOW: EAR: TEMPORAL LOBE: sensory center of hearing in the brain.
  3. SKY: NOSE: BRAINSTEM: control of reflexes and such essential internal mechanisms as respiration and heartbeat.
  4. BLUE: TONGUE: PARIETAL LOBE: Complex sensory information from the body is processed in the parietal lobe, which also controls the ability to understand language.
  5. RED:  JAW: FRONTAL LOBE: control of skilled motor activity, including speech, mood and the ability to think.
  6. ORANGE: BODY:  CEREBELLUM: regulation and coordination of complex voluntary muscular movement as well as the maintenance of posture and balance.


Everything is great so far, but there is the fact that there are two hemispheres to the brain and they interact through the Corpus Callosum which I claim is where the self resides.  One of the interesting things about my study of Latin is that I discovered most questions actually required a two part answer.  This answer would be composed of an Archetype and a Type.  After reading Jill Bolte Taylor’s book, My Stroke of Insight and listening to her account of her perceptions while the left hemisphere of her brain was being shut down by an exploded blood vessel, it became apparent to me that the left hemisphere of the brain contained the Types the Latin language required and the right hemisphere of the brain contained the Archetypes.  It was necessary to create a two axis model to accomodate a brain with two hemispheres:


Each of the light colored cells in this table represent a connection between one coordinate system association (row) and another coordinate system association (column).  This accounts for the broad variety of properties we encounter making the states we experience.

There are actually not one or two, but four directions you can take on the above table.    Top to Bottom is right hemisphere deduction.  Bottom to Top is right hemisphere induction. Left to Right is left hemisphere deduction.  Right to Left is left hemisphere induction.

This is a physiological model of human perception that I have arrived at.  Our current definitions of dimensionality are incorrect.  Each state has its own dimensionality, its own associations, its own sense organs, its own region of the brain and the brain two hemispheres connected by the corpus callosum.  If the work of Dr. David Bryson on Physical, Decisional and Perceptual Learning is right, then deduction happens during waking and induction happens during sleeping.

This is not a complete model by any means as it does not deal with scale-free networks.  Or does it?

But to this point, that is the Zen Universe.


Posted in Uncategorized. Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , . 5 Comments »

The Zen of Systems and Networks


My own work with Enterprise Frameworks and Networks has led me to come up with the following table.  It describes the Nodes and Links in a Complete System Network.  I am saying that the Nodes representing Goals, People, Time, Locations, Code, Data, Qualities and Quantities can all be represented as Scale-free Networks and that each of these Node Networks require only one datatype.  I am also saying that there are only three types of links in networks: recursive links within a set, multiple links between sets, single links between sets.  I know of no case where this has been attempted in the manner I am attempting to represent it.


If you have been following my blog you are aware that I have been struggling for a long time to come up with a framework and a clean terminological set to describe systems.  I think I have come one step closer to that goal today.  The table above describes a Fact composed of eight Nodes (first white row illustrating entities) and the Links (last three white rows illustrating recursive, multiple and singular relationships) for each of the System Networks (Interrogative columns).  One of the interesting aspects of this System Network Model is every Fact is composed of a Unique Set of all eight Nodes.  However, all the Nodes in one Fact do not have to have Links to all the Nodes in another Fact.  Each Node within a Fact is independent regarding its Links.  Therefore you have a single set of System Facts with each Fact containing a single set of Interrogative Nodes each connected by their respective Link Networks.

I have recently been writing with the intent to challenge centrism on any one of these networks and advocate a more integrated view. I still remember dealing with data centrism, event centrism, user centrism, goal centrism, program centrism and schedule centrism over the course of my career. All of them have a role to play. My insight into all of these Nouns being Linked by Verbs in only three ways required me to look at all of the Enterprise Architectures and disengtangle the Nouns, Links and Verbs from the reasoning and representations that extend back beyond computing itself.

The Data Model below is a hybrid of Relational Models and Dimensional Models.  I call this an Associational Model.  It is using Relational Architecture to represent it.  However, I think that an alternate Entity-Attribute-Value (EAV) architecture called the Associative Model of Data would be better suited to the task.  I am using relational representation as I am still trying to communicate with a community only familiar with Relational technology.

The first thing to note about this model is Links are represented by Associations.  Associations link two Nouns using a Verb.  What is interesting about this model is every Verb, Association, Noun and Fact is unique.  The vertical connections are Many to Many relationships which allow two vertically adjacent Verbs, Associations or Nouns to have multiple unique relationships between each other.  What this means is there are no integrity problems (duplicate values) as the system network would enforce uniqueness.


The premise of this model is that the Nodes are not dimensions at all.  I am rejecting the traditional concept of dimensionality instead I am saying that there are three dimensions of Links: recursive, multiple and singular.  All we perceive are Facts, Nodes and the Links between them.

So you could come away with the following Zen koan:

entity without entity,

source without source,

path without path,

target without target,

size without size,

dimension without dimension.

Databases: 50 years of stupidity


Database conventions are not best practices.  Database naming conventions are based on random ontological concepts.  Ideas about what constitutes an entity are misdirected.  Programmers know nothing about what a class or an object is or how to name them.  Hierarchical, Relational and Network databases have maintained a persistent and ignorant set of practices that the information technology intelligencia have followed mindlessly.  What we have after 50 years is a brute force patchwork of bad design practices and mediocre engineering that continues to work within the same set of assumptions.  It’s a product of the inertia of intellectual lethargy that dominates not just the technological world, but the world that uses technology in general.  Workers are too busy being inefficient and ineffective to improve their business practices.  They jump at silver bullet solutions that promise results without change.

Database people have never understood data.  Programmers have never understood data.  They have instead tried to please everybody’s ontological misconceptions with grotesque architecture and then shoehorn it all into a physical processor that is about as progressive and efficient as the internal combustion engine.  Eco-nut technologists like to use buzzwords like “organic” to describe the chaotic crap they are producing on the web.  It isn’t organic, its a massive slum composed of any piece of detritus the occupants can build with surrounding a district of monolithic towers of gross excess and shameless waste.  Google’s motto is “Don’t be evil.”  Has any company ever considered having the motto, “Be good”?  The more I work with corporations the more I recognize that goodness is discouraged and evil is whatever the corporation says it is.  If you work for anyone you are part of a Milgram experiment and you are delivering those electric shocks everyday under the direction of psychopaths.  The merit you get promoted for is based on your willingness to flip those switches more than anyone else.  Having a conscience is deemed unprofessional and grounds for termination.

This is the environment within which real innovation has to work.

Hungarian Backwords Notation, a naming convention by Charles Simonyi, has been abused and bastardized by programmers and database administrators with no understanding of semantics, which is most of them.  Consequently, it has been rejected by a large portion of the IT community.  Not even Microsoft knew what it had.  I fought with Simonyi’s concept for years and applied it in several working applications successfully against massive resistance.  The more I worked with it the more I realized that Object Oriented Programming was based on a completely false ontology.  The metaphors were completely wrong.  And the Unified Modeling Language entrenched the misconceptions even further.  Information technology is spawning increasing complexity without any appreciation for underlying order.  The order was datatypes.  There are only a handful of Classes and they are datatypes. The English are backwards, not the Hungarians.

If the world was looked at as a collection of datatype classes the entire philosophy of data and programming and systems would have to change.  Objects do not have properties, properties have objects.  And there are only a handful of properties.  I’ve realized this and it has changed my perspective of data design forever.  Throw away your OOP and your Data Model textbooks.  They’re crap.  Google, Apple and Microsoft are not the future.  Einstein had a better grip on reality than Turing ever did.  The typical mind, including the IT mind, still thinks elephants are bigger than the moon.

Related Links:

Universe: Interrogative Spaces


In my previous post I gave thought to Tim Brown of IDEO’s “design thinking”, Clayton Christensen’s “Innovator’s Dilemma”, Malcolm Gladwell’s “Tipping Point”, and Buckminster Fuller’s “Synergetics” concepts.  What emerged was the above Czerepak Framework.  My claim is this framework is fundamental to designing a system.

The thing that the above table shows is interaction within what I am now going to call the “Interrogative Spaces”: HowSpace, WhatSpace, WhySpace, WhoSpace, WhenSpace, WhereSpace, HowMuchSpace, HowManySpace.  Each ellipse I call a “vortice”.  The Interrogative Spaces are composed of one or more vortices.  The Framework above shows how Spaces are composed within the Interrogatives,  but what about interactions between the Interrogative Spaces?   A good example is speed or velocity.  Speed is the intersection of WhenSpace and WhereSpace:

v = r / t

Where v is velocity, r is radius and t is time.

If you are increasing Speed, which is acceleration, you have one dimension of WhereSpace and two dimensions of WhenSpace:

a = r / t’ * t”

Where a is acceleration, r is radius, t’ is the first clock and t” is the second clock.  You cannot measure acceleration with one clock. This uniqueness of every vortice applies to all the Interrogative Spaces and all inter-relationships between all of the Spaces.  .

Another way to look at the Interrogative Spaces is as sets and subsets.  The first row are the complete Space vortice sets.  The second row are the first Space vortice subsets.  The third row is the intersect between the row two and row three Space vortice subsets. And the fourth row are the intersects between the row two and row three and row four Space vortice subsets.

I do not believe that anything is constant.  Not the speed of light, not gravity, not cosmology.  Every intersection of dimensions creates a vortex in Universe and every one is unique.  We are simply unable to measure and manage the uniqueness of everything, therefore we make generalizations which create models that can always be falsified.

Systema: Operation, Tactic, Strategy




Systema: Geodesates, Nodes and Links

“To every action there is an equal and opposite reaction.” — Isaac Newton

A predominant issue arising from my work is the discovery of the difference between a node and a link.  A node type represents a state type while a link type represents a transaction between state types.  However I am finding there are a limited number of node types (self-ordered states) and link types (self-ordered state actions).

In the diagram below, each polyhedron is a first frequency geodesate and has a unique polytrope/polytype combination.  A polytrope is the number of edges per polyhedron vertex.  A polytype is the number of polyhedron vertexes.  This is not the final version.  I am still working to purify my geodesate concept.

What I am revealing here is that each of the seven Node Types on the Left has only one Link Type on the right.  In the same way that an association is composed of a source node type and target node type, an association is composed of a source link type and target link type.

Here is an example of a homogenous Entity to Entity association:

Here is an example of a hetergeneous Entity to Positity association:

Having considered this it is now possible to conclude that there are a unique set of nodes each with a unique link which can be used to build homogeneous or heterogeneous associations.  In otherwords, each node type can perform only one action type.  It is the reaction type of the target node type that makes the action reaction combination unique in the system.

Let’s look at some examples of node type and link type associations:

  1. To identify a positity, positifies an identity.
  2. To objectify a projectity, projectifies an objectity.
  3. To chronify a chronity, chronifies a chronity.
  4. To projectify a quantity, quantifies the projectity.
  5. To qualify an identity, identifies a quality.

Fourty-nine possible type combinations exist.  I think there are even more types which I will explore with Archimedean Solids and higher frequency Geodesates in later posts.

SQL: Old Soldiers Never Die

Structured Query Language (SQL) has been a phenomenally useful language for the relational database era. But I see that era coming to a close.

One of the primary flaws is SQL allows for database Alters, Drops, Updates and Deletes. When diskspace was expensive this made perfect sense, but with the unlimited disk resources we have today a greater principle holds true: NO SCHEMA OR DATA SHOULD BE ALTERED, DROPPED, UPDATED OR DELETED.

A second flaw is the lack of interactive modification of the schema in real time. Changes still blow most applications all to hell.

A third flaw is supertype/subtype hierarchies. Such things should not be hard coded into a design.

That being the case SQL has four unnecessary statements just waiting to be abused. We need a better language. In fact, we need a better database architecture.

A new language would provide no means for updates or deletes. I created the first Releases of this language I called “Structured Thinking Language” (STL).

STL has the following commands:

  1. CREATE – affordance concept (creates entities)
  2. DIRECT – affordance context (relates entities)
  3. POSIT – affordance method (entity output)
  4. OBJECT – affordance pragma (entity input)
  5. NEGATE – affordance cosmos (entity security)
  6. INTUIT – affordance chronos (entity manipulation)

As you can see there are no means to delete data.

Each entity (noun) has only one “attribute” in the relational ERD sense and each entity value is unique.

Each relationship between entities is called an direction with a subject, verb and object.

What we are actually dealing with is a database that has data states. Data being no longer affected by Alters and Deletes are instead affected by change of state without physical alteration or deletion.

After looking at STL recently I realized I had created a command language for an existing database architecture: The Associative Model of Data by Simon Williams.

The Book on the Model and a free copy of the Enterprise Edition software is available here.

An old release of STL can be found here.

Structured Thinking System: Motives

At the center of your being you have the answer;
you know who you are and you know what you want.
Lao Tzu

Out of my work on the Structured Thinking Language I have come to the realization that it is best suited to describe systems based upon its own core principles. Sort of a “it’s turtles all the way down” recursion.


I will systematically go through them and discuss their characteristics starting with Green Coat: Motives.

The MOTIVE column: Verity, Unity, Quality, Quantity, Safety, Entity.

The MOTIVE column is based on Maslow’s Hierarchy of Needs. Originally, I thought that the hierarchy required an additional level at the bottom to deal with interoceptive and exteroceptive perception, but as I worked with several other hexads I came to conclude that instead, as Maslow came to conclude, it required another level at the top. Maslow called this top level trascendence, but in the context of the other hexads I decided to call it Verity. Verity is defined as “1. the state or quality of being true; accordance with fact or reality and 2. something that is true, as a principle, belief, idea, or statement.” Personally, I consider it as “the desire to right what is wrong.” The next motive is Unity which is defined as “containing all the elements properly belonging”. Maslow uses the fancy term “self-actualization”, but I think a self-actualized person can simply be called an unified person. The third motive is Quality which is defined as “uniqueness and value”. The fourth motive is Quantity “low cost participation”. The fifth motive is Safety which can be defined “freedom from the occurrence or risk of injury, danger, or loss”. The sixth motive is Entity which I define as “existing or being”. One Verity has many Unities; one Unity has many Qualities; one Quality has many Quantities, one Quantity has many Safeties; one Safety has many Relieves and, here’s the clincher, One Relief has many Verities.

In Summary:

  1. Verity is to achieve Moral Law.
  2. Unity is to achieve Command.
  3. Quality is to achieve Discipline.
  4. Quantity is to achieve Training.
  5. Safety is to achieve Terrain.
  6. Relief is to achieve Climate.

Related Links:

Untangling Planar Graphs

Planarity is an excellent excercise for data modelers attempting to untangle their entity relationship diagrams.  Move up the levels and hone your skills.

Posted in Uncategorized. Tags: , , , . Leave a Comment »