LHRM — Liability Historical Record Module
LHRM — Liability Historical Record Module
Architecture: LIGA™ — Liability Governance Architecture
Parent Standard: Liability Continuity & Finality Standard (LCFS)
Category: Governance & Enforcement
Subcategory: Liability Governance
Type: Core Module
Governed Space: Liability Historical Record
Module ID: LIGA-LCFS-LHRM-001
Origin ID: OOF.CM.LIGA.12.02.01
Version: 1.0
Status: Canonical · Open Standard
Effective Date: 25 September 2026
Compatibility: OOF® Methodology OS™ · Modular OOF® Architecture Ecosystem
AI-Readable: Yes
Authority: OOF® — OriginOpen® Foundation
Protection: MIP® — Methodological Intellectual Property
Canonical Language: English (UCL™)
Canonical Definition
The Liability Historical Record Module (LHRM) governs the formation, preservation, organization, and reconstructability of the historical record of a Liability requirement, Liability Relationship, or Liability Network across its governed lifecycle.
LHRM transforms the continuity structure established by LCOIM into a chronologically and structurally coherent Liability history that preserves material governance states, transitions, determinations, changes, corrections, Transfers, Recourse, Resolution, Discharge, Re-entry, and Finality-related events without replacing earlier states with later ones.
Its purpose is to ensure that the current or terminal Liability state can be understood through the complete governed path that produced it.
Its principal output is:
Governed Liability Historical Record
Its foundational distinction is:
Current Liability State ≠ Complete Liability History.
Operational Role
The operational role of LHRM is:
to preserve a complete, ordered, attributable, and reconstructable history of material Liability governance states and transitions so that current State, Finality assessment, Re-entry, and future review can be understood without rewriting the lifecycle that produced them.
Position in the LCFS Internal Flow
The LCFS internal module progression is:
Liability Continuity Identification → Liability Historical Record → Liability Finality Assessment → Liability ReEntry → Liability Finality Record LHRM governs:
Liability Historical Record
Its principal input is:
Governed Liability Continuity Identification Structure
Its principal output is:
Governed Liability Historical Record
The output proceeds to:
LFAM — Liability Finality Assessment Module
Central Operational Question
What material Liability states, determinations, relationships, transitions, changes, and terminal events must be preserved, in what sequence and with what provenance, so that the complete Liability lifecycle remains historically reconstructable?
Historical Record Object
Every historical record should identify the Liability structure whose history is being preserved.
The Historical Record Object may be:
a Liability requirement, a Liability Relationship, a group of Relationships, a Recourse Relationship, or a Liability Network.
Historical Record Object vs Liability Object
The Historical Record Object is not necessarily identical to the original Liability Object.
Therefore:
Historical Record Object ≠ Liability Object by default.
Historical Record Boundary
The record should define which states, Relationships, Subjects, events, and governance transitions belong within the historical boundary.
The boundary should be broad enough to preserve reconstructability without absorbing unrelated Liability structures.
Origin Record
The historical record should preserve the applicable Liability Origin association.
A later lifecycle state should remain traceable to that Origin.
Context History
Material Liability Context relevant to understanding the lifecycle should remain reconstructable where applicable.
Liability Object History
Material changes to the identification, Scope, Boundary, or representation of the Liability Object should remain historically visible.
Liability Basis History
The record should preserve the Liability Basis under which potential Liability was governed and material changes to that Basis.
Relationship History
The historical record should preserve the formation, modification, continuation, termination, and other material states of relevant Liability Relationships.
Subject History
Material Subject roles should remain reconstructable across the lifecycle.
A later Subject configuration should not erase an earlier valid configuration.
Therefore:
Current Subject Structure ≠ Complete Subject History.
Conditions History
Material Liability Conditions and changes to their states should remain historically identifiable where relevant to later Liability governance.
Connection History
Material Liability-Relevant Connections supporting Determination should remain traceable to the Determination states they informed.
Determination History
The historical record should preserve material Liability Determinations, including later correction, reassessment, supersession, or Re-entry.
Therefore:
Current Liability Determination ≠ Complete Determination History.
Attachment History
Where Liability attachment was governed explicitly, the historical record should preserve when and how the applicable Liability became attached or determined.
Scope History
Changes in Liability Scope should remain historically represented.
Therefore:
Current Liability Scope ≠ Complete Liability Scope History.
Allocation History
Changes in Liability Allocation should remain historically represented.
Therefore:
Current Liability Allocation ≠ Complete Liability Allocation History.
State History
LHRM should preserve material Liability States and the transitions between them.
State Transition Record
A State transition should identify, where applicable:
prior State, new State, transition Basis, effective time, authority, relevant evidence association, and provenance.
Current State vs Historical State
A current State should not replace earlier valid states.
Therefore:
Current Liability State ≠ Historical Liability State.
Change History
Material Liability changes should remain represented even where the resulting current state no longer displays the prior configuration.
Transfer History
Where Liability is transferred, the historical record should preserve:
pre-Transfer state, Transfer structure, affected Subjects, affected Liability requirement, effective time, and post-Transfer state.
Transfer vs Historical Replacement
Therefore:
Liability Transfer ≠ Historical Subject Replacement.
Sharing History
Where Liability is shared, the historical record should preserve the relevant allocation and Relationship structures through time.
Recourse History
Recourse Relationships should possess their own history while remaining associated with the Liability structure from which their relevance arose.
Primary vs Recourse History
Primary and Recourse histories should remain distinguishable.
Therefore:
Primary Liability History ≠ Recourse Liability History.
Resolution Initiation History
The record should preserve when Resolution governance began and what Resolution Object was established.
Satisfaction History
Material Satisfaction events should remain associated with the exact Liability requirement they affected.
Payment History
Where payment is relevant to Liability governance, the record should preserve its association without treating payment itself as complete Liability history.
Therefore:
Payment Record ≠ Liability Historical Record.
Performance History
Where performance contributes to Satisfaction or Resolution, the record should preserve relevant performance states and their relationship to the Liability requirement.
Settlement History
Settlement history should preserve, where applicable:
Settlement formation, Subjects, Scope, terms, conditions, modifications, performance, failure, termination, supersession, and resulting Liability effects.
Settlement vs Liability History
Settlement history forms part of the Liability history where relevant.
It does not replace the broader Liability lifecycle.
Therefore:
Settlement History ≠ Complete Liability History.
Discharge History
The historical record should preserve Discharge events, Basis, Scope, Subjects, effective time, conditions, and subsequent changes.
Resolution History
The record should preserve how a Liability requirement moved from active governance into a resolved state.
Resolution vs Historical End
Resolution does not terminate the historical record.
Therefore:
Liability Resolution ≠ Liability History Termination.
Discharge vs Historical End
Discharge does not terminate historical continuity.
Therefore:
Liability Discharge ≠ Liability History Termination.
Finality Assessment History
Where Finality is assessed, the historical record should preserve the assessment and its Basis.
Finality History
Where Finality is established, the historical record should preserve:
Finality Object, Finality Scope, Finality Basis, Finality State, effective time, authority where applicable, rationale, and Re-entry conditions.
Finality vs Historical End
Finality ends active Liability governance within its legitimate Scope.
It does not terminate historical existence.
Therefore:
Liability Finality ≠ Liability History Termination.
Historical Record After Finality
The historical record should remain reconstructable after Finality.
Re-Entry History
Where Liability re-enters active governance, LHRM should preserve:
prior State, prior Resolution or Finality, Re-entry Trigger, Re-entry Basis, Re-entry destination, new active State, and subsequent governance.
Re-Entry vs Historical Rewrite
The canonical rule is:
Re-entry must not rewrite history.
Reopening History
A reopened Liability should preserve the fact that it had previously reached Resolution, Discharge, or Finality.
Therefore:
Reopening ≠ Deletion of Prior Finality.
Multiple Lifecycle Cycles
A Liability lifecycle may contain:
active governance, Resolution, Finality, Re-entry, renewed active governance, and later Finality.
The historical record should preserve all materially relevant cycles.
Chronological Integrity
Historical records should preserve the temporal order of material lifecycle states.
Event Time
The time at which an underlying event occurred should remain distinguishable from other lifecycle times.
Effective Time
The time at which a governance state became effective should be represented where available.
Recording Time
The time at which information was recorded should remain distinguishable from its effective time.
Therefore:
Recording Time ≠ Effective Time by default.
Discovery Time
Information may become known after the event to which it relates.
Therefore:
Discovery Time ≠ Event Time by default.
Determination Time
A Liability Determination may occur after the relevant underlying events.
Therefore:
Determination Time ≠ Liability Origin Time by default.
Resolution Time
Resolution time should remain distinct from Satisfaction, Settlement, Discharge, and Finality times where they differ.
Finality Time
Finality Effective Time should remain distinct from the time at which Finality was later recorded.
Retrospective Information
Information discovered later may relate to an earlier point in the lifecycle.
The record should preserve both:
the time to which the information relates, and the time at which it became available.
Retrospective Correction
A later correction should not silently rewrite the earlier record as though the corrected information had always been known.
Therefore:
Retrospective Correction ≠ Historical Backdating of Knowledge.
Historical Versioning
Material historical states should remain versionable where later changes affect their representation.
Superseded States
A superseded state should remain part of the historical record.
Therefore:
Supersession ≠ Historical Deletion.
Correction Record
A correction should identify:
the prior record, the corrected record, the reason for correction, the effective relevance of the correction, and provenance where applicable.
Correction vs Erasure
Therefore:
Correction ≠ Historical Erasure.
Reassessment Record
A reassessment should preserve the earlier state and the reason a later assessment became necessary.
Reassessment vs Correction
Therefore:
Reassessment ≠ Correction.
Reversal Record
Where a previously effective governance outcome is later reversed, both states should remain reconstructable.
Therefore:
Reversal ≠ Historical Deletion.
Record Provenance
Material historical entries should preserve sufficient provenance to explain their origin and governance relationship.
Provenance Elements
Provenance may include:
source, Origin reference, governance object, Subject, authority, time, version, evidence association, prior State, resulting State, and related lifecycle transition.
Provenance vs Evidence
Provenance identifies where a historical record came from and how it relates to the lifecycle.
Evidence supports claims about what occurred.
Therefore:
Provenance ≠ Evidence.
Evidence Association
LHRM may associate evidence with historical entries.
Evidence governance remains within the applicable evidence architecture.
Therefore:
Historical Record ≠ Evidence Repository by default.
Record Attribution
Where relevant, a historical entry should identify the source or governance actor responsible for creating, changing, or validating the record.
Authority History
Changes in authority relevant to Liability governance should remain historically represented.
Rationale History
Material governance decisions should preserve sufficient rationale where necessary to explain later states.
Historical Record vs Rationale
A historical record should preserve relevant rationale without treating rationale as the complete history.
Therefore:
Decision Rationale ≠ Complete Liability History.
Record Completeness
LHRM should assess whether the historical record contains the material lifecycle information required for reconstructability.
Complete Record vs Every Record
Historical completeness does not require preservation of every possible data point.
It requires preservation of materially necessary governance history.
Therefore:
Complete Liability History ≠ Every Available Record.
Materiality
Historical inclusion should focus on information necessary to reconstruct material Liability governance states and transitions.
Historical Gap
A Historical Gap exists where material lifecycle information necessary for reconstructability is unavailable, disconnected, or insufficient.
Gap Representation
Historical gaps should remain explicit.
Therefore:
Historical Gap ≠ Continuity by Assumption.
Unknown Historical State
Where a historical state cannot be established, it should remain Unknown.
Therefore:
Unknown History ≠ Authority to Invent History.
Uncertain Historical State
Where multiple materially plausible historical interpretations remain, uncertainty should remain represented.
Disputed Historical State
Where historical information is disputed, the dispute should remain part of the record until legitimately resolved.
Conflicting Records
Conflicting records should remain identifiable.
Therefore:
Conflicting Liability Records ≠ Authority to Select a Preferred History.
Conflict Reconciliation
Where conflicts are legitimately reconciled, the record should preserve:
the original conflict, the reconciliation Basis, the resulting state, and relevant provenance.
Duplicate Historical Records
Duplicate representations should not automatically create duplicate lifecycle events.
Therefore:
Duplicate Record ≠ Duplicate Liability Event.
Fragmented Historical Records
A Liability history may be distributed across multiple systems, organizations, repositories, or representations.
LHRM should preserve their governed association where sufficiently established.
System Migration History
System migration should remain identifiable as a representation transition rather than a new Liability lifecycle.
Therefore:
System Migration ≠ New Liability History.
Technical Deletion
Deletion of a technical record does not methodologically erase the historical event it represented.
Therefore:
Data Deletion ≠ Liability Historical Non-Existence.
Record Retention
Retention rules may affect the technical availability of records.
They do not redefine whether historical Liability existed.
Therefore:
Record Retention End ≠ Liability Historical Erasure.
Archival Transition
Movement from an active system into archival storage should preserve lifecycle association.
Therefore:
Archival Transition ≠ Liability History Termination.
Historical Network Record
Where a Liability Network exists, LHRM should preserve the history of individual Relationships and their network associations.
Relationship History vs Network History
Therefore:
Liability Relationship History ≠ Complete Liability Network History.
Network Evolution
The historical record should preserve material changes in the Liability Network, including:
new Relationships, terminated Relationships, Recourse formation, Subject changes, Transfer, Resolution, and Relationship Finality.
Local Finality History
Finality of one Relationship should remain represented without implying network-wide Finality.
Primary and Secondary Finality History
Primary and secondary Liability Relationships may reach Finality at different times.
The historical record should preserve those independent lifecycle paths.
Cross-Architecture Historical Inputs
Historical Liability governance may depend on inputs from adjacent architectures.
Those inputs should remain associated without collapsing their governed domains into LIGA™.
Harm History Distinction
Harm history and Liability history may overlap temporally but remain distinct.
Therefore:
Harm History ≠ Liability History.
Accountability History Distinction
Accountability history may inform Liability governance without becoming Liability history itself.
Therefore:
Accountability History ≠ Liability History.
Operational History Distinction
Operational history may provide relevant facts without replacing the governed Liability lifecycle.
Therefore:
Operational History ≠ Liability History.
Claim History Distinction
A Claim lifecycle may overlap with Liability governance.
It remains separate.
Therefore:
Claim History ≠ Liability History.
Automated Historical Reconstruction
AI or automated systems may assist with:
timeline construction, record association, state-transition detection, duplicate detection, gap detection, conflict detection, version comparison, network reconstruction, and provenance association.
Automation should preserve uncertainty and source distinctions.
Therefore:
Automated Historical Reconstruction ≠ Authoritative Historical Truth by default.
Inferred Historical State
Where an automated or human process infers a historical state rather than directly establishing it, the inference should remain identifiable.
Therefore:
Inferred Historical State ≠ Established Historical State.
Historical Record Integrity
LHRM should protect against:
silent overwriting, untraceable correction, false backdating, loss of prior states, unidentified duplication, unsupported record merging, unsupported fragmentation, and deletion of material lifecycle provenance.
Historical Reconstructability
A Liability history is sufficiently reconstructable when the material path from Origin to current or terminal State can be understood without inventing missing governance states.
Reconstructability vs Completeness
A record may contain large amounts of information while still failing to support reconstruction.
Therefore:
Record Volume ≠ Historical Reconstructability.
Historical Sufficiency
The historical record should be sufficient to support:
Finality assessment, Re-entry assessment, future review, network reconstruction, and explanation of the current Liability State.
Historical Record Failure
Where the record is materially insufficient, the deficiency should remain explicit.
Historical insufficiency should not be concealed through unsupported assumptions.
Upstream Re-Entry
If historical reconstruction reveals a material defect in an earlier LIGA™ governance space, the matter should return to the earliest materially affected governance space.
The canonical rule is:
Re-enter the earliest materially affected governance space.
Targeted Reassessment
The canonical principle is:
Reassess what materially changed. Preserve what remains valid.
Governed Liability Historical Record
The principal output of LHRM is:
Governed Liability Historical Record
It should preserve, where applicable:
Liability Origin, Historical Record Object, Liability Context history, Liability Object history, Liability Basis history, Subject history, Relationship history, Condition history, Connection history, Determination history, Scope history, Allocation history, State history, Transfer history, Sharing history, Recourse history, Resolution Initiation history, Satisfaction history, Settlement history, Discharge history, Resolution history, Finality assessment history, Finality history, Re-entry history, Reopening history, effective times, recording times, corrections, reassessments, reversals, superseded states, historical gaps, uncertainty, disputes, conflicts, provenance, and relevant rationale.
Meaning of the Output
A Governed Liability Historical Record means that the material Liability lifecycle has been preserved in a sufficiently ordered and reconstructable form for downstream Finality assessment and future Re-entry governance.
It does not establish Finality.
It does not establish that Re-entry is required.
It preserves the history necessary to govern those questions.
Minimum Implementation Framework
A conforming implementation of LHRM must provide exactly the following eight capabilities:
Historical Record Object, Origin & Lifecycle Boundary Governance
Capability to identify the Historical Record Object, associate it with the relevant Liability Origin, define the historical boundary, and distinguish Relationship-level from Liability Network history.
Determination, Scope, Allocation, State & Relationship History Governance
Capability to preserve material Liability Determinations, Subjects, Relationships, Scope, Allocation, State transitions, conditions, and relevant Liability-Relevant Connections across time.
Transfer, Sharing, Recourse, Resolution & Discharge History Governance
Capability to preserve material Transfer, Sharing, Recourse, Satisfaction, Settlement, Resolution, Discharge, and related lifecycle transitions without replacing earlier states.
Temporal, Version, Correction, Reassessment & Supersession Governance
Capability to distinguish event, discovery, effective, determination, recording, Resolution, and Finality times; preserve versions; and govern correction, reassessment, reversal, and supersession without historical erasure.
Provenance, Attribution, Authority, Rationale & Evidence Association Governance
Capability to preserve sufficient provenance, attribution, authority history, rationale, and evidence associations to explain material historical records and transitions.
Historical Gap, Uncertainty, Dispute, Conflict, Duplicate & Fragment Governance
Capability to identify gaps, preserve Unknown, Uncertain, and Disputed states, govern conflicting or duplicate records, and associate fragmented records without inventing missing history.
Re-Entry, Reopening, Finality & Post-Finality Historical Integrity Governance
Capability to preserve Re-entry, Reopening, Finality assessments, prior Finality States, renewed active governance, and later Finality without rewriting or deleting earlier lifecycle states.
Finality Assessment Handoff Governance
Capability to produce a Governed Liability Historical Record sufficiently complete, ordered, attributable, and reconstructable for Liability Finality Assessment governance.
Governance Logic
The canonical LHRM governance logic is:
Governed Liability Continuity Identification Structure
↓
Identify Historical Record Object
↓
Establish Historical Boundary
↓
Associate Liability Origin
↓
Reconstruct Subjects & Relationships
↓
Reconstruct Determination / Scope / Allocation
↓
Reconstruct Liability State Transitions
↓
Associate Transfer / Sharing / Recourse
↓
Associate Satisfaction / Settlement / Resolution / Discharge
↓
Associate Finality / Re-Entry / Reopening States
↓
Order Material Lifecycle Events
↓
Distinguish Event / Effective / Discovery / Recording Times
↓
Preserve Versions / Corrections / Reassessments / Supersession
↓
Associate Provenance / Authority / Rationale / Evidence
↓
Identify Gaps / Uncertainty / Disputes / Conflicts / Duplicates
↓
Assess Historical Reconstructability
↓
Governed Liability Historical Record
↓
Handoff to Liability Finality Assessment
Governance Outputs
LHRM may produce:
Historical Record Object
Historical Boundary
Liability Origin Record
Subject History
Liability Relationship History
Liability Network History
Determination History
Scope History
Allocation History
Liability State History
Transfer History
Sharing History
Recourse History
Satisfaction History
Settlement History
Discharge History
Resolution History
Finality Assessment History
Finality History
Re-Entry History
Reopening History
Temporal Record
Version History
Correction Record
Reassessment Record
Reversal Record
Supersession Record
Historical Gap Record
Historical Conflict Record
Historical Uncertainty Record
Provenance Record
Historical Rationale Record
The principal output is:
Governed Liability Historical Record
Critical Distinctions
LHRM preserves the following distinctions:
Current Liability State ≠ Complete Liability History Historical Record Object ≠ Liability Object by default Current Subject Structure ≠ Complete Subject History Current Liability Determination ≠ Complete Determination History Current Liability Scope ≠ Complete Liability Scope History Current Liability Allocation ≠ Complete Liability Allocation History Current Liability State ≠ Historical Liability State Liability Transfer ≠ Historical Subject Replacement Primary Liability History ≠ Recourse Liability History Payment Record ≠ Liability Historical Record Settlement History ≠ Complete Liability History Liability Resolution ≠ Liability History Termination Liability Discharge ≠ Liability History Termination Liability Finality ≠ Liability History Termination Reopening ≠ Deletion of Prior Finality Recording Time ≠ Effective Time by default Discovery Time ≠ Event Time by default Determination Time ≠ Liability Origin Time by default Retrospective Correction ≠ Historical Backdating of Knowledge Supersession ≠ Historical Deletion Correction ≠ Historical Erasure Reassessment ≠ Correction Reversal ≠ Historical Deletion Provenance ≠ Evidence Historical Record ≠ Evidence Repository by default Decision Rationale ≠ Complete Liability History Complete Liability History ≠ Every Available Record Historical Gap ≠ Continuity by Assumption Unknown History ≠ Authority to Invent History Conflicting Liability Records ≠ Authority to Select a Preferred History Duplicate Record ≠ Duplicate Liability Event System Migration ≠ New Liability History Data Deletion ≠ Liability Historical Non-Existence Record Retention End ≠ Liability Historical Erasure Archival Transition ≠ Liability History Termination Liability Relationship History ≠ Complete Liability Network History Harm History ≠ Liability History Accountability History ≠ Liability History Operational History ≠ Liability History Claim History ≠ Liability History Automated Historical Reconstruction ≠ Authoritative Historical Truth by default Inferred Historical State ≠ Established Historical State Record Volume ≠ Historical Reconstructability
Cross-Architecture Boundary
LHRM may associate historical inputs from adjacent OOF® architectures without absorbing their governed histories.
ORA™ may provide Operational Reality history.
HAGA™ may provide Harm lifecycle history.
AGA™ may provide Responsibility, Accountability, attribution, and authority history.
ADIT® may provide evidence and audit trails.
VALIDOS™ may provide Validation history.
OBIDENITY® may provide identity, Origin, provenance, succession, and continuity structures.
VFM® may provide payment and Value Flow history.
AIG® and ASGA™ may provide AI and autonomous-system operational histories.
Claims governance may provide Claim history.
These histories may be relevant to Liability.
They do not become the Liability history merely because they are associated with it.
The canonical interoperability principle is:
External architectures preserve the history of their governed objects; LHRM preserves how Liability itself developed through the LIGA™ lifecycle and how relevant external inputs affected that development.
Canonical Boundary
LHRM begins when the Liability structures identified by LCOIM require formation into a coherent and reconstructable historical lifecycle record.
LHRM governs:
Historical Record Objects, historical boundaries, Origin association, Subject history, Relationship history, Determination history, Scope and Allocation history, State transitions, Transfer, Sharing, Recourse, Satisfaction, Settlement, Resolution, Discharge, Finality-related history, Re-entry, Reopening, temporal ordering, versioning, correction, reassessment, reversal, supersession, provenance, attribution, rationale, historical gaps, uncertainty, disputes, conflicts, duplicates, fragmentation, and reconstructability.
LHRM does not independently determine:
Liability Finality, whether Re-entry is required, or the terminal Finality Record.
LHRM ends when the material Liability lifecycle is sufficiently preserved as a:
Governed Liability Historical Record
for Finality Assessment governance.
Use Case 1 — Liability Changes Across Several Years
A Liability Relationship is determined, partially reallocated, transferred between Subjects, partially satisfied, settled, and later discharged.
The current system displays only the discharged State.
LHRM preserves the earlier Determination, Allocation, Transfer, Satisfaction, Settlement, and Discharge states in their historical sequence.
The final State can therefore be reconstructed without treating the latest record as the entire Liability history.
Current Liability State ≠ Complete Liability History.
Use Case 2 — Final Liability Reopens After New Information
A Liability Relationship previously reached a governed Finality State.
New materially relevant information later requires Re-entry into Liability Determination.
LHRM preserves the original Determination, Resolution, Finality, new information, Re-entry Trigger, renewed Determination, and subsequent lifecycle states.
The earlier Finality is not deleted merely because the Liability becomes active again.
Re-entry must not rewrite history.
Canonical Closing Statement
A Liability history is not the latest status of a case.
It is the governed path that explains how that status came to exist.
Determinations may change.
Scope and Allocation may change.
Subjects and Relationships may change.
Liability may be transferred, shared, resolved, discharged, finalized, reopened, and finalized again.
Every material transition may alter the present without erasing the past.
Current Liability State ≠ Complete Liability History.
Preserve the path from Origin to the present so that Finality can be assessed from a reconstructable lifecycle rather than from a terminal label alone.