6.1 Definition of a Bus

Intuitively, a Bus is a route that can generate sustainable FCF under repeatable conditions and for which an r-structure can be meaningfully specified.

Formal notation:

Bus_i = { FCF_i(t), r_i(t), Holders_i, Boundaries_i }

  • FCF_i(t): the sequence of Free Cash Flows generated by Bus i across periods;
  • r_i(t): the discount-rate structure corresponding to that Bus;
  • Holders_i: the parties that share benefits and bear costs on the Bus (shareholders, creditors, labor, government, households, etc.);
  • Boundaries_i: the property-rights and institutional boundaries that support the Bus.

Identification criterion (concise version):

If a mechanism can generate FCF sustainably under repeatable conditions and an r-structure can be meaningfully specified for it, it is a Bus; otherwise, it is closer to a one-off opportunity, an inventory position, or a pure narrative.

6.2 Positive Buses and Negative Buses

  • Positive Bus
  • A route expected to generate net positive FCF over the long run—for example, a high-quality firm, effective education, health investment, or sound infrastructure.
  • Negative Bus
  • A route with a priority claim on future FCF, for example:
  • Principal and interest on various forms of debt;
  • Pensions, medical insurance, rigid fiscal expenditure, implicit guarantees, and similar commitments;
  • War debt and long-term costs of maintaining security and stability.
  • A Negative Bus does not necessarily create additional value itself, but it has priority in absorbing future FCF.

6.3 Checklist for Identifying Negative Buses

Anything that must be serviced first in a crisis can be treated as a Negative Bus. The main categories include:

  • Contractual Negative Buses: principal and interest on loans and bonds, leases, valuation-adjustment agreements, and similar obligations;
  • Institutional-commitment Negative Buses: pensions, medical insurance, rigid fiscal expenditure, implicit local-government debt, and similar commitments;
  • Political / narrative-commitment Negative Buses: implicit guarantees of repayment, bailout expectations, and institutions or projects considered “too important to fail”;
  • War- and mobilization-related Negative Buses: long-term military expenditure, war debt, postwar reparations, sanction-hedging costs, and similar burdens.

The larger and more rigid the Negative Buses, the more they crowd out the space available for FCF→P on Positive Buses.

6.4 Bus Networks and the Crowding-Out Effect

An economy can be viewed, in essence, as a network of Buses:

  • How many Buses are there?
  • Which are Positive Buses, and which are Negative Buses?
  • How is finite FCF allocated among the Buses?

A typical structural problem is:

  • Negative Buses keep expanding;
  • The growth of total FCF slows or even turns negative;
  • As a result, FCF→P on Positive Buses is crowded out, and the quality of education, maintenance, R&D, and infrastructure deteriorates;
  • FCF→R rises as parties compete through rent-seeking for the remaining resources;
  • r_s and r_u rise as social confidence erodes and perceived tail risk intensifies.

6.5 Bus Generation Interface: Entrepreneurial Experiments and Candidate Futures

6.5.1 Why a “Bus Generation Interface” Is Needed

Section 6.1 defines a Capitalization Bus as:

Bus_i = { FCF_i(t), r_i(t), Holders_i, Boundaries_i }

and stipulates that if a mechanism can generate relatively stable FCF under repeatable conditions and an r-structure can be meaningfully specified for it, the mechanism may be identified as a Bus.

This definition answers the question: how should a Bus that has already formed be identified, analyzed, and capitalized?

Logically, however, it leaves a prior question unresolved: how does a Bus that does not yet exist gradually acquire the qualifications to become a Formal Bus from an unverified conjecture about the future?

New products, technologies, organizational forms, business models, and boundary structures do not naturally begin with stable FCF and a clearly defined r-structure. They usually pass through an earlier sequence:

Future conjecture → Real Resource Commitment → real-world experiment → external validation → continuation, restructuring, or exit

Most experiments fail. A small minority gradually develop repeatable exchange, relatively stable Boundaries, and identifiable FCF, and only then enter Formal Bus and capitalization analysis.

This section therefore adds a limited “Bus Generation Interface.”

It does not construct a complete equation of innovation generation, nor does it attempt to predict who will become a successful entrepreneur, what the next major innovation will be, or the precise probability that a new project will succeed. Why a specific piece of new knowledge, idea, or recombination is proposed by a particular actor at a particular moment still involves dispersed knowledge that cannot be centrally calculated, subjective judgment, and historical contingency.

This section addresses only three questions:

1) How should futures that have not yet formed be distinguished from futures that can already be capitalized?

2) What minimum conditions must a conjecture about the future satisfy before it can enter Proto-Bus status?

3) How do institutions and budget constraints affect the validation, failure, exit, and eventual formation of Proto-Buses?

V3.54 adopts a restrained position here: the specific content of novelty is not modeled in advance; the generation ecology can be analyzed; and the selection mechanism can be observed.

CBT does not predict what the next future will be, but it can analyze whether a system allows enough conjectures about the future to be proposed, tested in real-world experiments, allowed to fail in a timely manner, and—when a small number prove viable—allowed to continue growing.

6.5.2 Generation Domain and Capitalization Domain

To avoid forcing every unrealized future into EPV, CBT distinguishes the Generation Domain from the Capitalization Domain.

I. Generation Domain

The Generation Domain is the stage in which a new product, technology, organization, mode of exchange, or boundary structure has not yet formed a stable Bus, and its future FCF, Holders, and Boundaries are still being tested and formed.

At this stage, future cash flow may not yet exist; whether demand exists may not yet have been validated; who will ultimately own the rights to returns and bear the costs may not yet be stable; transaction and property boundaries may still be changing; and therefore a stable valuation object does not yet exist.

The Generation Domain is not simply an “ultra-high-risk segment” within the Capitalization Domain. The problem is not merely that r is very high; rather, r does not yet have a stable object to which it can attach.

Before a Bus has formed, we may not even be able to answer consistently: which FCF is to be discounted; who owns the future returns; which boundary structure will ultimately hold; or what economic object the current experiment will eventually become.

For an existing Bus with high uncertainty, we at least know what object is being analyzed even if we do not know how its future will unfold. In the Generation Domain, the valuation object itself is still being generated.

II. Capitalization Domain

A mechanism enters the Capitalization Domain—and becomes suitable for Formal Bus analysis and EPV analysis—only when it has gradually acquired relatively repeatable exchange or resource flows, identifiable FCF, relatively stable Holders, describable and enforceable Boundaries, and an r-structure that can be meaningfully specified.

Unformed future → real experiment → Proto-Bus → selection and clearing → Formal Bus → capitalization

III. A Proto-Bus Must Not Be Assigned a Steady-State EPV Directly

Because a Proto-Bus has not yet formed stable FCF, r, Holders, and Boundaries, it should in principle not be valued directly with the steady-state approximations EPV ≈ FCF / r or EPV ≈ FCF / (r - g).

At the Proto-Bus stage, phased budgets, milestones, scenario trees, staged resource commitments, validation horizons, and Death Conditions are more appropriate.

This does not mean that a Proto-Bus cannot have a market price or financing valuation. Capital markets can still assign prices to a team, technology, exclusive resources, future experimentation rights, and optionality on a staged basis.

A Proto-Bus transaction price or financing valuation does not establish that the underlying Bus has already formed, nor that steady-state EPV can already be calculated reliably.

Financing price ≠ Formal Bus confirmation ≠ steady-state EPV

At the Proto-Bus stage, financing prices and financing capacity may in turn change the resources available to a project and thereby affect technical, organizational, and market-validation outcomes. Price and expectations can therefore shift from being “results” to becoming “causes,” creating the reflexive feedback described in Section 3.5. V3.54 merely marks this interface and does not construct a complete dynamic model of reflexivity here.

6.5.3 Entrepreneurial Function and Accounting Asymmetry

In CBT, the entrepreneur is understood primarily not as a fixed identity, occupation, or personality type, but as an action function.

The Entrepreneurial Function is the action function through which an actor, when the future cannot yet be fully calculated, commits real resources on the basis of local knowledge and subjective judgment; changes existing combinations of resources, organizational forms, transaction relationships, or boundary structures; and accepts feedback from reality as a test of the actor’s conjecture about the future.

An Entrepreneurial Experiment contains at least four elements:

First, subjective judgment

The actor judges that a new future state may be better than maintaining the status quo. The judgment may be right or wrong. The entrepreneur does not possess an objective answer about the future.

Second, Real Resource Commitment

The actor must actually bear some opportunity cost—for example time, capital, credit, reputation, career opportunities, organizational resources, or certain returns from an existing Bus. A narrative about the future that involves no Real Resource Commitment is not an Entrepreneurial Experiment in the sense used here.

Third, real-world experiment

The actor must change the status quo through real action—for example by developing a product, building an organization, changing a production process, creating a new mode of exchange, recombining existing resources, or redefining a set of executable rights and Boundaries.

Fourth, a real possibility of failure

The experiment must face some form of feedback from reality that the actor cannot fully reinterpret, cancel, or defer indefinitely—for example customers refusing to buy, technology failing to work, costs failing to be covered, an organization failing to survive, a key hypothesis being falsified, resources running out, or an alternative solution winning.

If a purported “innovation” can never, even in principle, be judged a failure, it is closer to an unfalsifiable narrative than to an Entrepreneurial Experiment.

Accounting Asymmetry of Entrepreneurial Action

Entrepreneurial action has an important ex ante structure: the sacrifice side is usually observable or partially measurable, while the future-claim side cannot yet be fully priced.

The cash, time, foregone income, equipment, credit, reputation, and organizational resources committed by the actor can usually be observed at least in part; but the future the actor is attempting to open may have no stable FCF, no reliable probability distribution, no mature market price, and perhaps not even a stable definition as an asset.

Entrepreneurial action is therefore not simply “commit known capital → purchase an already priced future asset.” It is closer to:

Using an observable sacrifice in the present to conduct a real experiment on a future that cannot yet be fully capitalized.

For identification, three ideal types may be used:

Investment-type action: the sacrifice side is measurable + the future claim is broadly priceable.

Entrepreneurial-type action: the sacrifice side is measurable + the future claim cannot yet be fully priced.

Purely narrative action: Real Resource Commitment is insufficient; the action relies mainly on language, financing narratives, identity performance, or having others bear the principal costs.

These are only structural ideal types, not permanent classifications of people. The same person may, across different decisions, act as an investor, an entrepreneur, or a promoter of narratives.

6.5.4 Proto-Bus: Admission, Death Conditions, and the Genealogy Ledger

To describe a structure that is not yet mature but has already entered real experimentation, CBT introduces a limited transitional concept:

Proto-Bus: an early-stage structure with Real Resource Commitment, a clear Core Hypothesis, a real-world validation interface, and an Effective Death Condition, but which has not yet met the criteria for a Formal Bus.

Idea ≠ Proto-Bus ≠ Bus

An idea, paper, business plan, policy slogan, financing story, or early-stage project does not automatically become a Proto-Bus merely because it “might succeed.”

I. Four Minimum Admission Criteria for a Proto-Bus

Criterion 1: Real Resource Commitment. At least one actor must genuinely bear opportunity cost.

Criterion 2: a clear Core Hypothesis. It must be possible to state what real-world structure the experiment hypothesizes can work.

Criterion 3: an External Validation Interface. There must be feedback from the real world; success cannot be defined entirely inside the project itself.

Criterion 4: an Effective Death Condition. A Proto-Bus must be constrained by a genuinely effective Death Condition. The condition may be structural or declared; at least one of the two must exist.

II. Structural Death Conditions

A Structural Death Condition is an exit mechanism naturally created by real budget constraints, such as depletion of the cash runway, inability to obtain follow-on financing, inability to repay debt when due, contract termination, persistent customer refusal to buy, bankruptcy, or market exit.

A project operating under genuine profit-and-loss responsibility may already face a strong Structural Death Condition even if no formal “death agreement” has been written.

A Structural Death Condition must have actual constraining force rather than existing only formally.

If a project can continually bypass its original Death Condition through unlimited related-party funding, implicit guarantees, fiscal backstops, persistent loss coverage by a parent company, or non-market refinancing, then its Structural D has been weakened or even dismantled.

Whether a Structural Death Condition has real constraining force should not be judged only from formal bankruptcy rules, financing terms, or cash-runway arrangements. It should also be assessed against the ex ante soft-budget indicators listed under Prediction 1 in Section 6.5.6, including the nature of the funding provider, guarantee structures, historical rescue records, budget-continuation mechanisms, and arrangements that externalize losses.

III. Declared Death Conditions

When the Structural Death Condition has been materially weakened, a substitute constraint should be established through an ex ante registered Declared Death Condition.

D = { T, Evidence, Exit Rule }

Here, T is the Validation Horizon; Evidence is the Minimum Evidence that must appear; and Exit Rule is the rule for exit, scaling down, or re-registration that should be triggered if the evidence does not appear.

A project with neither an effective Structural Death Condition nor an effective Declared Death Condition does not qualify as a Proto-Bus.

Declared D must not be merely formal. T should be broadly commensurate with the sustainable runway of committed resources, the technology-development cycle, and the structure of key milestones. An ultra-long T that clearly exceeds the resource horizon and lacks intermediate validation nodes is, in principle, an invalid Death Condition.

A typical case is an internal corporate innovation project. Because the parent organization can continue supplying resources, the Structural D originally provided by the market can easily be dismantled by internal budgets. Such projects therefore usually need Declared D, milestones, and stop-loss discipline more than independent entrepreneurial projects do.

IV. Soft Budget Constraints and Death Conditions

Section 3.4 already discussed Hard Budget Constraints. Here we can make a further operational inference: an important manifestation of a Soft Budget Constraint is the systematic dismantling of Structural Death Conditions.

Losses, cash depletion, payment failure, or customer rejection that would ordinarily trigger exit no longer cause resources to stop flowing. Declared Death Conditions then become a substitute constraint.

Declared D is not mandatory paperwork for every Entrepreneurial Experiment. It is a substitute discipline that becomes particularly necessary when Structural D has failed or been materially weakened.

V. Core-Hypothesis Change and Re-registration

Real-world experiments may be adjusted and reasonable pivots are allowed, but parameter adjustment must be distinguished from a change in the Core Hypothesis.

If the changes involve only pricing, product optimization, sales methods, or cost structure, while the core value proposition and the basic object of validation remain unchanged, the original Proto-Bus may continue.

But if the core customer, value proposition, principal FCF source, key technical route, or core boundary structure changes materially, the original Core Hypothesis should in principle be treated as ended and the new Core Hypothesis re-registered as a new Proto-Bus. The new Proto-Bus should reset its validation object, Validation Horizon, Minimum Evidence, and Death Conditions.

VI. Proto-Bus Genealogy Ledger

Re-registration does not erase history. Every newly registered Proto-Bus should retain the record of prior experiments, including the prior Core Hypothesis, prior Death Conditions, actual validation outcomes, reasons for falsification or exit, major resources already consumed, what changed in the current Core Hypothesis, and whether new high-quality external validation has accumulated.

This constitutes the Proto-Bus Genealogy Ledger.

The Genealogy Ledger has two uses. As an analytical tool, an analyst can reconstruct it ex post from available financing records, project announcements, board documents, product changes, customer records, and public information. As a governance tool, boards, fund managers, LPs, strategic investors, or providers of public capital can use it as a record-keeping discipline for subsequent resource commitments.

Its purpose is not to punish failure. Genuine Entrepreneurial Experiments must allow for failure and redirection. It is intended to prevent repeated failure from being disguised as one uninterrupted long-term exploration through repeated changes of name, sector, or metric.

Frequent re-registration and persistent resource consumption without long-run accumulation of high-quality external validation are important warning signals of Zombie State.

6.5.5 Validation Tiering, Hard Budgets, and Zombie State

The appearance of a first revenue stream does not automatically prove that a new structure has formed a Stand-Alone Bus. Transaction signals themselves can be manufactured by support, related-party relationships, or institutional arrangements. Validation evidence for a Proto-Bus must therefore be recorded in tiers. A-, B-, and C-Class validation must not be collapsed into a single “total amount of validation.”

A-Class: Stand-Alone Validation

Typical features include non-related-party transactions; counterparties using their own budgets; counterparties having real alternatives; prices not being created mainly by subsidies; and transactions having the potential to repeat or expand.

A-Class validation mainly asks whether the structure is beginning to generate stand-alone demand and exchange capacity independent of a specific supporter. It provides the strongest evidence for the future formation of a Stand-Alone Commercial Bus.

B-Class: Support-Backed Validation

Examples include fiscal subsidies, policy-driven procurement, strategic government procurement, industrial support, and explicit or implicit price support.

B-Class validation still has evidentiary value. It may show that a technology works, that a product has functional value, that genuine public demand exists, or that a strategic need warrants sustained resource expenditure. But it cannot by itself establish stand-alone commercial viability once the current support structure is removed.

Government procurement illustrates this particularly well. The issue is not whether the customer is the government, but whether the exchange corresponds to a persistent genuine functional demand or is mainly intended to keep a particular entity alive.

A Functional-Demand Counterfactual Test can be used: if the project exits, would the resource provider still be willing to spend a broadly comparable budget to obtain the same type of function or outcome—for example by switching to an alternative supplier, alternative technology, an import solution, or funding alternative R&D? If the demand remains while only the implementation changes, it is closer to genuine demand; if the demand itself disappears when that specific entity ceases to exist, it is closer to rescue support.

Genuine demand attaches mainly to the function; rescue support attaches mainly to the survival of a particular entity.

C-Class: Related-Party Validation

Examples include parent-company procurement, transactions with affiliated companies, orders arranged by controlling shareholders, internally circular revenue, or transactions manufactured for financing or performance evaluation.

C-Class validation can help prove whether technology works, processes function, and an organization can deliver, but it cannot directly prove the existence of independent market demand.

A-, B-, and C-Class validation should be recorded separately and must not be merged into a single validation metric. A Proto-Bus must not report only that it “already has revenue, already has customers, or already has orders”; it must also answer: what kind of revenue, customers, and orders are these?

This discipline is consistent with the principle in Section 3.4 that Stand-Alone and Support-Backed structures must not be reported as one combined number.

Hard Budget Constraint: the Selector in the Generation Mechanism

The main theory has already stated that EPV has more reliable signaling value only under relatively genuine Hard Budget Constraints. At the Bus-generation stage, the Hard Budget Constraint serves another function: it determines whether failed candidate futures can exit and thereby release experimental resources.

Future conjecture → resource commitment → real-world experiment → success or failure → resource reallocation

Most experiments failing does not mean the system itself has failed. As long as failure can be identified, confirmed, stopped, and absorbed—and human resources, capital, and attention can be released—failure itself is part of the selection mechanism.

A healthy mechanism of future generation must both allow conjectures about the future to be born and allow incorrect conjectures to die.

Zombie State: a degenerative state after loss of candidate eligibility

Zombie State—called “Zombie Proto-Bus” in earlier discussions—is not a normal subtype of Proto-Bus. It is a degenerative state in which a Proto-Bus has lost its Effective Death Condition, has failed for a prolonged period to complete the necessary validation, yet continues to consume resources, thereby losing its candidate eligibility.

Once a project enters Zombie State, it should be removed analytically from the normal set of Proto-Buses and marked separately. It may re-enter Proto-Bus status only after an Effective Death Condition has been re-established, a new falsifiable Core Hypothesis has been specified, and prior failure records have been retained in the Genealogy Ledger.

Proto-Bus → Death Condition failure / prolonged failure of necessary validation → Zombie

A typical Zombie process is: validation failure → Death Condition is canceled, delayed, or bypassed → continued receipt of resources → failure again → support again; or validation failure → Core Hypothesis changes → re-registration → failure again → re-registration again.

The result is that failure cannot release resources, experimental resources remain locked for the long term, and other candidate futures are crowded out.

The damage caused by Soft Budget Constraints therefore does not occur only in already formed firms and Formal Buses. It also occurs earlier, in the Generation Domain: conjectures about the future that should have ended continue to occupy resources that should have been redirected to other experiments.

A system may simultaneously display many projects, many funds, many “innovative firms,” and long average project lifetimes, yet produce few Formal Buses per unit of resources occupied for long periods. This structure can be described as: high experiment stock, low genuine generation rate.

On Modes of Bus Generation

New Buses can form in many ways—for example by discovering previously under-recognized demand, price differentials, or uses of resources; recombining existing technologies, resources, and organizational capabilities; or rewriting rights, responsibilities, and exchange boundaries. Rich theoretical traditions already exist around these mechanisms, and this section does not attempt to review the full history of innovation theory.

CBT pays particular attention to boundary-based generation because Boundaries are a first-order object in the definition of a Formal Bus. Some new Buses arise not first from new physical assets or technologies, but from redefining who may possess, use, benefit from, dispose of, and bear responsibility for something.

Assignable → exchangeable → capable of generating FCF → capitalizable

Boundary-based generation is more likely where frictions under old boundaries are high while an implementable window for a new boundary structure is opening. That window may arise from technological change, legal change, institutional opening, organizational innovation, or failure of an old institutional interface.

Entrepreneurial Function ≠ Positive Bus

The Entrepreneurial Function describes only how new structures are proposed and tested. It does not automatically imply that a new structure is positive for other actors or for the system as a whole.

A new Bus may generate mainly FCF_Produce or FCF_Exchange, but it may also depend mainly on FCF_Rent, FCF_Transfer, or even FCF_Plunder.

Generation capacity ≠ Positive Bus.

Once a new Bus has formed, analysis must return to the original CBT framework: where FCF comes from, where FCF goes, who shares the benefits, who bears the costs, how r is changed, whether Boundaries are stable, and how Multi-Agent EPV changes. The entrepreneurial mechanism is a descriptive interface for generation, not a moral evaluation.

6.5.6 Theoretical Boundary, SOP Interface, and Falsifiable Commitments

This section changes none of the Three Axioms, does not change the EPV formula, and adds no new component to r. It only supplies the logically prior interface missing from Section 6.1’s definition of a Formal Bus: how an as-yet unformed future structure gradually acquires eligibility for Formal Bus analysis through real experimentation, validation, and clearing.

Unformed future → real experiment → Proto-Bus → validation and clearing → Bus → capitalization

V3.54 does not claim to have built a dynamic model of “how the future is fully endogenously generated.” The source of specific novelty still involves dispersed knowledge, subjective judgment, historical contingency, and creative processes that cannot yet be fully modeled.

What V3.54 adds is: the boundary between the Generation Domain and Capitalization Domain; the Accounting Asymmetry of Entrepreneurial Action; the admission rules for Proto-Bus; Structural and Declared Death Conditions; tiered validation signals; the Proto-Bus Genealogy Ledger; the Hard Budget selection mechanism; and Zombie State as a degenerative condition.

I. The Bus Analysis SOP Adds “Step 0: Domain Gate”

With this section incorporated into the main theory, the existing Bus Analysis SOP gains a preliminary judgment: before formally decomposing FCF and r, first determine whether the object of analysis lies in the Generation Domain, the Capitalization Domain, or a mixed transitional state.

If the object lies in the Generation Domain, prioritize the Proto-Bus, validation, Death Condition, and clearing rules in Section 6.5 rather than entering the steady-state EPV procedure directly. If the object has already formed a Formal Bus, proceed to the original Four-Step Bus Analysis. If an organization contains both mature Buses and multiple Proto-Buses, analyze them in layers; do not combine the FCF of mature operations with the unvalidated futures of candidate projects into one steady-state EPV.

II. Three Principal Falsifiable Commitments of This Section

Prediction 1: Independently Identified Soft-Budget Intensity Should Predict the Formation of Zombie State

The degree of Soft Budget Constraint must be identified using ex ante indicators independent of the outcome variable—for example the nature of the funding provider, guarantee structures, explicit or implicit bailout arrangements, historical rescue records, budget-continuation mechanisms, whether losses can be externalized, and whether funding automatically continues after failure. Whether the project later exits must not itself be used retrospectively to define the Soft Budget Constraint.

Under such independent identification, this section predicts that experimental ecologies with higher soft-budget intensity should, over the long run, exhibit a higher share of Zombie State, longer periods in which failed projects continue occupying resources, and more repeated resource flows toward projects that have not completed validation.

If, after controlling for major differences such as project type and technology cycle, independently identified soft-budget intensity shows no stable long-run relationship with these phenomena—or systematically shows the opposite relationship—the explanatory power of the proposition that “Hard Budgets act as a selector in generation” should be weakened.

Prediction 2: Different Validation Types Should Predict Different Future Outcomes

This section does not simply predict that “A-Class projects will necessarily be better than B/C-Class projects.” Its more specific differentiated prediction is: A-Class Stand-Alone Validation should mainly predict future independent commercial sustainability; B-Class Support-Backed Validation can predict technical feasibility, functional value, or genuine public demand, but should not automatically be extrapolated into stand-alone commercial sustainability after support is removed; C-Class Related-Party Validation should mainly demonstrate internal technology, process, and delivery capability, but should not automatically be extrapolated into independent market demand.

A further prediction is that if B-Class or C-Class validation is persistently misreported as A-Class Stand-Alone Validation, the withdrawal of support, related-party backing, or implicit guarantees should be more likely to produce systematic downward revisions in revenue, valuation, or financing capacity.

If different types of validation show no stable long-run differences in the outcomes they are supposed to predict, the validation-tiering framework in this section should be re-examined.

Prediction 3: Effective Death Conditions Should Improve Resource-Conversion Efficiency at the Ecosystem Level

This section does not use “there is a Death Condition, therefore projects exit faster” as its core prediction, because that is close to a definitional consequence. The more important empirical proposition is that, other things being similar, experimental ecologies with effective Structural or Declared Death Conditions—and in which those conditions genuinely constrain continued resource commitment—should exhibit faster resource reallocation, a lower long-run share of Zombie State, and higher candidate-future resource-conversion efficiency.

Here, “resource-conversion efficiency” means the capacity to produce sustainable Formal Buses per unit of human resources, capital, and time committed over the long run.

If the existence and enforcement of Effective Death Conditions show no stable long-run relationship with these ecosystem-level outcomes, their theoretical status as a core discipline of Proto-Bus should be downgraded.

Closing of This Section

Once a mature Bus has formed, it is easy ex post to describe it as inevitable.

Before it formed, however, reality was rarely a roadmap with the probabilities already written in.

Someone saw a possibility, gave up part of what was already secure in the present, and committed time, capital, credit, or reputation to an action that might fail; reality then answered that conjecture through technology, customers, costs, competition, and losses.

Most conjectures disappear. A few begin to repeat. Repetition produces structure. Structure forms Boundaries. Boundaries carry cash flows. Only then does a possibility that previously could not be capitalized in an ordinary way truly become a Bus.

The entrepreneur converts a conjecture about a future that cannot yet be fully capitalized into an action that can be tested by reality.

Markets and institutions select which candidate futures can continue to exist; once a Formal Bus has formed, the capitalization system discounts its future returns back to the present.

V3.54 goes no further. Whether the full sequence “generation → capitalization → reflexivity → regeneration or destruction” should formally become CBT’s dynamic closed loop is a question about the theoretical identity of a later version and is not resolved in advance here.

Only when someone first bears a present that cannot be fully calculated can a future that later becomes calculable emerge.