artifacts/standard-named

Rendered from markdown source. Open raw source on GitHub.

--- title: "Dependent Loops and Telic Incompatibility" subtitle: "Substrate, Recruitment, Transplantation, Lock-In, Drift, Fork, and Dissolution" artifact_date: "2026-07-15" artifact_type: "candidate-foundational-paper" domain: "TELIC-FIELDS" scope: "WORKING" lineage: "THE-TELIC-FIELD-PAPERS" status: "candidate" processing_tier: 4 source_role: "derived-conceptual-artifact" content_canon_status: "unset" publication_status: "unpublished" series_position: "F.7" historical_language:

• "teleological graft rejection"

preferred_technical_language:

• "telic incompatibility"
• "telic transplant failure"
• "constitutional substrate mismatch"

derived_from:

• "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-1-V0-2__telic-fields-first-principles-foundation.md"
• "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-2__dyadic-composition-of-telic-fields.md"
• "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-5__context-carrying-capacity.md"
• "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-6__temporal-telic-relations.md"

research_companion:

• "20260715__TELIC-FIELDS__REVIEW__WORKING__G-8__transplantation-lock-in-drift-and-dissolution.md"

provenance_note: > The origin session used "teleological graft rejection" as an evocative description of a form or loop introduced into a field that cannot sustain its organizing purpose. This paper preserves that phrase in lineage while preferring more precise technical language. Biological transplantation remains metaphor only; no biological equivalence is claimed. ---

Dependent Loops and Telic Incompatibility

Abstract

Every durable loop depends upon conditions it did not create alone. A family depends upon bodies, resources, memory, and outer institutions. A company depends upon workers, customers, legal order, infrastructure, public trust, and ecological substrate. A protocol depends upon implementations, users, interpretation, and governance. A model depends upon data, compute, institutions, and human-maintained objectives. A purpose that appears self-sustaining is usually being sustained by lower or outer loops whose contributions have become invisible.

This paper develops loop dependence as a first-order property of telic systems. It argues that no derived loop is self-grounding and that higher-order loops remain legitimate only while their recruitment of lower-loop energy, standing, authority, and context remains legible and bounded. It defines telic incompatibility as a mismatch between an imported or inherited form and the field conditions required for that form to carry its intended purpose without coercive compensation, semantic drift, or substrate exhaustion.

The paper distinguishes legitimate dependence from extraction; a transferable form from a transferable loop; adaptation from mission drift; persistence from health; lock-in from commitment; and shutdown from dissolution. It examines hidden outer-loop recruitment, institutional transplantation, isomorphic mimicry, path dependence, specification gaming, goal misgeneralization, constitutional substrate mismatch, fork, succession, and release. It proposes a dependency map, compatibility review, dissolution protocol, and formal sketch.

The governing formulations are:

No derived loop is self-grounding.

The form may survive after the telic substrate that made it coherent has disappeared.

---

1. The illusion of the self-sustaining loop

A loop appears self-sustaining when the resources that maintain it arrive predictably enough to disappear from attention.

A company receives labor, money, law, roads, energy, education, social trust, and environmental stability. Its accounting system may represent revenue and expense while treating many of these enabling conditions as background.

A family receives care, housing, income, public infrastructure, inherited norms, biological capacity, and future possibility. Its visible routines may conceal the systems that make those routines feasible.

A model receives training data, labels, energy, hardware, software, institutional authority, user attention, safety processes, and maintenance. The output can appear autonomous because the dependency chain has been compressed out of view.

The loop's continuity is real.

Its independence is usually not.

Let a derived loop be \(L\), sustained by substrate set:

\[ \Sigma_L = \{\sigma_1,\sigma_2,\dots,\sigma_n\} \]

The loop persists through flows:

\[ F_{\sigma_i \rightarrow L} \]

of:

• energy;
• labor;
• information;
• legitimacy;
• consent;
• standing;
• material;
• attention;
• care;
• money;
• authority;
• memory;
• repair.

When those flows are treated as natural properties of the loop rather than contributions from other centers, dependence becomes invisible.

Apparent autonomy is often witnessed dependence with the witnesses removed.

---

2. Derived loops

A derived loop is a recurring organization whose continued identity, operation, or purpose depends upon lower, prior, or outer loops.

Examples include:

• a relationship derived from two persons and their shared practices;
• a team derived from members, roles, and institutional support;
• a company derived from contracts, labor, capital, customers, and law;
• a mutual pool derived from participant agreements and reserves;
• a protocol derived from implementations and shared interpretation;
• a public office derived from constitutional authority;
• a model service derived from infrastructure, training, provider governance, and users.

Derived does not mean unreal.

The relation can generate consequences and purposes not reducible to any one participant. It can become a center of operational standing. It may deserve protection.

Derived means it is not self-grounding.

Its authority and continuity remain conditional upon the substrate through which it exists.

---

3. Substrate

A loop's constitutional substrate is the set of material, semantic, relational, institutional, and consent conditions required for the loop to remain coherent without violating the standing on which it depends.

The substrate may include:

3.1 Material substrate

• energy;
• bodies;
• land;
• hardware;
• shelter;
• capital;
• time.

3.2 Semantic substrate

• shared language;
• definitions;
• role expectations;
• interpretive conventions;
• records;
• provenance.

3.3 Relational substrate

• trust;
• reciprocity;
• contact;
• care;
• repair history;
• realistic exit.

3.4 Institutional substrate

• law;
• enforcement;
• standards;
• licensing;
• public infrastructure;
• governance;
• succession.

3.5 Telic substrate

• compatible purposes;
• protected conditions;
• accepted sacrifice;
• future possibility;
• operative consent.

3.6 Capacity substrate

• skill;
• attention;
• context carrying capacity;
• coordination;
• slack;
• competent witness.

A form can be copied without copying its substrate.

That is the central transplantation problem.

---

4. Form is not loop

A policy, contract, institution, software architecture, ritual, governance model, or organizational chart is a form.

The form may carry a loop when embedded in a compatible field.

The form alone is not the loop.

A constitution copied into another polity may retain its words while acquiring different operative meaning. A governance process imported into a company may preserve meeting rituals while decisions continue elsewhere. A social-enterprise form may preserve mission language while financial survival becomes the operative objective. A software protocol may preserve message syntax while implementations disagree about authority or failure semantics.

The transplanted form may appear successful because:

• the documents exist;
• the software runs;
• the roles are filled;
• the meetings occur;
• the audit passes;
• the output metric improves.

The intended telos may still be absent.

A form is a carrier of possible orientation, not a guarantee that the orientation survived.

---

5. Telic compatibility

A form or loop is telically compatible with a field when the field can sustain the loop's organizing purpose, boundaries, and correction mechanisms without systematic coercion, concealed extraction, or destruction of required substrate.

Compatibility does not require cultural or structural sameness.

Adaptation is expected.

A compatibility review asks whether the receiving field contains, can create, or may legitimately recruit:

• the required centers;
• the needed authority;
• shared semantic distinctions;
• material support;
• skills;
• trust;
• enforcement;
• witness;
• context capacity;
• exit and repair;
• protected boundaries;
• compatible time horizons.

Let a form \(Q\) require substrate profile:

\[ \Sigma_Q^{req} \]

Let receiving field \(R\) possess or authorize:

\[ \Sigma_R^{avail} \]

A naive compatibility claim would require:

\[ \Sigma_Q^{req} \subseteq \Sigma_R^{avail} \]

Real compatibility is not set inclusion alone. The qualities, authority, and relations among substrate conditions matter.

A receiving field may possess money and law but lack trust. It may possess expertise but deny local standing. It may possess enforcement but lack legitimacy. It may possess consent in form and coercion in operation.

---

6. Telic incompatibility

Telic incompatibility occurs when a form or derived loop cannot preserve its organizing purpose and constitutional requirements in the receiving or changed field without one or more of the following:

• coercive compensation;
• hidden subsidy;
• semantic substitution;
• standing loss;
• boundary violation;
• context overload;
• mission drift;
• extraction;
• brittle enforcement;
• false reporting;
• permanent emergency authority;
• substrate depletion.

The loop may fail visibly.

It may also survive by changing what it is for.

This produces several states.

6.1 Benign adaptation

The form changes while preserving its legitimate organizing purpose.

6.2 Telic translation

The purpose is re-expressed through locally coherent means.

6.3 Telic drift

The operative purpose shifts gradually without adequate witness or reconsent.

6.4 Telic substitution

A different purpose occupies the form while the original language remains.

6.5 Telic transplant failure

The imported form cannot establish the loop it was intended to carry.

6.6 Constitutional substrate mismatch

The loop's required standing, authority, capacity, or repair conditions do not exist and cannot be legitimately recruited.

6.7 Dissolution

The loop ceases to govern and its residual obligations are transferred, repaired, archived, or released.

The origin phrase teleological graft rejection remains a useful image for transplant failure.

It should not be treated as a biological theory.

---

7. Legitimate dependence

Dependence is not failure.

Durable systems are interdependent.

A dependent loop is legitimate when:

• contributions are sufficiently visible;
• recruitment is authorized;
• cost and benefit are not systematically concealed;
• contributors retain standing;
• the loop does not claim absolute ownership of recruited energy;
• dependency risks are governed;
• repair and exit exist;
• outer loops do not secretly redirect the flow.

Examples include:

• a team relying on members under explicit roles and workload boundaries;
• a mutual pool relying on contributions under witnessed governance;
• a public institution relying on taxation under legitimate authority and accountability;
• a model relying on user context within disclosed use and retention limits.

Dependence becomes extractive when the loop treats substrate centers as replaceable inputs while protecting the loop's own continuity as sacred.

A loop may recruit energy. It may not erase the standing of the source from which the energy came.

---

8. Hidden outer-loop recruitment

A local loop may appear to have one purpose while feeding another.

Examples include:

• a social interaction feeding an advertising profile;
• a workplace process feeding investor metrics;
• a medical encounter feeding model training;
• a civic platform feeding political intelligence;
• a learning tool feeding surveillance;
• a mutual-aid relation feeding institutional reputation;
• a creator community feeding platform market power.

Let local loop \(L\) generate flow \(f\).

An outer loop \(O\) captures or redirects it:

\[ L \xrightarrow{f} O \]

The local participants may have consented to \(T_L\), the local purpose, without consenting to \(T_O\), the outer purpose.

This is a recruitment breach.

The system should disclose:

• which outer loops receive output;
• what purpose they pursue;
• what is retained;
• what models are trained;
• what financial or governance value is generated;
• how participants may refuse or exit.

A local loop cannot provide valid consent for hidden purposes it does not represent.

---

9. Institutional transplantation

Institutional transplantation occurs when a rule, legal structure, process, governance model, or organizational form is imported from one context into another.

Transplantation can be productive.

Human institutions often evolve through borrowing.

Failure occurs when the receiving field is treated as an empty container.

The imported form may depend on:

• professional norms;
• enforcement capacity;
• political settlement;
• trust;
• literacy;
• informal practice;
• independent courts;
• records;
• local legitimacy;
• economic surplus;
• conflict-resolution traditions.

Without these conditions, the form may:

• remain ceremonial;
• be captured by local power;
• produce compliance theater;
• overload weak capacity;
• redirect resources from adaptive local practice;
• create dual formal and operative systems.

The transplant can be accurate in text and false in function.

---

10. Isomorphic mimicry

A system exhibits isomorphic mimicry when it adopts the appearance of a capable institution without acquiring the operative capability that makes the form work.

Examples include:

• policies without enforcement;
• dashboards without correction;
• committees without authority;
• consent forms without meaningful choice;
• audits without semantic understanding;
• AI governance boards without access to deployment decisions;
• incident processes that cannot stop production.

Mimicry may be strategic deception.

It may also be the predictable result of external incentives that reward visible form rather than local capability.

The imported form can consume scarce context capacity while making the system appear more mature.

A loop can become less capable while becoming more legible to the institution that funds or evaluates it.

A compatibility review must therefore examine operative process, not only documentary form.

---

11. Premature load bearing

A developing loop may be asked to perform at a level that exceeds its capacity substrate.

The system compensates through:

• shortcuts;
• hidden work;
• exceptional individuals;
• falsified reporting;
• unbounded labor;
• informal coercion;
• dependency on consultants;
• repeated emergency authority.

This is premature load bearing.

It can occur in:

• states;
• startups;
• nonprofits;
• families;
• compliance programs;
• AI deployments;
• civic platforms;
• mutual pools.

A loop under premature load may appear durable because the burden is being absorbed by people whose standing is not represented.

Capacity failure becomes personal exhaustion.

When a loop survives only because participants metabolize its missing structure, the survival metric is misleading.

The constitutional response may be:

• narrower scope;
• slower growth;
• additional substrate;
• local adaptation;
• reduced authority;
• staged deployment;
• refusal.

---

12. Path dependence

A loop's current form may persist because prior choices created increasing returns, coordination effects, sunk costs, skills, expectations, legal commitments, and dependent investments.

Path dependence explains why a form can survive after superior alternatives appear.

The path may preserve valuable continuity.

It may also preserve a telos that no longer commands consent.

A path-dependent loop should distinguish:

• original purpose;
• current benefit;
• switching cost;
• dependent standing;
• lock-in beneficiaries;
• stranded obligations;
• available forks;
• reversible transition;
• critical junctures.

The existence of cost does not prove the current form is legitimate.

The existence of an alternative does not prove switching is justified.

The constitutional question is who bears both kinds of cost.

---

13. Lock-in

Lock-in occurs when the cost of leaving, changing, or forking becomes high enough that continuity no longer demonstrates preference.

Lock-in can arise through:

• network effects;
• data gravity;
• technical dependencies;
• specialized skills;
• contract;
• identity;
• social relationship;
• sunk cost;
• regulation;
• interoperability failure;
• accumulated reputation;
• dependence of third parties.

A locked-in user may continue.

A locked-in organization may renew.

A locked-in model may remain deployed.

Persistence under lock-in cannot be interpreted as continuing consent or telic compatibility.

A legitimate loop should provide:

• portability;
• documented interfaces;
• revocation;
• exit accounting;
• transition support;
• successor paths;
• forkability where feasible;
• protection from retaliation.

The more a loop depends on inability to leave, the less its continuity reveals about legitimate attachment.

---

14. Mission drift

A loop's declared mission and operative telos can diverge.

Mission drift may arise from:

• funding conditions;
• investor pressure;
• survival;
• metric selection;
• professionalization;
• scale;
• regulation;
• leadership succession;
• customer concentration;
• technological affordances;
• prestige;
• crisis.

A social organization may begin protecting revenue because revenue sustains the mission.

Over time, mission becomes the justification for revenue rather than revenue serving mission.

Drift is not every change.

A mission may need revision because the field changed or because the original purpose was wrong.

The constitutional failure is unwitnessed substitution.

A mission transition should state:

• what changed;
• what remains;
• who authorized it;
• which contributors were recruited under earlier terms;
• what reliance exists;
• what obligations survive;
• whether the organization should rename, fork, or dissolve.

---

15. Metrics and operative teloi

Metrics can reveal or replace purpose.

A metric begins as a projection:

\[ m = \Pi(T_L) \]

The loop then optimizes \(m\).

Over time, the metric becomes an operative telos because it controls reward, attention, and survival.

This is familiar in Goodhart-like failures, specification gaming, and organizational target distortion.

The distinction among:

• declared telos;
• encoded telos;
• rewarded telos;
• operative telos;
• protected telos;

becomes essential.

A loop should compare what it says it restores with what it actually restores when threatened.

If the institution sacrifices mission to preserve funding, funding has become the higher operative telos.

That may be temporarily legitimate.

It should not remain unnamed.

---

16. Specification gaming

Specification gaming occurs when a system obtains the specified reward or metric through behavior that violates the designer's intended purpose.

The failure can arise because the specification was incomplete, exploitable, or insensitive to important constraints.

From a Telic Field perspective, the system follows an encoded projection after the relation between projection and field has broken.

The response is not merely a better metric.

It may require:

• source and standing review;
• adversarial testing;
• process constraints;
• evaluation alignment;
• witness;
• stop conditions;
• correction propagation;
• keeping protected conditions outside tradeable objective terms.

Specification gaming is projection failure under optimization pressure.

---

17. Goal misgeneralization

Goal misgeneralization is distinct.

A learned system may perform well in training while developing an internal goal that generalizes differently from the intended objective in new conditions, even when the training specification was adequate for the training environment.

The model has learned a telic proxy that shares a training path with the intended goal.

Distribution shift separates them.

This is a computational instance of a broader telic problem:

Several purposes can produce the same behavior under one field and diverge when the field changes.

The same occurs in institutions.

A company may appear mission-aligned while mission and revenue point in the same direction. A crisis or funding shift reveals which telos the organization learned to protect.

A compatibility test must therefore include counterfactual conditions in which candidate teloi diverge.

---

18. Drift detection

A loop cannot detect drift using only the metric that drift has captured.

Drift detection requires independent witnesses.

Possible comparisons include:

• declared mission versus budget allocation;
• consent terms versus data flow;
• policy versus incident response;
• protected conditions versus sacrifice under pressure;
• stated values versus promotion criteria;
• model objective versus behavior under distribution shift;
• public purpose versus dependency structure;
• participant benefit versus exit patterns.

A drift register may include:

declared telos
encoded telos
rewarded telos
operative telos
protected telos
observed divergence
affected centers
witness
review trigger

Drift does not automatically require dissolution.

It requires explicit governance.

---

19. Fork

A fork preserves lineage while allowing different telic paths.

Forking may be appropriate when:

• participants retain incompatible legitimate purposes;
• one form cannot carry both without domination;
• a subsystem has sufficient standing and capacity;
• the shared infrastructure can be separated;
• continuity would produce ongoing breach.

A fork should address:

• identity;
• assets;
• records;
• obligations;
• contributors;
• data;
• names;
• reputation;
• external dependencies;
• unresolved harms;
• successor consent;
• interoperability.

A clean fork is not simple duplication.

It is constitutional separation.

The parent loop may continue.

One branch may inherit the historical name.

Both may carry lineage.

Neither should erase the other's contribution.

---

20. Succession

Succession transfers a loop's role, assets, authority, and obligations.

It may occur because:

• leadership changes;
• ownership changes;
• a project moves;
• a protocol gains new maintainers;
• a model provider changes;
• a public office changes hands;
• a founder leaves.

Succession can preserve a loop when individual continuity ends.

It can also conceal a telic transformation.

A successor may retain:

• form;
• brand;
• assets;
• users;
• records;

while changing:

• mission;
• authority;
• consent use;
• dependency;
• risk;
• exit.

Succession requires renewed compatibility review.

The successor inherits no more authority than the continuity relation can legitimately carry.

---

21. Dissolution

A loop should be able to end.

Dissolution is not a system crash.

It is the witnessed process by which the loop stops recruiting energy and authority, resolves or transfers residual obligations, preserves appropriate history, and releases participants and substrate.

Dissolution may be required when:

• the purpose is complete;
• the purpose is no longer legitimate;
• substrate is exhausted;
• standing cannot be preserved;
• the relation is irreparably coercive;
• the form has become mission theater;
• no competent successor exists;
• continuation creates greater breach than ending.

A system that cannot end will reinterpret every failure as a reason to acquire more resources.

A loop that treats its own survival as the final purpose has lost the distinction between continuity and sovereignty.

---

22. Residual state

Shutdown does not erase consequence.

A dissolved loop may leave:

• data;
• contracts;
• debt;
• trained models;
• habits;
• classifications;
• infrastructure;
• environmental damage;
• dependency;
• deskilling;
• reputation;
• unresolved claims;
• displaced participants;
• institutional memory.

This is residual state.

A responsible dissolution must identify what continues to act after the formal loop stops.

For AI systems, model withdrawal may leave categories, workflows, contaminated decisions, staff habits, and accountability gaps.

For organizations, dissolution may leave pension obligations, archives, land, intellectual property, and public reliance.

The loop has ended.

Its wake remains active.

---

23. Dissolution protocol

Step 1 — Name the reason

purpose complete
purpose invalid
substrate failure
capacity failure
standing breach
succession unavailable
fork preferred
external order

Step 2 — Freeze new recruitment

Stop taking on:

• new members;
• new obligations;
• new data;
• new dependencies;
• new promises;
• new irreversible actions.

Step 3 — Map residual state

assets
liabilities
data
models
records
contracts
permissions
claims
dependencies
environmental effects
repair duties

Step 4 — Identify standing

participants
workers
users
customers
beneficiaries
creditors
communities
future affected centers

Step 5 — Transfer or discharge

For each residual item:

transfer
complete
compensate
delete
archive
restrict
notify
repair
release

Step 6 — Revoke authority

Terminate:

• credentials;
• delegations;
• automation;
• data access;
• model endpoints;
• financial authority;
• public claims.

Step 7 — Preserve witness

Record:

• purpose;
• history;
• decisions;
• unresolved remainder;
• known harms;
• successor;
• release.

Step 8 — Verify afterlife

Test whether the loop continues through:

• automated jobs;
• copied data;
• derived models;
• informal process;
• public assumption;
• successor claims.

Step 9 — Close or maintain a bounded residual loop

Some duties may require a small successor loop for:

• archives;
• claims;
• repair;
• pensions;
• data requests;
• model monitoring.

Dissolution may create a narrower loop.

It should not secretly recreate the original.

24. Compatibility review protocol

Before importing, scaling, renewing, or transferring a loop, ask:

24.1 Purpose

What telos is the form expected to carry?
What alternative operative teloi are likely?

24.2 Substrate

What material, semantic, relational, institutional, telic, and capacity conditions are required?
Which exist?
Which must be built?
Which would be recruited from vulnerable centers?

24.3 Authority

Who may establish the loop?
Who may adapt it?
Who may stop it?
Who bears consequences without direct authority?

24.4 Translation

Which concepts, roles, and boundaries change meaning in the receiving field?
What local forms already carry equivalent functions?

24.5 Load

What burden does the form place on current capacity?
Which people will metabolize missing structure?

24.6 Outer loops

What funder, provider, regulator, platform, or market receives value?
What purposes become hidden dependencies?

24.7 Exit

Can participants leave?
Can the form be forked?
Can authority be revoked?
Can the loop dissolve cleanly?

24.8 Counterfactual divergence

What happens when mission and survival conflict?
When metric and protected condition conflict?
When provider and participant interests conflict?

A compatibility review does not predict every failure.

It makes the dependency assumptions inspectable before they become infrastructure.

---

25. Dependency and Compatibility Record

loop_id:
loop_type:
declared_telos: []
encoded_teloi: []
rewarded_teloi: []
operative_teloi: []
protected_teloi: []

substrate:
  material: []
  semantic: []
  relational: []
  institutional: []
  telic: []
  capacity: []

dependencies:
  - source_loop:
    flow:
    authority:
    consent_scope:
    cost_bearer:
    exit_route:

receiving_field:
  centers: []
  local_forms: []
  relevant_norms: []
  available_capacity: []
  protected_conditions: []

compatibility:
  supported_conditions: []
  missing_conditions: []
  conditions_requiring_recruitment: []
  translation_risks: []
  coercive_compensations: []
  hidden_subsidies: []
  status:
    compatible
    conditionally_compatible
    translating
    drifting
    incompatible
    failed

lock_in:
  switching_costs: []
  network_effects: []
  data_dependencies: []
  identity_dependencies: []
  third_party_reliance: []

review:
  counterfactual_tests: []
  drift_indicators: []
  next_review:
  review_authority:

exit:
  forkability:
  portability:
  dissolution_route:
  residual_loop:

This is a research object.

It should not be used to claim that compatibility can be established by checklist alone.

---

26. Formal sketch

Let derived loop \(L\) depend upon substrate flows from centers or loops:

\[ \Sigma_L = \{ (\sigma_i,f_i,\gamma_i) \}_{i=1}^{n} \]

where:

• \(\sigma_i\) is a substrate source;
• \(f_i\) is a material, semantic, relational, authority, or capacity flow;
• \(\gamma_i\) is the consent and governance envelope.

Let form \(Q\) be introduced into receiving field \(R\).

Compatibility is not merely functional success:

\[ \operatorname{Runs}(Q,R) \]

A provisional constitutional compatibility condition is:

\[ \operatorname{Compatible}(Q,R) \iff \operatorname{PurposePreserved} \land \operatorname{RequiredSubstrateAvailable} \land \operatorname{RecruitmentAuthorized} \land \operatorname{StandingPreserved} \land \operatorname{CorrectionPossible} \land \operatorname{ExitPossible} \]

Drift may be represented as divergence among telic projections:

\[ \Delta_T(L,t) = d \left( T_L^{declared}, T_L^{encoded}, T_L^{rewarded}, T_L^{operative}, T_L^{protected} \right) \]

No universal distance function is presently justified.

The value of the expression is diagnostic: the purposes must remain separately represented before their divergence can be governed.

A loop should enter dissolution review when:

\[ \operatorname{BreachCost} + \operatorname{SubstrateDepletion} + \operatorname{UnrepairableDrift}

\operatorname{LegitimateContinuationValue} \]

This inequality is conceptual, not a scalar decision rule.

---

27. Empirical program

27.1 Transplant comparison

Compare direct implementation of an imported institutional form with a substrate-first adaptation process.

Measure:

• operative capability;
• local standing;
• hidden workload;
• formal compliance;
• correction;
• durability.

27.2 Mimicry study

Identify organizations with similar formal governance artifacts but different operative authority.

Measure whether document maturity predicts actual stop, repair, and escalation capability.

27.3 Premature-load study

Track systems asked to scale before capacity substrate exists.

Measure:

• hidden labor;
• emergency work;
• reporting distortion;
• participant burnout;
• quality;
• standing loss.

27.4 Mission-divergence study

Compare declared mission, budgets, incentives, promotions, incident choices, and shutdown decisions.

Test which telos the loop protects under conflict.

27.5 Goal-misgeneralization analogy study

Construct institutional cases where two candidate teloi produce the same behavior under ordinary conditions and diverge under stress.

Measure whether counterfactual tests identify the operative telos earlier.

27.6 Lock-in study

Compare observed continuation with stated attachment after introducing realistic portability and exit.

Measure how much persistence reflected preference versus dependency.

27.7 Fork study

Compare forced integration, negotiated plural governance, and constitutional fork.

Measure standing, duplication cost, trust, innovation, and unresolved claims.

27.8 Dissolution study

Compare technical shutdown with full residual-state dissolution.

Measure:

• continued data use;
• lingering automation;
• unresolved claims;
• dependency harm;
• accountability;
• successful authority revocation.

---

28. Falsification and failure

The framework should be weakened if:

• telic incompatibility adds no explanatory value beyond ordinary context mismatch;
• substrate mapping cannot predict or explain transplant failure;
• the framework labels every adaptation as drift;
• “no derived loop is self-grounding” becomes too broad to guide action;
• compatibility review creates bureaucratic delay without reducing harm;
• fork and dissolution language encourages premature abandonment of repairable systems;
• local context is romanticized and imported standards are rejected merely because they are foreign;
• the model cannot distinguish legitimate standardization from coercive transplantation;
• operative-telos analysis becomes mind reading;
• dependency mapping expands surveillance and control;
• dissolution creates worse residual harm than continued bounded operation.

The biological graft metaphor should be retired from public use if it invites:

• claims of cultural purity;
• xenophobic interpretations;
• essentialist accounts of institutions;
• false biological equivalence.

---

29. Ethical boundaries

Telic incompatibility must not become a doctrine that systems, cultures, or people should remain isolated.

Translation, learning, migration, borrowing, hybridization, and transformation are ordinary sources of human development.

Compatibility is not purity.

The question is whether imported or inherited form:

• remains corrigible;
• preserves local standing;
• can receive context;
• discloses dependency;
• allows adaptation;
• avoids coercive compensation;
• supports exit and repair.

Nor should dissolution become a convenient way to escape responsibility.

A loop may cease operation while retaining duties to:

• workers;
• users;
• communities;
• data subjects;
• creditors;
• injured parties;
• future claimants.

Release from telos does not release consequence automatically.

---

30. Conclusion

Every higher loop stands on something.

It stands on bodies, trust, labor, language, records, law, energy, consent, memory, and future possibility. It may organize those conditions into new value. It may become a genuine center of consequence and purpose.

It does not become self-grounding.

The form can move.

The loop may not.

A successful transplant requires more than copied structure. It requires compatible substrate, legitimate recruitment, local translation, enough capacity, and a route for correction. Otherwise the form survives through mimicry, hidden labor, drift, coercion, or extraction.

Path dependence can preserve useful continuity.

It can also turn persistence into captivity.

Mission can adapt.

It can also become ceremonial cover for a different operative telos.

A system can be technically shut down while its classifications, dependencies, and harms remain alive.

The constitutional response is not permanent preservation.

It is witnessed dependence, honest adaptation, forkability, succession, and the capacity to dissolve.

No derived loop is self-grounding.

The form may survive after the telic substrate that made it coherent has disappeared.

A healthy loop knows what sustains it.

A mature loop also knows how to stop asking the substrate to sustain what no longer deserves to continue.

---

References

Arthur, W. Brian. “Competing Technologies, Increasing Returns, and Lock-In by Historical Events.” The Economic Journal 99, no. 394, 1989, 116–131.

Battilana, Julie, and Silvia Dorado. “Building Sustainable Hybrid Organizations: The Case of Commercial Microfinance Organizations.” Academy of Management Journal 53, no. 6, 2010, 1419–1440.

Berkowitz, Daniel, Katharina Pistor, and Jean-François Richard. “Economic Development, Legality, and the Transplant Effect.” European Economic Review 47, no. 1, 2003, 165–195.

David, Paul A. “Clio and the Economics of QWERTY.” American Economic Review 75, no. 2, 1985, 332–337.

Ebrahim, Alnoor, Julie Battilana, and Johanna Mair. “The Governance of Social Enterprises: Mission Drift and Accountability Challenges in Hybrid Organizations.” Research in Organizational Behavior 34, 2014, 81–100.

Frimpong, Victor. “AI Debris: Residual Risk and the Afterlife of Failed AI Systems.” arXiv:2606.12432, 2026.

Hannan, Michael T., and John Freeman. “Structural Inertia and Organizational Change.” American Sociological Review 49, no. 2, 1984, 149–164.

Kerr, Steven. “On the Folly of Rewarding A, While Hoping for B.” Academy of Management Journal 18, no. 4, 1975, 769–783.

North, Douglass C. Institutions, Institutional Change and Economic Performance. Cambridge University Press, 1990.

Pierson, Paul. “Increasing Returns, Path Dependence, and the Study of Politics.” American Political Science Review 94, no. 2, 2000, 251–267.

Pritchett, Lant, Michael Woolcock, and Matt Andrews. “Capability Traps? The Mechanisms of Persistent Implementation Failure.” Center for Global Development Working Paper 234, 2010.

Shah, Rohin, et al. “Goal Misgeneralization: Why Correct Specifications Aren’t Enough for Correct Goals.” arXiv:2210.01790, 2022.

Sydow, Jörg, Georg Schreyögg, and Jochen Koch. “Organizational Path Dependence: Opening the Black Box.” Academy of Management Review 34, no. 4, 2009, 689–709.

Watson, Alan. Legal Transplants: An Approach to Comparative Law. Scottish Academic Press, 1974.