Harm Determination Standard - (HDS)

OOF® Origin Open Foundation®

Independent Methodological Authority

---------- Forwarded message --------- From: Knowenger
<knowenger@gmail.com> Date: Tue, Sep 15, 2026, 10:35 AM Subject: 6Harm
Determination Standard (HDS) To: <Gutflex@gmail.com>, Miroslav Pis
<swissstaffingagency@gmail.com>, < originopenfoundation@gmail.com>


Harm Determination Standard (HDS)

Architecture: HAGA™ — Harm Governance Architecture Category: Governance &
Enforcement Subcategory: Harm Governance Type: Parent Standard Governed
Space: Harm Determination Standard ID: HAGA-HDS-006 Origin ID:
OOF.PS.16.06.00.01 Version: 1.0 Status: Canonical · Open Standard
Effective Date: 15 September 2026 Compatibility: OOF® Methodology OS™ ·
Modular OOF® Architecture Ecosystem AI-Readable: Yes Authority: OOF®
Protection: MIP® — Methodological Intellectual Property Canonical
Language: English (UCL™)


  • Canonical Definition


The Harm Determination Standard (HDS) governs whether Harm can
legitimately be determined to exist as a formally governed Harm object and
what Harm has been established, using qualified Recognition and Boundary
inputs, explicit determination criteria, governed evaluation, uncertainty,
contradiction, sufficiency, determination states, and a traceable Governed
Harm Record.


HDS establishes the transition:

Governed Harm Recognition State + Governed Harm Boundary → Qualified
Inputs → Determination Criteria → Evaluation → Determination State →
Governed Harm Record


  • Operational Role


Earlier HAGA™ layers establish that Harm:

may exist

has emerged

has become recognized

and:

has been bounded for governance

HDS performs a different function.

Its operational role is:

to determine whether the available governed basis is sufficient to
formally establish Harm and, where it is, to create the authoritative
methodological record of the Harm that has been determined.


HDS therefore separates:

Recognized Harm

from:

Determined Harm

and:

Determined Harm

from downstream questions of:

Harm State

causation

accountability

liability

claims

or:

resolution

  • Core Question


Can Harm legitimately be determined to exist, and what governed Harm has
been established?


  • Position Within HAGA™


The HAGA™ Governance Flow is:

Harm Context → Harm Exposure → Harm Emergence → Harm Recognition → Harm
Boundary → Harm Determination → Harm State → Harm Change & Propagation →
Harm Containment → Harm Mitigation → Harm Recovery & Residual Harm → Harm
Resolution & Finality


HDS receives:

Governed Harm Recognition State

and:

Governed Harm Boundary

It produces:

Governed Harm Record

for the Harm State Standard (HSS).

  • Internal Governance Flow


The internal HDS flow is:

Qualified Inputs → Determination Criteria → Evaluation → Determination
State → Governed Harm Record


The five Core Modules are:

HDIM — Harm Determination Input Module

HDCM-D — Harm Determination Criteria Module

HDEM — Harm Determination Evaluation Module

HDSM — Harm Determination State Module

HDRM — Harm Determination Record Module

Each governs a distinct part of the determination lifecycle.

  • Foundational Determination Principle


The foundational distinction is:

Recognition ≠ Determination

Recognition establishes that Harm has sufficient basis to become an
explicit governance object.


Determination establishes whether Harm can be formally established under
governed criteria.


A recognized Harm must not automatically become a determined Harm.

Equally:

Failure to reach Determination ≠ Proof That Harm Does Not Exist

The result may instead be:

Pending

Partially Established

or:

Insufficient Basis

  • Determination Object


HDS determines a specific:

Governed Harm Object

The determination must remain tied to the Harm Boundary established by
HBS.


It must not silently expand or narrow:

subjects

time

effects

or:

downstream scope

during determination.

If material boundary changes become necessary, the appropriate boundary
governance must be reopened.


  • Qualified Inputs


Determination must operate on governed inputs rather than unstructured
information.


Inputs may include:

Governed Harm Recognition State

Governed Harm Boundary

Recognition Basis

subject information

temporal information

effect information

downstream relationships

operational reality

evidence

validated findings

integrity-relevant information

material uncertainty

material contradictions

HDS must preserve the provenance and governance status of materially
relied-upon inputs.


  • Input Qualification


An input should be qualified according to characteristics such as:

relevance

fitness

reliability

scope

temporal applicability

provenance

uncertainty

and:

limitations

Qualification does not mean that HDS replaces ADIT®, VALIDOS™, INTEGROS®,
or OBIDENITY®.


It determines whether their outputs are fit for Harm Determination.

  • Information ≠ Qualified Determination Input


Canonical distinction:

Available Information ≠ Qualified Determination Input

The existence of data, reports, statements, observations, or records does
not automatically make them sufficient for formal Harm Determination.


  • Determination Criteria


HDS requires explicit criteria for determining Harm.

Criteria must be appropriate to the governed Harm and sufficiently clear
to distinguish:


what must be established

what may remain uncertain

what would prevent determination

and:

what would require further governance

Determination must not depend on an unexplained intuitive conclusion.

  • Criteria Must Precede Conclusion


Canonical principle:

A determination conclusion must be governed by criteria, not reconstructed
after the conclusion has already been chosen.


This protects HDS against outcome-driven reasoning.

  • Domain-Neutral Core


HDS is technology-neutral and domain-neutral.

Determination may concern Harm in:

physical

medical / health

digital

financial

property

environmental

organizational

cognitive

or:

societal

contexts.

Domain-specific methods may differ.

The methodological requirement for governed Determination remains
consistent.


  • Determination Threshold


A Determination Threshold defines the level of support required to
establish the applicable Determination State.


The threshold must be:

explicit

appropriate

consistent

traceable

and:

separate from downstream legal standards

Canonical distinction:

Harm Determination Threshold ≠ Legal Liability Threshold

  • Recognition Threshold ≠ Determination Threshold


HRS may recognize Harm before the basis is sufficient for formal
Determination.


Therefore:

Recognition Confirmation Threshold ≠ Harm Determination Threshold

This allows governance to act on recognized Harm without falsely claiming
that formal Determination has already occurred.


  • Emergence Threshold ≠ Determination Threshold


HEMS governs when Harm begins to exist.

HDS governs when the available governed basis can formally establish it.

Therefore:

Harm Emergence Threshold ≠ Harm Determination Threshold

The epistemic state of governance must not redefine the reality state of
Harm.


  • Determination Evaluation


Evaluation applies the governed criteria to the qualified inputs.

It must consider:

supporting information

contradictory information

uncertainty

limitations

scope

confidence

alternative interpretations

composite relationships

and:

material missing information

The purpose is not to eliminate uncertainty.

It is to govern uncertainty sufficiently to reach the legitimate
determination state.


  • Uncertainty Does Not Automatically Prevent Determination


Absolute certainty is not a universal requirement.

Canonical principle:

Determination does not require uncertainty to disappear; it requires
uncertainty to be governed.


A Harm may be:

Established

while some secondary characteristics remain uncertain.

  • Determination Sufficiency


Sufficiency concerns whether the complete governed basis meets the
applicable Determination Criteria.


It must not be reduced to:

number of reports

number of evidence items

number of affected subjects

visibility

or:

institutional acknowledgement

Canonical distinction:

More Information ≠ Sufficient Determination Basis by Default

  • Composite Determination Basis


Harm may be established through several individually insufficient elements
that become sufficient collectively.


Conceptually:

Input A + Input B + Input C → Sufficient Determination Basis

Therefore:

Individual Insufficiency ≠ Composite Insufficiency

This is essential for:

distributed Harm

accumulated Harm

collective Harm

cross-system Harm

and:

AI-mediated Harm

  • Fragmented Evidence ≠ Fragmented Harm


Evidence may exist across:

systems

organizations

subjects

agents

sessions

locations

or:

time periods

HDS must be capable of evaluating the governed basis as a coherent whole.

Canonical principle:

Evidence fragmentation must not make a materially coherent Harm
undeterminable by default.


  • Local Insufficiency ≠ Global Insufficiency


An individual component may not establish Harm independently.

The complete operational structure may.

Therefore:

Local Insufficiency ≠ Global Insufficiency

HDS must support determination at the level at which Harm actually exists.

  • No Single Harm-Producing Action


Some Harm cannot be reduced to one action.

It may emerge through:

accumulation

interaction

distributed execution

continuous conditions

multiple individually insufficient actions

or:

composite operational behavior

Therefore:

No Single Harm-Producing Action ≠ No Determinable Harm

  • Non-Linguistic Harm Determination


HDS must not require:

prompt history

textual reasoning

linguistic decision

or:

explicit verbal instruction

for Harm to be determinable.

Autonomous systems may move directly through:

Perception → Interpretation → Decision → Action → Consequence

Harm Determination must follow the consequence and governed reality.

  • Subject Report


A subject report may materially contribute to Determination.

But:

Subject Report ≠ Automatic Harm Determination

Nor may its absence establish:

No Harm

A report is an input whose governance status must be evaluated
appropriately.


  • Machine Detection


AI or automated systems may detect Harm-relevant conditions.

But:

Machine Detection ≠ Automatic Harm Determination

Automated analysis may contribute to Determination while remaining subject
to governed criteria, provenance, uncertainty, and validation.


  • Institutional Recognition


An institution may acknowledge Harm.

That acknowledgement may be relevant.

But:

Institutional Acknowledgement ≠ Harm Determination by Default

Likewise:

Institutional Non-Acknowledgement ≠ No Harm

Authority status alone does not determine methodological truth.

  • Visibility Bias


Highly visible Harm must not receive a lower Determination threshold
merely because it is obvious.


Less visible Harm must not receive an impossible threshold merely because
it is difficult to observe.


Therefore:

Visibility ≠ Determination Legitimacy

  • Severity Bias


Severe potential consequences must not substitute for Determination.

Similarly, apparently minor consequences must not prevent Determination
where criteria are satisfied.


Therefore:

Harm Severity ≠ Determination Sufficiency

  • Outcome Bias


The consequences of Determination may include:

organizational response

financial exposure

accountability review

claims

regulatory attention

or:

liability questions

These consequences must not determine whether Harm is established.

Canonical principle:

The consequences of a Harm Determination must not determine the Harm
Determination itself.


  • Accountability Neutrality


HDS determines Harm.

AGA™ governs accountability.

Therefore:

Harm Determination ≠ Accountability Determination

A Harm may be established while accountability remains:

unknown

distributed

disputed

or:

not established

  • Responsibility Neutrality


Harm may be determined without determining who had responsibility to
prevent it.


Therefore:

Determined Harm ≠ Responsibility Assigned

  • Liability Neutrality


Legal liability requires separate legal and jurisdictional analysis.

Therefore:

Determined Harm ≠ Liability Established

and:

No Liability ≠ No Harm

This boundary is fundamental.

  • Causation Boundary


HDS may require sufficient causal association to establish that the
governed Harm exists as bounded.


It does not become a general causation or forensic architecture.

Therefore:

Sufficient Harm Association ≠ Complete Causal Attribution

The determination should establish no more causation than necessary for
the Harm determination itself.


  • Boundary Integrity During Determination


HDS operates on the Governed Harm Boundary.

It must not silently change that boundary merely to make Determination
easier.


If evaluation reveals:

additional subjects

earlier Harm

new effects

new downstream consequences

or:

a separate Harm

the relevant HBS governance should be reopened.

Canonical principle:

Determination must evaluate the governed Harm Boundary, not rewrite it
invisibly.


  • Partial Determination


Not every dimension of Harm may be equally established.

A determination may therefore be:

Partially Established

Example:

Harm existence may be established while some:

subjects

historical periods

effects

or:

downstream consequences

remain unresolved.

Partial Determination must specify exactly what is established and what
remains open.


  • Determination States


HDS recognizes at minimum:

Established

Partially Established

Pending

Insufficient Basis

Not Established

These states must not be collapsed.

  • Established


Established means the governed basis satisfies the applicable
Determination Criteria sufficiently to formally establish the bounded
Harm.


Established does not mean:

every fact is known

every cause is known

every subject is identified

accountability is assigned

or:

liability exists

  • Partially Established


Partially Established means a material portion of the Harm can be formally
established while specified parts remain unresolved.


The unresolved portion must remain explicit.

Partial establishment must not be represented as complete establishment.

  • Pending


Pending means Determination cannot yet legitimately be completed because
relevant governance remains active or necessary.


Examples include:

required information pending

boundary reassessment

validation pending

material contradiction unresolved

additional evaluation required

Pending is not a negative conclusion.

  • Insufficient Basis


Insufficient Basis means the available governed basis does not currently
support the required Determination threshold.


Canonical distinction:

Insufficient Basis ≠ No Harm

The Harm may exist even where governance cannot currently establish it.

  • Not Established


Not Established means the governed evaluation does not establish the Harm
under the applicable criteria.


This state must remain distinguishable from:

Insufficient Basis

because:

failure of support

and:

support for non-establishment

are not necessarily the same epistemic condition.

  • Negative Evidence


Information materially supporting non-establishment must be distinguished
from simple absence of supporting information.


Therefore:

Absence of Supporting Evidence ≠ Evidence of Absence

This distinction must be preserved in the Determination Record.

  • Contradictory Inputs


Where materially credible inputs conflict, HDS must preserve:

supporting basis

contradictory basis

scope of conflict

effect on confidence

effect on Determination State

Conflict must not be silently discarded.

  • Determination Conflict


Different evaluators or systems may reach different determinations.

HDS must support:

Determination Dispute

without automatically treating either conclusion as authoritative merely
because of organizational status.


  • Determination Confidence


HDS may associate confidence with a Determination State.

Confidence must remain separate from the state itself.

For example:

Established — Moderate Confidence

may be legitimate where criteria are met but some uncertainty remains.

Canonical distinction:

Determination Confidence ≠ Harm Severity

  • Determination Scope


Every determination must specify what was determined.

At minimum, this may include:

Harm object

subject scope

temporal scope

effect scope

downstream scope where applicable

determination criteria

determination state

limitations

This prevents vague statements such as:

“Harm occurred”

from replacing a governed determination.

  • Determination Reassessment


A Determination State may require reassessment when:

new information appears

evidence changes

validation changes

integrity concerns arise

the Harm Boundary changes

material contradiction is resolved

previous assumptions become invalid

Reassessment must preserve prior states.

  • Determination Reopening


A closed Determination may be reopened where materially relevant new
information justifies reconsideration.


Reopening must not erase the original determination.

The record should preserve:

Determination₁ → New Basis → Reassessment → Determination₂

  • Determination Correction


Where an error is discovered, HDS must support correction.

Corrections must preserve:

original conclusion

error

corrected conclusion

reason

time

authority / methodology used

Canonical principle:

Correction must change the determination without rewriting its history.

  • Determination Version Continuity


A governed Harm may therefore have:

Determination State₁

Determination State₂

Determination State₃

Each state must remain traceable.

The latest determination does not erase the methodological history of how
the Harm was governed.


  • Governed Harm Record


The principal HDS output is:

Governed Harm Record

The record establishes the formal methodological representation of the
determined Harm.


It should preserve, where applicable:

Harm identity

Recognition reference

Governed Harm Boundary

qualified determination inputs

criteria

evaluation

uncertainty

contradictions

Determination State

confidence

limitations

history

reassessment status

  • Governed Harm Record ≠ Incident Record


An incident record describes an event or operational occurrence.

A Governed Harm Record represents the Harm object established through
HAGA™.


Therefore:

Incident Record ≠ Governed Harm Record

One incident may create:

no Harm

one Harm

or:

multiple Harms

Likewise, one Harm may arise without one discrete incident.

  • Governed Harm Record ≠ Claim


A claim is a downstream procedural, contractual, insurance, or legal
object.


Therefore:

Claim Record ≠ Governed Harm Record

The existence or absence of a claim must not define Harm Determination.

  • Governed Harm Record ≠ Liability Finding


A Harm Record may later support liability analysis.

It does not itself determine liability.

Therefore:

Governed Harm Record ≠ Liability Record

  • Evidence Traceability


Material evidence supporting Determination should remain traceable through
ADIT® where applicable.


HDS must know:

what was relied upon

without becoming the architecture that governs evidence formation itself.

  • Validation Dependency


Where a determination depends materially on validated information, HDS
should preserve the relevant validation state.


But:

Validated Evidence ≠ Harm Determination by Default

VALIDOS™ establishes validation.

HDS determines what the validated basis means for Harm.

  • Integrity Dependency


Integrity issues may materially affect Determination.

But:

Integrity State ≠ Harm Determination State

INTEGROS® governs integrity.

HDS uses relevant integrity conclusions without absorbing that governance
space.


  • Operational Reality Dependency


ORA™ may establish:

what actually happened

what system executed

what state existed

what operational sequence occurred

HDS may rely on that operational reality.

But:

Operational Failure ≠ Harm Determination by Default

A failure can occur without Harm.

Harm can also exist without a conventional operational failure.

  • AI Behavior Boundary


AIG® may establish unsafe or problematic AI behavior.

But:

Unsafe AI Behavior ≠ Determined Harm by Default

HDS determines whether Harm has been established.

  • Autonomous Execution Boundary


ASGA™ governs autonomous execution.

An autonomous system may violate a governance constraint without producing
Harm.


Conversely, Harm may emerge through a composite operation without one
individually prohibited action.


Therefore:

Autonomous Governance Violation ≠ Harm Determination by Default

  • Simulation Boundary


SIMULOS® may demonstrate that Harm could occur under simulated conditions.

But:

Simulated Harm ≠ Determined Actual Harm

Simulation may support analysis.

It does not replace real-world Harm Determination.

  • Prediction Boundary


Predicted future Harm remains distinct from existing Harm.

Therefore:

Predicted Harm ≠ Determined Existing Harm

HAGA™ governs Harm that has emerged into the Harm lifecycle.

  • Value Boundary


VFM® may establish Value change resulting from an event or Harm.

But:

Value Loss ≠ Harm Determination by Default

and:

No Value Loss ≠ No Harm

  • Tax and Jurisdiction Boundary


TREGA™ governs Tax-Relevant Events.

Jurisdictional systems may determine legal consequences.

Neither defines methodological Harm Determination.

Therefore:

Jurisdictional Classification ≠ Harm Determination

  • Determination Independence


A legitimate determination process must remain protected from pressure to
reach a preferred result.


Potential pressures include:

financial exposure

reputational impact

organizational hierarchy

insurance consequences

legal strategy

regulatory consequences

political pressure

system performance targets

Canonical principle:

The preferred consequence of a determination must not become the
methodology for reaching it.


  • Determination Consistency


Comparable Harm objects governed under comparable criteria should not
receive materially different Determination treatment without a documented
reason.


Consistency does not require identical conclusions.

It requires consistent methodology.

  • Human and Machine Determination


Determination may involve:

human evaluators

AI systems

automated decision support

or:

hybrid governance

Regardless of implementation:

the criteria, basis, uncertainty, state, and record must remain
governable.


Machine automation does not remove methodological accountability.

  • Determination Explainability


A Determination State should be explainable through:

what was evaluated

against which criteria

using which governed inputs

with what uncertainty

with what contradictions

and:

why the final state was reached

Explainability must follow the determination methodology rather than
reconstructing a plausible explanation afterward.


  • Handoff to Harm State


Once HDS establishes a:

Governed Harm Record

HSS can govern:

What is the current governed state of Harm?

This separation is essential.

HDS establishes:

whether and what Harm exists as a formally governed object.

HSS governs:

the state of that Harm over time.

Therefore:

Harm Determination ≠ Harm State Classification

  • Governance Requirements


HDS requires that:

  • Recognition remain distinct from Determination
  • Determination operate on a governed Harm Boundary
  • available information remain distinct from qualified
    Determination


inputs; - Determination Criteria be explicit and precede the conclusion; -
Determination thresholds remain distinct from Recognition, Emergence,
legal, liability, and claim thresholds; - uncertainty be governed rather
than artificially eliminated; - contradictory inputs remain visible; -
composite and distributed Determination bases remain supportable; - local
insufficiency not automatically become global insufficiency; - no single
Harm-producing action be required where Harm exists at composite level; -
subject reports, machine detection, and institutional acknowledgement not
automatically determine Harm; - visibility and severity not substitute for
Determination sufficiency; - accountability, responsibility, liability,
and claim consequences remain outside the HDS conclusion; - boundary
changes trigger appropriate boundary reassessment rather than silent
rewriting; - Established, Partially Established, Pending, Insufficient
Basis, and Not Established remain distinct; - absence of supporting
evidence remain distinct from evidence of absence; - Determination
confidence remain distinct from Harm severity; - reassessment, reopening,
and correction preserve history; - every formal Determination produce a
traceable Governed Harm Record.


  • Governance Logic


HDS applies the following logic:

Has HRS produced a governed Recognition state and HBS established a
Governed Harm Boundary?


If no:

→ formal Harm Determination is not ready.

If yes:

→ qualify the determination inputs.

Are the required inputs fit for the applicable determination?

If no:

→ identify missing or insufficient basis.

If yes:

→ apply explicit Determination Criteria.

Does the basis contain uncertainty or contradiction?

If yes:

→ govern it explicitly rather than removing it from analysis.

Do individually insufficient elements become sufficient collectively?

If yes:

→ evaluate the composite basis.

Does the complete basis satisfy the Determination threshold?

If yes:

→ establish Established or, where only part is supported, Partially
Established.


If evaluation remains materially incomplete:

→ establish Pending.

If the available basis cannot support Determination:

→ establish Insufficient Basis.

If governed evaluation supports non-establishment:

→ establish Not Established.

Has evaluation revealed a material boundary problem?

If yes:

→ return the affected boundary dimension to HBS rather than silently
changing it.


Has Harm been established?

If yes:

→ create or update the Governed Harm Record and hand it to HSS.

At every stage:

Recognition ≠ Determination

Uncertainty ≠ No Harm

Insufficient Basis ≠ No Harm

Composite Sufficiency ≠ Individual Sufficiency

Determined Harm ≠ Accountability

Determined Harm ≠ Liability

  • Governance Outputs


HDS may produce:

Qualified Harm Determination Input Set

Determination Criteria Set

Determination Threshold

Determination Evaluation

Determination Sufficiency State

Determination Uncertainty State

Determination Conflict State

Determination Confidence

Established Harm State

Partially Established Harm State

Pending Harm Determination

Insufficient Basis State

Not Established State

Determination Reassessment

Determination Reopening

Determination Correction

Determination History

and:

Governed Harm Record

The principal output is:

Governed Harm Record

  • Critical Distinctions


Recognition ≠ Determination

Failure to Reach Determination ≠ Proof That Harm Does Not Exist

Available Information ≠ Qualified Determination Input

Recognition Threshold ≠ Determination Threshold

Harm Emergence Threshold ≠ Harm Determination Threshold

Harm Determination Threshold ≠ Legal Liability Threshold

More Information ≠ Sufficient Determination Basis

Individual Insufficiency ≠ Composite Insufficiency

Local Insufficiency ≠ Global Insufficiency

No Single Harm-Producing Action ≠ No Determinable Harm

Subject Report ≠ Automatic Harm Determination

Machine Detection ≠ Automatic Harm Determination

Institutional Acknowledgement ≠ Harm Determination

Institutional Non-Acknowledgement ≠ No Harm

Visibility ≠ Determination Legitimacy

Harm Severity ≠ Determination Sufficiency

Harm Determination ≠ Accountability Determination

Determined Harm ≠ Responsibility Assigned

Determined Harm ≠ Liability Established

No Liability ≠ No Harm

Insufficient Basis ≠ No Harm

Absence of Supporting Evidence ≠ Evidence of Absence

Determination Confidence ≠ Harm Severity

Incident Record ≠ Governed Harm Record

Claim Record ≠ Governed Harm Record

Governed Harm Record ≠ Liability Record

Validated Evidence ≠ Harm Determination

Operational Failure ≠ Harm Determination

Unsafe AI Behavior ≠ Determined Harm

Simulated Harm ≠ Determined Actual Harm

Predicted Harm ≠ Determined Existing Harm

Value Loss ≠ Harm Determination

Harm Determination ≠ Harm State Classification

  • Canonical Boundary


The Harm Determination Standard (HDS) governs whether a recognized and
bounded Harm can legitimately be formally established as a governed Harm
object and what Harm has been established. It governs qualified
determination inputs, Determination Criteria, thresholds, evaluation,
sufficiency, composite determination, uncertainty, contradiction,
Determination States, confidence, reassessment, reopening, correction,
historical continuity, and the formation of the Governed Harm Record. It
does not determine Harm Emergence, perform Harm Recognition, establish or
silently modify the Harm Boundary, govern Harm State or propagation,
establish general causation beyond what is necessary for Harm
Determination, assign accountability or responsibility, determine
liability, govern claims or compensation, or replace operational reality,
evidence, validation, integrity, identity, AI behavior, autonomous
execution, simulation, Value, prediction, tax-event, or
jurisdiction-specific governance.


  • Canonical Closing Statement


Harm should not become formally established merely because it has been
alleged, observed, reported, recognized, feared, or institutionally
acknowledged. Nor should Harm disappear from governance merely because
absolute certainty is unavailable.


HDS governs the space between those two failures.

It requires Harm to be established through explicit criteria, qualified
inputs, governed uncertainty, and a traceable determination — while
preserving the fundamental distinction between what exists in reality and
what governance can currently prove.


A legitimate Harm Determination does not manufacture Harm. It establishes,
with governed discipline, what Harm can legitimately be said to have been
established.