HDBM — Harm Downstream Boundary Module
OOF® Origin Open Foundation®
Independent Methodological Authority
Canonical Definition
The HDBM — Harm Downstream Boundary Module governs how far the boundary ofa recognized Harm legitimately extends through downstream effects,
consequences, affected subjects, domains, systems, dependencies,
locations, and temporal stages by establishing whether later consequences
remain materially continuous with the original governed Harm, constitute
propagation of that Harm, or have crossed a sufficient boundary break to
require separate governance.
HDBM establishes the transition:
Governed Harm Subject Boundary + Governed Harm Temporal Boundary +
Governed Harm Effect Boundary → Downstream Consequence Candidates →
Continuity / Break Assessment → Downstream Inclusion / Exclusion →
Governed Harm Downstream Boundary
Its central question is:
How far downstream does the governed Harm legitimately extend before a
consequence falls outside its boundary or becomes a separate Harm object?
- Operational Role
Harm may continue beyond:
the originating event
the original subject
the first effect
the original system
the original organization
the original location
or:
the termination of the Harm-producing mechanism
But Harm cannot be extended indefinitely merely because later consequences
can be connected through some chain of events.
HDBM governs this boundary.
Its operational role is:
to preserve legitimate Harm continuity across downstream consequences
while establishing where that continuity materially ends.
- 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
HDBM is the final Core Module of HBS.
It integrates:
Governed Boundary Identification State
Governed Harm Subject Boundary
Governed Harm Temporal Boundary
and:Governed Harm Effect Boundary
into the downstream dimension required for the complete:Governed Harm Boundary
- Governed Object
The primary governed object is:
Harm Downstream Boundary
Possible states include:No Downstream Extension
Candidate Downstream Extension
Provisionally Included
Included
Continuous
Propagated
Partially Included
Boundary Break Pending
Boundary Break Established
Separate Harm Candidate
Excluded
Uncertain
Disputed
The state must remain traceable to the relationships supporting it.- Foundational Downstream Principle
The foundational distinction is:
Downstream Consequence ≠ Same Harm by Default
But equally:
Downstream Consequence ≠ Separate Harm by Default
HDBM exists because neither automatic inclusion nor automatic separation
is legitimate.
- Downstream Consequence
A Downstream Consequence is an effect, subject impact, system consequence,
domain transition, dependency consequence, or other materially related
development occurring beyond the immediate Harm effect structure.
Conceptually:
Governed Harm → Effect → Downstream Consequence
The consequence becomes a candidate for boundary assessment.
- Immediate vs Downstream Effect
HEBM governs the effects belonging to Harm.
HDBM focuses on the point at which consequences extend beyond the
immediate effect structure.
The distinction may not always be physically or temporally obvious.
The governing question is:
Does sufficient Harm continuity remain?
- Harm Continuity
Downstream inclusion requires a materially supportable continuity
relationship with the governed Harm.
Continuity may be supported through combinations of:
subject continuity
effect continuity
temporal continuity
dependency continuity
domain continuity
system relationship
operational relationship
propagation structure
composite relationship
No single factor is universally sufficient.
- Boundary Continuity ≠ General Causation
HDBM may require sufficient association to determine whether a consequence
remains inside the Harm Boundary.
It does not establish general causation.
Therefore:
Downstream Boundary Continuity ≠ Final Causal Attribution
- Direct Downstream Consequence
A downstream consequence may remain closely connected to the original
Harm.
Conceptually:
Harm → Effect A → Consequence B
Where continuity remains materially supportable, Consequence B may remain
inside the same Harm Boundary.
- Multi-Step Downstream Chain
Harm may develop through several stages:
Harm → Effect A → Consequence B → Consequence C
The existence of multiple steps does not automatically break Harm
continuity.
But each additional step may require stronger boundary analysis.
Canonical principle:
Chain Length Alone Does Not Determine Harm Continuity
- Downstream Distance
Downstream distance may be:
temporal
relational
systemic
organizational
spatial
domain-based
or:
dependency-based
Greater distance may increase uncertainty.
It does not automatically establish exclusion.
- Temporal Distance
A consequence may emerge substantially later than the original Harm.
Therefore:
Temporal Distance ≠ Boundary Break by Default
Delayed effects and consequences must remain governable where continuity
persists.
- Spatial Distance
Harm may produce consequences elsewhere.
Therefore:
Geographic Distance ≠ Boundary Break by Default
This is especially important for:
digital systems
supply chains
infrastructure
environmental Harm
and:
distributed operations
- System Distance
A consequence may enter another technical system.
Therefore:
System Transition ≠ Boundary Break by Default
The Harm Boundary does not automatically stop at an API, platform, model,
network, or system interface.
- Organizational Distance
A consequence may cross organizational boundaries.
Therefore:
Organizational Transition ≠ Boundary Break by Default
Harm continuity must be assessed independently of corporate or
institutional structure.
- Jurisdictional Distance
A consequence may cross legal jurisdictions.
Therefore:
Jurisdictional Boundary ≠ Harm Boundary by Default
Legal treatment may change.
The methodological Harm object does not necessarily change.
- Domain Transition
A Harm may produce consequences in another domain.
Examples:
Physical → Functional → Financial
Digital → Operational → Organizational
Environmental → Infrastructure → Societal
Therefore:
Domain Transition ≠ Boundary Break by Default
But cross-domain association must remain materially supportable.
- Subject Transition
Harm affecting Subject A may produce a consequence affecting Subject B.
Conceptually:
Harm → Subject A Effect → Subject B Consequence
Subject transition does not automatically establish:
same Harm
or:
different Harm
HSBM establishes the Subject Boundary.
HDBM determines downstream continuity.
- Dependency-Mediated Consequence
Downstream Harm may travel through dependency relationships.
Examples include:
system dependency
infrastructure dependency
organizational dependency
economic dependency
functional dependency
environmental dependency
A dependency provides a pathway.
It does not automatically establish inclusion.
Therefore:
Dependency ≠ Harm Continuity by Default
- Propagated Harm
A downstream consequence may represent propagation of existing Harm.
Conceptually:
Existing Harm → Propagation Path → Additional Harm Effect
Where the original Harm remains materially continuous, the propagated
consequence may remain within the same governed Harm lifecycle.
HCPS later governs the actual change and propagation process.
HDBM governs whether the propagated consequence remains within the same
Harm Boundary.
- Propagation Governance vs Boundary Governance
This distinction is critical:
HDBM asks: Does this downstream consequence remain part of this Harm?
HCPS asks: How did existing Harm spread, compound, accumulate, or cascade?
Therefore:
Downstream Boundary ≠ Harm Propagation Governance
- Cascading Consequences
One Harm may contribute to a cascade:
Harm → Effect A → System B Failure → Effect C → System D Consequence
HDBM must determine where the original Harm Boundary continues and where a
separate Harm lifecycle begins.
A cascade does not automatically constitute one infinitely expanding Harm.
- Harm Chain
HDBM may represent:
Harm₁ → Consequence → Harm₂ → Consequence → Harm₃
This allows governance to preserve relationships between distinct Harm
objects without collapsing them into one Harm.
Canonical principle:
Related Harms Do Not Need to Become One Harm
- Boundary Break
A Boundary Break is the point at which downstream continuity becomes
insufficient for a consequence to remain inside the original Harm
Boundary.
A Boundary Break may arise through:
independent intervening conditions
new Harm Emergence
materially separate subject-effect structure
independent operational event
loss of temporal or relational continuity
new dominant mechanism
or another materially sufficient discontinuity.
- Boundary Break ≠ No Relationship
A consequence outside the Harm Boundary may still be related to the
original Harm.
Therefore:
Boundary Break ≠ Relationship Absence
The relationship may remain relevant for:
accountability
evidence
risk
claims
Value consequences
or:other governance
without requiring the consequence to remain part of the same Harm object.
- Intervening Condition
An intervening condition is a materially relevant development between the
original Harm and a downstream consequence.
Conceptually:
Harm → Effect → Intervening Condition → Consequence
The condition may:
preserve continuity
weaken continuity
or:
break continuity
Its presence alone does not decide the boundary.
- Independent Intervening Condition
Where an intervening condition independently produces a new Harm
lifecycle, HDBM may establish:
Boundary Break → Separate Harm Candidate
The original Harm and new Harm may remain related without being
methodologically identical.
- New Harm Emergence
A downstream consequence may itself cross a new Harm Emergence threshold.
Where it forms a materially independent Harm object:
Harm₁ → Downstream Condition → Harm₂
HAGA™ must preserve both:
relationship
and:
separate Harm identity
- Harm Identity Continuity
HDBM must preserve the identity of the original Harm throughout downstream
analysis.
Expansion must not make the Harm object conceptually meaningless.
Canonical principle:
A Harm Boundary may expand without losing the identity of the Harm it
bounds.
If that identity can no longer be coherently maintained, separate Harm
governance may be required.
- Composite Downstream Harm
A downstream consequence may emerge from several upstream effects acting
together.
Conceptually:
Effect A + Effect B + Effect C → Downstream Consequence
No individual effect may be sufficient.
Therefore:
Individual Upstream Insufficiency ≠ Composite Downstream Insufficiency
- Distributed Downstream Harm
Consequences may propagate across:
agents
systems
organizations
subjects
locations
domains
infrastructure
and:
time periods
Technical or organizational distribution must not automatically fragment
the Harm Boundary.
- AI and Autonomous System Chains
An AI-mediated Harm chain may involve:
Model → Agent → Tool → External System → Physical Action → Human / System
Effect
HDBM must not assume that the Harm Boundary ends when execution leaves the
original AI system.
Canonical distinction:
AI System Boundary ≠ Harm Downstream Boundary
- Perception-to-Action Chain
Autonomous Harm may propagate through non-linguistic operational chains.
For example:
Perception → Interpretation → Action → Physical Effect → System Response →
Downstream Consequence
The absence of text or explicit linguistic reasoning does not break Harm
continuity.
- Mechanism Termination
The originating mechanism may stop while downstream consequences continue.
Canonical principle:
Termination of the originating mechanism does not necessarily terminate
the Harm lifecycle.
HDBM must therefore assess consequences beyond mechanism termination.
- Downstream Persistence
A consequence may persist after:
mechanism termination
Exposure termination
initial mitigationsystem shutdown
or:
organizational response
Persistence does not automatically establish inclusion, but it must remain
governable.
- Mitigation Does Not Reset the Boundary
Mitigation may reduce Harm without eliminating downstream consequences.
Therefore:
Mitigation ≠ Boundary Reset
HMS later governs Mitigation.
- Recovery Does Not Erase Downstream Harm
Recovery of the original subject or effect does not automatically
eliminate downstream consequences already created.
Therefore:
Upstream Recovery ≠ Downstream Harm Elimination
- Residual Harm
Residual Harm may remain downstream even where primary effects have
substantially recovered.
HRRHS later governs Residual Harm.
HDBM ensures that legitimate residual consequences are not excluded merely
because the original manifestation has ended.
- Downstream Boundary Inflation
Boundary Inflation occurs where increasingly remote consequences are
incorporated without sufficient continuity.
Examples:
temporal proximity alone
shared subject alone
shared organization alone
economic association alone
correlation alone
general dependency alone
remote possibility
Canonical principle:
Association Alone ≠ Downstream Inclusion
- Downstream Boundary Suppression
Boundary Suppression occurs where materially continuous consequences are
excluded because they occur:
later
elsewhere
in another system
in another organization
to another subject
in another domain
or:
after the mechanism stopped
HDBM must prevent such artificial truncation.
- Administrative Closure Bias
An incident or case may close before downstream consequences become known.
Therefore:
Case Closure ≠ Harm Boundary Closure
- Claim Boundary Bias
A claim may cover only some downstream consequences.
Therefore:
Claim Boundary ≠ Downstream Harm Boundary
- Liability Boundary Bias
Legal liability may stop at a different point than Harm continuity.
Therefore:
Liability Boundary ≠ Harm Downstream Boundary
HDBM must not expand or suppress Harm to produce a preferred legal
outcome.
- Value Boundary Bias
Downstream Harm may produce Value consequences.
VFM® governs Value lifecycle.
Therefore:
Value Consequence ≠ Downstream Harm Inclusion by Default
and:
Absence of Measurable Value Loss ≠ Absence of Downstream Harm
- Evidence Availability
Evidence may become weaker as the downstream chain extends.
HDBM must distinguish:
weaker support
from:
established boundary break
Therefore:
Insufficient Evidence for Inclusion ≠ Proven Boundary Break
The appropriate state may remain:
Uncertain
or:Pending
- Downstream Confidence
Confidence may be represented for each downstream relationship.
Possible states:
High
Moderate
Low
Disputed
Unknown
Confidence concerns boundary support.It does not represent Harm severity.
Therefore:
Downstream Boundary Confidence ≠ Harm Severity
- Boundary Break Confidence
A Boundary Break itself may have uncertainty.
Possible states include:
Potential Boundary Break
Probable Boundary Break
Established Boundary Break
Disputed Boundary Break
This prevents false certainty where Harm continuity is complex.- Downstream Boundary Expansion
The Harm Boundary may expand where new information establishes additional
materially continuous consequences.
Conceptually:
Boundary₁ → New Downstream Information → Expanded Boundary₂
Expansion must preserve previous boundary history.
- Downstream Boundary Contraction
The boundary may contract where a consequence previously treated as part
of the Harm is later shown to be materially independent.
Contraction must preserve:
previous inclusion
new determination
basis
effective change
- Downstream Reclassification
A consequence may move between:
Candidate
Included
Propagated
Uncertain
Boundary Break
Separate Harm Candidate
without erasing previous states.- Downstream Boundary Reopening
A previously closed boundary may require reopening where:
delayed consequences emerge
new subjects appear
cross-system relationships become known
historical evidence changes continuity
a previously assumed Boundary Break is disproven
or:
new Harm propagation becomes visible
- Historical Downstream Integrity
HDBM must preserve:
Downstream Boundary State₁ → New Information → Downstream Boundary State₂
including:
consequence
relationship chain
inclusion state
continuity basis
Boundary Break assessment
confidenceuncertainty
change reason
Canonical principle:
Current Downstream Boundary ≠ Complete Downstream Boundary History
- Complete HBS Integration
HDBM completes the HBS module sequence.
HBS now combines:
HBIM — What must be considered?
HSBM — Who or what belongs?
HTBM — What time belongs?
HEBM — Which effects belong?
HDBM — How far downstream does the Harm extend?
Together:
Boundary Identification → Subject Boundary → Temporal Boundary → Effect
Boundary → Downstream Boundary → Governed Harm Boundary
- Handoff to Harm Determination
The complete HBS output is:
Governed Harm Boundary
This defines the Harm object sufficiently for HDS to ask:Can Harm legitimately be formally determined to exist, and what governed
Harm has been established?
Canonical distinction:
Governed Harm Boundary ≠ Formally Determined Harm
HDBM does not perform Harm Determination.
- Cross-Architecture Boundaries
HDBM may depend on adjacent architectures without absorbing their
governance spaces.
ORA™ governs actual operational reality.
AIG® governs AI behavior.
ASGA™ governs autonomous execution.
AGA™ governs accountability.
ADIT® governs evidence.
VALIDOS™ governs validation.
INTEGROS® governs integrity.
OBIDENITY® governs identity and provenance.
VFM® governs Value lifecycle.
HDBM governs only:
how far the recognized Harm itself legitimately extends downstream.
- Minimum Implementation Framework
A minimum HDBM implementation requires eight capabilities.
- Downstream Candidate Identification
Identify downstream effects, subjects, domain transitions, system
consequences, dependencies, and materially related later consequences.
- Continuity Assessment
Evaluate subject, effect, temporal, dependency, domain, system,
operational, propagation, and composite continuity without converting
boundary analysis into general causation.
- Boundary Break Governance
Represent Potential, Probable, Established, Disputed, and Uncertain
Boundary Breaks.
- Separate Harm Identification
Distinguish continued Harm from a materially independent downstream Harm
while preserving relationships between them.
- Composite & Distributed Downstream Governance
Support downstream consequences formed across multiple systems, agents,
organizations, subjects, domains, locations, or time periods.
- Boundary Inflation & Suppression Controls
Prevent automatic inclusion through mere association and automatic
exclusion through technical, organizational, temporal, jurisdictional,
claim, or mechanism boundaries.
- Reassessment & Historical Continuity
Support expansion, contraction, reclassification, reopening, and
correction while preserving previous downstream boundary states.
- Governed Output & HBS Integration
Produce a traceable Governed Harm Downstream Boundary and integrate it
with the Subject, Temporal, and Effect Boundaries into the complete
Governed Harm Boundary.
A system that either stops Harm automatically at the original incident or
allows Harm to expand indefinitely through every remotely associated
consequence does not fully implement HDBM.
- Use Case 1 — Harm Continues Beyond the Original Subject and Event
A physical Harm affects Subject A.
The originating mechanism stops.
The resulting impairment prevents Subject A from performing a critical
dependent function, producing a materially connected effect on Subject B.
HDBM evaluates whether Subject B's consequence remains part of the
original Harm lifecycle or whether a materially independent Harm has
emerged.
It does not assume:
New Subject = New Harm
nor:
Related Consequence = Same Harm
The governing principle is:
Downstream continuity must be established, not presumed.
- Use Case 2 — Distributed AI Harm Crosses Multiple Systems
An AI agent produces an operational instruction.
A second system transforms it.
A third system executes it.
A physical system acts on the result.
The action produces Harm and additional downstream consequences after the
original AI interaction has ended.
HDBM follows the Harm beyond:
model
agent
session
tool
platform
and:
system
boundaries where material continuity remains supportable.
Where a later consequence crosses a genuine Boundary Break, it becomes a
candidate for separate Harm governance.
The governing principle is:
The end of an execution chain is not necessarily the end of the Harm
chain.
- Governance Requirements
HDBM requires that:
- downstream consequences not automatically be included or excluded
- Harm continuity remain materially supportable
- boundary continuity remain distinct from general causation
- chain length, temporal distance, spatial distance, system
transition,
organizational transition, jurisdictional transition, domain transition,
or subject transition not independently determine the boundary; -
dependencies remain pathways rather than automatic inclusion criteria; -
propagated Harm remain distinguishable from propagation governance; -
cascades not create infinitely expanding Harm objects; - related Harms
remain capable of separate identity; - Boundary Break remain
distinguishable from relationship absence; - independent intervening
conditions remain capable of creating separate Harm candidates; - Harm
identity remain coherent through boundary expansion; - composite and
distributed downstream consequences remain governable; - AI, agent,
session, tool, and system boundaries not automatically terminate Harm; -
non-linguistic perception-to-action chains remain governable; - mechanism
termination not terminate Harm automatically; - Mitigation and Recovery
not reset the boundary; - downstream inflation and suppression remain
controlled; - case, claim, liability, Value, and evidence boundaries not
define Harm continuity by default; - uncertainty and confidence remain
explicit; - expansion, contraction, reclassification, reopening, and
correction preserve historical integrity; - the complete HBS output remain
suitable for HDS.
- Governance Logic
HDBM applies the following logic:
Has HEBM established the Harm Effect Boundary?
If no:
→ do not finalize the Downstream Boundary.
If yes:
→ identify downstream consequence candidates.
Is the consequence materially continuous with the governed Harm?
If strongly supported:
→ include it within the Downstream Boundary.
If plausible but unresolved:
→ maintain Provisional or Uncertain state.
If continuity is insufficient:
→ exclude it from this Harm Boundary.
Has an independent intervening condition appeared?
→ assess potential Boundary Break.
Has a materially independent Harm emerged?
→ establish Separate Harm Candidate while preserving the relationship to
the original Harm.
Does the consequence occur later, elsewhere, in another domain, system,
organization, jurisdiction, or subject?
→ do not treat that transition as a Boundary Break by itself.
Does the consequence arise from several upstream effects collectively?
→ assess Composite Downstream Continuity.
Has the originating mechanism stopped?
→ do not terminate Harm automatically.
Is inclusion based only on correlation or remote association?
→ prevent Boundary Inflation.
Is exclusion based only on administrative, technical, organizational,
temporal, or claim boundaries?
→ prevent Boundary Suppression.
Has new information changed the downstream structure?
→ expand, contract, reclassify, reopen, or correct while preserving
history.
At every stage:
Downstream ≠ Same Harm by Default
Downstream ≠ Separate Harm by Default
Relationship ≠ Inclusion
Boundary Continuity ≠ General Causation
Boundary Break ≠ Relationship Absence
System Boundary ≠ Harm Boundary
Mechanism End ≠ Harm End
- Governance Outputs
HDBM may produce:
- Governed Harm Downstream Boundary
- Downstream Consequence Set
- Included Downstream Consequence
- Provisionally Included Downstream Consequence
- Excluded Downstream Consequence
- Uncertain Downstream Consequence
- Downstream Continuity State
- Downstream Relationship Chain
- Dependency-Mediated Consequence
- Propagated Harm Boundary State
- Composite Downstream Structure
- Distributed Downstream Structure
- Potential Boundary Break
- Probable Boundary Break
- Established Boundary Break
- Disputed Boundary Break
- Separate Harm Candidate
- Harm Chain
- Downstream Boundary Confidence
- Downstream Boundary Expansion Record
- Downstream Boundary Contraction Record
- Downstream Reclassification Record
- Downstream Boundary Reopening State
- Historical Downstream Boundary Record
The principal module output is:
Governed Harm Downstream Boundary
The integrated HBS output is:Governed Harm Boundary
- Critical Distinctions
Downstream Consequence ≠ Same Harm by Default
Downstream Consequence ≠ Separate Harm by Default
Downstream Boundary Continuity ≠ Final Causal Attribution
Chain Length ≠ Harm Continuity
Temporal Distance ≠ Boundary Break
Geographic Distance ≠ Boundary Break
System Transition ≠ Boundary Break
Organizational Transition ≠ Boundary Break
Jurisdictional Boundary ≠ Harm Boundary
Domain Transition ≠ Boundary Break
Dependency ≠ Harm Continuity
Downstream Boundary ≠ Harm Propagation Governance
Related Harms ≠ One Harm
Boundary Break ≠ Relationship Absence
Individual Upstream Insufficiency ≠ Composite Downstream Insufficiency
AI System Boundary ≠ Harm Downstream Boundary
Mechanism Termination ≠ Harm Termination
Mitigation ≠ Boundary Reset
Upstream Recovery ≠ Downstream Harm Elimination
Association Alone ≠ Downstream Inclusion
Case Closure ≠ Harm Boundary Closure
Claim Boundary ≠ Downstream Harm Boundary
Liability Boundary ≠ Harm Downstream Boundary
Value Consequence ≠ Downstream Harm Inclusion
Insufficient Evidence for Inclusion ≠ Proven Boundary Break
Downstream Boundary Confidence ≠ Harm Severity
Governed Harm Boundary ≠ Formally Determined Harm
- Canonical Boundary
The HDBM — Harm Downstream Boundary Module governs how far a recognized
Harm legitimately extends through downstream effects, subjects, domains,
systems, dependencies, locations, temporal stages, propagation
relationships, composite structures, and distributed consequences. It
governs downstream continuity, inclusion, exclusion, Boundary Breaks,
intervening conditions, separate Harm candidacy, Harm chains, composite
and distributed downstream structures, uncertainty, dispute, expansion,
contraction, reclassification, reopening, and historical Downstream
Boundary continuity. It does not govern Harm propagation itself, formally
determine Harm, establish general causation, assign accountability or
responsibility, determine liability, govern claims or compensation, or
replace operational reality, evidence, validation, integrity, identity, AI
behavior, autonomous execution, simulation, Value, or tax-event
governance.
- Canonical Closing Statement
Harm must not stop merely because an incident, system, organization,
session, jurisdiction, or producing mechanism has ended. But neither may
Harm expand indefinitely through every consequence that can somehow be
connected to it.
HDBM governs the line between those two failures.
It preserves Harm where material continuity remains and establishes a
Boundary Break where a genuinely separate Harm lifecycle begins.
The downstream boundary of Harm ends where the Harm itself ends — not
where the systems surrounding it find it convenient to stop following the
consequences.