HCLM — Harm Closure Module

OOF® Origin Open Foundation®

Independent Methodological Authority

Canonical Definition

The HCLM — Harm Closure Module governs how a governed Harm lifecycle
transitions from established Resolution into formal Closure after
applicable Resolution Criteria have been sufficiently satisfied.


HCLM determines whether the resolved Harm is ready for Closure, what
materially relevant conditions must remain represented at Closure, whether
Residual Harm, dependencies, monitoring requirements, unresolved but
Resolution-compatible conditions, uncertainty, and future Reopening
triggers have been sufficiently preserved, and whether active Harm
lifecycle governance can legitimately cease under the current Resolution
basis without destroying future governability.


It establishes the transition:

Governed Harm Resolution State + Governed Harm Resolution Criteria State →
Closure Readiness → Closure Conditions → Closure Determination → Lifecycle
Preservation → Governed Harm Closure State


Its central question is:

When can active governance of a resolved Harm lifecycle legitimately be
closed without erasing continuing governance-relevant conditions or
preventing future Reopening?


  • Operational Role


HRSM-F establishes:

the Resolution State.

HRCM-F establishes:

whether applicable Resolution Criteria are sufficiently satisfied.

HCLM determines:

whether the resolved Harm lifecycle can now be closed.

Its operational role is:

to terminate active Harm lifecycle handling under the current Resolution
basis while preserving everything required to understand, monitor,
reassess, reopen, and eventually determine Finality.


The foundational principle is:

Closure must reduce active governance without destroying future
governability.


  • Position Within HRFS


The HRFS governance flow is:

Resolution State → Resolution Criteria → Closure → Reopening → Finality

HCLM governs the third stage:

Closure

It receives principally:

Governed Harm Resolution State

and:

Governed Harm Resolution Criteria State

It produces:

Governed Harm Closure State

for:

HROM — Harm Reopening Module

and ultimately:

HFFM — Harm Finality Formation Module

  • Governed Object


The primary governed object is:

Closure of the Active Governed Harm Lifecycle

Closure does not mean that:

the Harm never existed

all Harm disappeared

Residual Harm is absent

all external processes ended

or:

Finality has been reached

Therefore:

Harm Closure ≠ Harm Erasure

  • Foundational Closure Principle


The foundational rule is:

A Harm lifecycle may close only when active governance can legitimately
cease under the current Resolution basis while sufficient continuity
remains for future reassessment and Reopening.


Closure therefore has two simultaneous requirements:

Active Governance Can Cease

and:

Future Governability Must Remain

Neither may replace the other.

  • Resolution Before Closure


Closure ordinarily requires legitimate Resolution.

Conceptually:

Resolution → Closure

Therefore:

Unresolved Harm ≠ Closure-Ready Harm

and:

Resolution Criteria Satisfied ≠ Closure Automatically Completed

Closure is its own governance determination.

  • Closure Readiness


Closure Readiness exists where:

Resolution is sufficiently established

applicable Resolution Criteria are sufficiently satisfied

material post-Resolution conditions are represented

and:

active Harm lifecycle governance may potentially cease

Closure Readiness does not itself close the lifecycle.

Therefore:

Closure Ready ≠ Closed

  • Closure Conditions


Before Closure, HCLM must determine what conditions must remain governed
after active lifecycle handling ceases.


These may include:

Residual Harm

conditional Resolution requirements

material dependencies

monitoring requirements

latent Harm conditions

uncertainty

reopening triggers

preservation requirements

or:

other materially relevant post-Closure conditions

Closure must not erase them.

  • Residual Harm at Closure


Residual Harm may remain when Closure occurs.

Therefore:

Residual Harm Exists ≠ Closure Impossible

Where Residual Harm remains, Closure must preserve its materially
relevant:


state

boundary

scope

distribution

dependencies

and:

conditions relevant to future reassessment

  • Conditional Resolution at Closure


A conditionally resolved Harm may potentially close where the conditions
supporting Resolution remain sufficiently governed.


The Closure State must preserve those conditions.

Therefore:

Conditional Resolution + Closure ≠ Unconditional Closure

The continuing conditions remain part of the Closure basis.

  • Dependency-Supported Closure


Closure may depend on continuing external conditions.

Examples may include:

ongoing support

protective infrastructure

monitoring systems

treatment

technical safeguards

or:

environmental controls

Such dependencies must remain visible.

Therefore:

Dependency-Supported Closure ≠ Dependency-Free Closure

  • Monitoring After Closure


Closure may legitimately coexist with continued monitoring.

Monitoring does not necessarily mean the Harm lifecycle remains actively
open.


Therefore:

Monitoring Continues ≠ Harm Lifecycle Open

Monitoring may instead preserve the ability to detect:

Resolution degradation

Residual Harm change

dependency failure

or:

Reopening triggers

  • Closure Under Uncertainty


Perfect certainty is not required for Closure.

But materially relevant uncertainty must be sufficiently:

identified

bounded

represented

and where necessary:

linked to Reopening conditions

Canonical principle:

Closure may coexist with bounded uncertainty, but not with hidden
uncertainty that materially undermines the Resolution basis.


  • Closure Scope


Every Closure determination must have explicit scope.

Closure may apply to:

the complete governed Harm

a defined Harm component

a specific subject set

a location

a domain

or:

another explicitly bounded Harm object

Therefore:

Closed Component ≠ Closed Complete Harm Lifecycle

  • Composite Closure


Composite Harm may contain different Closure conditions.

For example:

Component A → Closed

Component B → Closure Pending

Component C → Not Closure-Ready

HCLM must preserve these differences.

Therefore:

Closure of Components ≠ Composite Closure by Default

  • Collective Closure


Where Harm affects a group or population, Closure must correspond to the
governed collective Harm object.


Closure for most affected subjects does not automatically establish
collective Closure.


Therefore:

Majority Closure ≠ Collective Harm Closure

  • Distributed Closure


Distributed Harm may close differently across:

locations

systems

organizations

infrastructure

or:

environments

Therefore:

Local Closure ≠ Distributed Harm Closure

  • Cross-Domain Closure


Where Harm spans multiple domains, Closure may differ across those
domains.


For example:

Physical Harm → Closed

Operational Harm → Closed

Financial Harm → Closure Pending

Environmental Harm → Not Closure-Ready

The complete Closure determination must preserve materially relevant
differences.


  • Closure and Continuing Harm


Closure must not conceal actively changing Harm.

Where Harm remains materially:

emerging

accumulating

compounding

propagating

or:

cascading

Closure requires strong scrutiny and may be inappropriate.

Canonical principle:

Active Harm progression cannot be administratively transformed into Harm
Closure.


  • Closure and Stable Residual Harm


Stable Residual Harm may be compatible with Closure.

This is methodologically important.

The lifecycle does not necessarily need to remain actively open merely
because a stable, sufficiently governed Harm consequence continues to
exist.


Therefore:

Stable Residual Harm ≠ Permanently Open Harm Lifecycle

  • Closure and Permanent Harm


Permanent Harm may remain after Closure.

For example, a permanent impairment may remain materially real while
active Harm lifecycle progression is no longer required.


Therefore:

Permanent Harm ≠ Permanent Active Harm Governance

Closure does not deny the continuing Harm.

It changes the lifecycle governance condition.

  • Closure and Historical Harm


Closure must preserve the distinction between:

current Harm

and:

historical Harm

A closed lifecycle may continue to contain a complete historical record of
Harm that is no longer currently active.


Therefore:

Historical Harm Record ≠ Current Active Harm State

  • Administrative Closure Boundary


An organization may close an:

incident

ticket

case

investigation

complaint

or:

internal process

That does not establish HAGA™ Closure.

Therefore:

Administrative Closure ≠ Harm Lifecycle Closure

  • Legal Closure Boundary


Legal proceedings may end independently from the Harm lifecycle.

Therefore:

Legal Closure ≠ Harm Closure

and:

Legal Finality ≠ Harm Finality

HCLM does not substitute legal procedural status for Harm governance.

  • Claim Closure Boundary


An insurance or compensation claim may close while Harm continues.

Likewise, Harm may close while a claim remains active.

Therefore:

Claim Closure ≠ Harm Closure

  • Financial Settlement Boundary


Financial settlement does not establish Harm Closure.

Therefore:

Settlement Completed ≠ Harm Lifecycle Closed

A settlement may be materially relevant but remains a separate governance
object.


  • Accountability Boundary


Accountability may remain unresolved after Harm Closure.

Likewise, accountability may be determined before Closure.

Therefore:

Accountability Closure ≠ Harm Closure

  • Value Boundary


Value consequences may remain after Harm Closure.

HCLM does not determine whether value has been restored.

Therefore:

Harm Closure ≠ Value Restoration

VFM® governs the Value lifecycle.

  • Closure Preservation


Closure must preserve sufficient information to support:

future understanding

monitoring

audit

validation

reassessment

Reopening

and:

Finality

This includes the material basis on which Closure was established.

  • Minimum Closure Record


A governed Closure record should preserve materially relevant:

Harm identity

Harm Boundary

Resolution State

Resolution Criteria State

Recovery condition

Residual Harm condition

material dependencies

monitoring requirements

uncertainty

Closure scope

Closure basis

and:

Reopening conditions

The record must remain proportionate to the Harm.

  • Closure Traceability


Closure must remain traceable through the Harm lifecycle.

Conceptually:

Governed Harm → Containment → Mitigation → Recovery → Residual Harm →
Resolution → Resolution Criteria → Closure


Canonical principle:

Closure without lifecycle traceability is merely a status change.

  • Closure Does Not Erase Evidence


Closure must not destroy evidence required for legitimate future
governance.


ADIT® governs evidence and auditability.

HCLM requires that Closure remain compatible with necessary evidence
continuity.


Therefore:

Closure ≠ Evidence Destruction

  • Closure Does Not Freeze Reality


Closure represents the Harm condition at the time the Closure basis is
established.


It does not guarantee that reality will never change.

Therefore:

Closed Harm ≠ Immutable Harm Reality

This is why Reopening exists as the next HRFS governance stage.

  • Reopening Conditions at Closure


Where materially appropriate, Closure should establish the conditions that
may require Reopening.


These may include:

Residual Harm increase

Recovery regression

latent Harm manifestation

dependency failure

new materially relevant effects

Harm Boundary expansion

continuing Harm resumption

or:

material invalidation of the Resolution basis

  • Reopening Trigger Visibility


Reopening conditions must be sufficiently visible to the mechanisms or
actors responsible for detecting them.


A trigger that cannot realistically be observed cannot reliably protect
Closure.


Canonical principle:

A Reopening condition must be governable enough to become actionable when
the Harm reality changes.


  • Closure Monitoring Link


Where monitoring is required, HCLM must establish what monitoring is
relevant to the Closure basis.


This may include monitoring of:

Residual Harm

Recovery stability

dependencies

latent conditions

or:

specific Reopening triggers

Monitoring must remain proportionate.

  • Closure Persistence


Closure persists while the materially relevant Closure basis remains
valid.


Therefore:

Closed Once ≠ Closed Forever

Before Finality, Closure remains capable of being reopened.

  • Closure Degradation


A Closure basis may weaken without immediately requiring full Reopening.

For example:

dependency reliability decreases

or:

Residual Harm uncertainty increases

This may create:

Closure Under Reassessment

where appropriate.

The governance state should reflect uncertainty before reality justifies
stronger action.


  • Closure Invalidity


Where the basis supporting Closure materially fails, the lifecycle cannot
remain closed merely because Closure was previously legitimate.


Therefore:

Historical Closure ≠ Current Closure Validity

A Reopening determination may become necessary.

  • Closure History


The lifecycle must preserve material Closure history.

A Harm may experience:

Resolution → Closure → Reopening → Resolution → Closure

Each state remains part of the governed lifecycle.

Therefore:

Reopening ≠ Erasure of Historical Closure

  • Closure and Finality Readiness


Closure prepares the Harm lifecycle for eventual Finality.

But:

Closure ≠ Finality

After Closure, the lifecycle may still require:

observation

conditional continuity

monitoring

reopening availability

or:

other conditions

before Finality can legitimately be established.

  • Closure Duration


No universal duration transforms Closure into Finality.

A Harm may require:

short observation

long observation

or:

no defined waiting period

depending on its characteristics.

Therefore:

Elapsed Time Since Closure ≠ Finality

  • Closure Reassessment


Closure must be reassessed where materially relevant information
indicates:


the Resolution basis changed

Residual Harm changed

Recovery changed

dependencies changed

the Harm Boundary changed

new Harm manifestations appeared

or:

previous assumptions became unreliable

Reassessment determines whether Closure remains legitimate or requires
Reopening.


  • Closure State Model


HCLM may represent states such as:

Closure Not Ready

Closure Readiness Established

Closure Pending

Conditionally Closed

Closed

Closure Under Reassessment

or:

Closure No Longer Valid

These states remain distinct from Finality.

  • Governed Closure Determination


A legitimate Closure determination should answer:

What Harm is being closed?

What Resolution basis supports Closure?

What scope does Closure cover?

What Residual Harm remains?

What dependencies remain?

What monitoring remains?

What uncertainty remains?

What can reopen the lifecycle?

Only then can active Harm lifecycle governance legitimately cease under
the current basis.


  • Minimum Implementation Framework


A minimum HCLM implementation requires exactly eight capabilities.

  • Closure Readiness Determination


Determine whether Resolution and applicable Resolution Criteria provide
sufficient basis for Harm lifecycle Closure.


  • Closure Condition Formation


Identify the Residual Harm, dependencies, monitoring, uncertainty, and
other conditions that must remain represented after Closure.


  • Closure Scope Governance


Define which Harm, subjects, components, locations, domains, and
boundaries are covered by the Closure determination.


  • Composite, Collective, Distributed & Cross-Domain Closure
    Governance


Preserve materially different Closure conditions across complex Harm
structures.


  • Closure Preservation & Traceability


Maintain sufficient lifecycle records, Harm identity, Resolution basis,
Residual Harm condition, and governance continuity to support future
review.


  • Reopening Condition & Monitoring Linkage


Define materially relevant Reopening conditions and connect them to
proportionate monitoring or observation where necessary.


  • Closure Reassessment & History


Reassess Closure when its basis materially changes and preserve Closure,
degradation, invalidity, and Reopening history.


  • Governed Output


Produce a traceable Governed Harm Closure State suitable for Reopening and
Finality governance. 47. Use Case 1 — Closure With Stable Residual Harm


A person, system, organization, or infrastructure reaches legitimate
Resolution after substantial Recovery.


A limited Residual Harm condition remains, but it is:

identified

bounded

stable

sufficiently governed

and:

compatible with the applicable Resolution Criteria

HCLM does not require the lifecycle to remain permanently active merely
because Residual Harm exists.


It may establish:

Governed Harm Closure State

while preserving the Residual Harm condition and applicable Reopening
triggers.


The governing principle is:

Closure can end active Harm lifecycle handling without denying Harm that
legitimately remains.


  • Use Case 2 — Closure Depends on Continuing Protection


A system reaches Conditional Resolution because a continuing protective
control prevents a stable Residual Harm condition from producing
additional Harm.


HCLM may establish:

Conditionally Closed

while preserving:

the protective dependency

monitoring requirements

and:

dependency failure as a Reopening condition

If the protection later fails, the Closure basis can be reassessed and the
lifecycle reopened.


The governing principle is:

A Closure dependent on continuing conditions must preserve the conditions
on which its legitimacy depends.


  • Governance Requirements


HCLM requires that:

  • Closure remain distinct from Resolution and Finality
  • legitimate Resolution ordinarily precede Closure
  • Resolution Criteria satisfaction not automatically complete
    Closure
  • Closure Readiness remain distinct from Closure
  • materially relevant post-Resolution conditions remain represented
  • Residual Harm not automatically prevent Closure
  • Conditional Resolution conditions remain visible after Closure
  • dependencies remain explicit
  • monitoring remain compatible with Closure
  • bounded uncertainty remain representable
  • Closure scope remain explicit
  • composite, collective, distributed, and cross-domain differences


remain visible; - active Harm progression not be hidden through Closure; -
stable Residual Harm not automatically require permanent active
governance; - permanent Harm not automatically require permanent active
governance; - administrative, legal, claim, financial, accountability, and
value closure remain distinct from Harm Closure; - sufficient lifecycle
information remain preserved; - Closure maintain Harm identity and
lifecycle traceability; - necessary evidence continuity remain possible; -
Closure not be treated as immutable reality; - Reopening conditions be
defined where materially relevant; - Reopening triggers be sufficiently
governable to become actionable; - monitoring remain linked to material
Closure conditions where required; - Closure persist only while its basis
remains valid; - weakened Closure conditions permit reassessment; -
materially invalid Closure basis permit Reopening; - Closure history
remain preserved; - Closure remain distinct from Finality Readiness and
Finality; - elapsed time not substitute for Finality; - the principal
Closure output remain suitable for subsequent Reopening governance.


  • Governance Logic


HCLM applies the following logic:

Is the Harm legitimately resolved?

If no:

→ Closure Not Ready

If yes:

→ ask:

Are applicable Resolution Criteria sufficiently satisfied?

If no:

→ Closure Not Ready

If yes:

→ establish:

Closure Readiness

Then determine:

What Residual Harm remains?

What dependencies remain?

What monitoring remains necessary?

What uncertainty remains?

What is the Closure scope?

Are any components, subjects, locations, or domains still outside the
Closure basis?


Does active Harm progression continue?

If active Harm progression materially contradicts Closure:

→ do not close.

If Closure is dependent on continuing conditions:

→ establish where appropriate:

Conditional Closure

Then preserve:

Harm Identity

Resolution Basis

Resolution Criteria State

Residual Harm State

Closure Scope

Dependencies

Monitoring

Uncertainty

and:

Reopening Conditions

Then establish:

Governed Harm Closure State

After Closure:

Does the Closure basis remain valid?

If yes:

→ preserve Closure.

If uncertain:

→ Closure Under Reassessment

If materially invalid:

→ transfer to:

HROM — Harm Reopening Module

Throughout:

Resolved ≠ Closed

Closed ≠ Final

Residual Harm ≠ Closure Failure

Monitoring ≠ Open Lifecycle

Administrative Closure ≠ Harm Closure

Historical Closure ≠ Current Closure Validity

  • Governance Outputs


HCLM may produce:

Governed Harm Closure State

Closure Readiness State

Closure Condition Set

Closure Scope

Conditional Closure State

Closure Dependency Set

Post-Closure Monitoring Requirement

Residual Harm at Closure Record

Closure Uncertainty State

Composite Closure State

Collective Closure State

Distributed Closure State

Cross-Domain Closure State

Closure Preservation Record

Closure Traceability Record

Reopening Condition Set

Closure Monitoring Link

Closure Reassessment Trigger

Closure History

and:

Reopening Governance Readiness State

The principal output is:

Governed Harm Closure State

  • Critical Distinctions


Harm Closure ≠ Harm Erasure

Resolution ≠ Closure

Resolution Criteria Satisfied ≠ Closure Completed

Closure Ready ≠ Closed

Residual Harm Exists ≠ Closure Impossible

Conditional Resolution + Closure ≠ Unconditional Closure

Dependency-Supported Closure ≠ Dependency-Free Closure

Monitoring Continues ≠ Harm Lifecycle Open

Closed Component ≠ Closed Complete Harm Lifecycle

Closure of Components ≠ Composite Closure

Majority Closure ≠ Collective Harm Closure

Local Closure ≠ Distributed Harm Closure

Active Harm Progression ≠ Harm Closure

Stable Residual Harm ≠ Permanently Open Harm Lifecycle

Permanent Harm ≠ Permanent Active Harm Governance

Historical Harm Record ≠ Current Active Harm State

Administrative Closure ≠ Harm Lifecycle Closure

Legal Closure ≠ Harm Closure

Claim Closure ≠ Harm Closure

Settlement Completed ≠ Harm Lifecycle Closed

Accountability Closure ≠ Harm Closure

Harm Closure ≠ Value Restoration

Closure ≠ Evidence Destruction

Closed Harm ≠ Immutable Harm Reality

Closed Once ≠ Closed Forever

Historical Closure ≠ Current Closure Validity

Reopening ≠ Erasure of Historical Closure

Closure ≠ Finality

Elapsed Time Since Closure ≠ Finality

  • Canonical Boundary


The HCLM — Harm Closure Module governs how legitimately resolved Harm
transitions from active lifecycle governance into Closure while preserving
materially relevant Residual Harm, dependencies, monitoring, uncertainty,
scope, lifecycle traceability, Reopening conditions, and future
governability. It governs Closure Readiness, Closure Conditions,
Conditional Closure, Closure scope, preservation, monitoring linkage,
Closure reassessment, Closure history, and formation of the Governed Harm
Closure State. HCLM does not determine the original Harm, perform
Containment, Mitigation or Recovery, identify Residual Harm, independently
define Resolution Criteria, govern Reopening as its primary object,
establish Finality, determine general causation, accountability,
responsibility, liability, claims, compensation or value consequences, or
substitute administrative, legal, insurance, financial, or organizational
closure for Harm lifecycle Closure.


  • Canonical Closing Statement


Closure is not the disappearance of Harm and not the destruction of the
Harm lifecycle record.


It is the governed point at which active lifecycle handling may
legitimately cease while the conditions required to understand, monitor,
reassess, and reopen that Harm remain intact.


A closed Harm lifecycle must therefore preserve both what justified
Closure and what could invalidate it.


Closure ends active handling. It must never end governability.