The Portability Trap: Why Good Systems Need Both Freedom and Equilibrium

Hatched by Kevin

Jun 27, 2026

10 min read

2 views

78%

The hidden question behind every system you build

What if the real problem with knowledge systems, strategy, and even decision making is not that we choose the wrong tool, but that we expect one tool to solve two incompatible problems at once?

That is the tension sitting underneath both personal note systems and game theory. In one world, you want your notes to be portable, editable, and future proof. In the other, you want to understand how rational agents settle into stable patterns when each one is responding to the other. In both cases, the temptation is the same: find a universal representation that makes everything neat. But neatness often hides fragility.

Markdown promises simplicity and portability. Game theory promises a clean model of behavior without peering into people’s heads. Yet both run into the same limit: a system can be easy to move, or easy to optimize, but rarely both without tradeoffs. The deeper lesson is not about files or players. It is about how stability emerges when the underlying world is messy, interactive, and full of hidden assumptions.

The best systems do not eliminate friction. They place friction where it is cheapest and remove it where it is most dangerous.

That sentence could describe a note vault, a market, a negotiation, or a repeated game. The question is where to let structure harden, and where to keep things soft enough to adapt.

Markdown and Nash equilibrium: two answers to the same fear

Markdown exists because people learned that rich text can become a trap. A document that looks perfect in one app may become a broken, ugly, or uneditable artifact elsewhere. Plain HTML saved from a WYSIWYG editor may preserve images and links in the moment, but it can become painful to edit later. Markdown is valuable because it strips content down to a form that can survive migration, conversion, and reuse.

Game theory, in a very different domain, solves a similar problem. It refuses to explain behavior by looking inside people’s minds, because minds are hard to model and easy to fictionalize. Instead, it looks at choices, preferences, and interactions. Nash equilibrium gives a stable description of what happens when each person is doing the best they can, given what they expect others to do.

At first glance, these seem unrelated. One is about notes. The other is about players. But both are strategies for surviving uncertainty.

Markdown says: preserve the essence of the content, not the decorative surface.

Nash equilibrium says: preserve the logic of incentives, not speculative psychology.

Both make a sacrifice in exchange for robustness. Markdown gives up perfect visual fidelity. Game theory gives up rich internal explanation. That is not a flaw. It is the price of a model that can travel across contexts.

The deeper connection is this: both Markdown and game theory are built around the idea that the most useful representation is not the most expressive one, but the one that remains stable when moved into new environments.

Consider a note vault. If your notes are trapped in a proprietary format, the system may feel elegant until the day it is not. If your strategy model depends on assumptions about personalities rather than incentives, it may feel insightful until it fails in a new scenario. In both cases, portability is a form of epistemic humility. It admits that the future will not preserve the conditions under which the system was created.

Why elegance can be a trap

The temptation to overfit is everywhere. WYSIWYG editors can make documents look polished, just as narrative theories of behavior can make human action seem legible. But polish is not the same thing as resilience.

Imagine two notebooks. The first is a beautifully formatted notebook exported from an app that uses hidden structure, custom metadata, and rich text widgets. The second is plain text with simple Markdown links and image references. The first is prettier today. The second is easier to open, edit, grep, version, convert, and rescue ten years from now.

Now imagine two explanations of why two firms settle into a pricing pattern. The first says one CEO is aggressive, another is cautious, and both have deep psychological quirks. The second says each firm is best responding to the other under a particular payoff structure. The first may feel more vivid. The second is more portable.

This is where the analogy becomes powerful: simplicity is not the same as shallowness. Markdown is simple because it encodes only what matters for reuse. Nash equilibrium is simple because it encodes only what matters for strategic stability. In both cases, the stripped down representation can reveal deeper structure precisely because it refuses to clutter itself with decorative detail.

But simplicity has a second edge. A system can become too minimal to capture the forces that actually matter.

Markdown can represent a link, but it cannot by itself guarantee that the linked file will remain meaningfully organized. Game theory can represent strategic interaction, but it can flatten emotion, habit, history, and institutional power into payoffs. So the true challenge is not choosing simplicity over richness. It is deciding what kind of richness belongs inside the system and what kind belongs outside it.

That is the hidden art in both domains.

Good systems do not try to contain reality. They create a stable interface with reality.

Markdown is an interface between ideas and future tools. Nash equilibrium is an interface between individual actions and collective outcomes.

The equilibrium of a personal knowledge system

A personal knowledge system is often treated like a library problem. In reality, it is a strategic problem. Every note format is a bet on the future: future software, future habits, future retrieval needs, future collaboration, future migration. The system must be useful now, but also robust against unknown conditions later.

This is why the file format debate is more profound than it appears. If your notes live in a format that only one app can read well, you are effectively entering a dependency relationship. The app becomes a player in your system. Its incentives may not align with yours. It may optimize for convenience today at the expense of access tomorrow.

Markdown changes the game by making the content legible across tools. Obsidian’s file linking and image embedding underscore this point: a note vault can function as a graph without requiring path-heavy complexity. A file can move, yet remain findable by its name. An image can be embedded without dissolving the meaning of the note.

That is not just a technical convenience. It is a design philosophy. The system treats the identity of an item separately from the presentation of that item.

This distinction matters everywhere. In knowledge work, it means your content should outlive your app. In strategy, it means your best response should not depend on an overly specific model of the opponent’s personality. In both cases, durable structure comes from reducing dependence on brittle assumptions.

Here is a useful mental model: think of every system as having two layers.

The invariant layer: what must survive change.
The expressive layer: what can be sacrificed or reconstructed.

In a note system, the invariant layer is the text, links, and relationships. The expressive layer is the editor chrome, layout, and aesthetic polish.

In a strategic setting, the invariant layer is the payoff structure and incentive compatibility. The expressive layer is the story players tell about each other, their moods, and their self narratives.

Most systems fail when they confuse these layers. They preserve what should be fluid and harden what should remain portable.

Mixed strategies are the strategic version of good metadata

Mixed strategies can sound counterintuitive because they ask us to accept randomness as rational. But that is only paradoxical if we assume rationality means always choosing the same visible action. In many strategic settings, uncertainty itself is a tool.

A player randomizes when no pure strategy dominates, or when predictability would be exploited. Matching Pennies is the classic example. If one side becomes too regular, the other side wins by adapting. So the stable solution is not a fixed move, but a distribution over moves.

That is deeply similar to how good note systems work. A folder structure that is too rigid becomes brittle. A format that is too locked into one workflow becomes easy to break. A little randomness, or at least flexibility, can be a feature. You may tag notes in overlapping ways rather than forcing them into one taxonomy. You may link across projects instead of confining content to rigid silos. You may keep the representation lightweight so the content can be remixed later.

This is the hidden lesson of mixed strategies: stability does not always mean predictability.

In fact, some systems are most stable when they are partially indeterminate. That indeterminacy can prevent exploitation, preserve optionality, and make the whole structure more resilient. A well designed personal knowledge system often works the same way. It does not overcommit to a single path of retrieval. It keeps multiple avenues open: search, links, tags, backlinks, graph navigation, and plain text inspection.

The analogy can be pushed further. In game theory, a mixed equilibrium emerges when each player is indifferent at the margin. In a knowledge system, a robust workflow emerges when your future self is indifferent between tools because the content remains accessible regardless of interface. The best format reduces lock in. It makes switching less costly. That is a kind of strategic indifference, and it is valuable.

A resilient system is one where no single surface behavior can trap the underlying value.

That is true for game strategies, and it is true for file formats.

A practical framework: optimize for moveability, not for prettiness

The real synthesis here is a design principle for both thinking and building: optimize for moveability.

Moveability means your notes, ideas, models, or strategies can survive being placed in a different environment without collapsing. It is the opposite of overfitting to the present tool, present opponent, or present mood.

You can test moveability with a simple set of questions:

If I changed tools tomorrow, what would still be usable?
If my assumptions about the other side were wrong, what would still be true?
If I had to explain this to someone else, what is the irreducible core?
If I revisited this a year later, would the system still make sense?

These questions apply to note taking, planning, negotiations, and decision making. They force you to separate essential structure from accidental convenience.

For a PKMS, this may mean plain text files, stable links, and minimal reliance on proprietary features. For strategy, it may mean thinking in terms of incentives, commitments, and best responses rather than personalities alone. For life planning, it may mean building routines that work even when motivation fluctuates, rather than assuming a permanent state of enthusiasm.

The crucial insight is that durability often comes from reducing dependence on exact conditions. Markdown reduces dependence on a specific rendering engine. Nash equilibrium reduces dependence on a specific narrative of intention. Both are ways of saying: do not bet everything on the surface.

There is still room for richness. The most interesting systems are not bland. They are layered. They preserve a simple core while allowing expressive growth around it. A note vault can contain images, links, headings, and embedded references. A strategic model can incorporate bounded rationality, learning, and repeated play. But these additions work best when they sit on top of a stable base.

Key Takeaways

Choose representations that survive change. If a system only works in one app, one mindset, or one context, it is more fragile than it looks.
Separate the invariant from the expressive. Preserve what must endure, and keep presentation, workflow, or narrative flexible.
Treat randomness as a tool, not a flaw. Mixed strategies show that unpredictability can create stability when predictability invites exploitation.
Prefer incentive structure over personality mythology. In strategic situations, focus first on payoffs and constraints, not just stories about motives.
Design for future self, not just present self. A system that your future self can still understand is more valuable than a polished system that only feels good now.

The real lesson: stability is not sameness

We often confuse stability with repetition. We think a system is stable if it looks the same every day, if the file format is fixed, if the strategy is consistent, if the output is predictable. But the deeper lesson from both note systems and game theory is the opposite.

True stability is the ability to remain functional under change. It is the power to preserve meaning while altering surface form. Markdown does this by keeping content portable. Nash equilibrium does this by identifying a state where no one has an incentive to deviate, given the others. In both cases, what looks like simplicity is really resilience.

That reframes how we should build, write, and decide. Do not ask only whether something is elegant today. Ask whether it can travel. Ask whether it can survive a new app, a new collaborator, a new incentive structure, a new version of yourself.

Because the most valuable systems are not the ones that look complete in the moment. They are the ones that still make sense after the world has changed around them.