HTBM — Harm Temporal Boundary Module
OOF® Origin Open Foundation®
Independent Methodological Authority
Canonical Definition
The HTBM — Harm Temporal Boundary Module governs how the temporal extentof a recognized Harm object is established, including when the governed
Harm begins, continues, changes in temporal form, becomes intermittent,
recurs, remains open, ends, or requires retrospective correction, without
substituting Exposure, mechanism operation, manifestation, reporting,
Recognition, investigation, or administrative timestamps for the actual
temporal boundary of Harm.
HTBM establishes the transition:
Governed Boundary Identification State + Governed Harm Subject Boundary →
Harm-Relevant Temporal Information → Temporal Boundary Assessment → Harm
Start / Continuity / End → Governed Harm Temporal Boundary
Its central question is:
What period of time legitimately belongs to the governed Harm?
- Operational Role
A Harm Boundary cannot be legitimate without distinguishing the Harm's own
temporal lifecycle from the timestamps of the systems surrounding it.
A harmful mechanism may begin before Harm.
Harm may exist before Recognition.
Exposure may end while Harm continues.
A visible effect may disappear while Harm remains.
A mechanism may stop while downstream Harm persists.
HTBM therefore governs:
when the Harm itself begins and how long it remains within the governed
Harm object.
- Position Within HBS
The HBS internal flow is:
Boundary Identification → Subject Boundary → Temporal Boundary → Effect
Boundary → Downstream Boundary
The Core Module sequence is:
HBIM → HSBM → HTBM → HEBM → HDBM
HTBM receives relevant temporal candidates from HBIM together with the
established Subject Boundary.
It produces:
Governed Harm Temporal Boundary
for integration into the complete Harm Boundary.- Governed Object
The primary governed object is:
Harm Temporal Boundary
Possible temporal states include:Not Established
Provisionally Established
Exact
Bounded
Estimated
Continuous
Intermittent
Recurring
Progressive
Open
Historically Reconstructed
Closed
Disputed
Uncertain
The temporal state must preserve its supporting basis and level ofprecision.
- Foundational Temporal Principle
The foundational principle is:
The time at which Harm becomes visible, reported, recognized,
investigated, or administratively recorded does not necessarily establish
when Harm began.
Therefore:
Harm Time ≠ Governance Awareness Time
- Harm Temporal Start
The Harm Temporal Boundary begins at the earliest materially supportable
point at which Harm actually begins to exist.
That point derives from the Harm lifecycle governed through HEMS.
It must not be replaced automatically by:
Exposure Start
Mechanism Start
First Manifestation
First Signal
First Report
Recognition Time
Incident Creation
Investigation Start
Diagnosis
or:Claim Date
- Exposure Start ≠ Harm Start
Exposure may exist before Harm.
Conceptually:
Exposure → Exposure Continues → Harm Emergence → Harm
Therefore:
Exposure Start ≠ Harm Temporal Boundary Start
HES owns Exposure.
- Mechanism Start ≠ Harm Start
A Harm-producing mechanism may operate before sufficient conditions exist
for Harm.
Therefore:
Mechanism Activation ≠ Harm Emergence by Default
Operational execution does not define the Harm Temporal Boundary
automatically.
- Appearance Time ≠ Harm Start
Harm may exist before it becomes apparent.
Therefore:
First Visible Effect ≠ Harm Start by Default
This preserves latent and delayed Harm.
- Recognition Time ≠ Harm Start
HRS may recognize Harm substantially later than Harm Emergence.
Therefore:
Recognition Date ≠ Harm Temporal Boundary Start
HLRM preserves Recognition Latency.
HTBM preserves the actual Harm boundary.
- Administrative Time ≠ Harm Time
Administrative systems may generate timestamps such as:
incident opened
case created
claim submitted
investigation started
authority notified
file registered
These timestamps may be relevant evidence.
They do not define Harm time by default.
Canonical principle:
Administrative chronology must not replace Harm chronology.
- Exact Temporal Start
Where the Harm Emergence point is sufficiently supported, HTBM may
establish an exact Harm start.
The precision used must remain consistent with the available support.
- Bounded Temporal Start
Where the exact start cannot be established, HTBM may use:
Earliest Supported Harm Start
and:Latest Supported Harm Start
to create a governed temporal range.This is preferable to false precision.
- Estimated Temporal Start
Where a materially reasonable estimate can be established, HTBM may
preserve:
Estimated Harm Start
together with:basis
method
uncertainty
confidence
An estimate must not be represented as an exact timestamp.
- Unknown Harm Start
Where Harm is established but its exact or bounded beginning remains
unknown:
Unknown Start ≠ Recognition Date
The correct state may remain:
Harm Start Unknown
- Temporal Precision
HTBM applies the principle:
Temporal Precision Must Not Exceed Temporal Support
Permitted representations may include:
exact timestamp
date
time range
bounded interval
estimated period
before / after relationship
unknown
Methodological uncertainty is preferable to invented certainty.
- Harm Continuity
After Harm begins, HTBM determines whether the Harm remains temporally
continuous.
Continuity may exist despite changes in:
visibility
severity
manifestation
location
subject condition
mechanism activity
reporting
system state
Temporal continuity follows Harm, not constant observation.
- Continuous Harm
Continuous Harm remains materially present throughout a period.
Conceptually:
Harm Start → Harm → Harm → Harm → Harm End / Open Harm
Continuous Harm does not require constant measurement.
- Intermittent Harm
Harm may become observable or active intermittently while remaining part
of one Harm lifecycle.
Conceptually:
Harm → Reduced / Unobservable Interval → Harm Manifestation → Interval →
Harm Manifestation
The central question is whether Harm continuity remains materially
supportable.
- Interruption ≠ New Harm
A temporary interruption does not automatically terminate one Harm and
create another.
Canonical distinction:
Temporal Interruption ≠ New Harm Object by Default
HTBM must determine whether continuity survives the interruption.
- Recurring Harm
A harmful state may recur.
Recurrence may represent:
continued Harm
repeated manifestations of one Harm
reactivation of Harm
or:
a new Harm lifecycle
The answer must not be assumed from recurrence alone.
- Recurrence ≠ Continuity by Default
Just as interruption does not automatically create new Harm:
Recurrence ≠ Same Harm by Default
HTBM must preserve both possibilities.
- Progressive Harm
Some Harm develops progressively after Emergence.
Conceptually:
Harm Emergence → Harm₁ → Harm₂ → Harm₃
Increasing Harm does not create a new temporal start at every state
change.
HSS and HCPS later govern Harm State and change.
HTBM governs lifecycle continuity.
- Accumulated Harm
Accumulated Harm may emerge after effects or conditions accumulate beyond
the Harm Emergence threshold.
The temporal boundary begins when Harm exists, not necessarily when
accumulation first started.
Therefore:
Accumulation Start ≠ Harm Start by Default
- Delayed Harm
Harm may emerge after a Harm-relevant mechanism or Exposure occurred.
Conceptually:
Exposure / Mechanism → Delay → Harm Emergence
HTBM must preserve that distinction.
Mechanism Time ≠ Harm Time
- Latent Harm
Harm may exist while remaining hidden or not yet observable.
Therefore:
Invisible Harm May Still Be Temporally Existing Harm
The Temporal Boundary must not depend on visibility.
- Multi-Subject Temporal Structure
Subjects within the same Harm may become affected at different times.
Conceptually:
Subject A enters Harm at T1
Subject B enters Harm at T2
Subject C enters Harm at T3
HTBM must support subject-specific temporal sub-boundaries wherematerially necessary.
- Shared Harm ≠ Shared Harm Start for Every Subject
One Harm object may have an overall temporal boundary while individual
subjects have different Harm entry points.
Therefore:
Harm Object Start ≠ Every Subject Harm Start by Default
The complete temporal model may preserve both.
- Collective Harm Temporal Boundary
Collective Harm may develop progressively across a group or population.
There may be:
first individual effect
group pattern formation
collective Harm Emergence
later Recognition
These timestamps must remain distinguishable.
- Cross-Domain Temporal Structure
A Harm may enter different domains at different times.
Example:
Physical Harm at T1 → Functional Harm at T2 → Financial Consequence at T3
Domain transition does not automatically reset the Harm Temporal Boundary.
- Distributed Harm Temporal Structure
Composite or distributed Harm may emerge through interactions occurring
across:
agents
sessions
systems
organizations
locations
and:
time periods
The Temporal Boundary must be capable of representing the complete Harm
rather than only individual execution timestamps.
- Local Execution Time ≠ Harm Time
In distributed systems:
Agent A executes at T1
Agent B executes at T2
Tool C executes at T3
The Harm may emerge only from their combined effect at T4.Therefore:
Local Execution Timestamp ≠ Harm Emergence Timestamp by Default
- Non-Linguistic Harm
Embodied AI, autonomous vehicles, robots, industrial systems, and other
physical AI may produce Harm without a linguistic reasoning trace.
HTBM must remain capable of establishing:
when Harm began
how long it continued
and:
when it ended
without requiring a textual decision point.
- Harm Temporal End
The Temporal Boundary ends only when the governed Harm no longer remains
within the relevant Harm lifecycle.
This point must not be inferred automatically from:
mechanism termination
Exposure termination
signal disappearancereport closure
incident closure
system shutdown
subject discharge
claim closure
or:
organizational acknowledgement
- Mechanism End ≠ Harm End
Canonical principle:
Termination of the originating mechanism does not necessarily terminate
the Harm lifecycle.
A mechanism may stop while Harm:
persists
develops
propagates
requires recovery
or:
remains residual
- Exposure End ≠ Harm End
Exposure may cease while existing Harm continues.
Therefore:
End of Exposure ≠ End of Harm
This distinction is fundamental to HAGA™.
- Signal End ≠ Harm End
Recognition Signals may disappear.
That does not establish that Harm ended.
Therefore:
No Current Signal ≠ No Current Harm
- Observation End ≠ Harm End
A Harm manifestation may no longer be visible while underlying Harm
persists.
Therefore:
No Current Observation ≠ Harm Finality
- Intervention ≠ Harm End
Containment or mitigation may begin during the Harm lifecycle.
Successful intervention may reduce Harm.
But:
Intervention Start ≠ Harm End
HCOS and HMS later govern those mechanisms.
- Recovery Start ≠ Harm End
Recovery may begin while Harm remains.
Therefore:
Recovery Initiation ≠ Harm Termination
HRRHS later governs Recovery and Residual Harm.
- Apparent Recovery ≠ Temporal Finality
An apparent return to normal conditions may not establish that Harm has
ended.
Residual Harm may remain.
Therefore:
Observable Recovery ≠ Harm Finality
- Harm End and Residual Harm
Where Residual Harm remains, the relevant Harm lifecycle may continue even
after major effects have recovered.
HTBM must not artificially close the Temporal Boundary solely because the
principal manifestation disappeared.
- Closed Temporal Boundary
A Harm Temporal Boundary may become closed where the Harm lifecycle has a
materially supportable beginning and end.
A closed boundary must preserve:
start
end
basis
uncertainty
historical revisions
- Open Temporal Boundary
Where Harm continues:
Harm Start → Harm Continues → Present
HTBM establishes:
Open Harm Temporal Boundary
Open does not mean uncertain.A Harm may have a well-established start and a legitimately open end.
- Open ≠ Unknown
Canonical distinction:
Open Temporal Boundary ≠ Unknown Temporal Boundary
Open means Harm has not legitimately ended.
Unknown means the temporal state cannot yet be sufficiently established.
- Historical Reconstruction
Later information may reveal that Harm:
began earlier
continued longer
ended later
or:
never actually ended when previously assumed
HTBM must support retrospective reconstruction.
- Temporal Boundary Expansion
The Temporal Boundary may expand:
backward
or:
forward
Conceptually:
Boundary₁ → New Temporal Information → Expanded Boundary₂
The previous boundary must remain preserved.
- Temporal Boundary Contraction
New information may establish that the previously governed Harm period was
too broad.
HTBM may contract:
start forward
or:
end backward
where materially justified.
Contraction must remain traceable.
- Temporal Boundary Correction
Correction may be required where the previous boundary relied incorrectly
on:
Recognition Time
report dateincident date
diagnosis date
mechanism operation
claim period
or another unsuitable proxy.
The corrected boundary must preserve the reason for change.
- Temporal Boundary Dispute
Different sources may support different Harm start or end points.
HTBM must preserve:
competing temporal claims
supporting basis
confidence
uncertainty
areas of agreement
A dispute must not be resolved by choosing the administratively easiest
timestamp.
- Temporal Boundary Confidence
Confidence may be represented separately for:
Harm Start
Continuity
and:Harm End
For example:Start — Moderate Confidence
Continuity — High Confidence
End — Unknown / Open
A single confidence score should not erase meaningful temporaldifferences.
- Temporal Confidence ≠ Harm Severity
Canonical distinction:
Temporal Boundary Confidence ≠ Harm Severity
Precisely timed Harm may be minor.
Severe Harm may have uncertain historical timing.
- Administrative Closure
A case, incident, claim, investigation, or system record may be closed
before Harm ends.
Therefore:
Administrative Closure ≠ Harm Temporal Closure
This distinction must remain explicit.
- Legal Time Boundary
A jurisdiction may impose:
limitation periods
reporting periods
claim periods
regulatory windows
These may be legally important.
They do not redefine the methodological Harm Temporal Boundary.
Therefore:
Legal Time Window ≠ Harm Time by Default
- Accountability and Liability Boundary
The time at which responsibility or liability becomes established may
differ from the Harm lifecycle.
Therefore:
Accountability Timeline ≠ Harm Timeline
Liability Timeline ≠ Harm Timeline
HTBM must remain neutral to downstream legal conclusions.
- Evidence Boundary
Evidence may exist only for part of the Harm period.
But:
Evidence Availability Period ≠ Harm Temporal Boundary
The appropriate result may be a bounded or uncertain Harm period rather
than artificial temporal exclusion.
- Historical Evidence
Historical evidence may alter the Temporal Boundary.
ADIT® governs evidence.
VALIDOS™ may govern reliance on temporal claims.
HTBM governs what those supported temporal relationships mean for the Harm
Boundary.
- ORA™ Boundary
ORA™ may establish operational timestamps such as:
execution start
execution end
system state change
intervention
failure
HTBM may use them.
It does not equate operational execution time with Harm time.
Canonical distinction:
Operational Timeline ≠ Harm Timeline by Default
- Relationship to HEMS, HRS, and HLRM
HEMS determines:
when and how Harm began to exist.
HRS determines:
when Harm became recognized.
HLRM governs:
the temporal separation between Harm Emergence and Recognition.
HTBM determines:
which temporal extent belongs to the Harm Boundary itself.
Therefore:
Emergence Governance ≠ Recognition Governance ≠ Recognition Latency
Governance ≠ Temporal Boundary Governance
- Relationship to Later HAGA™ Standards
HTBM establishes the temporal extent of the Harm object.
It does not govern:
Harm State
Harm Change
Propagation
Containment
Mitigation
Recovery
Residual Harm
or:Finality
Those later standards operate within or upon the governed Harm lifecycle.- Historical Temporal Integrity
HTBM must preserve:
Temporal Boundary State₁ → New Information → Temporal Boundary State₂
including:
original start
original end
uncertainty
supporting basis
revised start
revised end
reason for revision
Canonical principle:
Current Harm Timeline ≠ Complete Harm Timeline History
- Minimum Implementation Framework
A minimum HTBM implementation requires eight capabilities.
- Harm Start Governance
Establish exact, bounded, estimated, or unknown Harm start without
substituting Exposure, mechanism, manifestation, reporting, Recognition,
incident, investigation, diagnosis, or claim timestamps by default.
- Harm Continuity Governance
Represent continuous, intermittent, recurring, progressive, accumulated,
latent, and distributed Harm temporal structures.
- Harm End Governance
Determine whether Harm has materially ended without equating mechanism
termination, Exposure termination, signal disappearance, administrative
closure, intervention, or apparent recovery with Harm termination.
- Temporal Precision & Uncertainty
Represent exact timestamps, ranges, estimates, open periods, unknown
states, disputes, and confidence without unsupported precision.
- Multi-Subject & Distributed Temporal Structure
Support subject-specific, collective, cross-domain, composite, and
distributed Harm timelines.
- Boundary Change Governance
Support temporal expansion, contraction, correction, dispute, reopening,
and retrospective reconstruction.
- Historical Continuity
Preserve previous Harm Temporal Boundary states and the basis for every
material change.
- Governed Output
Produce a traceable Governed Harm Temporal Boundary suitable for
integration into the complete Harm Boundary.
A system that defines Harm time only through incident, reporting,
Recognition, mechanism, claim, or administrative timestamps does not fully
implement HTBM.
- Use Case 1 — Harm Continues After the Producing Mechanism Stops
A harmful operational condition begins at T1.
Harm emerges at T2.
The condition is discovered and stopped at T3.
The affected subject continues experiencing the Harm until T5.
HTBM establishes:
Mechanism Start T1 → Harm Start T2 → Mechanism End T3 → Harm Continues →
Harm End T5
The Harm Temporal Boundary is:
T2 → T5
not:
T1 → T3
The governing principle is:
The temporal boundary of Harm follows Harm, not the operating period of
the mechanism that produced it.
- Use Case 2 — Historical Information Shows Harm Began Before
Recognition
A digital system recognizes Harm on Day 20.
Initial records use Day 20 as the case start.
Later operational and subject information establishes that Harm had
already emerged between Day 8 and Day 10.
HTBM replaces the administrative proxy with a bounded Harm start:
Harm Start = Day 8–10
while preserving:
Recognition = Day 20
and the previous temporal record.
The governing principle is:
Late Recognition must not become an artificial late beginning of Harm.
- Governance Requirements
HTBM requires that:
- Harm time remain distinct from Exposure, mechanism,
manifestation,
reporting, Recognition, administrative, legal, accountability, and
liability time; - Harm Temporal Start derive from materially supportable
Harm Emergence; - temporal precision never exceed temporal support; -
exact, bounded, estimated, unknown, and open boundaries remain
representable; - continuous, intermittent, recurring, progressive,
accumulated, latent, composite, and distributed Harm remain temporally
governable; - interruption not automatically create a new Harm; -
recurrence not automatically establish continuity; - multi-subject Harm
support different subject entry times; - domain transition not
automatically reset Harm time; - local execution timestamps not
automatically define Harm time; - non-linguistic Harm remain temporally
governable; - mechanism and Exposure termination not automatically
terminate Harm; - signal or observation disappearance not establish Harm
end; - intervention and Recovery initiation not establish Harm end; -
Residual Harm remain capable of extending the Harm lifecycle; - open and
unknown temporal boundaries remain distinct; - historical reconstruction
remain possible; - expansion, contraction, correction, dispute, and
reopening preserve history; - administrative or legal closure not redefine
Harm closure; - evidence availability not automatically define the Harm
period; - HTBM output remain suitable for the complete Governed Harm
Boundary.
- Governance Logic
HTBM applies the following logic:
Has Harm been recognized and boundary candidates established?
If no:
→ do not manufacture a Temporal Boundary.
If yes:
→ identify the Harm Emergence reference.
Is Harm Start precisely supportable?
If yes:
→ establish exact start.
If partially:
→ establish a bounded or estimated start.
If no:
→ preserve Unknown Harm Start.
Did Exposure or the mechanism begin earlier?
→ preserve those timestamps separately.
Did Recognition occur later?
→ preserve Recognition separately.
Does Harm continue continuously?
If yes:
→ maintain continuous temporal boundary.
If not:
→ assess interruption, recurrence, latency, or separate Harm lifecycle.
Did the producing mechanism stop?
→ do not close Harm automatically.
Did Exposure stop?
→ do not close Harm automatically.
Did signals or visible effects disappear?
→ determine whether Harm itself remains.
Has Harm materially ended?
If no:
→ maintain Open Temporal Boundary.
If yes:
→ establish supported Harm End.
Has new historical information changed the timeline?
→ expand, contract, correct, or reopen while preserving prior states.
At every stage:
Exposure Time ≠ Harm Time
Mechanism Time ≠ Harm Time
Recognition Time ≠ Harm Time
Administrative Time ≠ Harm Time
Mechanism End ≠ Harm End
No Observation ≠ No Harm
Recovery ≠ Finality
- Governance Outputs
HTBM may produce:
- Governed Harm Temporal Boundary
- Harm Temporal Start
- Exact Harm Start
- Bounded Harm Start
- Estimated Harm Start
- Unknown Harm Start State
- Harm Continuity State
- Continuous Harm Interval
- Intermittent Harm Structure
- Recurring Harm Structure
- Progressive Harm Structure
- Subject-Specific Temporal Boundary
- Collective Harm Temporal Boundary
- Cross-Domain Temporal Structure
- Distributed Harm Temporal Structure
- Harm Temporal End
- Open Harm Temporal Boundary
- Closed Harm Temporal Boundary
- Temporal Boundary Uncertainty
- Temporal Boundary Confidence
- Temporal Boundary Dispute State
- Temporal Boundary Expansion Record
- Temporal Boundary Contraction Record
- Temporal Boundary Correction Record
- Temporal Boundary Reopening State
- Historical Harm Timeline Record
The principal output is:
Governed Harm Temporal Boundary
- Critical Distinctions
Harm Time ≠ Governance Awareness Time
Exposure Start ≠ Harm Temporal Boundary Start
Mechanism Activation ≠ Harm Emergence by Default
First Visible Effect ≠ Harm Start by Default
Recognition Date ≠ Harm Temporal Boundary Start
Administrative Chronology ≠ Harm Chronology
Unknown Start ≠ Recognition Date
Temporal Precision Must Not Exceed Temporal Support
Temporal Interruption ≠ New Harm Object by Default
Recurrence ≠ Same Harm by Default
Accumulation Start ≠ Harm Start by Default
Mechanism Time ≠ Harm Time
Harm Object Start ≠ Every Subject Harm Start by Default
Local Execution Timestamp ≠ Harm Emergence Timestamp by Default
Mechanism End ≠ Harm End
End of Exposure ≠ End of Harm
No Current Signal ≠ No Current Harm
No Current Observation ≠ Harm Finality
Intervention Start ≠ Harm End
Recovery Initiation ≠ Harm Termination
Observable Recovery ≠ Harm Finality
Open Temporal Boundary ≠ Unknown Temporal Boundary
Administrative Closure ≠ Harm Temporal Closure
Legal Time Window ≠ Harm Time by Default
Accountability Timeline ≠ Harm Timeline
Liability Timeline ≠ Harm Timeline
Evidence Availability Period ≠ Harm Temporal Boundary
Operational Timeline ≠ Harm Timeline by Default
- Canonical Boundary
The HTBM — Harm Temporal Boundary Module governs the temporal extent of a
recognized Harm object by establishing and maintaining the materially
supportable Harm start, continuity, interruption, recurrence, progression,
open duration, Harm end, uncertainty, confidence, dispute, retrospective
reconstruction, expansion, contraction, correction, reopening, and
historical temporal continuity. It preserves the distinction between Harm
time and Exposure, mechanism, manifestation, reporting, Recognition,
investigation, administrative, legal, accountability, liability, and
evidence timelines. It does not determine Harm Emergence independently of
HEMS, govern Recognition Latency owned by HLRM, establish the Effect or
Downstream Boundary, formally determine Harm, assign accountability or
liability, or replace operational reality, evidence, validation,
integrity, identity, AI behavior, autonomous execution, simulation, Value,
or tax-event governance.
- Canonical Closing Statement
Harm has its own timeline.
It may begin after Exposure starts, exist before anyone recognizes it,
continue after the mechanism stops, remain after visible effects
disappear, and be reconstructed years after the original event.
HTBM prevents administrative timestamps, technical execution periods,
reporting dates, and governance awareness from replacing that temporal
reality.
The temporal boundary of Harm begins when Harm becomes real and ends when
the Harm lifecycle legitimately ends — not when the surrounding system
starts or stops looking at it.