Consequences
Describe what a signal may affect, and why.
Consequences relate a signal to the nodes and dependencies an organisation has modelled, producing a specific list of what may be affected together with the reasoning behind it.
What this helps you do
A consequence is a stated possibility with its supporting evidence attached, not a conclusion. Because dependencies are explicit and directional, second-order exposure is inspectable step by step rather than presented as a finished answer.
A dependency does not prove impact. Possible exposure and confirmed impact remain distinct states until evidence or verification moves one to the other.
What you can do after sign-in
- See which nodes a signal may expose, and through which dependency
- Open the evidence behind any stated consequence
- Raise a verification task where the evidence is insufficient
- Record confirmed impact separately from possible exposure
- Review the consequence history of a closed record