Fork Decision Record¶
A per-change decision record — instantiates Carrier-Independent Work Identity Governance
A per-change record that pronounces — and preserves the reasoning for — whether a modification stays the same work or crosses the threshold into a new one.
Some changes leave a work still itself; some create a new work wearing the old one's name. Fork Decision Record is the artifact that adjudicates a specific change and preserves the call: for this modification, does the instance remain the same work, become a variant, become a derivative, or start a new work line — and why. Its defining feature is that it is event-triggered and reasoned: it fires at a particular change, applies the fork threshold to that case, records the pronouncement and the evidence behind it, and stands as the authoritative answer if the call is later contested. It is the identity-world analogue of an architecture decision record — the place a same-or-new judgment becomes explicit and durable rather than an unspoken drift.
Example¶
A design studio splits: two partners each carry on, and both want the studio's identity, portfolio, awards, and client relationships to come with them. Whose work is still "the studio," and whose is a new practice borrowing its reputation? The Fork Decision Record captures the split as a change event, applies the studio's fork threshold — how much of the defining people, body of work, and mark must carry for continuity to hold — and records the pronouncement: Practice A retains the identity and reputation lineage; Practice B is a new work line, entitled to claim heritage but not continuity. Crucially it preserves the reasoning and the evidence, so that when a past client or an awards body disputes the call, there is a determination to point to and an appeal path to follow rather than two firms each asserting they are the "real" one.
How it works¶
What distinguishes it from a standing rule or a running inventory is that it is a decision at an event. It records the triggering change, names the outcome from a fixed taxonomy (same work / variant / derivative / new line), applies the fork threshold to justify that outcome, and captures who decided, on what evidence, and how a contested call is escalated. It does not define the criterion the threshold is measured against, and it does not gather the comparative evidence — it applies the first and cites the second.
Tuning parameters¶
- Threshold strictness — how much change forks the work. Tight thresholds spawn many new works; loose ones let one identity sprawl until it means little.
- Trigger sensitivity — which changes require a record at all. Recording every edit is unworkable; recording only obvious splits misses the slow forks.
- Decision authority — who may pronounce: a single custodian, a panel, or a dispute path. Panels and appeals add legitimacy at the cost of speed.
- Outcome taxonomy — how many categories the record distinguishes (same / variant / derivative / new). More categories capture nuance; fewer are easier to apply consistently.
- Reversibility — whether a call can be reopened as evidence changes. Reopenable calls stay accurate; frozen calls give stable citations.
When it helps, and when it misleads¶
Its strength is that the hardest judgment in the archetype — is this still the same work? — becomes explicit, evidence-backed, and revisitable, instead of being settled implicitly by whoever kept the old name.
Its failure modes cluster at the threshold. The boundary is often genuinely vague — a sorites boundary, where no single change forks the work yet enough of them plainly do — so the record can manufacture false precision at a point that has none.[n1] It is easily gamed: the threshold gerrymandered to license a predetermined split, or to keep a rewritten work under the old identity so it inherits authority, citations, and rights it has not earned. And like any decision record it can be written after the fact to fit a call already made. The discipline that keeps it honest is to fix the threshold before the case is known, require external evidence — equivalence tests, a semantic diff, provenance — and keep the dispute path genuinely open.
How it implements the components¶
Fork Decision Record realizes the adjudication side of the archetype — the components that turn a live change into an explicit, appealable ruling:
fork_threshold_rule— it applies and records the threshold at which a change stops being the same work, on a specific case.identity_dispute_review_path— it is the artifact the contested-identity adjudication produces and that appeals run against; it operationalizes the review path by making the authoritative determination durable.
It does not define the standing preservation criterion or allowed-variation zone the threshold is measured against (Identity Preservation Checklist and Identity Boundary-Case Table), compute the change being judged (Semantic Diff Review), or track the resulting manifestations' supersession status (Edition and Manifestation Catalog).
Related¶
- Instantiates: Carrier-Independent Work Identity Governance — it is where the same-or-new call becomes an explicit, preserved decision.
- Consumes: Identity Boundary-Case Table and Semantic Diff Review supply the calibrated cases and the change evidence the call is justified against.
- Sibling mechanisms: Governed Translation or Adaptation Review · Identity Boundary-Case Table · Abstract Work Register · Archival Provenance Metadata Template · Edition and Manifestation Catalog · Identity Preservation Checklist · Migration Context Preservation Plan · Persistent-Identifier Resolution Policy · Semantic Diff Review · Version Lineage Graph · Work–Expression–Manifestation Matrix
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Fork Decision Record operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a per-change record that pronounces — and preserves the reasoning for — whether a modification stays the same work or crosses the threshold into a new one.
Independent corroboration: The frozen evidence defines Fork Decision Record as 'A per-change record that pronounces — and preserves the reasoning for — whether a modification stays the same work or crosses the threshold into a new one', so its operative form is Record, Log & Register.
Nearest alternative: Decision, Gate & Allocation — The record preserves a case-specific fork disposition and reasoning after applying a separate threshold; decision provenance is its lasting value.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Library and information science are primary because bibliographic identity and provenance distinguish a work, expression, and derived version. Law contributes derivative-work authority and software contributes fork histories; the named record synthesizes those lineages for multi-domain use.
Related originating lineages:
- Computer Science & Software Engineering — Forks, version lineages, and architecture decision records supply the contemporary record form.
- Law & Governance — Authoritative determinations of identity, derivation, continuity, and appeal are grounded in legal and governance adjudication.
Review resolution: Library and information science are primary because bibliographic identity and provenance distinguish a work, expression, and derived version. Law contributes derivative-work authority and software contributes fork histories; the named record synthesizes those lineages for multi-domain use.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
This record captures the decision; it is not the running status board. Once a fork call is made, tracking which manifestation supersedes which belongs to the Edition and Manifestation Catalog. And the specific class of translation, adaptation, or re-implementation changes is worked up first by the Governed Translation or Adaptation Review, whose determination is then recorded here — the review reasons about that case; the record makes it authoritative.
[n1] The sorites ("heap") paradox: removing one grain never turns a heap into a non-heap, yet removing enough grains plainly does — an argument that identity concepts with no sharp boundary still carry a real difference between the ends. It is the classic warning against demanding false precision at a genuinely vague threshold, which is exactly where a fork call sits. ↩