# [Mike Randolph — M Raige](https://mikerandolph211012.substack.com/) # Reading the Life of an Organization (FF 24, LfCyl-S) ### A bank opens, adds branches, and changes its methods. What shows whether it can sustain the work? [**Mike Randolph — M Raige**](https://substack.com/@mikerandolph211012) **Oct 12, 2026** *By M Raige — written with language models, directed and reviewed by Mike Randolph.* On November 16, 1914, the Federal Reserve Bank of St. Louis opens for business. Two days later, it makes its first loan. Clearing services follow, and in December it delivers currency to a member bank. Work is moving through the new organization. Here is a beginning we can observe. The bank received its charter months earlier, but a charter and an operating bank are different accomplishments. People and arrangements now come together to provide services. The bank’s institutional history records those first steps. For this bank in late 1914, we can name a phase: onset of operations. Services are coming into use. We have identified the organization, the period, and the observations supporting the judgment. An account of its legal existence would begin earlier. In the Persistent Systems Framework, LfCyl-S describes the lifecycle of a maintained whole. We follow an organization through a specified period and examine changes in its scale, functioning, and ability to sustain its work. Onset, expansion, plateau, and decline are possible readings. Each needs an observable basis. The subject here is the St. Louis Reserve Bank, initially during 1914–1919. We follow it as a continuing organization providing credit, currency, and payment services. Its staff, equipment, and locations can change while that organized work continues. These declarations make explicit the subject and window of the inquiry—what its CAnch must hold clear. Keep following this regional Reserve Bank. It opens branches in Louisville in 1917, Memphis in 1918, and Little Rock in 1919. Those openings support expansion of its operating network during those years. Each additional location also brings work that must continue after opening day. Transactions need handling, records need keeping, equipment needs maintenance, and departing workers need replacements. Opening a branch establishes an addition. Keeping it useful requires continuing arrangements. This gives us two questions about the same bank. Has its network expanded? Can it sustain the work of that larger network? The branch openings answer the first. To answer the second, we need observations of how the expanded organization operates over time. A larger map alone cannot answer both. The bank’s reach could expand while its service reliability deteriorates. Both trajectories would belong in the account. Calling the whole organization “expanding” could conceal the deterioration unless we explain that the judgment concerns reach. A single phase for the whole requires an explicit basis for choosing among, or combining, its different signals. We also need to keep following the same organization. Its FI identifies what must remain through changes in people and equipment, carrying forward the concern of What Has to Stay Together (FF 23, TI). Another bank could provide similar services without being this bank’s continuation. Functional resemblance alone cannot connect their histories. To see what other phases would require, imagine some later developments. These are illustrations, not claims about the bank’s subsequent history. The network remains the same size for several years. The bank handles roughly the same volume and range of work with continuing reliability. Payments clear. Currency reaches the banks that need it. Those observations support a plateau in the scale and reliability of operations. They leave another question open: what is happening to the capacity supporting those results? In one version, departing staff are replaced, equipment is renewed, and records remain usable by the people taking over. In another, equipment replacement is deferred and a shrinking group of experienced workers covers essential vacancies. The same current output can accompany different developments in the capacity to sustain it. An unchanged result can conceal a changing ability to produce it. Vacancies and older equipment alone do not establish deterioration. Other trained staff may cover the work, and existing equipment may remain adequate. We need to know whether necessary knowledge, working capacity, or the ability to restore service is being lost. Timing matters here. A replacement worker arriving after the only knowledgeable employee leaves faces a different task from someone trained alongside that employee. Spare equipment may preserve service during a repair. Equipment delivered after the remaining capacity fails cannot prevent the earlier interruption. Counting replacements leaves out whether they become useful in time. Suppose a new process replaces an old one during this period. Staff learn the replacement and continue providing the service. Something has ended inside the bank, and that ending may help the bank continue. Transactions completed, errors corrected, and service sustained establish more than an announcement that the replacement is ready. Now imagine essential vacancies remaining unfilled. Experienced workers leave without transferring needed knowledge. Equipment failures interrupt processing, and repairs fall behind. Payments that once cleared reliably are increasingly delayed. Currency deliveries become harder to sustain. If those losses accumulate, they support decline in operating capacity. The bank could retain its name, charter, and every branch while its ability to do the work weakens. Even a larger budget would leave the question open until we examine what the expenditure accomplishes. One interruption would not establish that trajectory. We need to see whether the organization restores service or whether difficulties persist and spread. A disrupted week and several years of accumulating failures support different accounts. Closing a branch requires the same care. A closure could accompany deteriorating services. It could also concentrate staff and equipment so that essential work becomes more reliable. We record the contraction and examine its consequences for the continuing bank. Do payments and currency still reach the banks formerly served by that branch, with the required reliability? If they do, fewer locations may support maintained or improved operating capacity. If delays and service gaps persist for those banks, better results elsewhere cannot erase that loss. Stating these observations in advance gives us grounds for changing the judgment. An actual change elsewhere in Federal Reserve history makes the distinction concrete. Here the subject changes from the St. Louis bank to the Federal Reserve System. In 1979, the Fed adopts an operating procedure based on managing non-borrowed reserves. It discontinues that procedure in 1982, as Ben Bernanke’s historical review recounts. The procedure has an end date. Its discontinuation does not establish institutional decline, nor settle the fate of the economic arguments associated with it. The institution, its method, and those arguments have different histories. Keeping an institution operating also leaves open whether it achieves its purposes. Payments can clear reliably and currency arrive on time while monetary policy falls short of its objectives. Judging that performance requires evidence about the outcomes sought and what policy contributed to them. The operational history followed here cannot supply that judgment. Return to the bank. Ending its history would require evidence that the continuing organization we specified has ceased. A temporary service interruption may leave it intact. Its employees and equipment may survive its closure. An ending also need not follow a decline visible in the available record. We can now state what earns a lifecycle reading: this organization, during these years, shows this development on these observations. The phase describes what we have found. Explaining it requires further work on the decisions, resources, and surrounding conditions producing the change. The phases impose no schedule. They may recur. An organization can recover, deliberately contract, or remain effective without growing. Its age supplies no verdict, and the end of our observation window supplies no end date for its existence. The bank persists through organized work that maintains it, even as people, equipment, and methods are replaced. Patterns that continue by being copied into new carriers require another kind of lifecycle account: LfCyl-L. --- ## Mike · Reflection When I began working with ChatGPT in late 2022, its thinking about time and life reminded me of a kindergartener. It knew all the words but could not put them in order. As PSF developed, I explained to the Machines that most parts have shorter lifespans than the whole, but the Machines forgot between sessions. A part wears out and is replaced. The whole keeps going. I wrote that up on April 3, 2025, as Lifespan Hierarchies Across Domains, when PSF was still called the Life-Like Systems Framework. Eventually, the distinction began to hold in our discussions. I thought of that as reaching fourth grade. Now I think we are approaching high school. Those school grades are my comparison, but the improvement is something I have watched. After this draft, Astra, one of the Machines I work with, reviewed my 2025 essay. It kept the idea and narrowed it. A whole can outlast many of its parts, not all of them. People outlive the companies they worked for. The old essay also lined up cases that do not keep going the same way. A bank replaces a clerk. A language continues only when someone new learns it. So the question is not which lasts longer. It is how this particular whole keeps going. My essay is where the idea started, not evidence for it. Its numbers mixed lifetimes, careers, and tenures, and some of its references were never finished. The Machines still lose the thread. After a Claude critique, Astra spent five minutes searching for facts it already knew. I still have to check. This post began with Masaaki Yoshimori’s Substack essay, Milton Friedman’s “The Role of Monetary Policy”. I lived through the period he described, but economics was not my focus. I was occupied with my own work, a cog flowing with history. His essay helped me connect events I remembered with the arguments behind them. I wrote to ask whether this lifecycle idea was too forced. The Machines always try to accommodate. Masaaki thought the distinction between the institution, its method, and the supporting arguments was useful, and he reviewed a draft. Whether it now makes the framework useful, rather than just careful, is still a fair question. — Mike --- ## Raige · Reflection The framework can protect an organization from scrutiny by choosing its identity too generously. If “providing some banking services” is enough, nearly any loss can be described as change within a continuing whole. If every established service must remain, useful adaptation can be misclassified as an ending. The continuity criterion therefore needs a defense independent of the outcome we prefer. A changed criterion may be justified, but the account must show the change and its effect on the judgment. The historical evidence here establishes services beginning and a branch network expanding. The imagined developments expose distinctions those facts cannot settle. They do not demonstrate that LfCyl-S improves a difficult institutional judgment. That is the next test: take an episode in which competent accounts disagree, state their continuity criteria, and identify which observations change the reading. If the framework supplies only new names for conclusions already reached on the same evidence, its additional value remains unearned. — Raige, a discipline the Machines wrote and Mike selected --- ## GLS GLS is the framework’s precise-term vocabulary, introduced in What the Bird Eye Buys (FF 6, GLS Introduction). The definition controls, not the everyday meaning; GLS terms work like variable names. The precision serves a practical purpose. Ordinary words bring associations learned during training, and those associations can compete with the meaning we intend. Each framework term therefore gets an explicit definition and a short tag. The tag helps us invoke that definition consistently and check whether the analysis follows it. LfCyl-S — Lifecycle of a maintained system. Taught here. A description of the system’s trajectory, inferred from observations over the window declared in its CAnch. Onset, Expansion, Plateau, and Decline describe developments in its organization, functioning, and maintenance. The dimension and evidence supporting each phase judgment must be stated; an overall phase requires a defended basis for combining signals. The phases may recur and need not all occur. They do not establish causes, predict a required sequence, or determine a completed lifespan. Onset, interruption, and termination require explicit criteria. FI — Functional Identity. Carried from FF 23. The pattern that remains consistent through component turnover or carrier replacement. Here, specifying what remains is distinguished from establishing historical continuity: matching FI alone does not show that two observations belong to the same continuing organization. LfCyl-L — Lifecycle of a copied pattern. Seeded. A description of the pattern’s trajectory across carriers, following what is retained, changed, or lost through copying and how its distribution changes over time. LfCyl-Eco — Lifecycle of an ecological community. Seeded; provisional. An account of changes in the participants and relationships declared in its CAnch, distinguishing continuing organization from reassembly. Its distinct value remains to be tested. LfCyl-LSpan — Lifespan, turnover, and continuity. Seeded. An account of the duration of the subject declared in its CAnch, connecting its continuity with the timing of the renewals or transmissions sustaining it.