Viewingcoffee-machineversion main
·commit 1ec97db8New versionCompare STPA completeness
branch main · commit 1ec97db8
The analysis is AUTHORED; the check is COMPUTED. Modelwrite does not perform STPA, does not infer hazards from a design, and will never claim to. It holds your control structure and analysis as a versioned model, checks completeness and internal consistency, names everything missing, and reports each finding's basis.
The control structure
0 controllers · 0 controlled processes · 0 control actions · 0 feedback signals · 0 hazards · 0 constraints · 0 UCAs · 0 loss scenarios
computed over 99 graph nodes and 165 graph edges; the platform holds the authored analysis and checks its completeness - it does not perform STPA
This model declares no STPA vocabulary, so there is nothing to check. See the domain pack at sample/stpa/stpa-vocabulary.json for the convention.
Unanalysed control actions (0)
Every ControlAction must carry an UnsafeControlAction for each of the four types: not-provided, provided, wrong-timing-or-order, stopped-too-soon-or-applied-too-long.
None — every control action is analysed across the four types.
Control loops with no feedback (0)
A Controller with a ControlAction and no Feedback path is the classic STPA defect - structurally the same shape as the orphan/isolation the health view reports.
None — every controller with a control action has a feedback path.
Hazards with no constraint (0) · constraints reaching no element (0)
Every hazard the analysis names must be mitigated by a constraint; every constraint must reach the design - otherwise it is an aspiration.
None — every hazard is mitigated by a SystemConstraint.
None — every SystemConstraint reaches the design.
UCAs with no loss scenario (0)
A claim that a UCA could happen, without a causal scenario, is an assertion — a UCA must be explained by a LossScenario.
None — every UCA is explained by a loss scenario.
Trend across baselines (1)
The same counts across the commits of the branch, oldest first. Computed directly over each commit's model - there is no cached trend path to reuse.
| commit | unanalysed | no feedback | hazards | constraints | UCAs | total |
|---|
1ec97db8 seed platform scenario | 0 | 0 | 0 | 0 | 0 | 0 |
See the control-structure view · See model health