PRR Case Study | Same Mechanism, Opposite Metabolism
Infrastructure failure / chokepoint & grid disruption

OSI Systems (OSIS) vs Iris Energy (IREN)

Two firms on one mechanism: infrastructure failure. One has historically behaved like a beneficiary. One has historically behaved like a stressed firm.

What is PRR? PRR (Political Risk Resilience) is an evidence system for how individual public companies have historically transmitted political and geopolitical events. It estimates the firm value response firm by firm, mechanism by mechanism, then puts each signal through robustness benchmarks. PRR identifies observed beneficiary and stressed profiles on the same event class. Business-model explanations below are plausible interpretations, not causal proof.

The Old View

Infrastructure failure -- a power grid collapse, a port closure, a pipeline rupture, a critical chokepoint attack -- is treated as uniformly bad. Risk dashboards bucket it under "operational risk" or "physical risk" and apply a directional haircut:

"Infrastructure failure risk is elevated. Reduce exposure to operationally sensitive names."

This collapses two very different observed firm value responses into one. Some firms have historically behaved like beneficiaries around infrastructure-failure events -- with business positioning that suggests channels like screening, security, detection, hardening, or industrial substitution. Others have historically behaved like stressed firms -- with positioning suggesting channels like energy disruption, throughput loss, or capex strain. Same event class, opposite observed metabolism.

The PRR Question

If a major infrastructure event hits tomorrow -- a chokepoint attack, a grid failure, a port shutdown -- do OSIS (OSI Systems -- security screening and inspection) and IREN (Iris Energy -- energy-intensive data center / mining operator) transmit the risk the same way?

Both are mid-cap U.S.-listed. Both show up on operational-risk screens. A naive cross-section would treat them as similarly exposed to "infrastructure disruption." PRR disagrees.

The Contrast

OSIS (OSI Systems)IREN (Iris Energy)
SectorSecurity screening / inspection systemsEnergy-intensive data center / mining
Mechanisminfrastructure_failureinfrastructure_failure
Spearman rho+0.428-0.813
p-value0.01450.000731
Evidence gradeA_global_robustA_cell_robust_holdout_pass
Directionbeneficiarystressed
Sample (n)32 infrastructure-failure events13 infrastructure-failure events (holdout-pass cell)

Same mechanism. Opposite firm value responses. Both signals robustness-survived against their respective event samples.

Why

OSIS -- observed beneficiary on infrastructure-failure events

OSI Systems builds security inspection and screening hardware: cargo X-ray, baggage and people screening, threat detection.

Observed pattern. OSIS has historically shown a positive market-implied firm value response around infrastructure-failure events (rho = +0.428, A_global_robust).

Plausible interpretation. A firm positioned near security/inspection and government-procurement demand may benefit when hardening, screening, and compliance budgets become more salient after infrastructure disruption. This is consistent with the observed pattern -- not a proven causal chain.

Evidence claim. PRR does not prove that infrastructure failures cause OSIS to rise because of screening demand. It shows that OSIS has historically behaved like a beneficiary in this event class, with the cell surviving primary, alt-market, sector, and FX-residual benchmarks.

IREN -- observed stressed on infrastructure-failure events

Iris Energy operates energy-intensive data centers tied to power infrastructure and grid availability.

Observed pattern. IREN has historically shown a strongly negative market-implied firm value response around infrastructure-failure events on the holdout-pass cell (rho = -0.813, A_cell_robust_holdout_pass).

Plausible interpretation. A heavily energy-intensive operator with high utilization is positioned in ways where power availability, energy-price spikes, and uptime constraints would plausibly compress economics. Consistent with the observed pattern -- not a proven causal chain.

Evidence claim. PRR does not prove that infrastructure failures cause IREN to fall because of power costs or uptime risk. It shows that IREN has historically behaved like a stressed firm in this event class, with the cell surviving the robustness benchmarks and the holdout-validation gate.

Decision Implications

DomainOSISIREN
PortfolioCandidate beneficiary screen on infrastructure-failure events; government-spend exposure to monitorCandidate stress screen on infrastructure-failure events; energy-dependence exposure to monitor
Insurance / PRILower trigger relevance -- the event has historically been a demand catalystReview business-interruption and energy-supply cover; stress-test trigger design
CreditMonitor backlog and government-revenue stability under stressWatch energy-cost passthrough and uptime risk; stress-test covenant headroom
Corporate strategyConsider reviewing capacity in screening / detection product linesConsider site diversification, power-supply hedging, redundancy capex

Who This Matters For

Persona / IndustryWhy this contrast matters
Portfolio managers & relative-value desksA candidate hedge or relative-value screen for further diligence: security/screening exposure vs energy-dependent operations on infrastructure-failure events. Opposite-sign signals on the same mechanism.
Political risk insurers (PRI / DFC / MIGA)Trigger design raises different underwriting questions by firm type even when the underlying event is the same. IREN-type exposures may warrant review of business-interruption and energy-supply riders. OSIS-type exposures may not warrant PRI at all -- the event has historically been a demand catalyst.
Credit & project finance lendersLoans against government-procurement backlogs behave differently from loans against energy-intensive operating assets under the same infrastructure event. Covenant structures and DSCR assumptions should differ.
Corporate strategy & CFOsScenario planning around infrastructure failure cannot use a single "operational risk" line. Screening / detection businesses should be planning capacity expansion; energy-intensive operations should be running uptime and power-cost stress tests.
Reinsurance & business-interruption underwritersInfrastructure-failure events activate opposite demand and cost dynamics across the same panel. Cross-class pricing should reflect both the demand pull (security spend) and the cost push (energy and throughput).
Operators of critical infrastructureA firm's posture toward infrastructure failure should reflect which side of the mechanism it sits on -- supplier of resilience or consumer of it. The two require opposite capex postures.

The Punchline

PRR is not predicting whether infrastructure fails -- and it is not claiming causality on how either firm responds. It identifies which firms have historically transmitted the same event class in opposite directions, with separate robustness-survived evidence.

A single-direction "infrastructure risk" score sees both OSIS and IREN as exposed. PRR sees one firm with an observed beneficiary profile and another with an observed stressed profile on the same mechanism. Security/inspection demand and energy/uptime constraints are plausible interpretations; the evidence claim is the observed difference in risk metabolism.

Same mechanism. Different observed risk metabolism. PRR does not claim causality; it identifies which firms have historically transmitted the same political-risk event class in opposite directions.

PRR evidence is observational. It identifies repeatable firm-level value transmission patterns around audited political-risk event classes. Business-model explanations are plausible interpretations, not causal proof. PRR starts with market-implied firm value because it is observable and comparable, but the framework is not limited to public equity data. It can test any firm-level outcome that can be measured consistently around political-risk events.
← Back to Explorer