Latent Condition Rounds¶
Monitoring routine — instantiates Layered Defense Gap Decorrelation
Recurring scheduled rounds that watch defensive holes drift — widening, moving, or synchronizing — and trip a stop threshold before the drift lines them up into a path.
Holes are not static. Alerts get overridden a little more each month, maintenance backlogs grow, staffing thins on night shift, a workaround becomes the norm — and a barrier that was healthy a year ago is quietly porous now. Latent Condition Rounds is the recurring surveillance mechanism that exists to catch that drift: on a fixed cadence, a team sweeps the defensive layers looking not for a fresh census of holes but for evidence that known holes are widening, moving, or beginning to synchronize across layers. Its defining trait is that it monitors a trend, not a snapshot — the same barriers, sampled again and again over time, so the signal is the change. It maintains a running health score per layer and carries a standing rule: when the aggregate condition drifts past a set tolerance, it trips a stop. Where a walkthrough asks "what holes are here today?", the rounds ask "which way are the holes moving, and are they starting to line up?"
Example¶
A hospital runs weekly patient-safety leadership rounds focused on its medication-error barriers, tracking the same indicators each week rather than re-auditing from scratch. The barriers were mapped and catalogued earlier; the rounds now watch their condition trend. Over eight weeks the data drifts: barcode-scanning compliance on one ward slides from 96% to 88% as a scanner battery problem goes unfixed; pharmacy verification turnaround creeps up as a vacancy stays open; override rates on the smart-pump drug library climb during a busy stretch. No single reading is alarming, but the rounds are watching the slopes — and three barriers are degrading at once on the same ward, under the same staffing pressure.
The rounds' running health score for that ward crosses the pre-agreed tolerance in week eight. That trips the standing rule: high-alert infusions on the ward revert to a mandatory independent double-check until scanning and pump-library health recover. The rounds did not discover new holes or re-catalog the barriers — they caught known holes drifting into alignment and halted before the path completed. The widening scanner gap is handed back for a fresh census; the rounds' job was the trend and the stop.
How it works¶
The rounds' leverage is repetition and trend-reading, not fresh discovery:
- Sample the same barriers on a cadence. Revisit the identical set of layers at fixed intervals so the comparison is over time, not over place.
- Track the slope, not the level. Watch whether each barrier's condition is degrading, and how fast; a slowly widening hole is the signal, even while still "in tolerance."
- Score the stack's aggregate health. Roll the per-layer readings into a running health score that reflects simultaneous degradation, since holes drifting together is the danger.
- Trip the stop on threshold breach. When aggregate drift crosses the agreed tolerance, invoke the standing stop rule rather than waiting for confirmation of a complete path.
Tuning parameters¶
- Round cadence — daily, weekly, monthly. Frequent rounds catch fast drift but consume time and habituate observers to the routine.
- Indicator set — which leading signals per barrier are tracked. Well-chosen leading indicators warn early; lagging ones only confirm decline.
- Trend sensitivity — how small a slope counts as drift worth flagging. Sensitive settings warn sooner and raise more false alarms.
- Aggregation weighting — how simultaneous degradation across layers inflates the health score. Heavier weighting on co-drift fires the stop earlier on alignment specifically.
- Stop-threshold tightness — how far the score may drift before the stop trips. Tighter is safer and halts operations more often.
When it helps, and when it misleads¶
Its strength is early warning: it catches the slow version of the archetype's failure — latent gap drift — while there is still time to act, and it converts vague unease about "things slipping" into a tracked slope with a hard stop attached. Watching for the accumulating latent conditions that lie dormant in a system until they combine is exactly the resident-pathogen view of organizational accidents.[n1] Its failure mode is measuring the wrong thing steadily: rounds can track convenient indicators that trend nicely while the real hole widens off-instrument, and a routine that never trips its stop becomes a comfortable ritual that manufactures false assurance. The classic misuse is metric fixation — the numbers look monitored, so the barriers are assumed healthy, while the important drift hides where no indicator points. The guarding discipline is to choose leading indicators tied to actual failure modes, refresh them as the system changes, and honor the stop when it trips rather than explaining the breach away.
How it implements the components¶
Latent Condition Rounds fills the drift-and-trigger components:
latent_condition_monitor— its core function: recurring sampling of the same barriers to detect holes widening, moving, or synchronizing over time.defensive_layer_health_score— it maintains a running, trend-aware health score per layer and for the stack, weighted so simultaneous degradation stands out.stop_operation_alignment_threshold— it carries a standing rule that trips a stop when aggregate drift crosses the agreed tolerance, ahead of a completed path.
It does NOT produce the point-in-time census of holes and owners (layer_gap_catalog, barrier_ownership_register) — that snapshot is the Barrier Gap Walkthrough. The walkthrough establishes what the holes are and who owns them; these rounds watch those known holes drift and hand a widening one back for a fresh census.
Related¶
- Instantiates: Layered Defense Gap Decorrelation — supplies the ongoing drift watch and stop trigger that keep the model from going stale.
- Consumes: Barrier Gap Walkthrough for the baseline hole census whose drift the rounds track.
- Sibling mechanisms: Swiss-Cheese Barrier Review · Barrier Gap Walkthrough · Aligned Gap Heatmap · Bowtie Analysis with Layer Gaps · Common-Cause Layer Audit · Independent Barrier Test Drill · Near-Miss Trajectory Review
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Latent Condition Rounds operates as an ongoing sensing arrangement that repeatedly observes actual state and surfaces changes or alerts because it recurring scheduled rounds that watch defensive holes drift — widening, moving, or synchronizing — and trip a stop threshold before the drift lines them up into a path
Independent corroboration: The frozen evidence defines Latent Condition Rounds as 'Recurring scheduled rounds that watch defensive holes drift — widening, moving, or synchronizing — and trip a stop threshold before the drift lines them up into a path', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Aviation safety and Reason's latent-condition model supplied recurring surveillance of drifting defensive holes.
Related originating lineages:
- Engineering & Design — Reliability and barrier-management practice shaped layer checks and stop thresholds.
- Medicine & Healthcare — Patient-safety rounds materially shaped recurring frontline inspection of latent hazards.
Review resolution: Both independent reviews place the primary lineage in aviation_aeronautics. The queued differences (reported_ambiguity) concern secondary metadata rather than primary provenance. The final retains engineering_design, medicine_healthcare only where a reviewer supplied a formative-lineage rationale; downstream application by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis records the relationship among origin traditions, while domain_reach=multi_domain records application breadth separately. encyclopedia_synthesis=true reflects whether either reviewer identified a corpus-specific synthesis, and confidence=medium preserves the more cautious evidence assessment.
Attribution caveat: The rounds format is a synthesis applied to an established systems-safety concept.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Latent conditions (James Reason) are dormant weaknesses built into a system — deferred maintenance, tolerated overrides, understaffing — that lie inactive until combined with local triggers to open a path through the defenses. Reason likened them to resident pathogens in the body; these rounds are the routine that watches those conditions accumulate and move toward alignment. ↩