Replacement or Fork Decision Record¶
Decision record — instantiates Identity-Bounded Change
The authoritative record that declares whether a change continues the same entity, replaces it, or forks a new line — naming who decided, under what rule, and preserving the link to the predecessor.
A Replacement or Fork Decision Record captures the moment the identity question is settled: it records the verdict that a given change is a continuation, a replacement, or a fork — and, crucially, who had the authority to declare it and which rule they applied. Its defining move is making that call explicit and accountable rather than letting a filename, a version bump, or organizational habit decide it silently. When the verdict is "replace" or "fork," the record preserves the link to the predecessor so history is not erased, and it typically turns on a compatibility test: a change that breaks the guarantees dependents rely on is the signal that the thing has become a successor rather than the same thing continued.
Example¶
In 2016 the Ethereum community faced a contested change after the exploit of an application called "The DAO": alter the ledger's history to reverse the theft, or leave the chain as it was. The change was backward-incompatible — nodes that rejected it would follow a different chain from those that accepted it. The choice, made through the project's governance, was in effect a fork: the amended chain carried on as Ethereum, while the unaltered chain persisted as Ethereum Classic, each with a declared lineage from the shared predecessor.
A Replacement or Fork Decision Record is what formalizes exactly that: who decided, under what rule, which line inherits which identity, name, and obligations, and how the two relate to the predecessor. The value is that instead of two chains both asserting "we are the real one," there is a documented verdict about which change continued the identity and which began a new one — with the predecessor relation preserved rather than argued over after the fact.
How it works¶
What distinguishes it from a mere log of what changed:
- It classifies, it doesn't just describe — the entry records the category of the event: continue / replace / fork / split / merge.
- It names the deciding authority and the invoked rule — a maintainer, a board, a regulator — so the verdict is accountable to someone and to a stated criterion, not to convenience.
- It hinges on a compatibility test — how badly the change breaks the guarantees dependents rely on is what pushes a change from in-place continuation toward a new identity.
- It preserves predecessor links and an effective date, so downstream references can attach obligations and permissions to the right identity.
Tuning parameters¶
- Authority level — who may declare a replacement or fork; higher authority lends the verdict legitimacy but slows the call.
- Compatibility test — how breaking a change must be to force a new identity rather than a continuation; a strict test forks readily, a loose one preserves identity through larger changes.
- Predecessor-linking depth — how much of the prior lineage, obligations, and citations the record carries forward to the successor.
- Reversibility of the verdict — whether a decision is provisional (revisitable as evidence lands) or final; provisional verdicts hedge genuine uncertainty but leave identity briefly ambiguous.
When it helps, and when it misleads¶
Its strength is that it turns a contested "is it still the same?" into an accountable, citable verdict with a named authority and preserved history — preventing the two worst outcomes at once: a replacement laundered as a continuation (to inherit a name and its obligations) and a genuine continuation needlessly declared dead.
The hard part is where to draw the line, which is at bottom a question about essential versus accidental properties[n1] — which changes touch the entity's defining nature and which do not — and reasonable authorities disagree. The classic misuse is writing the record to rubber-stamp a decision already made for convenience or politics: declaring continuity to inherit a valuable identity, or declaring a fork to shed inconvenient obligations. The discipline that guards against it is to state the replace/fork rule and the compatibility test before the change, require the named authority to reason against them in the record, and always preserve the predecessor link so a contested verdict stays auditable.
How it implements the components¶
This record fills the decision-and-authority components of the archetype — the ones that settle and own the identity verdict:
replacement_or_fork_rule— it applies and documents the rule distinguishing a continuation from a replacement or fork.decision_authority— it names the party authorized to make and own the identity verdict.compatibility_rule— it uses the breaking-versus-compatible test as the trigger that pushes a change from in-place continuation toward a new identity.
It does not assess the cumulative drift that motivates the call (that's Identity Continuity Review), nor record the mechanical before/after of the split or merge itself (that's Split/Merge Change Log).
Related¶
- Instantiates: Identity-Bounded Change — it is where the archetype's continuation-versus-replacement decision is made explicit, authorized, and recorded.
- Consumes: Identity Continuity Review — its continuity verdict is the evidence the decision formalizes and acts on.
- Sibling mechanisms: Identity Continuity Review · Split/Merge Change Log · Version Control System · Event-Sourced Entity History · Conservation Treatment Record · Document Revision History · Persistent Identifier Resolver · Chain-of-Custody Record · Legal Amendment Record · Policy Amendment Register
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Replacement or Fork Decision Record operates as a persistent ledger, log, register, or case record that preserves history and traceability because it the authoritative record that declares whether a change continues the same entity, replaces it, or forks a new line — naming who decided, under what rule, and preserving the link to the predecessor.
Independent corroboration: The frozen evidence defines Replacement or Fork Decision Record as 'The authoritative record that declares whether a change continues the same entity, replaces it, or forks a new line — naming who decided, under what rule, and preserving the link to the predecessor', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Computer Science & Software Engineering
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Branching and forking preserve a predecessor-linked history while declaring a new development line; archival identity and legal succession independently govern continuity outside software.
Related originating lineages:
- Law & Governance — law_governance contributes rights, duties, authorization, disclosure, and accountable procedure to the mechanism’s formative or independently convergent form; that contribution does not displace the primary computer_science lineage.
- Library & Information Science — library_information_science contributes classification, provenance, access, and persistent-reference stewardship to the mechanism’s formative or independently convergent form; that contribution does not displace the primary computer_science lineage.
Review resolution: Neither blind primary fully captures the historical lineage; authoritative research supports the better third domain computer_science. Branching and forking preserve a predecessor-linked history while declaring a new development line; archival identity and legal succession independently govern continuity outside software. The cited Git documentation: Git Branching provides direct evidence for that defining form. Alternates are retained only where they contributed an independent formative tradition, while domain_reach=multi_domain records later transfer separately from historical origin.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] The distinction between essential properties — those a thing cannot lose without ceasing to be what it is — and accidental properties — those it can change while remaining itself — rooted in Aristotelian metaphysics. Deciding whether a change is a continuation or a replacement is, at bottom, a judgment about which of the entity's properties are essential. ↩