We already live inside systems. Your family is a system. Your workplace is a system. A school is a system. A government is a system. A computer is a system. A supply chain is a system. An ecosystem is a system. Even a conversation is a system of relationships between people, words, assumptions, and meanings.
We rely on networks constantly, whether we realize it or not. The internet is a technological testament to the power of systems thinking.
Yet most people are never explicitly taught how to see a system. We are taught how to collect information, memorize maps, analyze individual objects, defend positions, and navigate institutions. We are much less often taught how to recognize the underlying structure connecting everything we are looking at.
That matters because the largest system we belong to is the universe itself. The universe is the set of all that exists: past, present, and future. And there is a peculiar problem with trying to understand it.
You are trapped inside it. You cannot step outside the universe, put it on a table, and examine it from every direction like a ball in your hand. You cannot become a completely external observer of the system because you are one of its members.
So how do you develop the ability to understand a system you can never completely step outside of?
You learn to think in systems, but there is an important qualification:
Learning to think in systems is not enough. You have to learn to think about systems coherently.
That requires learning to see both the structure and your own position within it.
The observer inside the system
There is a difference between being present and being internally captured. You can be physically sitting in a room while your attention is completely absorbed by an argument happening inside your own head. You can be reacting to someone without actually observing what they are doing. You can become so emotionally invested in a narrative that you stop noticing the structure producing the narrative.
A person who cannot step out of that internalized state is easier to redirect. If you can keep someone confused, distracted, reactive, or permanently absorbed in their own internal interpretation, you have gained an advantage over them.
This is why systems thinking is not merely an intellectual exercise. A systems thinker learns to recognize the structure around them. Epistemology then helps condition the mind to respond to that structure rather than becoming trapped inside an immediate reaction.
At the same time, you can train someone to be calm and present, but if they cannot recognize the structural red flags in front of them, if they are not trained to evaluate a system at hand, that presence does not necessarily help. And you can give someone an enormous amount of information, but if they cannot distinguish the map from the terrain, more information can simply give them a more elaborate way of being confused.
This is where ontology becomes important.
The map and the terrain
Ontology and epistemology are two areas of study that majority of people do not necessarily understand. Yet they are two sides of the same task.
Epistemology concerns how we know, perceive, interpret, categorize, and respond. Ontology concerns what exists and how what exists is structured. A useful way to think about the distinction is that epistemology builds the map. Ontology describes the terrain.
A map is incredibly useful. But a map is not the territory. You can become extraordinarily skilled at reading a map while never checking whether the map actually corresponds to the terrain.
That is one of the mistakes our culture increasingly makes. We have become extremely sophisticated at building maps—cognitive theories, narratives, perceptions, categories, concepts, models, symbols, language, ideologies, identities, values, explanations, and systems of measurement—and then quietly begin treating the map as though it were the terrain itself.
But the purpose of a map is to correspond to something beyond the map. The status quo that tells you to rely exclusively on the map while discouraging you from checking the domain is making a bet on your lack of due diligence. It is betting that you will confuse representation with reality.
Systems thinking gives you a way to check.
The recipe and the cake
There is another way to see the same relationship. Ontology is like the recipe. Epistemology is like the cake. The recipe describes the underlying structure that produces the product. The cake is the experienced, observed product.
If you have a cake and pass it from person to person in a game of telephone, eventually the instructions for producing it can disappear. Each generation remembers the product as it experienced it, but small changes accumulate.
The cake may eventually become something completely different. Perhaps the cake becomes a pie. But if you preserve the recipe, you can reconstruct the product even after generations have passed.
This is one reason ontology matters. It preserves the structure rather than merely preserving one experience of the structure. But there is an important problem on the other side. A recipe is useless to someone who cannot recognize what it is describing.
You need the recipe and the cognitive ability to produce the cake.
This is especially important because of how we talk about objectivity today. We usually describe objectivity epistemologically. We talk about removing bias, examining evidence, considering different perspectives, controlling emotional reactions, remaining present, and trying to observe rather than react.
All of that matters. But it describes the behavior of the observer. It does not fully describe the structure the observer is trying to align with.
The ontological and epistemological definitions of objectivity are not competing definitions. They are complementary. Without the ontological structure, the observer does not know what objective alignment actually means. Without the epistemological discipline, the observer may know the structure but lack the cognitive ability to recognize it in practice.
Imagine looking into the night sky. The stars are right there. But if you have never learned how to read a constellation map, the pattern may be invisible to you. You can see the stars without recognizing the structure. That is epistemology without sufficient ontology.
But the reverse is equally dangerous.
You can possess an elaborate constellation map while looking at the wrong part of the sky. You can force the stars in front of you to conform to the map because you are too attached to the story you already have. That is ontology without sufficient epistemology.
You need both to build a genuinely objective outlook. You will never be able to hold the universe in your hand like a ball. But you can develop the ability to recognize its structure, zoom in and out of your perspective, identify your assumptions, observe your position within the system, and continually check whether your map corresponds to the terrain.
That is about as close as a member of the universe can come to observing the whole system.
Learning to read the graph
The simplest way to begin thinking in systems is to think in nodes. A node is simply something that can be identified within a system.
●
Two nodes can have a relationship.
● ───── ●
A system contains many relationships.
●
/ \
● ●
/ \ \
● ● ●
Now comes the important part. A node can itself contain a system.
[ ● ]
Zoom in:
●
/ \
● ●
/ \ \
● ● ●
Zoom back out:
[ NETWORK ]
│
│
●
The network that was visible when you zoomed in becomes a single node when you zoom out. This ability to move between levels is what makes systems thinking powerful. You can examine the component. You can examine the relationship between components. You can examine the system containing those components. And you can examine the larger system containing that system. This is what makes a graph capable of becoming transcendent or meta.
But there is a catch. Ontology can show you the structure. Epistemology gives you the cognitive ability to zoom in and out of it. A node graph without context can become dry and meaningless.
The advantage of learning generic graphs is not that you will walk around thinking about dots and lines all day. The advantage is that you develop pattern recognition for structures that you cannot physically step outside of and inspect from every angle.
Parent and child
One of the most basic relationships in a system is the parent-child relationship.
P
/ | \
A B C
Here, P is the parent and A, B, and C are children.
P = {A, B, C}
The important thing is not the word “parent.” It is the relationship. The parent provides a constraint within which the children are organized.
This relationship is contextual. A child can be a parent at another level. For example, a person can simultaneously be a child within a family, a parent within their own family, an employee within a company, a manager within a department, a citizen within a government, and a customer within a marketplace.
The relationship changes depending on which system you are examining. Two nodes can even have reciprocal relationships at the same time between two simultaneous contexts.
A
↕
B
A person can be dependent on another person in one respect while the other person is dependent on them in another. This is why hierarchy does not automatically mean permanent superiority in our day to day experiences. It describes a relationship within a particular context.
Consensus is not coherence
Now we can distinguish two things that are often confused. Consensus is agreement between nodes.
A ───── agrees ───── B
The relationship exists because A and B agree. But what keeps it binding? Nothing necessarily. They can agree today and disagree tomorrow.
Day 1: A ───── B
Day 2: A B
Coherence is different. Coherence requires a constraint that explains why the relationship should hold.
P
/ | \
A B C
The parent provides the organizing constraint. This is why consensus needs coherence. Coherence does not need consensus. Two people can agree about something that is incoherent. An entire group can agree about something that is incoherent. And a person can discover something coherent that nobody else yet accepts.
Consensus tells you that nodes agree. Coherence tells you that the relationships fit.
The words we use every day
We constantly use language that implies structural relationships. We say something is. Something is not. People are or are not something. An answer is correct or incorrect. An action is right or wrong. Something is left or right. Something comes before or after. Something is equal, different, consistent, inconsistent, compatible, or contradictory.
Every one of these judgments implies a relationship. When we say that something is correct, we do not normally expect to produce a physical object called “correctness” and put it on the table. We are referring to a structure. We are quietly cohering upon some reference that tells us what counts as correct.
This is why coherence is deeper than consensus. We use these concepts constantly without necessarily being able to articulate the parent node that makes the relationship intelligible.
Coherence creates levels
A ratio of a 1:many relationship creates a level.
P
┌───────┼───────┐
A B C
A, B, and C now occupy the same structural level relative to P. This is one way to understand equality. Equality does not mean that every node must perform the same function. Equality, and our use of the equal sign (=) means that nodes can occupy the same level of relationship to a parent.
But levels themselves create positional relationships. Whenever you organize a set, there will be a top and a bottom. There will be a first and a last. There will be a right and a left. You cannot permanently eliminate positional relationships simply by declaring everyone equal. This is why systems thinking is so important. When systems thinking is abandoned, those unavoidable relationships are left unexamined, making it easier for incoherent ideologies such as fascism to emerge by disguising hierarchy and power rather than understanding and constraining them.
The question is therefore not how to eliminate hierarchy. The question is how to prevent hierarchy from becoming permanently cast. If the top position becomes permanently owned by one node, the set stops being fluid.
A
│
┌─────┼─────┐
(B) C D
B has become permanently dominant.
A more sustainable structure allows the first position to remain accessible for all nodes in the set.
A
│
┌─────┼─────┐
B C D
↓
A
│
┌─────┼─────┐
C B D
↓
A
│
┌─────┼─────┐
D B C
The position can change while the underlying relationship to the parent remains. Everyone can potentially occupy the first position. And the person occupying the last position should not simply be discarded because they are currently at the bottom. A safety net preserves their ability to remain part of the system.
This is how equality becomes sustainable rather than merely declared.
Pseudo-coherence
Now we can see the problem with intersubjective parents. Suppose we create a group of nodes and call their consensus the highest authority.
A B C
\ | /
\ | /
GROUP
│
↓
"TRUTH"
But where did the authority of the group come from? If the answer is another group, we have simply moved the question upward.
GROUP 1
/ | \
A B C
│
↓
GROUP 2
│
↓
GROUP 3
If every parent is generated by another set of nodes, the system never reaches an independent reference. It becomes consensus layered upon consensus. That is pseudo-coherence.
This is the basis of institutionalization. It can be socially powerful without being objectively binding.
This is why systems thinking is useful. You can zoom in and ask: What is actually functioning as the parent here?
Then zoom out: Is that parent genuinely independent of the nodes it governs, or is it simply another collection of nodes?
That distinction is the difference between objectivity and intersubjectivity. If the parent is objective within its context, it provides an actual constraint. If the parent is merely intersubjective, the apparent constraint can become a tool for arbitrary dominance.
Brute force
This gives us a useful definition of brute force. Brute force is forced dominance or dependence between nodes that do not actually possess the asserted dominance or dependence relationship.
A ─────X─────> B
The relationship is imposed rather than derived from the structure. A can force B. A can threaten B. A can overwhelm B. A can use institutional authority against B. But none of those actions establish that A is actually the legitimate parent of B. They only establish that A currently has the ability to impose itself.
This distinction matters because power can temporarily imitate coherence. A system can look organized because nobody is permitted to challenge it. But silence is not coherence. Obedience is not coherence. Consensus is not coherence. Force is not coherence.
The Red Flags of Incoherence
Once you learn to see relationships structurally, incoherence becomes easier to recognize. It usually appears as a relationship that does not actually fit the nodes involved.
The important thing is that incoherence is not simply “something I disagree with.” A system can contain a conclusion we dislike and still be coherent. The question is whether the relationships actually support the conclusion.
While there are too many forms of incoherence to cover, here are some of the most common forms.
1. Non sequitur: the conclusion does not follow from the premises
A non sequitur occurs when the system jumps from one node to another without a valid connecting relationship.
For example:
“She is successful, so she must be telling the truth.”
Success and truth may both be real properties, but success does not logically establish truthfulness.
The graph looks like this:
SUCCESS
|
?
|
TRUTH
There is no demonstrated edge connecting them. Another everyday example:
“Everyone at work likes him, therefore his proposal must be correct.”
The first statement describes a social relationship. The second makes a claim about the validity of an idea. The relationship between popularity and correctness has not been established. A systems thinker asks:
What is the actual edge between these two nodes?
If there isn’t one, the conclusion is not supported simply because the statements were placed next to each other.
2. Category error: the relationship belongs to the wrong type of thing
A category error occurs when a property or relationship appropriate to one type of node is incorrectly applied to another. For example:
“Where is the university?”
A person might point to the administration building, the library, or the football stadium. But the university is not simply one of those buildings. The buildings are components of the university. The mistake is treating a system as though it were merely one of its nodes.
UNIVERSITY
/ | \
Library Labs Stadium
Another example is asking:
“What color is the number seven?”
Numbers and colors belong to different conceptual categories. The question combines two structures that do not share the requested relationship.
This is why some questions are not difficult because their answers are complicated. They are difficult because the question itself has connected the wrong kinds of nodes.
3. Circularity: the system uses itself as its own justification
Circular reasoning occurs when a conclusion is used to establish the premise that was supposed to establish the conclusion. For example:
“This rule is correct because the authority says it is correct.”
Then:
“How do we know the authority is correct?”
“Because the authority established the correct rule.”
The justification travels in a circle:
RULE
↙ ↖
AUTHORITY
Nothing outside the circle has constrained either node. A more subtle version appears in social systems:
“This is true because everyone agrees.”
“Why does everyone agree?”
“Because it is true.”
The apparent support is actually the same claim pointing back at itself.
This is why intersubjectivity can become pseudo-coherence. Many nodes can reinforce one another while still failing to provide an independent parent.
4. Hidden parent: the system has an authority it refuses to identify
Sometimes a system appears neutral because its governing reference has simply been left unnamed. Consider a workplace that says:
“We promote people based entirely on merit.”
That sounds like a neutral principle. But immediately we have to ask, what definition of merit? Does merit mean productivity? Revenue? Seniority? Creativity? Leadership? Compliance? Customer satisfaction? The moment the organization chooses one definition over another, a parent criterion has entered the system.
MERIT
/ | \
Productivity Revenue Seniority
If the organization refuses to acknowledge that parent, it may still govern everyone through it. The problem is not necessarily having a criterion. Every coherent system needs criteria. The problem is pretending the criterion does not exist. The same thing happens in everyday arguments:
“I’m just being objective.”
Objective according to what reference? If the reference is never examined, it can quietly govern the entire conversation while appearing to be neutral. A hidden parent is therefore not necessarily absent. It may simply be unacknowledged.
5. Missing parent: relationships exist, but nothing explains why they are binding
A hidden parent is an unacknowledged reference. A missing parent is different: the system genuinely has no identified reference capable of explaining the relationships. Imagine a group of people trying to determine whether a statement is true by voting:
A ─── B
│ \ │
│ \ │
C ─── D
Everyone asks everyone else what they think. But eventually someone has to answer, what makes the majority correct? If the answer is simply “because more people agreed,” then the system has explained agreement, not truth. The missing parent is the independent reference that could constrain the group regardless of what the group happens to believe.
This is one reason consensus can be extremely stable while still being wrong.
6. Role confusion: a node is performing a function it does not actually possess
Role confusion occurs when a node is treated as though it occupies a different position in the system. Consider a child arguing with a parent:
“You cannot tell me what to do because I am your equal.”
The child may be equal in human worth. But equality of worth does not erase the parent-child relationship.
PARENT
|
CHILD
The relationship has a particular function. The same person can occupy multiple roles simultaneously:
GOVERNMENT
|
CITIZEN
EMPLOYER
|
EMPLOYEE
PARENT
|
CHILD
The person has not changed, but the relevant relationship has. Role confusion happens when one relationship is imported into another. For example:
“You are my friend, so you cannot evaluate my work objectively.”
Friendship is one relationship. Professional evaluation is another. The existence of one does not automatically eliminate the other. Systems thinking asks which relationship are we actually talking about right now?
7. Map-terrain confusion: the representation becomes more authoritative than what it represents
A map is useful because it represents something. But imagine looking at a map that says a road exists where there is actually a river. If the map is treated as authoritative simply because it is the map, the traveler has a problem.
TERRAIN
↑
|
MAP
The map is supposed to conform to the terrain. Now reverse the relationship:
MAP
|
↓
"REALITY"
Reality is being forced to conform to the representation. This happens in much more ordinary ways. A job description says a person is a “manager,” so everyone assumes the person has authority over a particular process even after the organization has changed. A diagnostic category describes a pattern, and people begin treating the category as though it were the person. A statistical model predicts an outcome, and decision-makers begin acting as though the prediction itself were the underlying reality.
The representation is useful only while it remains accountable to what it represents.
8. Arbitrary dominance: one node is forced above another without a real parent-child relationship
Dominance can be legitimate when the system actually establishes the relationship. A manager can assign work to an employee because the organizational structure establishes that relationship. Arbitrary dominance occurs when someone simply imposes the relationship.
A
|
B
The diagram looks coherent, but the question is what establishes A’s authority over B? If the answer is merely:
“Because A says so.”
then the system has not demonstrated coherence. It has demonstrated force.
This can happen in a family, workplace, institution, online community, or political system. A person with more money, status, physical power, social influence, or institutional leverage can force another node into dependence without that dependence being structurally justified.
The distinction matters because power can create compliance without creating coherence.
9. Brute force: forcing the nodes to fit the model instead of correcting the model
Brute force is what happens when a system encounters a contradiction and responds by forcing the node to conform rather than examining whether the model is wrong. Imagine a software system designed around the assumption that every person has exactly one address. Then the system encounters someone who legitimately has two addresses. There are two possibilities:
MODEL
|
↓
PERSON
The system can force the person into one address and discard the other.
Or:
PERSON
|
↓
MODEL UPDATE
The model can be corrected to accommodate the actual structure. The second approach preserves the node and improves the model. The first preserves the model by damaging the representation of reality.
This distinction appears everywhere. When a theory conflicts with an observation, we can either investigate the theory or manipulate the observation until it fits the theory. When an institution’s rules repeatedly produce obvious contradictions, we can either examine the rules or punish people for exposing the contradictions.
Brute force is therefore not simply physical force. It is structural force, making the nodes conform to an incoherent model.
10. Missing or broken edge: the relationship being assumed does not actually exist
Sometimes the problem is even simpler: a relationship is being assumed without evidence that the nodes are connected in the claimed way. For example:
“My neighbor drives an expensive car, so he must be wealthy.”
Perhaps he is wealthy. Perhaps the car is borrowed, rented, financed, leased, or decades old. The assumed edge is:
EXPENSIVE CAR ————→ WEALTH
But the relationship has not been established. This kind of error is everywhere because human beings are extremely good at filling gaps. We see two nodes near one another and instinctively draw an edge. Systems thinking slows that process down.
Is the edge actually there? What establishes it? What type of relationship is it?
The General Pattern
These errors look different on the surface, but they share a common structure. A non sequitur invents an edge. A category error connects the wrong types of nodes. Circularity sends the edge back into the system without an independent reference. A hidden parent conceals the node governing the relationships. A missing parent leaves the relationships without an adequate source of constraint. Role confusion assigns the wrong relationship to a node. Map-terrain confusion reverses representation and reality. Arbitrary dominance invents a hierarchy. Brute force forces the nodes to fit the hierarchy. A missing edge assumes a relationship that has not actually been established.
These are not merely logical mistakes. They create leverage. Once a system becomes incoherent, somebody has to force the pieces back together. That creates an opportunity for brute force.
The practical lesson is simple, when something feels incoherent, don’t immediately reject the conclusion. Inspect the graph. Ask:
What are the nodes?
What are the edges?
What establishes each edge?
Which node is the parent?
Is that parent actually independent of consensus?
Are we confusing a map with the terrain?
Are we confusing agreement with constraint?
Are we forcing the nodes to fit the model, or allowing the model to be corrected by the nodes?
This is what makes systems thinking practical. Instead of merely saying, “That doesn’t make sense,” you can begin identifying where the sense breaks down. And once you can locate the broken relationship, you have something much more useful than disagreement. You have a place to begin correcting the system.
Why sustainable systems correct instead of destroy
A sustainable system will contain mistakes. That is unavoidable. The important question is whether the system can correct those mistakes without destroying the nodes inside it. An unsustainable model says:
The node doesn’t fit the model. Remove the node.
A sustainable model asks:
Does the model need to be corrected?
That distinction is enormous.
MODEL
│
↓
NODE DOESN'T FIT
│
├───────────────┐
↓ ↓
Destroy node Examine model
│
↓
Correct model
│
↓
Preserve node
Coherence respects the existence of the nodes as much as possible. Brute force does not. Brute force prioritizes the preservation of a particular position, model, or authority over the integrity of the system.
Coherence asks how the parts can be reorganized so the system works again. This is why sustainability is fundamentally a systems concept. A sustainable system does not need to be flawless. It needs to be correctable.
The coherence we experience before we identify its source
There is an even deeper problem. We often experience coherence before we can explicitly identify the parent node upon which that coherence depends.
Think about recognizing that something is wrong before you can explain exactly why. You notice that something does not fit. You notice a contradiction. You recognize that a relationship feels structurally broken.
The coherence is being experienced before the ultimate reference producing it has been fully identified. This matters because we can make an institutional mistake if we assume:
If the parent cannot yet be observed, the coherence cannot be legitimate.
But those are two different questions. The inability to point to the parent does not automatically mean the relationship is incoherent.
We are beings locked inside our own perception. We encounter the graph from within the graph. We therefore often cohere before we can completely identify what we are cohering upon.
This is one reason empiricism can become a cultural gatekeeper when it is treated as the only legitimate route to truth. If observation of a particular node becomes a prerequisite for acknowledging every form of coherence, then coherence occurring in real time can be dismissed simply because its parent reference has not yet been identified.
The problem is not empirical observation itself. Observation is indispensable. The problem is turning one epistemological method into a requirement that every ontological relationship must first present itself as an observable object.
The terrain does not cease to exist because our map is incomplete. And a relationship does not necessarily cease to be coherent because we have not yet identified the ultimate reference that makes it so.
Ontology at the level of presence and absence
This brings us to ontology in its deepest sense. At the level of what is present, every relationship we encounter is mediated through perception, language, interpretation, and perspective. At this level, all coherence is intersubjectively encountered. But as we have examined, intersubjectivity without a true objective foundation is circular, which is an incoherent structure. Yet we are experiencing real coherence in real time. The coherence we are experiencing is not all suspended on incoherence. Facts are binding. 1+1=2. Touch fire and you will get burned. These are facts, they have consequences. They are real. They are objective because they stand independently of our opinions on them. That means that the entire graph at the most comprehensive evaluation possible needs to have a true coherent reference to justify the constraint we are actively experiencing, otherwise it really doesn’t matter what 1+1 equals, or if you touch fire.
But if the entire graph is to have an objective reference, the parent cannot simply be another arbitrary node inside the graph. The truly objective parent of all that is present needs to fully terminate. These six conditions offer full termination with no opportunity for regress to continue which then gives it its ultimate authority as justification to every fact we experience everyday. It remains completely neutral to set, while allowing the contingent set below to remain dynamic and fluid:
singularity, externality, invariance, universality, non-derivation, and independence.
OBJECTIVE PARENT
singular • external • invariant
universal • non-derivative • independent
│
│
↓
┌─────────────┐
│ UNIVERSE │
│ SET OF ALL │
│ THAT EXISTS │
└─────────────┘
/ | \
● ● ●
/ \ / \ / \
● ● ● ● ● ●
This is the node of all nodes. It is ontologically testable in that it is justifiably terminal without restricting the ongoing dynamism of the set. And it is not simply another member of the set.
U = {A, B, C, (D, E), …}
It is the reference that allows the graph to remain coherent as it expands and contracts.
SMALLER GRAPH
U
/ | \
A B C
LARGER GRAPH
U
┌─────┼─────┐
A B C
/ \ / \ / \
D E F G H I
/ \ / \
J K L N
/
O
The graph can expand. The graph can contract. Nodes can appear and disappear from our field of knowledge. Relationships can change. But the parent remains the independent reference against which coherence can be evaluated. That is what makes it objective.
Consensus Cannot Produce Truth
Once we can distinguish consensus from coherence, we can ask a more important question: what actually makes truth possible?
Consensus cannot do it. Consensus is simply agreement between nodes. If ten people agree that something is true, we have learned something about the relationship between those ten people. We have not yet established that the thing they agree upon is actually true. This graph makes the difference clear:
A ─── B
\ /
\ /
C
These nodes may agree with one another, but nothing in this structure tells us why their agreement is binding. Their agreement is another relationship inside the graph. It does not provide a reference outside the relationship that constrains all three nodes.
Now compare that with coherence:
P
/ | \
A B C
Here, P provides a constraint that organizes A, B, and C. The nodes do not become coherent because they happen to agree with one another. They are coherent because they are all constrained by the same parent relationship. This is why coherence is the structure that makes truth possible.
Truth requires more than agreement. It requires a relationship between what we are saying and a reference that constrains what can coherently be said about it. Consensus can tell us what a group currently believes. Coherence tells us whether those beliefs actually fit the structure they are describing. This also explains why consensus can change while truth does not have to change.
Consensus:
A ─── B ─── C
"We agree"
Later:
A B ─── C
"We disagree"
The agreement changed, but nothing about that change tells us whether reality changed. Consensus is therefore responsive to the nodes participating in it. It cannot independently constrain them.
Intersubjectivity Can Mimic Coherence
This is where things become more subtle.
A sufficiently large network of agreement can look like an objective structure.
A
/ \
B───C
/ \ / \
D───E───F
Everyone can point to everyone else and say, “This is how things are.” The network can become extremely sophisticated. It can develop language, institutions, rules, measurements, traditions, and procedures for maintaining agreement. But if every node ultimately receives its authority from another node in the same network, the structure still has no independent parent.
That is intersubjectivity, agreement that exists between subjects. There is nothing inherently wrong with intersubjectivity. It is useful and unavoidable. We depend on other people to communicate, coordinate, build institutions, preserve knowledge, and correct one another.
The problem occurs when intersubjectivity is mistaken for objectivity. If the highest reference in the system is simply another collection of nodes, then the system is ultimately referring back to itself:
A
↙ ↘
B ← C
↘ ↖
D
Everyone can provide justification for everyone else, but no one has supplied the independent reference that makes all the justification binding. The system has become circular.
This is why consensus can imitate coherence while still failing to produce truth. It can reproduce the shape of a coherent network without providing the independent parent that gives the relationships their constraint.
Consensus needs coherence. Coherence does not need consensus.
A truth does not become true because everyone agrees with it. Rather, people can agree because they have successfully aligned with something that constrains their agreement.
The Question at the Boundary
This becomes especially important when we reach the boundary between what we know and what we do not know. Every system has such a boundary. There is what we can currently identify:
?
|
┌────┼────┐
A B C
| | |
D E F
And there is everything beyond our current ability to identify, explain, or inspect. The mistake is to assume that because we cannot yet identify the parent, there is therefore no parent. But coherence is already happening.
We are already distinguishing correct from incorrect, consistent from inconsistent, compatible from contradictory, and connected from disconnected. We are already navigating a structured reality before we have completely explained the source of that structure.
So at the boundary of knowing and unknowing, the central systems question becomes, what is making this system coherent? Not merely, what do we currently believe about it? Not: how many people agree about it? And not even: can we currently observe the thing we are using as the reference?
The deeper question is structural: What must be true for the coherence we are already experiencing to be possible?
That question moves us from epistemology back into ontology. We are no longer asking only how the nodes know. We are asking what makes the relationships between the nodes capable of being true in the first place.
And this brings us directly to the parent node. If the parent is merely another node inside the network, then it remains subject to the same system it is supposed to explain. If the parent is generated by the network, then it cannot independently constrain the network that generated it. If there are multiple competing parents, then the system has no singular reference.
So the question becomes not simply whether there is a parent. The question is what kind of parent could actually serve as the independent reference for the whole system?That is where the six conditions become important, and it is also where the parent must remain generic.
Why the parent must remain generic
This is where the distinction between ontology and mythology becomes important. Every religion attempts, in one form or another, to define or communicate something about the parent of the coherent structure at the boundary between knowing and unknowing we all have.
Religions preserve cosmologies. They preserve stories. They preserve symbols. They preserve models of reality across generations. In that sense, mythology can be understood as the stratification of coherence at the boundary between knowing and unknowing. It is attempting to define the terminus condition of the parent that coherently justifies the universal set. It may articulate a mythology as elaborate as Zeus with an entire soap opera alongside it, or it may change the topic altogether and point to a cake rather than articulate the recipe.
Throughout history, recipe for the terminus position is rediscovered. Then it is merely believed to be true because a population forgets the significance of both ontology and epistemology in tandem. The recipe is then represented as a cake and the recipe itself becomes forgotten. The representation is turned into a story. The story is transmitted. The story becomes tradition. The tradition becomes institution.
Structure
│
↓
Representation
│
↓
Story
│
↓
Tradition
│
↓
Institution
This can be extraordinarily useful. It allows knowledge to survive individual lifetimes. But it also creates a danger. Eventually the representation can be mistaken for the underlying structure. The map becomes the terrain. Our cognition becomes reality. The cake becomes the recipe. The story becomes the parent. And once that happens, correcting an error becomes much harder.
A generic representation of the parent recognized thru the six conditions that describe the terminus that justifies the objectivity we are actively experiencing can remain accessible as a reference even when the model changes.
But a mythologized parent can become attached to a particular representation that people feel obligated to defend. The distinction is therefore not simply between religion and non-religion. It is between preserving the generic structure of objective coherence—singularity, independence, universality, invariance, nonderivation, externality—and making a particular representation of that structure itself the highest authority.
A truly sustainable model keeps coherence accessible as the model expands and contracts. It permits mistakes to be corrected by referencing those six conditions ontologically to then operationally execute epistemologically.
Those six conditions of the objective terminus does not require brute force to preserve itself. And it does not make the continued existence of the model dependent upon protecting one node in the system from correction over everything else. The objective terminus gives the system the opportunity to self correct at any given time by leveraging systems thinking skills and building the cognitive capacity to execute correction.
Two ways of becoming blind
There are two opposite ways a civilization can lose its ability to see how truth works. One is to become epistemologically hyper-developed. You accumulate enormous amounts of information. You build sophisticated maps. You create increasingly complex models. You catalog everything. But you stop asking whether the map corresponds to the terrain. This is the reality of our contemporary civilization.
The other is to become ontologically hyper-developed without developing the epistemological ability to evaluate the map. You build elaborate cosmologies. You construct mythologies. You map the stars. You develop symbolic systems. But you lack the cognitive ability to determine whether the inherited map still corresponds to the reality you are currently experiencing. Many ancient civilizations fell into this trap.
Both situations can produce blind trust.
EPISTEMOLOGICAL EXCESS
│
↓
enormous map
│
X
terrain ignored
ONTOLOGICAL EXCESS
│
↓
elaborate structure
│
X
context ignored
The answer is not to choose one side. The answer is to reunite them.
Faith is not supposed to be blind
Every person has a boundary between what they know and what they do not know. That boundary moves constantly.
KNOWN
████████████████│░░░░░░░░░░░░░░
↑
knowing/unknowing boundary
The question is what you trust at that boundary. Do you trust whatever the surrounding group currently agrees upon? Do you become apathetic and deny naming the coherence you are experiencing at hand because the parent cannot yet be pointed to?Do you surrender to whatever inherited map is closest at hand? Or do you prioritize coherence and remain oriented toward an objective reference even while your knowledge is incomplete?
This is where faith belongs. Faith is trusting coherence at the boundary between knowing and unknowing. It means prioritizing objectivity over intersubjectivity or any incoherence so that brute force is kept at bay. It is having the wherewithal to bind the coherence you are experiencing towards a yet to be identified parent by positioning it as singular, external, independent, invariant, nonderivative, and universal to the coherence you are experiencing in order to maintain a coherent map of reality. The parent is yet to become a member of the set, but in the interim, the terminus parent will stand in its place as an anchor to ensure the system remains coherent. That is different from believing something merely because it cannot be proven.
Faith is supposed to involve trust in something stable and reliable within a dynamic reality that is constantly changing. A compass does not tell you where every wave will be. It tells you how to remain oriented while the waves change. It has the advantage between remaining in an internalized mindset versus regaining an observer mindset to be present and problem solve.
Within the context of reality and the universe, the compass is not a physical object. It is understood ontologically. Those six conditions give you a way to interpret the sea of noise without allowing the noise to become chaos.
Faith without a compass is blind faith, and blind faith is vulnerable to manipulation.
How confusion becomes leverage
If you can complicate someone’s ability to move between internalization and observation, you make them easier to steer. If you can obscure the parent node, you make them dependent upon whatever local authority claims to possess it. If you can make a mythology indistinguishable from the underlying structure, you can direct attention toward the map rather than the terrain. If you can make consensus appear to be objective coherence, you can turn agreement into authority. And if you can make people believe that something cannot be true until its ultimate parent has been physically observed, you can delegitimize coherence that is already being experienced.
None of these mechanisms requires the person using them to understand the entire system. They only require a structural advantage. Even a temporary advantage matters.
If you can make someone abandon their observing position for a moment and become completely internalized, you have changed the conditions under which they are processing the system. That can be enough to redirect them.
This is why learning to recognize the graph matters. This is why systems thinking matters. You want to be able to notice:
Where is the parent?
What makes this relationship binding?
Is this coherence or consensus?
Is the parent objective (does it fit those six conditions in this context) or intersubjective?
Is the hierarchy legitimate or arbitrary?
Is the map being mistaken for the terrain?
Is brute force being used to compensate for incoherence?
Can the model correct itself without destroying the nodes inside it?
These questions turn systems thinking into a practical skill.
Seeing the system is not the same as owning the system
There is one final question. Suppose you actually develop this ability. Suppose you can zoom in and out. Suppose you can recognize the parent-child relationships. Suppose you gain the ability to easily distinguish coherence from consensus. Suppose you can recognize incoherence before everyone else does.
What are you going to do with that ability?Are you trying to help everyone win? Or are you trying to come out on top?
That question is more structural than it initially appears. If you use systems thinking to position yourself permanently above everyone else, you eventually have to preserve that position.
You (A)
│
│
┌──────┼──────┐
B C D
The longer A remains permanently dominant, the more effort is required to protect A’s position. The system becomes increasingly dependent on force. But if the system remains fluid:
A
│
┌─────┼─────┐
B C D
↓
C
│
┌─────┼─────┐
A B D
↓
D
│
┌─────┼─────┐
A B C
the position can change without destroying the underlying structure. Everyone remains part of the system. The point is not to eliminate the top position. The point is to prevent the top position from becoming an object of permanent ownership.
If your goal is to help everyone participate in a coherent system, you have an incentive to preserve the structure that makes everyone’s participation possible. If your goal is simply to get ahead, you may reach extraordinary heights by exploiting the structure around you. But the position you gain by making the system less coherent becomes increasingly expensive to maintain.
Eventually the terrain pushes back. Reality will not follow the model you are trying to maintain. The fall can be as steep as the climb. This is why the objective position is not simply the position that gives you the most power. It is the position that remains accountable to what is ultimately real. None of us can actually stand in the objective terminus position. We will never hold the universe in our hand and observe it like a ball no matter how proficient of a systems thinker we may become.
Becoming a systems thinker
Systems thinking begins with a simple realization, that nothing exists in isolation. Every node exists within relationships. Those relationships exist within larger relationships. Those larger systems exist within still larger systems. And every node, even if seeemingly irreducible, is further reducible to objective identity.
You are one node within the system you are trying to understand. You cannot step outside the universe and hold it in your hand. But you can learn to approximate that perspective.
You can learn to zoom in. You can learn to zoom out. You can learn to distinguish nodes from relationships. You can learn to identify parents and children. You can learn to recognize legitimate hierarchy without confusing hierarchy with permanent superiority. You can learn to distinguish consensus from coherence. You can learn to identify intersubjective parents. You can learn to recognize incoherence before it becomes brute force. You can learn to distinguish the map from the terrain. And you can learn to recognize the difference between having a model of reality and having an objective reference against which the model can be corrected.
A practical systems thinker therefore keeps asking:
What are the nodes?
↓
What are their relationships?
↓
What constrains those relationships?
↓
What is the parent?
↓
Is the parent actually independent?
↓
Is this coherence or consensus?
↓
Can I zoom in?
↓
Can I zoom out?
↓
Does the structure remain coherent at another level?
↓
What happens when the model is wrong?
↓
Can the system correct itself without brute force?
↓
Am I preserving the system or exploiting it?
The goal is not to become detached from reality. It is the opposite. The goal is to become sufficiently present to reality that you can recognize when your map has stopped matching the terrain. And the more capable you become at seeing the whole system, the more important your intention becomes.
You can use systems thinking to manipulate people. You can use it to accumulate power. You can use it to find weaknesses and exploit them. Or you can use it to understand how the pieces fit together so that the system remains coherent for everyone inside it.
The latter requires a particular kind of humility. You are still a node. You are not the whole graph. You can zoom out, but you never become external to the universe. You can improve your map, but you never become the terrain. You can recognize the parent, but you do not become the parent.
The point of systems thinking is therefore not to place yourself above the system. It is to become capable of seeing your place within it.
The closer you come to seeing the whole system, the more important it becomes to remember that you are still part of it.