HSVM — Harm State Monitoring Module
OOF® Origin Open Foundation®
Independent Methodological Authority
Canonical Definition
The HSVM — Harm State Monitoring Module governs the continuingobservation, reassessment readiness, signal detection, monitoring cadence,
monitoring scope, monitoring continuity, monitoring adequacy, escalation
triggers, and termination conditions required to maintain a reliable
representation of a governed Harm State over time.
HSVM ensures that Harm State governance remains responsive to material
change without requiring constant observation of every Harm dimension and
without allowing missing, failed, outdated, or discontinued monitoring to
be interpreted as disappearance, improvement, Resolution, or Finality of
Harm.
It establishes the transition:
Governed Harm State + Monitoring Requirements → Monitoring Scope →
Monitoring Cadence → State Observation → State Signal Detection →
Reassessment Trigger → Governed Harm State Monitoring
Its central question is:
What must continue to be observed, at what cadence, and under what
conditions so that material changes in the governed Harm State can be
detected and governed in time?
- Operational Role
The preceding HSS modules establish:
HSIM — what current Harm condition is identifiable
HSCM — what canonical Harm State applies
HSTM — whether that State persistsHSPM — whether a State transition has occurred
HSVM provides the continuing observation mechanism that keeps thosedeterminations connected to changing reality.
Its operational role is:
to maintain sufficient awareness of the governed Harm so that material
State persistence, deterioration, improvement, recurrence, uncertainty,
and possible transition can be detected without confusing monitoring
activity with the Harm itself.
- Position Within HSS
The HSS governance flow is:
State Identification → State Classification → State Persistence → State
Transition → State Monitoring
The Core Module sequence is:
HSIM → HSCM → HSTM → HSPM → HSVM
HSVM receives the current:
Governed Harm State
together with relevant State history, qualifications, uncertainty, andmonitoring requirements.
It produces:
Governed Harm State Monitoring
and, where applicable:State Signals and Reassessment Triggers
that feed continued HSS governance.
- Governed Object
The primary governed object is:
Harm State Monitoring
Monitoring concerns the continuing observability and governance of theHarm State.
It is not the Harm State itself.
Therefore:
Monitoring State ≠ Harm State
- Foundational Monitoring Principle
The foundational rule is:
Monitoring must follow the dynamics of Harm, not the convenience of the
system observing it.
A Harm that can materially change within minutes cannot necessarily be
governed through monthly observation.
A slowly developing Harm may not require continuous observation.
Therefore:
Uniform Monitoring ≠ Effective Harm Monitoring
- Monitoring Purpose
HSVM monitoring exists to detect whether information materially relevant
to the governed Harm State has changed.
Monitoring may support detection of:
continued State persistence
worsening
stabilization
reduction
recovery
Residual Harm
recurrenceunexpected manifestation
scope change
new uncertainty
or:
possible State transition
Monitoring does not itself decide these outcomes.
- Monitoring Scope
Monitoring scope should correspond to the governed Harm.
It may include relevant:
subjects
effects
domains
locations
systems
environments
collective conditions
composite components
and:
material downstream conditions
Only information necessary for legitimate Harm State governance should be
monitored.
- Monitoring Scope ≠ Harm Boundary
The Governed Harm Boundary is established elsewhere in HAGA™.
HSVM determines what within or materially relevant to that Boundary
requires continuing observation.
Therefore:
Monitoring Scope ≠ Governed Harm Boundary
Monitoring may focus on selected indicators without redefining the Harm
itself.
- Monitoring Cadence
Monitoring cadence must correspond to:
rate of potential Harm change
materiality of change
severity where relevant to monitoring urgency
State volatility
State uncertainty
potential escalation speedintermittency
latency
and:
practical observability
Canonical principle:
The faster Harm can materially change, the faster governance may need to
observe it.
- Continuous Monitoring
Continuous monitoring may be appropriate where:
Harm changes rapidly
escalation could become material before periodic reviewautonomous execution continues
physical processes remain active
or:
critical infrastructure consequences require immediate detection
Continuous monitoring must still remain proportionate and governed.
- Periodic Monitoring
Periodic monitoring may be appropriate where Harm changes more slowly or
continuous observation is unnecessary.
Possible cadence may be:
hourly
daily
weekly
monthly
or another governed interval.
The interval must follow the Harm dynamics rather than administrative
habit.
- Event-Triggered Monitoring
Monitoring may intensify or initiate when a defined event occurs.
Triggers may include:
new Harm manifestation
system change
subject report
measurement threshold
new downstream effect
intervention
recovery event
new evidence
or:
material environmental change
- Condition-Triggered Monitoring
Monitoring may also change when the governed Harm reaches a particular
condition.
For example:
Escalating → increase monitoring
Stabilized → maintain appropriate observation
Recovering → monitor recovery trajectory
Residual → monitor persistence or recurrence
The monitoring model should therefore be capable of adapting to State.
- Adaptive Monitoring
Monitoring requirements may change throughout the Harm lifecycle.
Conceptually:
State Change → Monitoring Requirement Reassessment → Monitoring Adaptation
Canonical principle:
Monitoring requirements must be capable of changing when the Harm changes.
- State Signal Detection
A State Signal is information indicating that the existing Harm State may
require reassessment.
A signal may indicate:
possible worsening
possible improvement
possible stabilization
possible recurrence
possible scope change
or:
possible Resolution condition
But:
State Signal ≠ State Transition
HSVM detects signals.
HSPM governs transitions.
- Signal Materiality
Not every observed fluctuation should become a governance event.
HSVM should distinguish:
noise
ordinary variation
expected fluctuation
from:
material State Signal
Canonical principle:
Observation Change ≠ Material Harm Change
- Signal Correlation
Where multiple monitoring signals relate to the same Harm, HSVM should
support correlation.
For example:
subject report + system measurement + operational observation
may collectively create a stronger State Signal than any individual
observation.
However:
Signal Volume ≠ Signal Independence
Repeated copies of the same source must not be treated as independent
confirmation.
- Distributed Monitoring
A Harm may require monitoring across:
multiple systems
multiple agents
multiple organizations
multiple subjects
multiple locations
or:
multiple domains
HSVM must preserve the relationship between distributed observations and
the same governed Harm.
Canonical principle:
Distributed Monitoring Must Not Produce Fragmented Harm Governance.
- Composite Harm Monitoring
Where Harm is composite, monitoring only one component may create a false
representation of the whole.
Therefore:
Component Monitoring ≠ Complete Harm Monitoring
Monitoring scope should cover the materially necessary components of the
composite Harm.
- Collective Harm Monitoring
Collective Harm may require monitoring at both:
individual level
and:
collective level
where appropriate.
A collective condition must not be inferred solely from a convenient
subset of individuals where that subset is not sufficiently
representative.
- Monitoring Blind Spots
HSVM must identify material portions of the Harm that are not adequately
observable.
Blind spots may result from:
missing sensors
unreported subjects
inaccessible systems
data gaps
organizational boundaries
technical limitations
geographic limitations
or:
unknown downstream effects
Canonical principle:
Unmonitored Harm ≠ Non-Existing Harm
- Monitoring Coverage
Where useful, HSVM should represent whether monitoring coverage is:
Sufficient
Partially Sufficient
Insufficient
or:Unknown
Coverage status must remain separate from Harm State.Therefore:
Monitoring Coverage ≠ Harm State Confidence by Default
- Monitoring Failure
Monitoring may fail because of:
system outage
sensor failure
data corruption
provider interruption
access loss
organizational transfer
or:
human reporting failure
A monitoring failure must become a governance condition.
It must not become evidence of Harm disappearance.
Canonical principle:
Monitoring Failure ≠ Harm Resolution
- Monitoring Continuity
Monitoring continuity should survive materially irrelevant technical or
organizational transitions.
Examples include:
model replacement
system migration
provider change
case transfer
department change
agent replacement
or:
platform migration
Where Harm remains governed, monitoring continuity should be explicitly
transferred or re-established.
- Monitoring Handoff
Where responsibility for monitoring changes, the handoff should preserve:
Harm identity
current Harm Statemonitoring scope
monitoring cadence
known blind spots
open State Signals
uncertainty
and:
next required observation
Canonical principle:
Monitoring Transfer Must Not Reset Harm Awareness.
- Monitoring Staleness
Monitoring information may become too old to reliably represent the
current Harm State.
HSVM should identify:
fresh
aging
or:
stale
monitoring information where appropriate.
But:
Stale Observation ≠ Harm End
Staleness should trigger renewed observation or reassessment.
- Monitoring and Intervention
Containment, Mitigation, and Recovery interventions may require monitoring
before, during, and after action.
Monitoring may establish whether the Harm condition changed.
However:
Intervention Completed ≠ Monitoring Complete
A Harm may continue, recur, or change after an intervention ends.
- Monitoring After Mechanism Termination
The producing mechanism may terminate before the Harm does.
Monitoring should therefore continue where the Harm lifecycle still
requires governance.
Canonical principle:
Monitoring Need Follows Harm Continuity, Not Mechanism Continuity.
- Monitoring After Apparent Improvement
Monitoring should not necessarily terminate immediately when Harm becomes:
Reduced
Recovering
or:Residual
These States may require continued observation for:regression
recurrence
persistence
or:
new downstream effects
- Monitoring and Resolution
A transition to Resolved may change monitoring requirements.
But Resolution does not itself establish Finality.
Where HRFS requires continued observation before Finality, HSVM may
support that observation.
Therefore:
Resolved ≠ Monitoring Automatically Terminated
- Monitoring Termination
Monitoring may legitimately end where:
the applicable Harm lifecycle has reached Finality
monitoring is no longer methodologically required
another governed process assumes the necessary observation function
or:
a legitimate governance determination establishes termination
Monitoring must not end solely because:
a case closes
a system is repaired
a contract ends
an organization transfers responsibility
or:
monitoring becomes inconvenient
- Monitoring Proportionality
Monitoring must remain proportionate.
More monitoring is not automatically better governance.
Excessive monitoring may create:
privacy intrusion
unnecessary data accumulation
operational burden
false signal volume
or:
unjustified surveillance
Canonical principle:
Effective Harm Monitoring Requires Sufficient Observation — Not Maximum
Observation.
- Human, Machine and Hybrid Monitoring
HSVM may support:
human monitoring
machine monitoring
or:
hybrid monitoring
No monitoring method is authoritative merely because it is automated.
Machine-generated observations must remain governed according to their:
reliability
scope
limitations
and:
applicable validation and integrity conditions
- Monitoring and Operational Reality
ORA™ may provide operational observations relevant to Harm.
But:
Operational Monitoring ≠ Harm Monitoring
A system may operate normally while Harm persists elsewhere.
HSVM therefore monitors the governed Harm condition, not merely the
producing system.
- Evidence, Validation and Integrity Boundaries
ADIT® may govern monitoring evidence.
VALIDOS™ may govern validation of relevant monitoring information.
INTEGROS® may govern integrity conditions.
HSVM may rely on those outputs.
But:
Evidence Monitoring ≠ Harm State Monitoring
Validated Data ≠ Harm State
Monitoring Integrity ≠ Harm Resolution
- Prediction and Simulation Boundary
Prediction may estimate future State change.
SIMULOS® may model possible Harm trajectories.
These may inform monitoring design.
For example, they may justify:
higher cadence
additional indicators
or:
specific trigger conditions
But:
Predicted Change ≠ Observed Change
and:
Simulated State ≠ Monitored Actual State
- Monitoring Record
HSVM should maintain sufficient record of:
what was monitored
when
at what cadence
with what coverage
what signals appeared
what blind spots existed
what failures occurred
what reassessments were triggered
and:
how monitoring requirements changed
This creates:
Harm State Monitoring History
- Minimum Implementation Framework
A minimum HSVM implementation requires eight capabilities.
- Monitoring Scope Definition
Identify the subjects, effects, dimensions, locations, systems, or
collective conditions that require observation.
- Monitoring Cadence Governance
Establish continuous, periodic, event-triggered, condition-triggered, or
adaptive monitoring according to Harm dynamics.
- State Signal Detection
Detect materially relevant signals without confusing noise, ordinary
variation, or duplicated signals with actual Harm change.
- Distributed & Complex Monitoring
Support composite, collective, multi-subject, multi-domain, and
distributed Harm without fragmenting the governed Harm object.
- Coverage, Blind-Spot & Failure Governance
Identify insufficient coverage, blind spots, monitoring failure, stale
information, and observation gaps without interpreting them as Harm
disappearance.
- Adaptive Monitoring & Reassessment
Change monitoring requirements when the Harm State, uncertainty,
intervention context, or material risk of change requires it and generate
appropriate reassessment triggers.
- Continuity & Termination Governance
Preserve monitoring across technical and organizational handoffs and
terminate monitoring only through a legitimate governance basis.
- Governed Output
Produce traceable Governed Harm State Monitoring, including material State
Signals and Reassessment Triggers for continued HSS governance. 39. Use
Case 1 — Autonomous System Stops but Harm Monitoring Continues
An autonomous system causes a governed Harm and is immediately removed
from operation.
The system is no longer producing additional Harm.
However, the affected Harm remains:
Active
HSVM reduces monitoring of the terminated execution mechanism whereappropriate but continues monitoring the actual Harm condition.
Later observations indicate improvement and generate a State Signal for
reassessment.
The governing principle is:
Monitoring follows the Harm lifecycle, not the lifecycle of the system
that produced it.
- Use Case 2 — Distributed Harm Contains an Unobserved Component
A governed Harm spans several organizational systems and affected
subjects.
Monitoring shows improvement across most observed components.
One materially relevant downstream component, however, is temporarily
inaccessible.
HSVM does not interpret:
Observed Majority Improving
as:Complete Harm Reduced
Instead, it records:partial monitoring coverage
material blind spot
and:
reassessment requirement
until sufficient observation becomes available.
The governing principle is:
Improvement in what can be observed must not erase uncertainty about what
cannot.
- Governance Requirements
HSVM requires that:
- monitoring remain linked to the correct Governed Harm identity
and
State; - monitoring scope reflect materially relevant Harm dimensions; -
monitoring scope remain separate from the Governed Harm Boundary; -
cadence correspond to Harm dynamics; - continuous monitoring not be
required where unnecessary; - periodic, event-triggered,
condition-triggered, and adaptive monitoring remain available where
appropriate; - State Signals remain distinct from State Transitions; -
ordinary variation and noise remain distinguishable from material signals;
- duplicated signals not become false independent corroboration; -
distributed monitoring not fragment Harm governance; - composite and
collective Harm receive appropriate monitoring coverage; - blind spots
remain explicit; - monitoring failure not become Harm Resolution; -
monitoring continuity survive irrelevant technical or organizational
change; - monitoring handoffs preserve Harm awareness; - stale information
trigger appropriate governance rather than assumed State termination; -
intervention completion not automatically terminate monitoring; -
mechanism termination remain separate from monitoring termination; -
Reduced, Recovering, Residual, and Resolved States not automatically
terminate monitoring; - monitoring remain proportionate and not become
unlimited surveillance; - human and machine monitoring remain subject to
appropriate governance; - prediction and simulation remain separate from
actual observation; - monitoring history remain traceable; - monitoring
terminate only through a legitimate governance basis.
- Governance Logic
HSVM applies the following logic:
Does a governed Harm State exist?
If no:
→ formal Harm State Monitoring cannot proceed through HSVM.
If yes:
→ determine what materially needs to be observed.
How quickly can the Harm materially change?
→ establish appropriate monitoring cadence.
Is Harm continuous, intermittent, latent, distributed, composite, or
collective?
→ adapt monitoring scope and method.
Is monitoring coverage sufficient?
If no:
→ identify blind spots and limitations.
Has monitoring failed or become stale?
If yes:
→ record the failure or staleness and trigger appropriate renewed
observation or reassessment.
Do not infer Harm disappearance.
Has a material State Signal appeared?
If no:
→ continue monitoring according to the governed cadence.
If yes:
→ generate a reassessment trigger.
Does the signal indicate possible State transition?
→ route to appropriate HSS State Identification, Classification,
Persistence, and Transition governance.
Has an intervention or mechanism termination occurred?
→ reassess monitoring requirements based on the Harm, not merely the
intervention or mechanism status.
Has the Harm become Reduced, Recovering, Residual, or Resolved?
→ determine whether continued monitoring remains methodologically
required.
Has legitimate monitoring termination been established?
If yes:
→ close monitoring while preserving history.
If no:
→ continue or adapt monitoring.
At every stage:
Monitoring ≠ Harm
Monitoring Scope ≠ Harm Boundary
State Signal ≠ State Transition
Observation Change ≠ Material Harm Change
Monitoring Failure ≠ Harm Resolution
Stale Observation ≠ Harm End
Mechanism Termination ≠ Monitoring Termination
Resolved ≠ Monitoring Automatically Terminated
- Governance Outputs
HSVM may produce:
Governed Harm State Monitoring
Monitoring Scope
Monitoring Cadence
Continuous Monitoring Requirement
Periodic Monitoring Requirement
Event-Triggered Monitoring
Condition-Triggered Monitoring
Adaptive Monitoring Requirement
State Signal
Material State Signal
Signal Correlation
Monitoring Coverage State
Monitoring Blind Spot
Monitoring Gap
Monitoring Failure
Monitoring Staleness
Monitoring Continuity Record
Monitoring Handoff
Monitoring Adaptation
Reassessment Trigger
Monitoring Termination Determination
Harm State Monitoring History
The principal output is:Governed Harm State Monitoring
- Critical Distinctions
Monitoring State ≠ Harm State
Uniform Monitoring ≠ Effective Harm Monitoring
Monitoring Scope ≠ Governed Harm Boundary
State Signal ≠ State Transition
Observation Change ≠ Material Harm Change
Signal Volume ≠ Signal Independence
Distributed Monitoring ≠ Fragmented Harm Governance
Component Monitoring ≠ Complete Harm Monitoring
Unmonitored Harm ≠ Non-Existing Harm
Monitoring Coverage ≠ Harm State
Monitoring Failure ≠ Harm Resolution
Monitoring Transfer ≠ Harm Reset
Stale Observation ≠ Harm End
Intervention Completed ≠ Monitoring Complete
Mechanism Termination ≠ Monitoring Termination
Reduced Harm ≠ Monitoring Automatically Terminated
Recovering Harm ≠ Monitoring Automatically Terminated
Residual Harm ≠ Monitoring Automatically Terminated
Resolved ≠ Monitoring Automatically Terminated
Maximum Observation ≠ Best Governance
Operational Monitoring ≠ Harm Monitoring
Predicted Change ≠ Observed Change
Simulated State ≠ Monitored Actual State
- Canonical Boundary
The HSVM — Harm State Monitoring Module governs the continuing
observation, monitoring scope, cadence, signal detection, signal
materiality, monitoring coverage, blind spots, failures, staleness,
adaptive monitoring, continuity, handoff, reassessment triggers,
proportionality, termination conditions, and historical monitoring record
required to maintain reliable Harm State governance over time. It does not
itself identify or classify the Harm State, determine State Persistence or
State Transition, redetermine whether Harm exists, redefine the Governed
Harm Boundary, govern Harm accumulation, compounding, propagation or
cascading, perform Containment or Mitigation, govern Recovery or Residual
Harm determination, establish Resolution or Finality, determine general
causation, assign accountability or liability, govern claims or
compensation, or replace operational reality, evidence, validation,
integrity, identity, AI behavior, autonomous execution, simulation,
prediction, Value, tax-event, privacy, surveillance, or
jurisdiction-specific governance.
- Canonical Closing Statement
A Harm State can remain governable only while governance remains capable
of detecting when reality materially changes.
Too little monitoring allows Harm to change unnoticed. Too much monitoring
can become unnecessary surveillance without improving Harm governance.
HSVM governs the space between those failures.
Monitoring must continue for as long as the Harm requires observation,
adapt when the Harm changes, and end only when governance — not silence —
establishes that it should.