Before we start, a boundary.
This is not a medical theory. It is not a diagnostic framework. It is not a claim about how every mind or body works.
Medica Ontologica is a field guide of models.
That is the safest way to hold it.
Not final explanations. Not proof. Not a replacement for medicine, psychology, neuroscience, or lived experience.
Models.
Ways of looking at parts of being human that are often hard to explain from the inside and easy to misread from the outside.
This first volume is about performance.
Not performance in the motivational sense. Not productivity. Not optimisation. Not how to get more out of yourself.
Something simpler than that.
Why what a person can do, what they try to do, and what actually happens are often different things.
That difference matters because a lot of human judgement happens at the level of outcome. Someone succeeds, so we assume ability. Someone fails, so we assume lack. Someone starts, so we assume motivation. Someone does not start, so we assume refusal.
Sometimes that is fair.
Often it is too clean.
There is usually more in the system than the result shows.
A person may understand something and still be unable to explain it. They may care deeply and still be unable to begin. They may be highly capable in one context and almost unusable in another. They may seem inconsistent from the outside while internally following a pattern that has never been named properly.
That is the space this volume sits in.
The point is not to excuse every outcome. Outcomes still matter. Reality still matters. If something did not happen, it did not happen.
The question is what kind of system produced that result.
Was the problem ability?
Was it access?
Was it load?
Was it timing?
Was it friction?
Was it a mismatch between the task and the operating state of the person trying to do it?
Those questions are not softer than judgement. They are sharper. They ask where the failure actually happened instead of placing it automatically inside the person.
The models in this volume are deliberately simple.
A shoebox with something complex inside it.
A high-spec computer struggling under background load.
A hard game running on a system that should be powerful but keeps stuttering.
A team of huskies pulling in too many directions at once.
None of these are the truth.
They are lenses.
Each one preserves a different part of the same problem: performance is not a clean window into ability. It is what ability looks like after access, pressure, energy, environment, timing and load have already shaped it.
That is the frame.
Not “why people fail.”
Not “why smart people struggle.”
Not “how to fix yourself.”
A quieter question:
What changes when we stop treating performance as a simple measure of what someone had available?
The Strange Case of Missing Ability
One of the reasons I became interested in these kinds of models is that I kept running into a particular kind of contradiction.
The contradiction is simple.
People often seem to possess abilities they cannot reliably access.
Most of us have experienced some version of this.
You leave a conversation and suddenly think of the perfect response.
You understand a topic well until somebody asks you to explain it.
You sit down intending to work and discover that something which felt straightforward an hour ago now feels strangely inaccessible.
You remember the answer after the exam.
You find the words after the argument.
You solve the problem after the deadline.
The ability appears.
Just not when it was needed.
This creates an odd situation.
From the outside, it can look as though the ability was never there. The evidence seems obvious. If somebody understood the material, surely they would have explained it. If they knew the answer, surely they would have written it down. If they were capable of doing the work, surely the work would have been completed.
That logic is understandable.
It is also where many misunderstandings begin.
Because it assumes that possessing something and accessing something are the same process.
They are not.
A book can exist on a shelf without being open.
A file can exist on a computer without being loaded.
A memory can exist without being immediately available.
The existence of something and access to something are related, but they are not identical.
That distinction sounds obvious when applied to objects.
It becomes surprisingly difficult to remember when applied to people.
Part of the problem is that access failures often look exactly like ability failures from the outside. Both produce the same visible outcome.
The answer is not given.
The task is not completed.
The words do not arrive.
The action does not happen.
The difference exists inside the system rather than outside it.
This volume is largely about that difference.
Not because access is the only thing that matters.
Sometimes the limitation genuinely is knowledge.
Sometimes it genuinely is skill.
Sometimes the answer really is that more learning, more practice, or more experience is required.
But there are also situations where the ability is already present and the difficulty lies somewhere between the ability and its expression.
Those situations are harder to see.
They are also the situations many people struggle to explain.
The first model in this volume starts from exactly that problem.
The Shoebox
One way I sometimes think about this problem is through a shoebox.
Imagine there is a complex object inside it.
Not a simple object. Something intricate. A structure with lots of parts, relationships, and connections. The sort of thing that only really makes sense once you can see it all together.
Now imagine the box is closed.
You cannot open it.
The only access you have is a small hole cut into one side.
That changes the problem completely.
The structure inside the box has not changed. It has not become simpler or more complicated. Nothing has been added and nothing has been removed. The only thing that has changed is your access to it.
Instead of seeing the whole thing, you see fragments.
A corner.
An edge.
A connection.
A shadow of something larger.
Over time you begin building an internal picture of what might exist inside. Sometimes that picture is accurate. Sometimes it is not. Sometimes you can sense the shape of the thing long before you can describe it properly.
I think many people have experienced something similar in their own thinking.
There are moments when you know you understand something, but the understanding arrives as shape rather than language. You can navigate it. You can work with it. You can often recognise when something fits or does not fit. Yet when somebody asks for a clean explanation, it feels as though the understanding retreats back into the box.
The common assumption is that explanation and understanding are the same thing.
The shoebox suggests otherwise.
It suggests that understanding may exist at one level while access exists at another.
A person may possess a structure without possessing a clear route to it.
That possibility matters because many of our systems quietly assume the opposite.
Schools often reward explanation.
Interviews reward explanation.
Meetings reward explanation.
Assessments reward explanation.
In each case, what is being measured is not simply whether something exists inside the box. It is whether a sufficiently large opening exists between the structure and the outside world.
Most of the time those two things overlap.
Not always.
Sometimes a person has a small structure and excellent access.
Sometimes they have a large structure and poor access.
Sometimes they have both.
Sometimes they have neither.
From the outside, these situations can look surprisingly similar.
The person who understands something deeply but cannot express it fluently may be judged in much the same way as the person who genuinely does not understand it.
The outcome appears identical.
The internal reality may be very different.
That does not mean every failure to explain is hidden brilliance. Sometimes confusion is simply confusion. The shoebox is not a defence against criticism or evidence.
It is a reminder that expression and possession are not identical processes.
The thing inside the box and the route into the box are different objects.
Once you begin looking for that distinction, it starts appearing in more places than you might expect.
The High-Spec PC
The Shoebox solves one problem.
It explains how somebody can possess understanding without being able to express it cleanly.
What it does not explain is why access seems to change.
Why does the hole sometimes feel larger?
Why does it sometimes feel smaller?
Why can the same person explain something perfectly one day and struggle with it the next?
Most people have experienced this.
There are days when everything feels available.
Thoughts arrive easily. Connections appear naturally. Conversations flow. Problems that seemed complicated yesterday become manageable. The system feels responsive.
Then there are other days.
You read the same sentence three times.
Simple decisions feel strangely expensive.
A conversation requires more effort than it should.
The things you know are still there, but reaching them feels slower.
Nothing obvious has changed.
Yet something clearly has.
One way I think about this is through a computer.
Not because people are computers.
They are not.
The comparison is useful because most people have experienced a powerful machine behaving as though it were weak.
You buy a laptop.
The processor is excellent.
The graphics card is excellent.
The memory is more than sufficient.
On paper, everything looks capable.
Then six months later it feels slow.
Applications take longer to open.
Simple tasks become frustrating.
Everything feels heavier.
The first instinct is often to assume the machine has somehow become worse.
Sometimes that is true.
Often it is not.
The processor is still the processor.
The memory is still the memory.
The hardware has not fundamentally changed.
What has changed is what the system is carrying.
Background applications accumulate.
Storage becomes crowded.
Updates run silently.
Resources become fragmented.
Heat builds.
The machine spends increasing amounts of effort maintaining itself before it can begin helping you.
Performance changes even when capability does not.
That distinction matters.
Because many people describe themselves as though they have become less capable when what they are actually describing is increased load.
Pain is load.
Stress is load.
Poor sleep is load.
Uncertainty is load.
Illness is load.
Sensory overload is load.
Grief is load.
Responsibility is load.
The important thing is not that these things make performance impossible.
The important thing is that they consume resources before the task even begins.
Two people may sit down to do exactly the same piece of work.
One begins with most of their resources available.
The other begins after spending half the day compensating for things nobody else can see.
The task is identical.
The starting position is not.
This is one reason human performance can be so difficult to interpret from the outside.
We see what the system produced.
We rarely see what the system had to carry beforehand.
The language people often reach for is motivation.
Sometimes motivation matters.
But motivation is a strange explanation for many of these situations.
Most people do not need additional motivation to get out of a burning building.
Most people do not need additional motivation to stop chronic pain.
Most people do not need additional motivation to remember something important.
The desire already exists.
The difficulty lies elsewhere.
A system under sufficient load can possess the intention to act while lacking the available resources required to express it effectively.
That is not laziness.
It is not weakness.
It is not a moral category at all.
It is a description of a system operating under conditions.
The computer analogy has limits.
People are not machines.
People adapt.
They compensate.
They learn.
They change their environments.
They influence their own operating conditions.
Computers are useful here for one reason only.
They make visible something that is often ignored when discussing people.
Performance is not determined solely by what a system can do.
It is also shaped by what the system is already carrying.
That distinction becomes important once we start thinking about effort.
Because effort turns out to be one of the easiest things to observe badly and one of the hardest things to measure well.
The Hard Game
There is a particular kind of misunderstanding that appears whenever people talk about effort.
The misunderstanding comes from the fact that effort is largely invisible.
Outcomes are visible.
Time is visible.
Results are visible.
Effort is not.
If two people complete the same task, it is tempting to assume they paid roughly the same price to get there. Sometimes that is true. Often it is not.
Imagine two people playing the same game.
The rules are identical.
The map is identical.
The enemies are identical.
The objective is identical.
From a distance it appears fair.
Then you notice one small difference.
One person is playing on normal difficulty.
The other is playing on hard mode.
Enemies hit harder.
Resources are scarcer.
Mistakes are punished more heavily.
Recovery takes longer.
The destination has not changed.
The cost of reaching it has.
This matters because many people spend large parts of their lives comparing outcomes while remaining blind to difficulty settings.
A student submits an assignment.
An employee finishes a project.
A parent gets through the week.
A friend turns up to an event.
The visible outcome exists.
The invisible cost rarely does.
Sometimes a person who appears to be underperforming is simply operating in a more expensive environment.
Pain increases cost.
Fatigue increases cost.
Uncertainty increases cost.
Anxiety increases cost.
Sensory overload increases cost.
Illness increases cost.
Financial pressure increases cost.
The task remains the same.
The price changes.
This is one reason comparison becomes so unreliable.
We often compare achievements while ignoring operating conditions.
We compare scores without comparing difficulty settings.
The result is a picture that looks objective but contains only part of the story.
The point is not that outcomes stop mattering.
The point is that outcomes are not the only thing that matters.
A difficult victory and an easy victory may look identical from the outside.
A difficult survival and an easy survival may also look identical.
The difference is carried by the person who lived through it.
One way to think about performance is to ask not only what happened, but what it cost.
Sometimes the most important information about a system is not where it arrived.
It is how much had to be spent to get there.
The Husky Team
One of the strangest experiences a person can have is wanting several incompatible things at the same time.
You want to work.
You want to rest.
You want to leave.
You want to stay.
You want certainty.
You want freedom.
You want change.
You want stability.
None of these desires are necessarily irrational.
The difficulty is that they do not always point in the same direction.
Most descriptions of behaviour quietly assume a single decision-maker.
A single self.
A single intention.
A single direction of travel.
That picture is useful.
It is also often incomplete.
One way I think about this is through a team of huskies.
Imagine a sled being pulled by several dogs.
Each dog is strong.
Each dog is trying to help.
Each dog is responding to something real.
The problem is that they do not always agree on where to go.
One notices danger.
One notices opportunity.
One notices exhaustion.
One notices curiosity.
One notices responsibility.
One notices reward.
If all the dogs pull together, the sled moves quickly.
From the outside this looks like motivation, discipline, confidence, or clarity.
If the dogs pull in different directions, movement becomes difficult.
Progress slows.
Energy is spent.
The sled may barely move at all.
From the outside this often looks like laziness, indecision, inconsistency, or lack of commitment.
From the inside it can feel very different.
It can feel like being pulled by multiple valid priorities at the same time.
Part of you wants to start.
Part of you wants more information.
Part of you wants to recover.
Part of you wants to avoid risk.
Part of you wants the reward.
Part of you wants to avoid the cost.
The stronger the conflict, the more energy is spent negotiating between directions.
This is one reason awareness does not always create action.
People often assume that once the correct answer is known, behaviour should follow automatically.
In reality, knowing where to go and having all the dogs agree to move there are different problems.
The Husky Team is not a model of personality.
It is not a theory of cognition.
It is simply a reminder that internal conflict is not always evidence of weakness.
Sometimes it is evidence that several parts of a system are responding to different pressures at the same time.
The question is not which dog is “correct”.
The more useful question is often:
Which direction is each dog responding to?
And what happens when they are finally able to pull together?
Closing Thoughts
The models in this volume are deliberately simple.
A shoebox.
A computer.
A difficult game.
A team of huskies.
None of them are intended to be literally true. They are tools. Ways of making certain experiences easier to see.
The Shoebox asks whether something can exist inside a system without being easily accessible.
The High-Spec PC asks what happens when a capable system is already carrying a substantial amount of background load.
The Hard Game asks what happens when two people face similar tasks under very different operating conditions.
The Husky Team asks what happens when multiple valid priorities pull in different directions at the same time.
They are different models.
They are all pointing at a similar observation.
Human beings are often judged by outcomes while living through conditions.
The outcome is visible.
The conditions usually are not.
That does not mean outcomes stop mattering. It does not mean every difficulty is hidden brilliance. It does not mean every struggle is evidence of untapped potential.
The claim is narrower than that.
Sometimes what appears to be a problem of ability is actually a problem of access.
Sometimes what appears to be a problem of motivation is actually a problem of load.
Sometimes what appears to be a problem of character is actually a problem of competing demands.
Sometimes it is not.
The difficulty is that these situations can look remarkably similar from the outside.
That is why models can be useful.
Not because they provide answers.
Because they improve questions.
Instead of asking:
“Why can’t this person do it?”
we might ask:
“What is standing between the person and the thing they are trying to do?”
Sometimes the answer will still be knowledge.
Sometimes it will still be skill.
Sometimes it will still be practice.
But not always.
And if there is a theme running through this volume, it is probably that.
Human experience is often easier to understand once we stop treating performance as a direct window into capacity.
The distance between what a person possesses and what they can express is rarely empty.
Something lives in that space.
Load.
Friction.
Conflict.
Timing.
Access.
History.
Constraint.
The next volume turns toward one of the places that space becomes most visible.
Memory.
Not memory as storage.
Not memory as a recording.
Memory as something stranger.
Something reconstructed, revisited, compressed, forgotten, rediscovered, and continually rewritten by the act of remembering itself.
However, the models in this volume are not complete i’ve kept them light intentionally, so i can explore the breadths of them in pieces dedicated so keep tuned for those as well.