EQUILIBRIUM DIAGRAM FOR A BEGINNER

MEANING

This is the answer to the question:

why is all this needed in the first place?

Examples:

• human development,
• growing trust,
• education,
• cooperation,
• stability.

Meaning is the beginning.

Without it, the system is empty.

SUBJECTS

This is the answer to the question:

who is involved?

Examples:

• a person,
• an organisation,
• a cooperative,
• an expert,
• an agent,
• a community.

Subjects are active forces.

RESOURCES

This is the answer to the question:

what sustains it?

Examples:

• money,
• knowledge,
• energy,
• time,
• data,
• infrastructure.

The resource feeds the system.

NORMS

This is the answer to the question:

what rules does everything follow?

Examples:

• a law,
• a regulation,
• a contract,
• an ethical principle,
• a standard.

The norm keeps the system from coming apart.

Protocol

This is the main working block.

It answers the question:

how exactly does all this come together as a living process?

The protocol is:

• not an idea,
• not a person,
• not money,
• not a law,

but the living combination that brings action together.

That is:

meaning + participants + resources + norms = protocol

The protocol is the heart of the system.

EFFECT

This is the answer to the question:

what was the outcome?

Examples:

• growth in employment,
• increased trust,
• reduced conflict,
• a project launch,
• territorial development.

METRIC

This is the answer to the question:

How do you know if it worked or not?

Examples:

• trust index,
• number of participants,
• employment level,
• stability coefficient.

The metric turns the effect into a measurement.

FEEDBACK

This is the answer to the question:

what should be done next, after the result?

If the result is good:

• we strengthen it.

If it's bad:

• we change it.

If incomplete:

• we adjust it.

Feedback makes the system alive.

Second diagram — how it looks on the map

Now imagine all this drawn on a screen.

   [Meaning] ----\

                \

   [Subject] ----> [Protocol] ----> [Effect] ----> [Metric]

                /

   [Resource] ----/

                \

                 -> [Norm restricts]

In other words, the protocol is at the centre. Everything flows into it and out of it.

Why the protocol is at the centre

Because in life, what matters is not simply having elements, but having them work together.

Separately:

• meaning,
• a person,
• money,
• rules

achieve nothing. They come to life only when assembled into a process. That is why the protocol is the centre of the structure.

Third diagram — what the screen consists of. On screen, the system looks like this:

┌──────────────────────────────────────────────────────────┐

│ TOP PANEL │

│ search / mode / level / AI / settings │

├───────────────┬───────────────────────────┬─────────────┤

│ LEFT PANEL │ CENTRE: GRAPH │ RIGHT │

│ filters │ nodes + links + protocols │ PANEL │

│ │ │ details │

├───────────────┴───────────────────────────┴─────────────┤

│ BOTTOM PANEL │

│ time / events / history │

What each part of the screen does

Left panel

Allows you to choose what to show.

For example:

• only meanings,
• only resources,
• only crises,
• only educational processes.

Centre

The main map. It shows:

• nodes,
• links,
• protocols,
• areas of growth,
• areas of overload.

Right panel

Shows details of what you clicked.

If you click on a subject, you see its profile.

If you click on a protocol, you see the whole process.

If you click on a link, you see the type of participation.

Bottom panel

Shows time. Here you can view:

• what happened before,
• what is happening now,
• what will happen next.

Fourth diagram — how a decision moves through the system

Here is the decision-making diagram within the system:

1. A meaning emerges

        ↓

2. Participants are identified

        ↓

3. Resources are connected

        ↓

4. Norms are checked

        ↓

5. A protocol is created

        ↓

6. The protocol produces a result

        ↓

7. The result is measured

        ↓

8. The system is adjusted

This is a very important diagram.

In fact, this is the life cycle of any project, programme or action.

Fifth diagram — how the system finds a problem

The system asks simple questions:

Is there a meaning?

Is there a participant?

Is there a resource?

Is there a rule?

Is there a result?

Is there a measurement?

Is there any feedback?

If something is missing, it is already a weak point.

For example:

• there is a project, but no resource;
• there is a process, but no norm;
• there is a result, but no way to measure it;
• there is an overload, but nobody responds.

This is how diagnostics works.

Sixth diagram — the state of the system

Each element of the system can be in one of these states:

[Harmony] — everything is coordinated

[Growth] — development is underway

[Tension] — there is an overload

[Crisis] — the system is breaking down

[Transformation] — profound change is underway

[Unknown] — there is still too little data

In other words, the system shows not just an object, but its state of health.

The shortest diagram of the entire architecture. Reduced to its essentials, it looks like this:

NODES → LINKS → PROTOCOLS → EFFECTS → METRICS → CORRECTION

• nodes — what exists,
• links — who participates and how,
• protocols — how a living process is assembled,
• effects — what the outcome was,
• metrics - how it is measured,
• correction — how the system learns.

An example in one small diagram. Suppose the topic is education.

[Meaning]

Development of competences

        ↓

[Subject]

FENIX Cooperative

        ↓

[Resource]

Education Fund

        ↓

[Norm]

Programme regulations

        ↓

[Protocol]

Cooperative learning

        ↓

[Effect]

Employment growth

        ↓

[Metric]

Employment index

        ↓

[Feedback]

Programme adjustment

A single framework like this can already be shown on an interactive map.

What you, as a non-programmer, need to keep in mind. Not code. These 4 things:

What is a node

Exactly what we regard as an entity.

What is a connection

How one element participates in another.

What constitutes a protocol

How a living process is assembled.

What a person should see on the screen

So you can understand the system rather than drown in details. If you keep this in mind, you already have control of the project’s logic.

The final diagram in a single frame

                EQUILIBRIUM

         [MEANING]

             ↓

        [SUBJECTS]

             ↓

         [RESOURCES]

             ↓

          [NORMS]

             ↓

        [PROTOCOL]

             ↓

         [EFFECTS]

             ↓

         [METRICS]

             ↓

     [FEEDBACK]

       All this is displayed on the screen:

   filters | map | details | time | diagnostics

The next useful step is to make a more polished visual flowchart of 1 page for your project, as the basis for a document or slide.

EQUILIBRIUM — VISUAL FLOWCHART

Central diagram (the system’s core)

                 ┌──────────────┐

                 │ MEANING │

                 │ (WHY) │

                 └──────┬───────┘

                        ↓

                 ┌──────────────┐

                 │ SUBJECTS │

                 │ (WHO) │

                 └──────┬───────┘

                        ↓

                 ┌──────────────┐

                 │ RESOURCES │

                 │ (WITH WHAT) │

                 └──────┬───────┘

                        ↓

                 ┌──────────────┐

                 │ NORMS │

                 │ (RULES) │

                 └──────┬───────┘

                        ↓

        ╔════════════════════════════╗

        ║ PROTOCOL ║

        ║ (LIVING PROCESS) ║

        ╚════════════════════════════╝

                        ↓

                 ┌──────────────┐

                 │ EFFECT │

                 │ (RESULT) │

                 └──────┬───────┘

                        ↓

                 ┌──────────────┐

                 │ METRIC │

                 │ (MEASUREMENT) │

                 └──────┬───────┘

                        ↓

                 ┌──────────────┐

                 │ FEED- │

                 │ BACK │

                 └──────┬───────┘

                        ↺

The essence of this diagram

👉 Everything in the system is a flow of action, not a set of objects

👉 The protocol is at the centre because that is where life happens

Interaction diagram (how it is connected)

 [MEANING] ───────┐

                │

 [SUBJECTS] ────┤

                │

 [RESOURCES] ─────┼───► [ PROTOCOL ] ───► [ EFFECT ]

                │                         │

 [NORMS] ───────┘ ▼

                                    [ METRIC ]

                                          │

                                          ▼

                                   [ FEEDBACK ]

                                          │

                                          ↺

💡 An important insight. Usually, lines are drawn. Here: 👉 everything converges at one point — the protocol. This is:

• programme
• draft
• action
• decision

 Interface diagram (how a person sees it)

┌──────────────────────────────────────────────────────────┐

│ TOP PANEL │

│ Search | Mode | Level | AI | Settings │

├───────────────┬───────────────────────────┬─────────────┤

│               │                           │             │

│ FILTERS │ GRAPH │ DETAILS │

│ │ (THE WHOLE SYSTEM) │ │

│ - node types │ │ - node │

│ - states │ ● nodes │ - protocol │

│ - links │ ↔ links │ - metrics │

│ │ ⬢ protocols │ │

│               │                           │             │

├───────────────┴───────────────────────────┴─────────────┤

│ TIME / EVENTS / HISTORY │

└──────────────────────────────────────────────────────────┘

What a person does. They do not read data. They:

• look at the map
• click on elements
• see links
• understand processes
• change the system

System operation diagram (life cycle)

Idea → Assembling elements → Protocol → Action → Result → Analysis → Change

Or more specifically:

1. A meaning emerges

2. Participants are identified

3. Resources are connected

4. Norms are checked

5. A protocol is formed

6. A process is launched

7. An effect is produced

8. The result is measured

9. An adjustment is made

Diagnostic diagram (how the system finds problems)

Protocol

├─ is there a meaning? ❌ → emptiness

├─ is there a subject? ❌ → no one to do the work

├─ is there a resource? ❌ → it will not start

├─ is there a norm? ❌ → chaos / risk

├─ is there an effect? ❌ → useless

├─ is there a metric? ❌ → cannot be evaluated

└─ is there feedback? ❌ → the system is blind

👉 This is very important. The system does not just show things. It asks questions: where is the gap?

System states diagram

🟢 Harmony → everything is coordinated  

🔵 Growth → the system is developing  

🟡 Tension → there is an overload  

🔴 Crisis → the system is breaking down  

🟣 Transformation → profound change  

⚫ Unknown → no data  

Final diagram (condensed)

        NODES

         ↓

       LINKS

         ↓

     PROTOCOLS

         ↓

       EFFECTS

         ↓

       METRICS

         ↓

     FEEDBACK

         ↓

      EVOLUTION

The main thing you need to understand

Stripped of everything unnecessary:

👉 EQUILIBRIUM is a system that shows how elements come together into living processes

The key idea (the most important)

The world is not a collection of objects.

The world is a network of processes.

And EQUILIBRIUM shows:

👉 where these processes work

👉 where they break down

👉 how to change them