Requirements
============
Potential Errors
----------------
Documentation Build
^^^^^^^^^^^^^^^^^^^
.. requirement:definition:: UseCases.Missing_Requirement_In_Output

:Description: 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.

.. requirement:definition:: UseCases.Broken_Cross_Reference

:Description: A cross-reference between requirements (e.g. derived_from) is
not resolved correctly in the rendered documentation, showing
a broken link or missing reference.

Requirement Traceability
^^^^^^^^^^^^^^^^^^^^^^^^
.. requirement:definition:: UseCases.Undetected_Missing_Traceability

:Description: 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.

.. requirement:definition:: UseCases.Incorrect_Provider_Chain

:Description: The Bazel provider chain (TrlcProviderInfo, SphinxSourcesInfo)
is assembled incorrectly so that downstream rules receive stale
or incomplete requirement data.

Safety Analysis
^^^^^^^^^^^^^^^
.. requirement:definition:: UseCases.Missing_Failure_Mode_In_Render

:Description: A failure mode defined in TRLC is not rendered in the FMEA
documentation output, causing an incomplete safety analysis
artefact.

Architecture
^^^^^^^^^^^^
.. requirement:definition:: UseCases.Silent_Diagram_Parse_Failure

:Description: 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.

AoU Forwarding
^^^^^^^^^^^^^^
.. requirement:definition:: UseCases.AoU_Silently_Dropped

:Description: 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.

.. requirement:definition:: UseCases.Invalid_Forwarding_YAML_Accepted

:Description: 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.