Organizational Continuity
Organizational Continuity is a lineage relation across interruption, evaluated under a pre-specified individuation frame.
The problem
Organization is actively realized while coordinated processes are operating.
But systems are often treated as the same system after an interval in which those processes are strongly suppressed or interrupted.
Similarity does not settle the question. A type-identical substitute or independently initialized copy can reproduce a capability without inheriting the earlier system's actual provenance.
Persistence through turnover is not the same as continuity across interruption
During ongoing operation, a system may maintain Organizational Persistence while individual nodes are replaced, roles are reassigned, and material flows pass through it.
That question is different from asking whether a resumed system after interruption continues the same lineage.
A valid node replacement can preserve the continuing organization when the replacement occurs through the organization's own causal process and the relevant role, relations, state, and interfaces are transferred or reconstructed. By contrast, reproducing the same role architecture in an independently instantiated system does not by itself establish continuity.
Thus:
node continuity is not required for Organizational Continuity
but
role/structural similarity is not sufficient for Organizational Continuity.
Current criterion
Connection Theory v4.6 states the criterion as follows:
Given a pre-specified individuation frame, Organizational Continuity holds where the resumed system is connected to the earlier system by a qualifying non-forking causal lineage carried through an identifiable continuity-bearing substrate that causally contributes to resumption.
The individuation frame specifies:
- system boundary;
- lineage level;
- adjudication interval.
The frame is chosen methodologically before the continuity judgment. Within that frame, provenance facts are empirically assessable.
Copying is not automatically a fork
A previous website formulation used a stronger "non-duplicated custody" rule. That is no longer canonical.
Copying dormant state is not itself a fork.
A fork occurs when two or more independently continuable bounded systems are instantiated from the same ancestral state within the adjudication interval.
A single migration or restoration can therefore preserve lineage when:
- the predecessor has terminated;
- no parallel independently continuable successor is realized in the relevant interval;
- the resumed system inherits a qualifying causal provenance path.
Serialized state is not the same as an external description
A continuity-bearing substrate does not have to remain continuously active, and it need not preserve one physical carrier forever. A dormant, frozen, migrated, or serialized state can participate in continuity when it is itself a causally descended state carrier of the tracked system and later resumption follows that qualifying provenance path.
This differs from independently measuring a system, retaining a description of it, allowing the earlier organization to end, and later building a new system from that external description. Informational similarity alone is insufficient; information can participate in continuity when it is itself part of the causal lineage.
Branching is judged over the declared interval
The no-fork condition is interval-relative by design. If a second independently continuable successor is instantiated from the same ancestral state within the pre-declared adjudication interval, the lineage structure in that interval is branched. That does not mean that destroying an original or creating an unrelated copy can retroactively turn an independently reconstructed system into a continuous one. Independent reconstruction does not acquire continuity merely because a competitor is absent; branch-sensitive continuity concerns the actual causal lineage being adjudicated over the declared interval.
The causal provenance of a transition is fixed by that transition; whether a lineage remains uniquely continuable is evaluated over the pre-declared adjudication interval.
Capability, persistence, and lineage are different
A system can recover an equivalent capability without continuing the earlier lineage.
A continuing organization can also lose a particular capability while remaining the same organization.
Therefore:
capability retention ≠ Organizational Persistence ≠ Organizational Continuity
and
behavioural equivalence ≠ Organizational Continuity.