A framework for understanding how systems — biological, cultural, technological, institutional — meet futures beyond what they were designed for.
Someone included what the system was previously designed to exclude, and the system got better for everyone.
No individual can hold all the context needed for complex decisions. The future always contains information we don't have yet.
Every system eventually encounters something it wasn't designed for. The question is whether it breaks or adapts.
FC is a tool for understanding what makes worldviews work — and how they can work for more people. When communities share frameworks for integrating perspectives, they collectively hold more context than any member can alone. Forward compatibility asks what else might be true.
Forward compatibility started as an engineering concept — the structural property that lets a system handle input that doesn't exist yet. But the same pattern appears across biology, language, institutions, and culture. Wherever systems persist across time, the ones that can integrate what they weren't originally designed for tend to outlast the ones that can't.
Don't break when you encounter something unfamiliar. HTML renders what it can and skips unrecognized tags — it doesn't reject the whole page. A person hearing a new word continues the conversation rather than stopping it.
Two systems find the best shared capability. USB devices handshaking to the highest speed they both support. Two people code-switching to a shared language.
Design for inputs you can't predict. TCP's options field reserves space for future capabilities the original designers couldn't foresee. Grammar is broad enough to accept vocabulary that hasn't been coined. JSON — the format most of the web uses to exchange data — lets any new field appear without breaking the systems already reading it.
Older systems get a complete but less rich experience. JPEG base layer readable by old decoders while new decoders get enhancement layers. Innate immunity handling anything imprecisely while adaptive immunity adds precision.
Don't just skip or preserve unfamiliar input — learn from it. The immune system's memory cells remember every pathogen they've encountered and respond faster the next time. A person who encounters a new word enough times doesn't just know a new word — they can think thoughts they couldn't think before.
Systems that developed together break when separated. Melbourne's trams and urban density. Indigenous polyculture — the Three Sisters co-evolved to support each other. Separating them into monoculture rows loses what makes each one thrive.
The capacity to keep the system alive has to itself be forward compatible. Ise Shrine's apprenticeship cycle — 1,300 years of renewal. Libraries depending on political funding cycles.
A technology isn't finished when it works. It's finished when you can describe the living system it enters — and how to tend that system's health while using it. Antibiotics shipped without microbiome guidance. Social platforms launched without guidance on what they do to attention, trust, and community. The technology "worked"; the ecology it entered was left untended.
Care compounds with no diminishing returns.
A working tool — not just a way to describe systems, but a way to evaluate, compare, and design them.
Humans need shared frameworks that provide orientation, meaning, and priorities. Religions, constitutions, scientific paradigms, and cultural traditions all fill this need. FC describes the pattern they share when they work well, and offers a framework for building new shared understanding across difference.
Makes unrelated things visible as the same phenomenon. The immune system and HTML parsing are doing similar structural work in different substrates. Insights from one field become actionable in another.
Gives you specific, answerable questions to ask of any system. Does it handle what it doesn't yet understand? Does it have room for what doesn't exist yet? Does it protect the relationships that make it work?
Hold any two systems next to each other. Melbourne kept its trams, American cities ripped theirs out. The HGP opened its data, Celera kept it proprietary.
Walk up to any system and ask: what's the interface, where's the capacity, is there room for the unknown, what's the renewal mechanism, what's fragile?
If the flexibility hasn't been exercised, it's probably ossifying. If the renewal mechanism depends on something fragile, you can see the vulnerability before it collapses.
Leave room. Make the interface stable but extensible. Protect co-evolved relationships. Exercise your flexibility or lose it. Ship stewardship alongside the system.
An engineer, a linguist, an immunologist, and an urban planner are all doing versions of the same thing but can't talk to each other about it. FC gives them shared vocabulary.
Most people think progress means new things replacing old things. The best progress is when systems expand — when contact with the future makes things more capable rather than obsolete.
You don't notice the USB negotiation, the browser skipping unknown tags, grammar handling a new word. FC reveals the design decisions behind the seamless experience.
The examples aren't cherry-picked success stories — they're a pattern that appears independently across biology, engineering, culture, and institutions. Systems that build room for the unknown tend to outlast systems that close down. That's not a wish. It's a structural observation.
Different domains, but a recognizable pattern across all of them.
CBS built a technically superior color system that was incompatible with 28 million existing black-and-white sets. NTSC won because it was forward compatible — old TVs could still display the signal. The better technology lost to the more compatible one.
Japan's Ise Shrine has been rebuilt every 20 years for over a millennium. The structure changes; the knowledge of how to build it transfers across generations through apprenticeship. The renewal mechanism is itself forward compatible — tokowaka, "eternal youth through renewal."
Across the Americas, many peoples practiced polyculture agroforestry at landscape scale — interplanting diverse species in ways that were often not recognized as agriculture by colonizers whose frameworks defined farming as monoculture rows. Monoculture optimizes for one known output — efficient short-term, catastrophically fragile. Polyculture includes diversity that lets the system absorb shocks, cycle nutrients, and sustain itself across generations.
Melbourne kept its trams. American cities ripped theirs out. The trams co-evolved with urban density, walkability, and street life. Removing them didn't just lose transit — it broke a web of relationships that had developed together.
Traditional vaccination was deliberate but bespoke — each vaccine designed for one pathogen. The mRNA platform is deliberate and modular — the delivery system stays stable while the payload changes.
Curb cuts were designed for wheelchair users. They turned out to help everyone — parents with strollers, delivery workers, cyclists, travelers with luggage. Including what was excluded made the system better for everyone.
After crashes caused by captains who couldn't be questioned, aviation redesigned cockpit culture to include the co-pilot's perspective by default. Including what hierarchy excluded — dissenting input — made the system dramatically safer.
Technologies increasingly work with living systems — editing genomes, cultivating microbiomes, managing ecosystems. You can't "deploy" a microbiome. You cultivate it.
The mechanical vocabulary was precise for machines, but it closed off categories of responsibility that ecological work has always required. "Tend the living system this enters" was always part of farming, fermentation, and medicine — it just wasn't part of the prestige vocabulary.
Experience the full vocabulary →
Forward compatibility is not free. The costs are real and worth naming.
Postel's Law ("be liberal in what you accept") has a real critique: systems that are too tolerant can entrench flaws that become impossible to fix. TLS downgrade attacks exploit graceful degradation. Compatibility has costs, and naming them honestly is part of the work.