Potential Errors

Coverage: 100.0% (8 of 8 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:

• UseCases.Render_All_TRLC_Records

---

Derived from:

• UseCases.Build_Traceable_Documentation

---

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:

• UseCases.Resolve_Derived_From_References

---

Derived from:

• UseCases.Validate_Requirement_Chains

• UseCases.Build_Traceable_Documentation

---

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:

• UseCases.Validate_Traceability_Completeness

• UseCases.Extract_Lobster_From_Requirements

---

Derived from:

• UseCases.Validate_Requirement_Chains

---

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:

• UseCases.Emit_Correct_Provider_Info

• UseCases.Emit_Sphinx_Sources

---

Derived from:

• UseCases.Assemble_Dependable_Element

• UseCases.Validate_Requirement_Chains

---

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:

• UseCases.Render_All_Failure_Modes

---

Derived from:

• UseCases.Assemble_Dependable_Element

• UseCases.Render_Safety_Analyses

---

Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:72: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:

• UseCases.Reject_Invalid_PlantUML

---

Derived from:

• UseCases.Assemble_Dependable_Element

• UseCases.Parse_Architectural_Diagrams

---

Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:87: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:

• UseCases.Forward_Own_AoUs_To_Dependees

• UseCases.Chain_Forward_Received_AoUs

• UseCases.Include_Forwarded_AoUs_In_Traceability

---

Derived from:

• UseCases.Gate_Traceability_At_Test_Time

• UseCases.Forward_AoU_To_Dependees

---

Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:102: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:

• UseCases.Reject_Unknown_AoU_In_Forwarding_YAML

---

Derived from:

• UseCases.Forward_AoU_To_Dependees

---

Source: bazel/rules/rules_score/docs/requirements/potential_errors.trlc:113:42