Help & Methodology
A straightforward guide to interpreting this demonstration.
From dependency to decision
Discover Dependencies → Identify Exposure → Simulate Disruption → Explore Structural Improvements → Report and Validate
Shared Dependency
A resource supporting more than one critical activity. A disruption may affect multiple workflows.
Hidden Dependency
An indirect or insufficiently documented relationship that needs human verification.
Operational Exposure
Vulnerability created by dependency concentration, constrained recovery or limited usable alternatives.
Available Alternative
A replacement option whose capacity, activation time and practical readiness must be assessed, not just its existence.
Evidence status
Confirmed means confirmed within the fictional demonstration records. Needs review means a potential relationship still requires verification.
Methodology terms
Operational Dependency State Graph
The connected model of activities, resources and their supporting relationships.
Latent Dependency Inference
The proposed method for identifying possible relationships not explicitly documented.
Dependency Convergence
Where several important activities rely on the same resource.
Substitutability Intelligence
Assessing whether another resource can realistically take over.
Dependency Drift
How operational relationships change over time.
Exposure Reduction Optimisation
The proposed method for comparing structural changes intended to reduce exposure.
Prototype limitations
Opslucent is at the UI prototype and pre-MVP stage. Analytical engines, inference methods and optimisation have not been technically validated. All records and outputs in this workspace are simulated.
Return to Overview