Introduction

APS seeks to explain how increasingly complex forms of living organisation become possible. Throughout the framework, explanatory pathways are used to connect concepts that appear to stand in systematic organisational relationships with one another. These pathways are not intended merely as summaries of previously established ideas. They are explanatory tools that help reconstruct how different forms of organisation relate, identify transitions that require investigation, and reveal the continuity linking life, cognition, mind, meaning, morality, and ethics.

Yet the use of pathways immediately raises a methodological question. Why should these concepts appear in this order? At first glance, a pathway can seem persuasive simply because it is visually coherent. An arrow may suggest necessity even when no argument has been supplied. A progression from agency to evaluation, or from significance to cognition, can appear to express little more than the theoretical preferences of the person who arranged the sequence. Unless the status of each transition is made explicit, a pathway risks becoming conceptual storytelling presented in diagrammatic form.

APS accepts the legitimacy of this concern. A sequence does not become scientifically credible because its concepts are plausible, its transitions are intuitive, or its visual structure is elegant. Every arrow requires justification. The framework must explain what relationship the arrow represents, why that relationship is proposed, what evidence supports it, what observations might challenge it, and whether alternative architectures provide a more adequate explanation.

Architectural Dependency is the methodological principle through which APS addresses this challenge. Rather than treating pathways as conceptual narratives, APS interprets them as hypotheses concerning the organisational conditions through which increasingly complex forms of living organisation become possible. The central question guiding this methodology is straightforward:

What organisational conditions must already be present for this phenomenon to become possible?

Architectural Dependency provides a systematic way of investigating that question and evaluating the answers that emerge.

Why APS Uses Explanatory Pathways

APS frequently presents concepts in pathways such as:

Agency → Biological Evaluation → Significance

or:

Biological Evaluation → Significance → Meaning → Value → Human Values → Shared Evaluation → Social Norms → Moral Evaluation → Morality → Ethics

These pathways occupy an important place within the explanatory organisation of the framework because they reveal how concepts relate to one another, identify organisational transitions that require explanation, and make visible the continuity linking increasingly complex forms of organisation. Their purpose is not simply to arrange concepts in a memorable sequence but to propose relationships that can be examined, supported, challenged, or revised.

More importantly, pathways allow APS to move beyond isolated definitions. Biological concepts rarely function as independent explanatory units. Agency, evaluation, significance, cognition, mind, and morality do not exist as separate explanatory islands. Each participates in broader organisational architectures whose structure itself requires explanation. Pathways therefore provide a means of reconstructing those architectures and making their underlying assumptions explicit.

Their value, however, depends entirely upon the legitimacy of the relationships they represent. An arrow is not a decorative feature of a diagram, nor is it a substitute for argument. Each transition must correspond to a defensible claim concerning organisation. APS pathways should therefore not be interpreted as self-validating diagrams. They represent dependency hypotheses.

A dependency hypothesis proposes that one form of organisation establishes conditions required for another form of organisation to emerge, operate, persist, or become intelligible. The order of concepts is consequently neither decorative nor merely pedagogical. It expresses a claim about organisational conditions of possibility. When APS proposes:

Biological Evaluation → Significance

it is not merely placing two associated concepts beside one another. It is proposing that conditions become significant because evaluative activity establishes that they matter differently for an agent. Likewise, when APS proposes:

Social Norms → Moral Evaluation

it is not simply suggesting that norms are historically earlier than moral reflection. It is proposing that socially organised expectations provide conditions through which assessment, criticism, justification, and revision become possible.

These are substantial explanatory claims. They may be supported, refined, challenged, or rejected. Their scientific value depends upon making their structure available for investigation rather than treating them as assumptions built into the architecture. Architectural Dependency provides the methodological framework through which that investigation proceeds.

What Is Architectural Dependency?

Architectural Dependency is a relationship in which one form of organisation establishes conditions necessary for the emergence, operation, intelligibility, or persistence of another.

The term architectural indicates that the relationship concerns organised conditions rather than isolated components. A later phenomenon depends not merely upon the physical presence of an earlier component but upon an organisation already capable of supporting what follows. Dependency therefore concerns how activities, constraints, relations, capacities, and processes must be organised before a further organisational achievement becomes possible.

The term dependency indicates that the later organisation cannot be adequately understood as wholly independent of those prior conditions. This does not imply identity between earlier and later forms of organisation, nor does it imply that one mechanically produces the other. Dependency identifies a relationship of organisational requirement while preserving the explanatory distinctiveness and novelty of what emerges.

Within APS, Architectural Dependency functions as a methodological principle rather than an explanatory projection. It should not be added to Agency, Process, and Scale as a fourth component of the framework. Agency, Process, and Scale are complementary analytic perspectives on one viability-oriented, constraint-closed organisation. Architectural Dependency performs a different task. It provides a method for reconstructing relationships among forms of organisation and evaluating the explanatory architectures built from those relationships.

Architectural Dependency therefore asks:

What organisational conditions must already be established before this phenomenon becomes possible?

This question differs from asking only what caused an event, what occurred earlier in time, or what components compose a system. It seeks to identify the organisational conditions presupposed by the phenomenon under investigation.

Consider Biological Evaluation. APS understands evaluation as the process through which agency generates significance. Evaluation requires more than differential physical response. It requires a living organisation whose activity is modulated relative to conditions bearing upon viability and continued functioning. Agency therefore supplies an organisational condition required for Biological Evaluation.

Significance, in turn, depends upon Biological Evaluation. Conditions become significant because evaluative activity establishes that they matter differently for an agent. This does not reduce significance to the mechanics of response. Rather, it identifies the organisational relationship through which mattering becomes possible.

The pathway:

Agency → Biological Evaluation → Significance

therefore expresses two linked organisational dependency claims rather than a simple list of associated concepts.

Architectural Dependency provides the methodological framework through which such claims can be formulated, evaluated, challenged, refined, and, where necessary, revised.

What Does an APS Pathway Arrow Mean?

An APS pathway arrow should be read as a compressed organisational dependency claim.

In its most general form:

A → B

means:

Organisation A establishes one or more conditions necessary for the emergence, operation, intelligibility, or persistence of Organisation B.

The arrow does not establish the claim by itself. It records a proposed relationship that must be defended through argument, clarified through definition, and assessed against relevant evidence.

Different arrows may express different forms of dependency. Some relationships are close to constitutive. Life and Biological Agency are related because agency is the present-tense activity through which living organisation is enacted and sustained. Other relationships are enabling. Integration enables significance to become organised into functional unity without constituting cognition itself. Still others involve explanatory presupposition. Ethics presupposes morality because ethical inquiry requires moral practices, obligations, institutions, beliefs, or forms of concern to investigate.

Pathway arrows therefore should not be interpreted as if they all represented a single mechanism. Their shared meaning is more disciplined and more limited. They indicate that the later organisation depends upon conditions established earlier in the architecture.

This interpretation carries an important consequence. An arrow should never be inserted merely because two concepts appear naturally associated. APS must be able to specify what organisational development occurs at the transition. For example:

Shared Evaluation → Social Norms

requires the claim that recurring collective evaluation becomes sufficiently stabilised to generate expectations concerning conduct. Similarly:

Social Norms → Moral Evaluation

requires the claim that socially sustained expectations become objects of assessment, criticism, justification, and revision. And:

Morality → Ethics

requires the claim that organised moral life becomes the object of reflective investigation.

Each transition introduces a distinct organisational development. If that development cannot be identified, the dependency claim remains unsupported.

The pathway format therefore imposes a methodological obligation upon APS. It requires the framework to make organisational dependencies explicit, distinguish them from neighbouring relationships, and expose them to challenge. APS pathways should consequently be read neither as completed demonstrations nor as speculative illustrations. They are compact representations of structured hypotheses concerning the organisational conditions through which increasingly complex forms of living organisation become possible, persist, and become intelligible.

Types of Architectural Dependency

Not all organisational dependencies are alike.

Some forms of organisation are so closely related that the later phenomenon exists partly through organisational structures already present in the earlier one. Other relationships are less intimate. In these cases, the earlier organisation establishes conditions that make a later phenomenon possible without constituting it. Distinguishing between such relationships is important because APS pathway arrows do not all express the same kind of dependency.

APS therefore recognises a small number of dependency forms while distinguishing them from the evidential strategies used to support dependency claims.

Organisational Dependency

Architectural Dependency is the methodological investigation of organisational dependencies. Organisational dependency refers to the relationship itself, whereas Architectural Dependency refers to the explanatory framework through which such relationships are identified, evaluated, compared, and revised.

Organisational dependency is the general category to which all Architectural Dependencies belong.

An organisational dependency exists whenever one form of organisation establishes conditions required for another form of organisation to emerge, operate, persist, or become intelligible. Architectural Dependency is therefore concerned with organisational relationships rather than causal sequences, temporal orderings, or conceptual associations. The central question is always whether the later phenomenon genuinely presupposes organisational conditions established by the earlier one.

Every APS pathway arrow ultimately expresses a claim of organisational dependency.

Constitutive Dependency

A constitutive dependency exists when the later organisation is inseparable from organisational structures already present in the earlier one.

In such cases the later phenomenon is not merely enabled. It exists partly through the organisation that precedes it.

The relationship between Life and Agency illustrates this form of dependency. APS understands Biological Agency as the present-tense activity through which living organisation is enacted and sustained. Agency is therefore not an optional addition to life. It is part of the organisation through which life persists.

The pathway:

Life → Agency

expresses a constitutive dependency because agency depends upon life as an activity of living organisation rather than as an independently existing phenomenon.

Constitutive dependencies represent the strongest dependency relationships recognised within APS because the organisational connection between earlier and later forms is especially close.

Enabling Dependency

An enabling dependency exists when one form of organisation establishes conditions that make another form of organisation possible without constituting it.

Most APS pathway relationships appear to take this form.

Consider the relationship between Biological Evaluation and Significance. APS proposes that significance arises because evaluative activity establishes differential consequences for organised persistence. Evaluation therefore creates conditions under which significance becomes possible. Yet significance is not identical with evaluation. It possesses its own explanatory role and organisational properties.

The pathway:

Biological Evaluation → Significance

therefore expresses an enabling dependency.

The later phenomenon depends upon the earlier one while remaining organisationally distinct from it.

Many of the transitions linking significance, integration, cognition, mind, selfhood, reflective agency, and meaning are best understood in these terms.

Dependency Forms and Explanatory Practice

The distinction between constitutive and enabling dependency should not be interpreted as a rigid classification imposed upon every pathway. Its purpose is explanatory rather than taxonomic. The distinction helps clarify the nature of the organisational relationship being proposed.

The guiding question remains unchanged:

What organisational conditions must already be present for this phenomenon to become possible?

Different answers reveal different forms of dependency.

Architectural dependency and organisational transition address different explanatory questions.

Architectural dependency identifies relations of organisational necessity. It asks what must already be organised for a capacity, process, or form of activity to operate or become intelligible.

Organisational transition asks how those relations become established, reorganised, or stabilised through time.

Architectural dependency maps necessary organisational relations. Organisational transition explains how those relations become operative.

The two approaches are therefore complementary. Dependency identifies the architecture of a system; transition investigates the transformations through which that architecture emerges, changes, or becomes consolidated.

Dependency and Evidence

Dependency relations should be distinguished from the evidence used to support them.

A common mistake is to treat developmental order, evolutionary history, or comparative similarity as dependency relations in their own right. APS rejects this interpretation because dependency and evidence perform different explanatory functions. Dependency identifies an organisational relationship. Evidence helps determine whether that relationship is well supported.

Developmental, evolutionary, and comparative analyses therefore do not define dependencies. They provide reasons for accepting, rejecting, strengthening, or revising dependency claims. A developmental sequence may reveal an organisational dependency. An evolutionary transition may support one. Comparative variation may increase or decrease confidence in a proposed architecture. Yet none of these observations establishes dependency by itself.

Maintaining this distinction is important because it prevents evidential support from being confused with explanatory structure. APS pathways identify proposed organisational relationships. Developmental, evolutionary, and comparative evidence help determine whether those proposals are justified.

Dependency is not transition

A pathway showing that one capacity depends upon another does not by itself explain how that capacity arose.

For example, a pathway may show that cognition depends upon biological evaluation and significance. This identifies an organisational dependency. It does not automatically explain the developmental, evolutionary, or historical transition through which cognitive organisation became possible.

Dependency explains necessity. Transition explains transformation.

How APS Validates Dependency Claims

If Architectural Dependency is to function as a scientific methodology rather than a conceptual preference, APS must provide a systematic way of evaluating dependency claims. A pathway arrow cannot be justified merely because a sequence appears intuitive, aesthetically satisfying, or consistent with the broader architecture of the framework. Every proposed dependency must be supported by explicit argument and assessed against identifiable standards.

The central methodological question is therefore:

How do we know whether a dependency claim is justified?

APS answers this question by distinguishing dependency relations from the evidence used to support them. A dependency claim proposes that one form of organisation establishes conditions required for another. Validation concerns the assessment of that proposal. The goal is not to prove dependency with absolute certainty but to determine whether the proposed organisational relationship provides the most coherent and explanatory account currently available.

No single form of evidence is sufficient in isolation. Organisational relationships are rarely established by a single observation, experiment, or developmental sequence. Instead, dependency claims are strengthened when multiple lines of support converge upon the same explanatory architecture. For this reason APS employs a family of complementary validation criteria, each addressing a different aspect of organisational necessity.

Organisational Necessity

The most important validation criterion concerns organisational necessity.

A dependency claim is strengthened when the later phenomenon cannot be adequately characterised without reference to the organisation proposed as its prerequisite. The question is not whether the earlier phenomenon happened first, nor whether the two phenomena are correlated. The question is whether the later organisation remains intelligible once the proposed prerequisite is removed.

For example, APS proposes:

Biological Evaluation → Significance

This dependency claim becomes stronger if significance cannot be adequately explained without evaluative activity. If conditions matter differently for an agent because they are differentially evaluated relative to organised persistence, then evaluation establishes an organisational condition required for significance. If significance could be explained equally well without reference to evaluation, the dependency would weaken.

Organisational necessity therefore directs attention toward explanatory indispensability rather than temporal order. It asks whether the later organisation genuinely presupposes the earlier one or merely happens to coexist with it.

Explanatory Necessity

Organisational necessity concerns the phenomenon itself. Explanatory necessity concerns the adequacy of explanation.

A dependency claim gains support when explanation of the later phenomenon requires systematic reference to the earlier organisation. The issue is not whether the earlier phenomenon participates in the explanation but whether the explanation becomes incomplete, incoherent, or substantially weakened when that reference is removed.

Consider the relationship:

Social Norms → Moral Evaluation

APS proposes that moral evaluation depends upon socially organised expectations concerning conduct. If attempts to explain moral evaluation repeatedly require reference to norms, obligations, expectations, or standards sustained within a social community, then explanatory necessity supports the dependency claim.

Explanatory necessity is especially important because it helps distinguish genuine dependencies from mere associations. Two concepts may frequently appear together without one being required for explanation of the other. Dependency becomes more plausible when explanatory reconstruction consistently returns to the same organisational prerequisite.

Counterfactual Dependency Testing

The strongest validation criterion often takes counterfactual form.

A dependency claim can be investigated by asking:

What would the later phenomenon look like if the proposed prerequisite were absent?

The purpose of this question is not speculative imagination but explanatory stress testing. If a coherent account of the later organisation remains possible without the earlier condition, the dependency weakens. If the later phenomenon becomes unintelligible, the dependency strengthens.

For example, APS proposes:

Agency → Biological Evaluation

The relevant question becomes:

What would Biological Evaluation be if agency were absent?

If evaluation requires a living organisation actively regulating conditions relative to viability, then the removal of agency may eliminate the phenomenon being explained. In that case the dependency gains support.

Counterfactual analysis is especially valuable because it forces dependency claims to expose their organisational commitments. A proposed dependency must show not merely that the earlier phenomenon contributes to the later one but that its absence would significantly alter or undermine the organisational architecture.

Developmental Support

Developmental evidence can provide important support for dependency claims.

If one form of organisation consistently appears only after another has become established during development, this pattern may indicate an underlying organisational relationship. Developmental trajectories often reveal which capacities, structures, or activities must already be present before later organisational achievements become possible.

Developmental support, however, should not be confused with dependency itself. A developmental sequence does not automatically establish an organisational dependency. Earlier developmental appearance may simply reflect contingent biological history. The significance of developmental evidence therefore depends upon whether it aligns with an independently plausible dependency claim.

Developmental observations are most valuable when they reveal organisational transitions that mirror the architecture proposed by the dependency framework.

Evolutionary Support

Evolutionary history can provide a second source of support.

Many APS pathways concern organisational capacities whose historical emergence may leave detectable traces within evolutionary transitions. If a proposed dependency relationship corresponds with broad evolutionary patterns, confidence in the architecture may increase.

For example, increasingly sophisticated forms of cognition appear historically later than simpler forms of evaluative organisation. Such observations do not prove that cognition depends upon evaluation, but they may support the plausibility of that claim when considered alongside organisational and explanatory arguments.

As with developmental evidence, evolutionary support contributes to validation without determining it. Evolutionary history can strengthen a dependency claim, but dependency remains an organisational relationship rather than a historical sequence.

Comparative Support

Comparative evidence provides a third form of support.

If variation in one form of organisation is systematically associated with variation in another, this relationship may illuminate underlying dependencies. Comparative analysis allows APS to examine how organisational differences influence the presence, absence, or character of later phenomena.

For example, differences in evaluative organisation may correspond with differences in significance processing. Variations in cognitive organisation may influence forms of selfhood or reflective agency. Such observations do not establish dependency by themselves, but they may reveal recurring patterns consistent with a proposed architecture.

Comparative support is particularly valuable because it introduces variation into the analysis. Organisational dependencies become easier to investigate when systems differ in ways that make underlying relationships visible.

Rival Architecture Testing

Validation requires more than support for a preferred pathway.

A dependency claim becomes scientifically meaningful only when alternative architectures are considered and evaluated. APS must therefore compare proposed pathways against plausible rivals rather than assuming that the first coherent sequence is necessarily correct.

For example, consider the pathway:

Agency → Biological Evaluation → Significance

A rival architecture might propose:

Agency → Significance → Biological Evaluation

or:

Agency → Cognition → Biological Evaluation

The question is not whether such alternatives can be imagined. The question is whether they provide a more coherent account of the organisational relationships under investigation.

Rival architecture testing is essential because it transforms pathway construction from assertion into comparative explanation. A dependency claim gains credibility when it consistently explains organisational phenomena more effectively than competing alternatives.

Strong, Provisional, and Speculative Dependencies

Not all dependency claims possess equal evidential maturity.

Some relationships are supported by converging organisational, explanatory, developmental, evolutionary, comparative, and counterfactual considerations. Others remain plausible but incompletely developed. Still others function primarily as exploratory hypotheses whose status remains uncertain.

APS therefore distinguishes among different levels of confidence.

Strong dependencies are supported by multiple forms of evidence and survive comparison with plausible alternatives. Such dependencies remain open to revision, but they currently possess substantial explanatory support.

Provisional dependencies possess credible organisational arguments yet remain incompletely validated. They may depend upon unresolved conceptual questions, limited evidence, or ongoing theoretical development. Provisional status does not imply weakness. It reflects recognition that explanatory work remains incomplete.

Speculative dependencies represent hypotheses whose organisational plausibility exceeds their current evidential support. These dependencies may identify promising directions for inquiry, but they should not be presented as established components of the architecture.

The distinction between strong, provisional, and speculative dependencies serves an important methodological purpose. It prevents pathways from being treated as fixed doctrines while preserving their value as explanatory tools. Architectural Dependency is therefore not a mechanism for ending inquiry. It is a framework for organising and guiding inquiry.

A mature dependency architecture is one that makes its confidence levels explicit. Scientific credibility increases when uncertainty is acknowledged rather than concealed, because doing so allows dependency claims to remain open to refinement, revision, and empirical challenge.

Dependency, Feedback, and Constraint Closure

Architectural Dependency is often misunderstood because living systems are not organised as simple linear sequences. APS defines life as viability-oriented, constraint-closed organisation, and such organisation is characterised by extensive reciprocal interaction, ongoing regulation, and continuous mutual modification among organisational processes. At first glance, these features appear difficult to reconcile with asymmetrical dependency relations. If organisational forms influence one another reciprocally, how can one legitimately be said to depend upon another?

This challenge arises because dependency and influence address different explanatory questions. Architectural Dependency asks what organisational conditions must already be present for a phenomenon to become possible. Feedback, reciprocal influence, and constraint closure ask how established organisational forms interact, regulate one another, and contribute to ongoing persistence. The apparent tension therefore results from treating distinct explanatory relationships as if they were identical.

APS maintains that dependency, feedback, and constraint closure are compatible because they operate at different explanatory levels. Dependency concerns organisational prerequisites. Feedback concerns ongoing interaction. Constraint closure concerns reciprocal maintenance. Understanding these distinctions is essential if pathway architectures are to be interpreted correctly.

Dependency versus Influence

A dependency relationship identifies conditions required for the emergence, operation, intelligibility, or persistence of a later organisational form. Influence, by contrast, concerns the capacity of one established organisational form to modify, regulate, shape, or stabilise another. Although the two relationships may occur within the same system, they should not be conflated.

Consider the pathway:

Agency → Biological Evaluation

APS proposes that agency establishes conditions required for Biological Evaluation because evaluative activity presupposes a living organisation actively engaged in viability-oriented regulation. Once evaluation exists, however, evaluation may influence future agency. Evaluative activity can alter behavioural tendencies, modify patterns of interaction, and contribute to subsequent organisational regulation. The existence of this influence does not remove the original dependency. Evaluation may affect agency while still depending upon agency as a condition of its own existence.

The same logic applies throughout the framework. Significance may influence evaluation, cognition may influence significance, and reflective agency may influence selfhood. Such relationships reveal ongoing interaction among organisational forms. They do not eliminate the asymmetries that originally made those forms possible.

Dependency therefore concerns conditions of possibility. Influence concerns conditions of operation. The existence of one relationship does not invalidate the other.

Dependency versus Circular Causation

A second source of confusion arises from circular causation. Biological systems frequently exhibit reciprocal causal relationships in which the effects of one process subsequently alter the conditions under which that process continues. Such dynamics are common in physiology, development, behaviour, ecology, and social organisation.

Architectural Dependency does not deny the existence of circular causation. Rather, it addresses a different explanatory question.

Circular causation concerns the dynamics of interaction among already established organisational forms. Architectural Dependency concerns the organisational conditions required for those forms to exist in the first place. These relationships are therefore complementary rather than contradictory.

For example, APS proposes:

Biological Evaluation → Significance

Once significance exists, it may influence future evaluation. Conditions that acquire significance for an agent can reshape subsequent evaluative activity, alter behavioural priorities, and modify patterns of interaction. This reciprocal influence creates circular dynamics within the living organisation. Yet significance still depends upon evaluation because evaluative activity establishes the conditions through which significance becomes possible.

Circular causation therefore describes how organisational forms interact once established. Dependency identifies the conditions under which those forms become possible. One concerns ongoing dynamics. The other concerns organisational architecture.

Dependency versus Constraint Closure

Constraint closure occupies a central place within APS because life is understood as viability-oriented, constraint-closed organisation. Constraint closure refers to a situation in which organisational processes participate in the production, maintenance, and modulation of the constraints that sustain the system’s continued functioning. Closure therefore involves reciprocal maintenance among organisational components.

Because closure is reciprocal, it can appear incompatible with asymmetrical dependency. If organisational components participate in one another’s maintenance, why should any component depend upon another more than the reverse?

The answer lies in recognising that closure and dependency address different explanatory problems. Constraint closure concerns the maintenance of established organisation. Architectural Dependency concerns the conditions through which organisational forms become possible.

A system may therefore contain reciprocal maintenance relationships while still exhibiting asymmetrical dependencies. Once significance exists, it may contribute to the regulation of evaluation. Once evaluation exists, it may contribute to the regulation of agency. Such reciprocal influences help sustain the organisation as a whole. Yet the existence of reciprocal maintenance does not eliminate the organisational conditions required for significance, evaluation, or agency to emerge in the first place.

Constraint closure and Architectural Dependency should therefore be understood as complementary explanatory perspectives. Closure explains how organised persistence is maintained. Dependency explains how organisational architectures are structured.

Dependency and Organisational Maturity

Many apparent tensions between dependency and reciprocity disappear when organisational maturity is taken into account.

During emergence, organisational relationships are often strongly asymmetrical. One form of organisation must become established before another can arise. As development proceeds, however, organisational forms increasingly interact, regulate one another, and participate in shared patterns of maintenance. What begins as an asymmetrical dependency may become embedded within a network of reciprocal influences.

This distinction is particularly important for interpreting APS pathways. A pathway frequently identifies organisational conditions associated with emergence, intelligibility, or explanatory reconstruction. Once the organisations involved are established, they may participate in extensive reciprocal interaction without altering the underlying dependency relation.

The pathway:

Agency → Biological Evaluation → Significance

illustrates this pattern. Evaluation depends upon agency. Significance depends upon evaluation. Yet mature living organisation exhibits continual interaction among all three. The resulting reciprocity reflects operational integration rather than the disappearance of dependency.

Dependency therefore often describes organisational architecture, whereas reciprocity frequently characterises organisational operation.

Dependency and Scale

Dependency relationships may also appear differently when viewed from different scales of analysis.

A dependency that is clearly visible during development may become difficult to detect in mature behaviour. A dependency supported by evolutionary reconstruction may appear reciprocal within physiological organisation. Organisational architectures may therefore remain stable even when their manifestation varies across developmental, ecological, behavioural, physiological, or historical domains.

This observation is consistent with the APS understanding of scale. Scale identifies the spatial and temporal extent through which organisation is investigated. Architectural Dependency does not change because scale changes, but the visibility of a dependency may differ across scales.

Recognising this point helps avoid a common error. Apparently reciprocal relationships observed at one scale should not automatically be interpreted as evidence against dependency relations identified at another. Different scales may reveal different aspects of the same organisational architecture.

Modulatory Feedback versus Dependency Reversal

Feedback becomes methodologically problematic only when it genuinely removes the organisational requirement identified by a dependency claim.

Most feedback is modulatory rather than foundational. It alters how an organisational form operates without eliminating the conditions required for that form to exist. Modulatory feedback therefore strengthens, weakens, regulates, stabilises, or reshapes organisational activity while leaving the dependency architecture intact.

Dependency reversal would be fundamentally different. A reversal occurs only if the later phenomenon becomes a prerequisite for the earlier one in a way that eliminates the original asymmetry. In such cases the dependency claim itself would require revision.

APS does not assume that existing dependency architectures are immune to challenge. If convincing evidence demonstrated that a proposed prerequisite was not genuinely required, the architecture would need to be modified. The possibility of revision is part of what distinguishes Architectural Dependency from conceptual doctrine.

The important point is that feedback alone does not constitute dependency reversal. Reciprocal influence is common throughout living organisation. Genuine reversal requires evidence that the original organisational prerequisite no longer performs the explanatory role attributed to it.

Four Principles for Interpreting APS Pathways

The relationship between dependency, feedback, and constraint closure can be summarised through four interpretive principles that guide pathway construction throughout APS.

First, organisational dependency identifies conditions required for the emergence, operation, intelligibility, or persistence of a later organisational form. A pathway arrow therefore expresses a claim concerning organisational prerequisites rather than a claim concerning simple causal succession.

Second, reciprocal influence does not eliminate dependency. Once organisational forms become established, they may regulate, modify, and stabilise one another while retaining the asymmetries that originally made them possible.

Third, constraint closure and dependency are compatible because they address different explanatory questions. Constraint closure concerns reciprocal maintenance among established organisational forms, whereas dependency concerns organisational conditions of possibility.

Fourth, dependency architectures remain open to revision. Feedback, developmental evidence, evolutionary reconstruction, comparative analysis, and rival architectures may all contribute to reassessment of a dependency claim. Pathways therefore remain scientific hypotheses rather than fixed doctrines.

Taken together, these principles clarify how APS can employ pathway architectures while remaining fully consistent with the view that life is viability-oriented, constraint-closed organisation. Architectural Dependency identifies the organisational asymmetries through which increasingly complex forms of organisation become possible, while feedback and constraint closure explain how those forms subsequently participate in reciprocal patterns of maintenance and regulation. Dependency therefore concerns conditions of possibility, whereas feedback and closure concern conditions of operation. The two perspectives are complementary rather than contradictory because they address different aspects of organised persistence.

Applying Architectural Dependency

Architectural Dependency is valuable only if it can be applied. A methodological principle that remains confined to abstract discussion contributes little to biological explanation. The purpose of the framework is therefore not merely to define dependency but to provide a systematic way of constructing, evaluating, and revising explanatory architectures.

Application begins by identifying a phenomenon whose organisational conditions require explanation. The task is then to ask what forms of organisation must already be established before that phenomenon becomes possible. Each proposed answer generates a dependency claim. Those claims can then be evaluated using the criteria developed in the preceding sections, compared with rival architectures, and revised where necessary.

This procedure transforms pathway construction from conceptual arrangement into explanatory investigation. Rather than beginning with a fixed sequence and seeking evidence to support it, Architectural Dependency begins with organisational questions and uses those questions to generate hypotheses concerning conditions of possibility. Pathways are therefore products of inquiry rather than substitutes for inquiry.

The value of this approach is especially evident when applied across large explanatory domains. Complex phenomena such as cognition, mind, selfhood, morality, and ethics are often treated as isolated topics possessing independent explanatory foundations. Architectural Dependency instead asks how these phenomena relate to one another within broader organisational architectures and what conditions may be required for their emergence and intelligibility.

The APS Dependency Map provides an example of this methodology in operation.

The APS Dependency Map

One of the central explanatory architectures currently employed within APS is:

Life → Agency → Biological Evaluation → Significance → Integration → Cognition → Mind → Selfhood → Reflective Agency → Meaning

This pathway should not be interpreted as a chronological sequence, a developmental timetable, or a claim that later organisational forms can be reduced to earlier ones. It is a structured series of dependency hypotheses concerning the organisational conditions through which increasingly complex forms of living organisation become possible.

APS explains cross-scale influence through materially implemented constraints that alter the conditions under which constituent processes occur. Wider organisational relations do not supersede local causation; they modify the organisational context within which local causal processes operate.

Each transition proposes a specific organisational relationship. Life and agency are linked because living organisation is enacted through viability-oriented activity. Biological Evaluation depends upon agency because evaluation presupposes active regulation relative to conditions bearing upon organised persistence. Significance depends upon evaluation because conditions become significant through evaluative differentiation. Integration depends upon significance because what matters must become organised into functional unity before more sophisticated forms of regulation become possible.

The pathway continues by proposing that cognition depends upon the organisation of significance across time, that mind depends upon the integrated organisation of evaluative cognitive processes, that selfhood depends upon the persistent organisation of mind through change, that reflective agency depends upon selfhood, and that meaning depends upon forms of organisation capable of sustaining reflective relationships to significance, self, and world.

What is important methodologically is not whether every element of this architecture is ultimately retained. What matters is that every transition is explicit. Each dependency claim can be examined, challenged, refined, or rejected. The pathway therefore functions as a structured explanatory proposal rather than an unquestionable doctrine.

Different parts of the architecture also possess different levels of evidential maturity. Some transitions currently possess strong organisational and explanatory support. Others remain provisional and require further investigation. Recognising these differences is a methodological strength rather than a weakness because it keeps the architecture open to improvement.

The APS Dependency Map therefore serves two purposes simultaneously. It provides a working explanatory architecture for the framework while also demonstrating how Architectural Dependency generates research questions. Every arrow identifies a relationship requiring investigation. Every transition invites clarification of the organisational conditions that justify it. Every dependency claim remains open to refinement in light of future theoretical and empirical work.

Architectural Dependency as a Research Programme

Architectural Dependency is not merely a method for organising concepts that have already been explained. It is a method for identifying explanatory work that remains unfinished.

Once a dependency architecture is constructed, attention naturally shifts toward the transitions themselves. Why does one organisational form depend upon another? What evidence supports the claim? What observations might challenge it? Are rival architectures more adequate? How does the dependency appear across developmental, ecological, physiological, evolutionary, or social domains? These questions transform pathway construction into an ongoing research programme.

This feature is especially important because APS addresses phenomena that often resist simple mechanistic explanation. Cognition, mind, selfhood, meaning, morality, and ethics are frequently approached through competing conceptual traditions whose relationships remain unclear. Architectural Dependency provides a way of reconstructing those relationships while preserving the explanatory distinctiveness of each phenomenon. The result is neither reduction nor fragmentation but a structured investigation of organisational continuity.

The methodology also encourages cumulative theoretical development. As dependency claims are clarified, challenged, and revised, architectures become more precise. Strong dependencies gain additional support. Weak dependencies are reformulated or abandoned. New organisational transitions may be identified. Existing pathways may be simplified, expanded, or reorganised. In this way the architecture remains responsive to evidence while preserving explanatory coherence.

Perhaps most importantly, Architectural Dependency redirects attention toward organisational questions that might otherwise remain implicit. Rather than asking only what phenomena exist, APS asks what organisational conditions make those phenomena possible. This shift encourages explanation to focus on the structure of organised persistence itself and on the relationships through which increasingly complex forms of organisation emerge from, depend upon, and transform one another.

Architectural Dependency therefore functions not merely as a tool for representing knowledge but as a framework for generating it.

Conclusion

APS frequently employs pathways to represent relationships among concepts spanning life, cognition, mind, meaning, morality, and ethics. Such pathways are scientifically useful only if the relationships they express are made explicit and subjected to critical evaluation. Architectural Dependency provides the methodological framework through which this becomes possible.

A dependency claim proposes that one form of organisation establishes conditions necessary for another. These claims should not be confused with causal sequences, chronological order, conceptual association, or logical implication. They identify organisational conditions of possibility. Because they are explanatory hypotheses rather than assumptions, they require justification, evidential support, and continual exposure to challenge.

The methodology developed in this article provides a way of constructing, evaluating, and revising such claims. Organisational necessity, explanatory necessity, counterfactual analysis, developmental support, evolutionary support, comparative evidence, and rival architecture testing all contribute to assessment of dependency relations. None is sufficient alone, but together they provide a systematic framework for investigating organisational architectures.

Architectural Dependency also clarifies how pathway-based explanation remains compatible with viability-oriented, constraint-closed organisation. Dependency identifies organisational prerequisites. Feedback, reciprocal influence, and constraint closure describe the interactions through which established organisation is maintained and modified. These relationships are complementary rather than contradictory because they address different explanatory questions.

The broader significance of the methodology extends beyond any individual pathway. Architectural Dependency provides a principled way of reconstructing relationships among organisational forms while preserving their explanatory distinctiveness. It allows increasingly complex phenomena to be investigated as parts of coherent organisational architectures without reducing them to simpler components or treating them as isolated domains.

APS therefore employs pathways not as conceptual narratives but as structured dependency hypotheses. Their purpose is not to end inquiry but to organise it. Every arrow expresses a claim. Every claim requires justification. Every justification remains open to revision. Architectural Dependency thus provides a systematic way of investigating the organisational conditions through which increasingly complex forms of living organisation become possible. In this way pathway construction becomes not a matter of theoretical preference but a disciplined approach to biological explanation.