Potential Errors
Coverage: 100.0% (13 of 13 items OK)
[OK] TRLC Potentialerror UseCases.Missing_Requirement_In_Output
A requirement defined in a TRLC source file is silently omitted from the rendered RST output, causing the documentation to be incomplete without any build error.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:20:42
[OK] TRLC Potentialerror UseCases.Broken_Cross_Reference
A cross-reference between requirements (e.g. derived_from) is not resolved correctly in the rendered documentation, showing a broken link or missing reference.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:31:42
[OK] TRLC Potentialerror UseCases.Undetected_Missing_Traceability
A component requirement that lacks a derived_from reference to a feature requirement is not flagged as an error during the build, allowing gaps in the traceability chain.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:46:42
[OK] TRLC Potentialerror UseCases.Incorrect_Provider_Chain
The Bazel provider chain (TrlcProviderInfo, SphinxSourcesInfo) is assembled incorrectly so that downstream rules receive stale or incomplete requirement data.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:57:42
[OK] TRLC Potentialerror UseCases.Missing_Failure_Mode_In_Render
A failure mode defined in TRLC is not rendered in the FMEA documentation output, causing an incomplete safety analysis artefact.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:72:42
[OK] TRLC Potentialerror UseCases.Unassessed_Root_Cause_Accepted
A fault-tree root cause that no root cause assessment lists, or an own assumption of use that no assessment uses, passes the build, and the documentation shows no gap.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:83:42
[OK] TRLC Potentialerror UseCases.Ambiguous_Root_Cause_Assessment
A root cause is listed by several root cause assessments, or an assessment lists a root cause or measure that does not belong to its safety analysis, so the rendered argument does not match the analysed fault trees and measures.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:94:42
[OK] TRLC Potentialerror UseCases.Stale_Root_Cause_Assessment
A measure changes, but the root cause assessment that relies on its earlier version is not reviewed again.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:106:42
[OK] TRLC Potentialerror UseCases.Underrated_Root_Cause_Assessment
A root cause of a failure mode is assessed with a lower ASIL than the failure mode, or a root cause assessment relies on a measure of a lower ASIL than its own, and the build passes.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:116:42
[OK] TRLC Potentialerror UseCases.Silent_Diagram_Parse_Failure
A syntactically invalid PlantUML diagram is not rejected by the parser, producing an incorrect or empty FlatBuffers output that is consumed silently by downstream rules.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:132:42
[OK] TRLC Potentialerror UseCases.AoU_Silently_Dropped
An assumption of use defined by a dependency is not forwarded to the dependee, causing the integrating project to be unaware of a condition it must satisfy.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:147:42
[OK] TRLC Potentialerror UseCases.Invalid_Forwarding_YAML_Accepted
A chain-forwarding YAML file that references a non-existent AoU identifier is accepted without error, causing the build to succeed while the intended forwarding does not take effect.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:158:42
[OK] TRLC Potentialerror UseCases.Conflicting_AoU_Definitions_Merged
An assumption of use reaches a dependable element along several paths with different content, for example in two versions, and one definition silently replaces the other.
Traces to:
Derived from:
Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:169:42