Legacy
From Foundation to Legacy
Legacy is the temporal conclusion of everything that has flowed through the hourglass, the results of that motion shaped by the project, and it represents the refreshed engagement of what the project has become. When the hourglass turns again, this legacy at the end becomes the beginning again. Before that turn, legacy records what the project now embodies. It is the imprint left by missions, the expectations shaped by experience, and the structural residue of everything the project has attempted, succeeded at, struggled with, or abandoned. This final work is a recognition of the project’s new gravity, for worse or for better. It must avoid the temptation of introspection or retrospection, but instead, conclude its narratives and efforts so that the Legacy speaks for itself in its accuracy, in turn.
Preferences
Every project develops expectations about itself. These expectations begin as intentions but eventually harden into preferences. These preferences reflect what the agency believes “good work” looks like. They show which kinds of missions the project gravitates toward, the quality thresholds it refuses to compromise, the styles of execution it now considers normal. These preferences are not mandates, but they characterize the motion and emotion, the expectations and aspirations, and the guidance and autonomy that nurtures success. This project culture influences how new missions are interpreted, how decisions are framed, and how the project evaluates its own output. Preferences are the project’s self‑formed identity, expressed through repeated choices.
Marketing
As the hourglass turns, it continues to project itself into the world. Ideas, presentations, values, and ultimately a form of product, service, experience, connection, knowledge, or capital. Marketing, like preferences, reflects what the project believes "good work" looks like. It is the project’s projected narrative footprint. It reflects how the project has been described, understood, and positioned by its stewards, by its users, and by the broader environment. This projection shapes expectations. It influences who approaches the project, what they believe it can do, and how they interpret its purpose. Marketing becomes part of Legacy because the story a project tells and the story told about it becomes a structural condition of its own legacy.
Sales
Sales represents the project’s history of adoption. It records where the project has been embraced, where it has struggled to gain traction, and where it has been misunderstood or misapplied. Sales, a forever companion to marketing, is the project's received narrative footprint. The project's adoption patterns reveal the project’s resonance: which audiences found value, which contexts amplified its strengths, and which environments exposed its limitations. Sales is not a performance metric; it is a necessary triangulation between the agency of the project, how the project is marketed, and its own value as an inarguable cultural signal. It shows how the project has moved through the world and how the world has responded. These adoption patterns shape future cycles by defining where the project already has footholds and where it must work harder to be understood.
Auditing
Auditing is the project’s deeper investigation and specific area assessment. Where preferences, marketing, sales, and onboarding are naturally subjective and heavily cultural, Auditing seeks to distill truths of condition by performing intentional and direct examination. It records what has worked, what has failed, what has drifted, and what has remained stable across cycles. Auditing is not a judgment; it is a map of verification. It shows where the project’s architecture is sound, where its processes are fragile, where its assumptions have held, and where they risk collapse under real‑world conditions. Auditing is another form of culture that informs legacy with a transparency that is unavailable otherwise, and can only be successful when the project's inner workings are allowed to speak in a fair volume to the stories the project seeks to tell about itself.
Auditing, Sales, Marketing, and Preferences
Auditing assures that Sales are honest, Marketing is accurate, and that Preferences are balancing the work fairly across the team. Audits help the team stay aligned on critical points.
However, each must also be protected from inappropriate uses of Auditing disguised as an earnest review being implemented as an attack surface against team delegation and trust.
Together, these four form the cornerstones of a more accurate and precise legacy process.
Onboarding
Every project develops a naturally increasing difficulty of entry. Onboarding in Legacy captures how accessible the project has become: how easy it is to understand, how difficult it is to adopt, how much context a newcomer must acquire before they can participate meaningfully. Onboarding attempts to capture how to preserve this legacy, for worse or better, by producing the artifacts needed to return to this very state. Such is literally impossible, but it still shows how to bring things closer to that evolved state of normal that produced the projects results. This is the persistent layer of Legacy that hopes to survive succession, or calls out plainly what needs to be challenged to explicitly change it. Some of that complexity is necessary; some is inherited; some is accidental. The next turn must inherit the project’s current accessibility, not the accessibility it wishes it had.
Archives
Every project accumulates documents, prototypes, decisions, experiments, navigated paths, paths not travelled, and paths only briefly explored before choosing another. When a company retraces its steps to a familiar crossroad, archives serve as a reference point on where the project was then, so that it can look at these paths again based on where the project is now. Archives can speak on why certain paths were not travelled further, so that new preparations can complete the journey, or the path can continue to be avoided. Some of these archives remain relevant while other archives fade into obscurity. Legacy does not distinguish between them. Archives shape how the project understands its past, how it interprets its present, and how it imagines its future. Archives are the memory the project should not erase, less it risks repeating the work that may have failed before none the wiser.
Legacy concludes when the project has acknowledged the full consequence of its own motion: the team preferences it has formed, the marketing narrative it has projected, the sales adoption it has achieved, the audited truths revealed by its performance, the accessible complexity it has accumulated, and the archived artifacts it has left behind. This Legacy grows and perpetually informs itself as the starting point of the next turn. They define the gravity the project now carries through the hourglass. Once this inheritance is recorded, the hourglass can turn again, allowing Situation to observe the present terrain with clarity and PROGRAM to define the next mission with a characterized history.