What does it mean that legacy and sustainability?

A legacy that depends on your continued effort is fragile — build self-sustaining contributions.

Example: In 1991, Linus Torvalds wrote the first version of the Linux kernel as a personal project — a hobby operating system for his new PC. He could have maintained it as a personal codebase, making every architectural decision himself, reviewing every contribution, remaining the single point of control and failure. Instead, over the following years, he built something structurally different: a distributed development model where thousands of contributors could work independently, where subsystem maintainers held real authority over their domains, where the contribution process itself — patch submission, review, merge — was documented and reproducible by anyone. He created a governance structure (the 'benevolent dictator' model with delegated lieutenant maintainers) that distributed decision-making rather than concentrating it. He built Git — an entire version control system — specifically to support decentralized collaboration at scale. Today, Linux runs on everything from smartphones to supercomputers to Mars rovers. Torvalds still contributes, but the system does not depend on his continued effort. When he took a leave of absence in 2018 for personal reasons, the kernel development process continued without interruption. That is the difference between a contribution and a sustainable legacy: one requires your presence, the other has outgrown it.

Try this: Select the legacy contribution you care about most — the one you identified in your legacy statement (L-1469) or refined through legacy revision (L-1478). Now conduct a sustainability stress test. First, write a one-paragraph description of what would happen to this contribution if you disappeared tomorrow — not died, just became completely unavailable for twelve months. Be brutally honest. Would it continue functioning? Would it grow? Would it slowly decay? Would it collapse immediately? Second, identify every point of single-person dependency: decisions only you can make, knowledge only you hold, relationships only you maintain, resources only you provide. These are your fragility points. Third, for each fragility point, design one structural change that would distribute that dependency — a documented process, a trained successor, a self-funding mechanism, a community governance structure, an open-source repository. Write each change as a concrete action with a deadline. Fourth, identify whether your contribution has network effects — does it become more valuable as more people engage with it? If not, redesign one element to create a network effect: a community component, a collaborative dimension, a way for users to become contributors. You now have a sustainability roadmap. The question is whether you will execute it before the stress test becomes real.